* [gentoo-user] Nvidia drivers and KDE problem
@ 2013-05-26 9:12 Dale
2013-05-26 9:41 ` Alan McKinnon
` (3 more replies)
0 siblings, 4 replies; 14+ messages in thread
From: Dale @ 2013-05-26 9:12 UTC (permalink / raw
To: gentoo-user
Howdy,
I been letting portage upgrade nvidia drivers as usual. Thing is, the
last two or three drivers seems to cause a issue. First, versions that
cause the issue:
=x11-drivers/nvidia-drivers-319.12
=x11-drivers/nvidia-drivers-319.17
=x11-drivers/nvidia-drivers-319.23
I'm currently using this one which works fine:
x11-drivers/nvidia-drivers-313.30
This is KDE info:
[IP-] [ ] kde-base/kdelibs-4.10.3-r2
Video card info:
01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT
220] (rev a2) (prog-if 00 [VGA controller])
Subsystem: NVIDIA Corporation Device 069a
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at de000000 (64-bit, prefetchable) [size=32M]
I/O ports at ef00 [size=128]
[virtual] Expansion ROM at d0000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 3
Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Express Endpoint, MSI 00
Capabilities: [b4] Vendor Specific Information: Len=14 <?>
Capabilities: [100] Virtual Channel
Capabilities: [128] Power Budgeting <?>
Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1
Len=024 <?>
Kernel driver in use: nvidia
Kernel modules: nvidia
The problem. After I am logged into KDE for a good while, like several
hours to maybe a day or so, the kicker thingy at the bottom locks up
tight. I can't switch desktops, clock stops working, can't click the K
menu thingy either. Everything in the kicker thingy is dead as a door
nail. I can switch desktops with the keyboard and everything else works
in KDE just fine. I can also switch to a console too. Killing X and
restarting it fixes it, xdm restart in my case. I don't have to reload
drivers or restart the system. I do go back and downgrade the drivers
after testing it.
So, is this a nvidia bug, KDE bug or is it something else? Since it
works when I go back a version of nvidia, it looks like nvidia. Think
is, it only affects KDE and nothing else. Is it possible that my card
is not supposed to use the 319.* series of drivers? The versions that
don't work are all 319.* series.
Thoughts?
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 9:12 [gentoo-user] Nvidia drivers and KDE problem Dale
@ 2013-05-26 9:41 ` Alan McKinnon
2013-05-26 9:51 ` Dale
2013-05-26 11:50 ` [gentoo-user] " Nikos Chantziaras
` (2 subsequent siblings)
3 siblings, 1 reply; 14+ messages in thread
From: Alan McKinnon @ 2013-05-26 9:41 UTC (permalink / raw
To: gentoo-user
On 26/05/2013 11:12, Dale wrote:
> Howdy,
>
> I been letting portage upgrade nvidia drivers as usual. Thing is, the
> last two or three drivers seems to cause a issue. First, versions that
> cause the issue:
>
> =x11-drivers/nvidia-drivers-319.12
> =x11-drivers/nvidia-drivers-319.17
> =x11-drivers/nvidia-drivers-319.23
>
> I'm currently using this one which works fine:
>
> x11-drivers/nvidia-drivers-313.30
>
> This is KDE info:
>
> [IP-] [ ] kde-base/kdelibs-4.10.3-r2
>
> Video card info:
>
> 01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT
> 220] (rev a2) (prog-if 00 [VGA controller])
> Subsystem: NVIDIA Corporation Device 069a
> Flags: bus master, fast devsel, latency 0, IRQ 18
> Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
> Memory at c0000000 (64-bit, prefetchable) [size=256M]
> Memory at de000000 (64-bit, prefetchable) [size=32M]
> I/O ports at ef00 [size=128]
> [virtual] Expansion ROM at d0000000 [disabled] [size=512K]
> Capabilities: [60] Power Management version 3
> Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [78] Express Endpoint, MSI 00
> Capabilities: [b4] Vendor Specific Information: Len=14 <?>
> Capabilities: [100] Virtual Channel
> Capabilities: [128] Power Budgeting <?>
> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1
> Len=024 <?>
> Kernel driver in use: nvidia
> Kernel modules: nvidia
>
>
> The problem. After I am logged into KDE for a good while, like several
> hours to maybe a day or so, the kicker thingy at the bottom locks up
> tight. I can't switch desktops, clock stops working, can't click the K
> menu thingy either. Everything in the kicker thingy is dead as a door
> nail. I can switch desktops with the keyboard and everything else works
> in KDE just fine. I can also switch to a console too. Killing X and
> restarting it fixes it, xdm restart in my case. I don't have to reload
> drivers or restart the system. I do go back and downgrade the drivers
> after testing it.
>
> So, is this a nvidia bug, KDE bug or is it something else? Since it
> works when I go back a version of nvidia, it looks like nvidia. Think
> is, it only affects KDE and nothing else. Is it possible that my card
> is not supposed to use the 319.* series of drivers? The versions that
> don't work are all 319.* series.
I get a similar issue, my video card is an ATI and I use the radeon drivers.
Same symptom as you - plasma stops updating it's widgets like clocks and
stops responding to the mouse. Keyboard works.
In my case, it's usually linked to nfs and smb mounts that went away
(eg, if I forget to umount my NFS media server at home and go to work)
which indicates a blocking issue somehow. I've read many reports on the
internet that krunner is somehow involved, so that might be a good
starting point for investigation. krunner is the thing you get in KDE
when typing Alt-F2
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 9:41 ` Alan McKinnon
@ 2013-05-26 9:51 ` Dale
2013-05-26 10:39 ` Alan McKinnon
0 siblings, 1 reply; 14+ messages in thread
From: Dale @ 2013-05-26 9:51 UTC (permalink / raw
To: gentoo-user
Alan McKinnon wrote:
> I get a similar issue, my video card is an ATI and I use the radeon
> drivers. Same symptom as you - plasma stops updating it's widgets like
> clocks and stops responding to the mouse. Keyboard works. In my case,
> it's usually linked to nfs and smb mounts that went away (eg, if I
> forget to umount my NFS media server at home and go to work) which
> indicates a blocking issue somehow. I've read many reports on the
> internet that krunner is somehow involved, so that might be a good
> starting point for investigation. krunner is the thing you get in KDE
> when typing Alt-F2
So this may not be a nvidia issue at all since you get the same with a
ATI card. Right?
What package provides the kicker thingy? I think in KDE3 it was called
kicker but it appears to have changed to something else. Is that
krunner that has it now?
Thanks.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 9:51 ` Dale
@ 2013-05-26 10:39 ` Alan McKinnon
2013-05-26 11:03 ` Dale
0 siblings, 1 reply; 14+ messages in thread
From: Alan McKinnon @ 2013-05-26 10:39 UTC (permalink / raw
To: gentoo-user
On 26/05/2013 11:51, Dale wrote:
> Alan McKinnon wrote:
>> I get a similar issue, my video card is an ATI and I use the radeon
>> drivers. Same symptom as you - plasma stops updating it's widgets like
>> clocks and stops responding to the mouse. Keyboard works. In my case,
>> it's usually linked to nfs and smb mounts that went away (eg, if I
>> forget to umount my NFS media server at home and go to work) which
>> indicates a blocking issue somehow. I've read many reports on the
>> internet that krunner is somehow involved, so that might be a good
>> starting point for investigation. krunner is the thing you get in KDE
>> when typing Alt-F2
>
> So this may not be a nvidia issue at all since you get the same with a
> ATI card. Right?
yes
>
> What package provides the kicker thingy? I think in KDE3 it was called
> kicker but it appears to have changed to something else. Is that
> krunner that has it now?
Maybe it's time you used the "thingy" suffix a little less and the real
names of things a little more :-)
What thing are you asking about? The panel that is usually at the bottom
and holds the plasma widgets? Or the thin popup you get with Alt-F2?
The panel is called plasma-desktop and comes from kde-base/plasma-workspace
The popup is krunner and comes from kde-base/krunner
I doubt very much it's a real bug as such in either KDE app (although
the fix might go in there). It looks much more to me like a side-effect
of IO blocking - two or more apps are trying to get something done and
unexpectedly are not getting answers, so they hang around waiting in the
doorway and get get in the way of everything else. And just for fun,
video drivers are also trying to get in on the act as they have to deal
with mouse pointer repaints...
Debugging this one is going to be fun (for peculiar definitions of fun)
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 10:39 ` Alan McKinnon
@ 2013-05-26 11:03 ` Dale
2013-05-26 11:31 ` Alan McKinnon
0 siblings, 1 reply; 14+ messages in thread
From: Dale @ 2013-05-26 11:03 UTC (permalink / raw
To: gentoo-user
Alan McKinnon wrote:
> On 26/05/2013 11:51, Dale wrote:
>
>> What package provides the kicker thingy? I think in KDE3 it was called
>> kicker but it appears to have changed to something else. Is that
>> krunner that has it now?
> Maybe it's time you used the "thingy" suffix a little less and the real
> names of things a little more :-)
>
> What thing are you asking about? The panel that is usually at the bottom
> and holds the plasma widgets? Or the thin popup you get with Alt-F2?
>
> The panel is called plasma-desktop and comes from kde-base/plasma-workspace
> The popup is krunner and comes from kde-base/krunner
>
> I doubt very much it's a real bug as such in either KDE app (although
> the fix might go in there). It looks much more to me like a side-effect
> of IO blocking - two or more apps are trying to get something done and
> unexpectedly are not getting answers, so they hang around waiting in the
> doorway and get get in the way of everything else. And just for fun,
> video drivers are also trying to get in on the act as they have to deal
> with mouse pointer repaints...
>
> Debugging this one is going to be fun (for peculiar definitions of fun)
>
>
The thingy is the thing at the bottom where I can switch desktops, click
the K menu and where my clock is. I think it was called Kicker in
KDE3. KDE4 seems to have changed it but not sure what the new name is.
I hope they fix this thing soon. If they remove the driver from the
tree, I'm in a bit of a pickle.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 11:03 ` Dale
@ 2013-05-26 11:31 ` Alan McKinnon
2013-05-26 12:10 ` Dale
0 siblings, 1 reply; 14+ messages in thread
From: Alan McKinnon @ 2013-05-26 11:31 UTC (permalink / raw
To: gentoo-user
On 26/05/2013 13:03, Dale wrote:
> Alan McKinnon wrote:
>> On 26/05/2013 11:51, Dale wrote:
>>
>>> What package provides the kicker thingy? I think in KDE3 it was called
>>> kicker but it appears to have changed to something else. Is that
>>> krunner that has it now?
>> Maybe it's time you used the "thingy" suffix a little less and the real
>> names of things a little more :-)
>>
>> What thing are you asking about? The panel that is usually at the bottom
>> and holds the plasma widgets? Or the thin popup you get with Alt-F2?
>>
>> The panel is called plasma-desktop and comes from kde-base/plasma-workspace
>> The popup is krunner and comes from kde-base/krunner
>>
>> I doubt very much it's a real bug as such in either KDE app (although
>> the fix might go in there). It looks much more to me like a side-effect
>> of IO blocking - two or more apps are trying to get something done and
>> unexpectedly are not getting answers, so they hang around waiting in the
>> doorway and get get in the way of everything else. And just for fun,
>> video drivers are also trying to get in on the act as they have to deal
>> with mouse pointer repaints...
>>
>> Debugging this one is going to be fun (for peculiar definitions of fun)
>>
>>
>
> The thingy is the thing at the bottom where I can switch desktops, click
> the K menu and where my clock is. I think it was called Kicker in
> KDE3. KDE4 seems to have changed it but not sure what the new name is.
It's a plasma widget called a panel, the only useful thing it does is to
be a container for other widgets that do useful stuff.
The panel is started by plasma-desktop as one of the standard widgets it
manages. The idea is to give you stuff on the screen that looks more or
less like a familiar desktop. Plasma can do other things and give you
completely different layouts; like for instance not giving you a panel
at all. This would be useful on a phone with small screen
The whole thing is heavily event based and has to react to a bucket load
of system events being generated such as what the mouse is doing.
There's a fantastic number of ways this could go wrong, some might be
plasma's fault, some might be faults that happen to plasma
>
> I hope they fix this thing soon. If they remove the driver from the
> tree, I'm in a bit of a pickle.
No, you won't be. You have the ebuild right now, copy it to your overlay
and "remove" becomes something that will not happen
--
Alan McKinnon
alan.mckinnon@gmail.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [gentoo-user] Re: Nvidia drivers and KDE problem
2013-05-26 9:12 [gentoo-user] Nvidia drivers and KDE problem Dale
2013-05-26 9:41 ` Alan McKinnon
@ 2013-05-26 11:50 ` Nikos Chantziaras
2013-05-26 12:14 ` Dale
2013-05-26 21:17 ` [gentoo-user] " Volker Armin Hemmann
2013-05-29 22:28 ` Paul Hartman
3 siblings, 1 reply; 14+ messages in thread
From: Nikos Chantziaras @ 2013-05-26 11:50 UTC (permalink / raw
To: gentoo-user
On 26/05/13 12:12, Dale wrote:
>[...]
> The problem. After I am logged into KDE for a good while, like several
> hours to maybe a day or so, the kicker thingy at the bottom locks up
> tight. I can't switch desktops, clock stops working, can't click the K
> menu thingy either. Everything in the kicker thingy is dead as a door
> nail. I can switch desktops with the keyboard and everything else works
> in KDE just fine. I can also switch to a console too. Killing X and
> restarting it fixes it, xdm restart in my case. I don't have to reload
> drivers or restart the system.
Hmm, something similar happens here sometimes. But not as severe. It
usually happens when I close many windows rapidly in succession, but
it's not permanent. The panel becomes responsive again after 10 seconds
or so. I'm also on latest nvidia-drivers, but it was happening with
older versions too. I happened very rarely though, so it didn't bother
me enough to go investigating.
Here's something to try out: when it happens, hit the shortcut on your
keyboard that temporarily suspends desktop effects. I don't remember
what the default shortcut for it is, as I've changed it, but it's shown
and configured in the "General" tab of "Desktop Effects" in System
Settings. See if hitting the shortcut twice to disable and then
re-enable desktop effects fixes it.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 11:31 ` Alan McKinnon
@ 2013-05-26 12:10 ` Dale
2013-05-27 15:43 ` Fast Turtle
0 siblings, 1 reply; 14+ messages in thread
From: Dale @ 2013-05-26 12:10 UTC (permalink / raw
To: gentoo-user
Alan McKinnon wrote:
> On 26/05/2013 13:03, Dale wrote:
>> Alan McKinnon wrote:
>>> On 26/05/2013 11:51, Dale wrote:
>>>
>>>> What package provides the kicker thingy? I think in KDE3 it was called
>>>> kicker but it appears to have changed to something else. Is that
>>>> krunner that has it now?
>>> Maybe it's time you used the "thingy" suffix a little less and the real
>>> names of things a little more :-)
>>>
>>> What thing are you asking about? The panel that is usually at the bottom
>>> and holds the plasma widgets? Or the thin popup you get with Alt-F2?
>>>
>>> The panel is called plasma-desktop and comes from kde-base/plasma-workspace
>>> The popup is krunner and comes from kde-base/krunner
>>>
>>> I doubt very much it's a real bug as such in either KDE app (although
>>> the fix might go in there). It looks much more to me like a side-effect
>>> of IO blocking - two or more apps are trying to get something done and
>>> unexpectedly are not getting answers, so they hang around waiting in the
>>> doorway and get get in the way of everything else. And just for fun,
>>> video drivers are also trying to get in on the act as they have to deal
>>> with mouse pointer repaints...
>>>
>>> Debugging this one is going to be fun (for peculiar definitions of fun)
>>>
>>>
>> The thingy is the thing at the bottom where I can switch desktops, click
>> the K menu and where my clock is. I think it was called Kicker in
>> KDE3. KDE4 seems to have changed it but not sure what the new name is.
> It's a plasma widget called a panel, the only useful thing it does is to
> be a container for other widgets that do useful stuff.
>
> The panel is started by plasma-desktop as one of the standard widgets it
> manages. The idea is to give you stuff on the screen that looks more or
> less like a familiar desktop. Plasma can do other things and give you
> completely different layouts; like for instance not giving you a panel
> at all. This would be useful on a phone with small screen
>
> The whole thing is heavily event based and has to react to a bucket load
> of system events being generated such as what the mouse is doing.
> There's a fantastic number of ways this could go wrong, some might be
> plasma's fault, some might be faults that happen to plasma
I'll try to remember to call it a panel thingy then. ROFL
>> I hope they fix this thing soon. If they remove the driver from the
>> tree, I'm in a bit of a pickle.
> No, you won't be. You have the ebuild right now, copy it to your overlay
> and "remove" becomes something that will not happen
>
>
>
Last time I did that, it didn't work out well. Actually, it just plain
didn't work. May as well tell it like it is. ;-) I'll save a copy
just in case.
Cross that bridge when I get there I guess.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Re: Nvidia drivers and KDE problem
2013-05-26 11:50 ` [gentoo-user] " Nikos Chantziaras
@ 2013-05-26 12:14 ` Dale
2013-05-26 12:55 ` Nikos Chantziaras
0 siblings, 1 reply; 14+ messages in thread
From: Dale @ 2013-05-26 12:14 UTC (permalink / raw
To: gentoo-user
Nikos Chantziaras wrote:
> On 26/05/13 12:12, Dale wrote:
>> [...]
>> The problem. After I am logged into KDE for a good while, like several
>> hours to maybe a day or so, the kicker thingy at the bottom locks up
>> tight. I can't switch desktops, clock stops working, can't click the K
>> menu thingy either. Everything in the kicker thingy is dead as a door
>> nail. I can switch desktops with the keyboard and everything else works
>> in KDE just fine. I can also switch to a console too. Killing X and
>> restarting it fixes it, xdm restart in my case. I don't have to reload
>> drivers or restart the system.
>
> Hmm, something similar happens here sometimes. But not as severe. It
> usually happens when I close many windows rapidly in succession, but
> it's not permanent. The panel becomes responsive again after 10
> seconds or so. I'm also on latest nvidia-drivers, but it was happening
> with older versions too. I happened very rarely though, so it didn't
> bother me enough to go investigating.
>
> Here's something to try out: when it happens, hit the shortcut on your
> keyboard that temporarily suspends desktop effects. I don't remember
> what the default shortcut for it is, as I've changed it, but it's
> shown and configured in the "General" tab of "Desktop Effects" in
> System Settings. See if hitting the shortcut twice to disable and then
> re-enable desktop effects fixes it.
>
>
>
Mine wasn't set at all. I set it to ctrl alt F12. Now to remember that
and try it. Also, I'm using the good nvidia version right now so it
won't happen right now. Maybe on the next upgrade. :/
At least I know it is not just me. So far, two people have had this
issue to some degree.
Thanks.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
^ permalink raw reply [flat|nested] 14+ messages in thread
* [gentoo-user] Re: Nvidia drivers and KDE problem
2013-05-26 12:14 ` Dale
@ 2013-05-26 12:55 ` Nikos Chantziaras
0 siblings, 0 replies; 14+ messages in thread
From: Nikos Chantziaras @ 2013-05-26 12:55 UTC (permalink / raw
To: gentoo-user
On 26/05/13 15:14, Dale wrote:
> Nikos Chantziaras wrote:
>> On 26/05/13 12:12, Dale wrote:
>>> [...]
>>> The problem. After I am logged into KDE for a good while, like several
>>> hours to maybe a day or so, the kicker thingy at the bottom locks up
>>> tight. I can't switch desktops, clock stops working, can't click the K
>>> menu thingy either. Everything in the kicker thingy is dead as a door
>>> nail. I can switch desktops with the keyboard and everything else works
>>> in KDE just fine. I can also switch to a console too. Killing X and
>>> restarting it fixes it, xdm restart in my case. I don't have to reload
>>> drivers or restart the system.
>>
>> Hmm, something similar happens here sometimes. But not as severe. It
>> usually happens when I close many windows rapidly in succession, but
>> it's not permanent. The panel becomes responsive again after 10
>> seconds or so. I'm also on latest nvidia-drivers, but it was happening
>> with older versions too. I happened very rarely though, so it didn't
>> bother me enough to go investigating.
>>
>> Here's something to try out: when it happens, hit the shortcut on your
>> keyboard that temporarily suspends desktop effects. I don't remember
>> what the default shortcut for it is, as I've changed it, but it's
>> shown and configured in the "General" tab of "Desktop Effects" in
>> System Settings. See if hitting the shortcut twice to disable and then
>> re-enable desktop effects fixes it.
>
> Mine wasn't set at all. I set it to ctrl alt F12. Now to remember that
> and try it. Also, I'm using the good nvidia version right now so it
> won't happen right now. Maybe on the next upgrade. :/
Ctrl+Alt+F12 will probably be intercepted by the X server and switch to
virtual console 12. Try something like Ctrl+Shift+F12 instead (I've set
mine to the "My Computer" button on the keyboard though, since that
one's useless otherwise.)
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 9:12 [gentoo-user] Nvidia drivers and KDE problem Dale
2013-05-26 9:41 ` Alan McKinnon
2013-05-26 11:50 ` [gentoo-user] " Nikos Chantziaras
@ 2013-05-26 21:17 ` Volker Armin Hemmann
2013-05-29 22:28 ` Paul Hartman
3 siblings, 0 replies; 14+ messages in thread
From: Volker Armin Hemmann @ 2013-05-26 21:17 UTC (permalink / raw
To: gentoo-user
Am 26.05.2013 11:12, schrieb Dale:
> Howdy,
>
> I been letting portage upgrade nvidia drivers as usual. Thing is, the
> last two or three drivers seems to cause a issue. First, versions that
> cause the issue:
>
> =x11-drivers/nvidia-drivers-319.12
> =x11-drivers/nvidia-drivers-319.17
> =x11-drivers/nvidia-drivers-319.23
>
> I'm currently using this one which works fine:
>
> x11-drivers/nvidia-drivers-313.30
>
> This is KDE info:
>
> [IP-] [ ] kde-base/kdelibs-4.10.3-r2
>
> Video card info:
>
> 01:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT
> 220] (rev a2) (prog-if 00 [VGA controller])
> Subsystem: NVIDIA Corporation Device 069a
> Flags: bus master, fast devsel, latency 0, IRQ 18
> Memory at fb000000 (32-bit, non-prefetchable) [size=16M]
> Memory at c0000000 (64-bit, prefetchable) [size=256M]
> Memory at de000000 (64-bit, prefetchable) [size=32M]
> I/O ports at ef00 [size=128]
> [virtual] Expansion ROM at d0000000 [disabled] [size=512K]
> Capabilities: [60] Power Management version 3
> Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [78] Express Endpoint, MSI 00
> Capabilities: [b4] Vendor Specific Information: Len=14 <?>
> Capabilities: [100] Virtual Channel
> Capabilities: [128] Power Budgeting <?>
> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1
> Len=024 <?>
> Kernel driver in use: nvidia
> Kernel modules: nvidia
>
>
> The problem. After I am logged into KDE for a good while, like several
> hours to maybe a day or so, the kicker thingy at the bottom locks up
> tight. I can't switch desktops, clock stops working, can't click the K
> menu thingy either. Everything in the kicker thingy is dead as a door
> nail. I can switch desktops with the keyboard and everything else works
> in KDE just fine. I can also switch to a console too. Killing X and
> restarting it fixes it, xdm restart in my case. I don't have to reload
> drivers or restart the system. I do go back and downgrade the drivers
> after testing it.
>
> So, is this a nvidia bug, KDE bug or is it something else? Since it
> works when I go back a version of nvidia, it looks like nvidia. Think
> is, it only affects KDE and nothing else. Is it possible that my card
> is not supposed to use the 319.* series of drivers? The versions that
> don't work are all 319.* series.
>
> Thoughts?
>
> Dale
>
> :-) :-)
>
next time as root do:
killall -9 krunner
killall -9 plasma-desktop
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 12:10 ` Dale
@ 2013-05-27 15:43 ` Fast Turtle
0 siblings, 0 replies; 14+ messages in thread
From: Fast Turtle @ 2013-05-27 15:43 UTC (permalink / raw
To: gentoo-user
On Sun, 26 May 2013 07:10:53 -0500
Dale <rdalek1967@gmail.com> wrote:
> Alan McKinnon wrote:
> > On 26/05/2013 13:03, Dale wrote:
> >> Alan McKinnon wrote:
> >>> On 26/05/2013 11:51, Dale wrote:
> >>>
> >>>> What package provides the kicker thingy? I think in KDE3 it was called
> >>>> kicker but it appears to have changed to something else. Is that
> >>>> krunner that has it now?
> >>> Maybe it's time you used the "thingy" suffix a little less and the real
> >>> names of things a little more :-)
> >>>
> >>> What thing are you asking about? The panel that is usually at the bottom
> >>> and holds the plasma widgets? Or the thin popup you get with Alt-F2?
> >>>
> >>> The panel is called plasma-desktop and comes from kde-base/plasma-workspace
> >>> The popup is krunner and comes from kde-base/krunner
> >>>
> >>> I doubt very much it's a real bug as such in either KDE app (although
> >>> the fix might go in there). It looks much more to me like a side-effect
> >>> of IO blocking - two or more apps are trying to get something done and
> >>> unexpectedly are not getting answers, so they hang around waiting in the
> >>> doorway and get get in the way of everything else. And just for fun,
> >>> video drivers are also trying to get in on the act as they have to deal
> >>> with mouse pointer repaints...
> >>>
> >>> Debugging this one is going to be fun (for peculiar definitions of fun)
> >>>
> >>>
> >> The thingy is the thing at the bottom where I can switch desktops, click
> >> the K menu and where my clock is. I think it was called Kicker in
> >> KDE3. KDE4 seems to have changed it but not sure what the new name is.
> > It's a plasma widget called a panel, the only useful thing it does is to
> > be a container for other widgets that do useful stuff.
> >
> > The panel is started by plasma-desktop as one of the standard widgets it
> > manages. The idea is to give you stuff on the screen that looks more or
> > less like a familiar desktop. Plasma can do other things and give you
> > completely different layouts; like for instance not giving you a panel
> > at all. This would be useful on a phone with small screen
> >
> > The whole thing is heavily event based and has to react to a bucket load
> > of system events being generated such as what the mouse is doing.
> > There's a fantastic number of ways this could go wrong, some might be
> > plasma's fault, some might be faults that happen to plasma
>
>
> I'll try to remember to call it a panel thingy then. ROFL
>
>
> >> I hope they fix this thing soon. If they remove the driver from the
> >> tree, I'm in a bit of a pickle.
> > No, you won't be. You have the ebuild right now, copy it to your overlay
> > and "remove" becomes something that will not happen
> >
> >
> >
>
> Last time I did that, it didn't work out well. Actually, it just plain
> didn't work. May as well tell it like it is. ;-) I'll save a copy
> just in case.
>
> Cross that bridge when I get there I guess.
>
> Dale
>
> :-) :-)
>
> --
> I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
>
>
I suspect it's the fact your using the ~arch version of kde (4.10.3) is not fully stable yet and yes there be bugs in them valleys.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-26 9:12 [gentoo-user] Nvidia drivers and KDE problem Dale
` (2 preceding siblings ...)
2013-05-26 21:17 ` [gentoo-user] " Volker Armin Hemmann
@ 2013-05-29 22:28 ` Paul Hartman
2013-05-29 23:08 ` Dale
3 siblings, 1 reply; 14+ messages in thread
From: Paul Hartman @ 2013-05-29 22:28 UTC (permalink / raw
To: gentoo-user
On Sun, May 26, 2013 at 4:12 AM, Dale <rdalek1967@gmail.com> wrote:
> The problem. After I am logged into KDE for a good while, like several
> hours to maybe a day or so, the kicker thingy at the bottom locks up
> tight. I can't switch desktops, clock stops working, can't click the K
> menu thingy either. Everything in the kicker thingy is dead as a door
> nail. I can switch desktops with the keyboard and everything else works
> in KDE just fine. I can also switch to a console too. Killing X and
> restarting it fixes it, xdm restart in my case. I don't have to reload
> drivers or restart the system. I do go back and downgrade the drivers
> after testing it.
I recently started having trouble where KDE becomes unresponsive at
login and logout for about 20 seconds or more. In my case it was
because of pulseaudio and KDE not getting along together for some
reason. The facts are a bit more nuanced but the work-around that
makes everything normal for me again was to edit
/etc/xdg/autostart/pulseaudio.desktop and add a line which says:
NotShowIn=KDE
Maybe unrelated to your problem but I thought I would mention it just in case.
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [gentoo-user] Nvidia drivers and KDE problem
2013-05-29 22:28 ` Paul Hartman
@ 2013-05-29 23:08 ` Dale
0 siblings, 0 replies; 14+ messages in thread
From: Dale @ 2013-05-29 23:08 UTC (permalink / raw
To: gentoo-user
Paul Hartman wrote:
> On Sun, May 26, 2013 at 4:12 AM, Dale <rdalek1967@gmail.com> wrote:
>> The problem. After I am logged into KDE for a good while, like several
>> hours to maybe a day or so, the kicker thingy at the bottom locks up
>> tight. I can't switch desktops, clock stops working, can't click the K
>> menu thingy either. Everything in the kicker thingy is dead as a door
>> nail. I can switch desktops with the keyboard and everything else works
>> in KDE just fine. I can also switch to a console too. Killing X and
>> restarting it fixes it, xdm restart in my case. I don't have to reload
>> drivers or restart the system. I do go back and downgrade the drivers
>> after testing it.
> I recently started having trouble where KDE becomes unresponsive at
> login and logout for about 20 seconds or more. In my case it was
> because of pulseaudio and KDE not getting along together for some
> reason. The facts are a bit more nuanced but the work-around that
> makes everything normal for me again was to edit
> /etc/xdg/autostart/pulseaudio.desktop and add a line which says:
> NotShowIn=KDE
>
> Maybe unrelated to your problem but I thought I would mention it just in case.
>
>
I don't use pulseaudio but thanks for the post tho. If I did, could
have helped. :-)
Also, I still have two posts I have not replied to because it hasn't
locked up yet. I haven't been able to test the things yet. If it locks
up again, will reply with the results.
Dale
:-) :-)
--
I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2013-05-29 23:08 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-05-26 9:12 [gentoo-user] Nvidia drivers and KDE problem Dale
2013-05-26 9:41 ` Alan McKinnon
2013-05-26 9:51 ` Dale
2013-05-26 10:39 ` Alan McKinnon
2013-05-26 11:03 ` Dale
2013-05-26 11:31 ` Alan McKinnon
2013-05-26 12:10 ` Dale
2013-05-27 15:43 ` Fast Turtle
2013-05-26 11:50 ` [gentoo-user] " Nikos Chantziaras
2013-05-26 12:14 ` Dale
2013-05-26 12:55 ` Nikos Chantziaras
2013-05-26 21:17 ` [gentoo-user] " Volker Armin Hemmann
2013-05-29 22:28 ` Paul Hartman
2013-05-29 23:08 ` Dale
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox