1 |
Volker Armin Hemmann wrote: |
2 |
> On Tuesday 05 July 2011 15:41:13 Dale wrote: |
3 |
> |
4 |
> update your fucking drivers. |
5 |
> |
6 |
> Seriously, no userspace app does something like this. The driver is broken, |
7 |
> KDE touches the broken part and BOOM. |
8 |
> |
9 |
> Don't blame KDE, blame nvidia. |
10 |
> |
11 |
> And update the driver. |
12 |
> |
13 |
> |
14 |
> |
15 |
|
16 |
I don't think a bad video driver would cause this: |
17 |
|
18 |
*root@fireball / # emerge -av =x11-drivers/nvidia-drivers-270.41.19 |
19 |
|
20 |
These are the packages that would be merged, in order: |
21 |
|
22 |
Calculating dependencies | |
23 |
|
24 |
!!! Invalid or corrupt dependency specification: |
25 |
|
26 |
Invalid atom (????1), token 1 |
27 |
|
28 |
(dev-perl/Net-SSLeay-1.36::unxlngx, installed) |
29 |
|
30 |
Portage is unable to process the dependencies of the 'dev-perl/Net- |
31 |
SSLeay-1.36' package. In order to correct this problem, the package |
32 |
should be uninstalled, reinstalled, or upgraded. As a temporary |
33 |
workaround, the --nodeps option can be used to ignore all dependencies. |
34 |
For reference, the problematic dependencies can be found in the *DEPEND |
35 |
files located in '/var/db/pkg/dev-perl/Net-SSLeay-1.36/'. |
36 |
... done! |
37 |
root@fireball / # |
38 |
|
39 |
Whatever the problems is, things are breaking. I think something in KDE |
40 |
is broke, like corrupt file or some corrupt config somewhere, and it was |
41 |
just the first symptom of the problem. No matter what I try to emerge, |
42 |
I get errors like this. |
43 |
|
44 |
Still think emerging a new video driver is going to help? ;-) |
45 |
|
46 |
Dale |
47 |
|
48 |
:-) :-) |
49 |
* |