sorry to be such a bother, but as long as i'm bringing things up, here's one that has been an issue for a couple of years and survived into R14.
my desktop crashes, but in such a way as to not even be noticeable at first.
i have in lieu of wallpaper xplanet set up as a realtime moon phase indicator, updating hourly. the way i tell the desktop has crashed is that it doesn't update -- in this case it last refreshed at 10:30 a.m. yesterday. i believe that i was probably editing pictures at that time, though would not swear to it.
after it crashes, a right click on the desktop does not produce the expected menu. as it happens, kicker and everything else continues to function as expected -- in fact, it was just now that i noticed that the desktop itself had gone south.
i thought i'd look in the x error log, bit i see that the one i have, ~/.xsession-errors, is of an unspecified file type and won't open in a text editor (it reports its size as 500.0 k).
any idea if there's a log that might let me see what's going on here and if so what log it might be? bonus points, how i might restart the desktop without logging out and back in? extra bonus points, how i might fix it so it doesn't do this anymore? i'm running some flavor of ubuntu 12.04LTS -- i say some flavor because when i sought to upgrade a few days ago the ubuntu upgrader refused, citing third-party apps or a beta version of the opsys, or something; it didn't specify. i thought i had bog standard 12.04LTS on the machine but am apparently wrong.
On Sunday 28 December 2014, dep wrote:
sorry to be such a bother, but as long as i'm bringing things up, here's one that has been an issue for a couple of years and survived into R14.
my desktop crashes, but in such a way as to not even be noticeable at first.
i have in lieu of wallpaper xplanet set up as a realtime moon phase indicator, updating hourly. the way i tell the desktop has crashed is that it doesn't update -- in this case it last refreshed at 10:30 a.m. yesterday. i believe that i was probably editing pictures at that time, though would not swear to it.
after it crashes, a right click on the desktop does not produce the expected menu. as it happens, kicker and everything else continues to function as expected -- in fact, it was just now that i noticed that the desktop itself had gone south.
i thought i'd look in the x error log, bit i see that the one i have, ~/.xsession-errors, is of an unspecified file type and won't open in a text editor (it reports its size as 500.0 k).
any idea if there's a log that might let me see what's going on here and if so what log it might be? bonus points, how i might restart the desktop without logging out and back in? extra bonus points, how i might fix it so it doesn't do this anymore? i'm running some flavor of ubuntu 12.04LTS -- i say some flavor because when i sought to upgrade a few days ago the ubuntu upgrader refused, citing third-party apps or a beta version of the opsys, or something; it didn't specify. i thought i had bog standard 12.04LTS on the machine but am apparently wrong.
you might find hints following this thread:
http://trinity-users.pearsoncomputing.net/?0::6738
if the problem is the same. Here are some quotes: On Friday 10 October 2014, Gerhard Zintel wrote:
On Tuesday 07 October 2014, Slávek Banko wrote:
On Tuesday 07 of October 2014 11:34:25 Ilya Dogolazky wrote:
Hi !
I'm running trinity desktop on Debian Testing linux. Sometimes all the icons from desktop disappear and (at the same time!) the desktop lock button (blue lock symbol in the kicker panel) stops to work.
What service/program to I have to restart in order to fix it without logging out and in again?
Cheers
Ilya Dogolazky
Disappearing icons from the desktop shows to crash KDesktop. Starting kdesktop should correct the problem.
At this situation please take a look into ~/.xsession-error, if there is listed a backtrace about KDesktop crash? It could help to detect and fix the problem.
Update: Today I faced the problem again. Unfortunately I did not look into the .xsession-errors file before I started to relaunch kdesktop. Nevertheless it did not crash. First action: I started kdesktop from Konsole. It told me that kdesktop is already running but didn't come back to the prompt. Icons were not recreated. I had to Ctrl-C for the promt. "ps ax" showed me an old version of kdesktop and a second new one with <defunct> message. Killing the defunct one was not possible. I killed the original kdesktop program (Desktop went black) and relaunched it and - voila - the icons reapeared on the desktop. Also the defunct process of kdesktop was gone.
I do not find anything special in the xsession errors file. I try to investigate more accurate next time.
Hope this helps Gerhard
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 12/28/2014 08:15 AM, dep wrote:
sorry to be such a bother, but as long as i'm bringing things up, here's one that has been an issue for a couple of years and survived into R14.
my desktop crashes, but in such a way as to not even be noticeable at first.
i have in lieu of wallpaper xplanet set up as a realtime moon phase indicator, updating hourly. the way i tell the desktop has crashed is that it doesn't update -- in this case it last refreshed at 10:30 a.m. yesterday. i believe that i was probably editing pictures at that time, though would not swear to it.
after it crashes, a right click on the desktop does not produce the expected menu. as it happens, kicker and everything else continues to function as expected -- in fact, it was just now that i noticed that the desktop itself had gone south.
i thought i'd look in the x error log, bit i see that the one i have, ~/.xsession-errors, is of an unspecified file type and won't open in a text editor (it reports its size as 500.0 k).
any idea if there's a log that might let me see what's going on here and if so what log it might be? bonus points, how i might restart the desktop without logging out and back in? extra bonus points, how i might fix it so it doesn't do this anymore? i'm running some flavor of ubuntu 12.04LTS -- i say some flavor because when i sought to upgrade a few days ago the ubuntu upgrader refused, citing third-party apps or a beta version of the opsys, or something; it didn't specify. i thought i had bog standard 12.04LTS on the machine but am apparently wrong.
Hi, sorry for the late reply. The desktop behavior is controlled by the kdesktop process. When your desktop stops updating, from CLI type: ps aux | grep desktop and see if there is something like: username 8414 0.4 0.7 260192 28956 pts/8 Sl 12:50 0:00 kdesktop
If not, kdesktop has crashed. You can type: kdesktop & from CLI to restart it (or alternatively Alt-F2 and then kdesktop).
If this brings everything back in order, please let us know because we need some more advanced testing to understand why and where kdesktop crashed.
Cheers Michele
said Michele Calgaro: | On 12/28/2014 08:15 AM, dep wrote: | > sorry to be such a bother, but as long as i'm bringing things up, | > here's one that has been an issue for a couple of years and survived | > into R14. | > | > my desktop crashes, but in such a way as to not even be noticeable at | > first. | > | > i have in lieu of wallpaper xplanet set up as a realtime moon phase | > indicator, updating hourly. the way i tell the desktop has crashed is | > that it doesn't update -- in this case it last refreshed at 10:30 a.m. | > yesterday. i believe that i was probably editing pictures at that | > time, though would not swear to it. | > | > after it crashes, a right click on the desktop does not produce the | > expected menu. as it happens, kicker and everything else continues to | > function as expected -- in fact, it was just now that i noticed that | > the desktop itself had gone south. | > | > i thought i'd look in the x error log, bit i see that the one i have, | > ~/.xsession-errors, is of an unspecified file type and won't open in a | > text editor (it reports its size as 500.0 k). | > | > any idea if there's a log that might let me see what's going on here | > and if so what log it might be? bonus points, how i might restart the | > desktop without logging out and back in? extra bonus points, how i | > might fix it so it doesn't do this anymore? i'm running some flavor of | > ubuntu 12.04LTS -- i say some flavor because when i sought to upgrade | > a few days ago the ubuntu upgrader refused, citing third-party apps or | > a beta version of the opsys, or something; it didn't specify. i | > thought i had bog standard 12.04LTS on the machine but am apparently | > wrong. | | | sorry for the late reply. The desktop behavior is controlled by the | kdesktop process. When your desktop stops updating, from CLI type: | ps aux | grep desktop | and see if there is something like: | username 8414 0.4 0.7 260192 28956 pts/8 Sl 12:50 0:00 | kdesktop
avahi 1973 0.0 0.0 32308 1732 ? S 2014 0:01 avahi-daemon: running [dep-desktop.local] dep 3200 0.0 0.1 252184 17972 ? Sl 2014 1:04 /opt/trinity/bin/kdesktop dep 11289 0.0 0.0 0 0 ? Z 2014 0:02 [kdesktop_lock] <defunct> dep 29758 0.0 0.0 9388 904 pts/0 S+ 16:12 0:00 grep desktop
nevertheless, it hasn't updated since 10:19:53 AM 26 December. and a rmb click on the desktop does not produce the expected menu.
| If not, kdesktop has crashed. You can type: | kdesktop & from CLI to restart it (or alternatively Alt-F2 and then | kdesktop).
dep@dep-desktop:~$ kdesktop is already running!
| If this brings everything back in order, please let us know because we | need some more advanced testing to understand why and where kdesktop | crashed.
fwiw, top reports 3 zombies.
On Friday 02 January 2015, dep wrote:
said Michele Calgaro: | On 12/28/2014 08:15 AM, dep wrote: | > sorry to be such a bother, but as long as i'm bringing things up, | > here's one that has been an issue for a couple of years and survived | > into R14. | > | > my desktop crashes, but in such a way as to not even be noticeable at | > first. | > | > i have in lieu of wallpaper xplanet set up as a realtime moon phase | > indicator, updating hourly. the way i tell the desktop has crashed is | > that it doesn't update -- in this case it last refreshed at 10:30 a.m. | > yesterday. i believe that i was probably editing pictures at that | > time, though would not swear to it. | > | > after it crashes, a right click on the desktop does not produce the | > expected menu. as it happens, kicker and everything else continues to | > function as expected -- in fact, it was just now that i noticed that | > the desktop itself had gone south. | > | > i thought i'd look in the x error log, bit i see that the one i have, | > ~/.xsession-errors, is of an unspecified file type and won't open in a | > text editor (it reports its size as 500.0 k). | > | > any idea if there's a log that might let me see what's going on here | > and if so what log it might be? bonus points, how i might restart the | > desktop without logging out and back in? extra bonus points, how i | > might fix it so it doesn't do this anymore? i'm running some flavor of | > ubuntu 12.04LTS -- i say some flavor because when i sought to upgrade | > a few days ago the ubuntu upgrader refused, citing third-party apps or | > a beta version of the opsys, or something; it didn't specify. i | > thought i had bog standard 12.04LTS on the machine but am apparently | > wrong. | | | sorry for the late reply. The desktop behavior is controlled by the | kdesktop process. When your desktop stops updating, from CLI type: | ps aux | grep desktop | and see if there is something like: | username 8414 0.4 0.7 260192 28956 pts/8 Sl 12:50 0:00 | kdesktop
avahi 1973 0.0 0.0 32308 1732 ? S 2014 0:01 avahi-daemon: running [dep-desktop.local] dep 3200 0.0 0.1 252184 17972 ? Sl 2014 1:04 /opt/trinity/bin/kdesktop dep 11289 0.0 0.0 0 0 ? Z 2014 0:02 [kdesktop_lock] <defunct> dep 29758 0.0 0.0 9388 904 pts/0 S+ 16:12 0:00 grep desktop
nevertheless, it hasn't updated since 10:19:53 AM 26 December. and a rmb click on the desktop does not produce the expected menu.
| If not, kdesktop has crashed. You can type: | kdesktop & from CLI to restart it (or alternatively Alt-F2 and then | kdesktop).
dep@dep-desktop:~$ kdesktop is already running!
| If this brings everything back in order, please let us know because we | need some more advanced testing to understand why and where kdesktop | crashed.
fwiw, top reports 3 zombies.
have you tried to kill the running kdesktop beforehand (not the defuncts)? I assume it runns under process number 3200. Thus: $ kill -9 3200
and than launch kdesktop again?
Gerhard PS: "killall kdesktop" might work as well; be sure to have a konsole open for it.
said Gerhard Zintel: | On Friday 02 January 2015, dep wrote: | > said Michele Calgaro: | > | On 12/28/2014 08:15 AM, dep wrote: | > | > sorry to be such a bother, but as long as i'm bringing things up, | > | > here's one that has been an issue for a couple of years and | > | > survived into R14. | > | > | > | > my desktop crashes, but in such a way as to not even be noticeable | > | > at first. | > | > | > | > i have in lieu of wallpaper xplanet set up as a realtime moon | > | > phase indicator, updating hourly. the way i tell the desktop has | > | > crashed is that it doesn't update -- in this case it last | > | > refreshed at 10:30 a.m. yesterday. i believe that i was probably | > | > editing pictures at that time, though would not swear to it. | > | > | > | > after it crashes, a right click on the desktop does not produce | > | > the expected menu. as it happens, kicker and everything else | > | > continues to function as expected -- in fact, it was just now that | > | > i noticed that the desktop itself had gone south. | > | > | > | > i thought i'd look in the x error log, bit i see that the one i | > | > have, ~/.xsession-errors, is of an unspecified file type and won't | > | > open in a text editor (it reports its size as 500.0 k). | > | > | > | > any idea if there's a log that might let me see what's going on | > | > here and if so what log it might be? bonus points, how i might | > | > restart the desktop without logging out and back in? extra bonus | > | > points, how i might fix it so it doesn't do this anymore? i'm | > | > running some flavor of ubuntu 12.04LTS -- i say some flavor | > | > because when i sought to upgrade a few days ago the ubuntu | > | > upgrader refused, citing third-party apps or a beta version of the | > | > opsys, or something; it didn't specify. i thought i had bog | > | > standard 12.04LTS on the machine but am apparently wrong. | > | | > | sorry for the late reply. The desktop behavior is controlled by the | > | kdesktop process. When your desktop stops updating, from CLI type: | > | ps aux | grep desktop | > | and see if there is something like: | > | username 8414 0.4 0.7 260192 28956 pts/8 Sl 12:50 0:00 | > | kdesktop | > | > avahi 1973 0.0 0.0 32308 1732 ? S 2014 0:01 | > avahi-daemon: running [dep-desktop.local] | > dep 3200 0.0 0.1 252184 17972 ? Sl 2014 | > 1:04 /opt/trinity/bin/kdesktop | > dep 11289 0.0 0.0 0 0 ? Z 2014 0:02 | > [kdesktop_lock] <defunct> | > dep 29758 0.0 0.0 9388 904 pts/0 S+ 16:12 0:00 grep | > desktop | > | > nevertheless, it hasn't updated since 10:19:53 AM 26 December. and a | > rmb click on the desktop does not produce the expected menu. | > | > | If not, kdesktop has crashed. You can type: | > | kdesktop & from CLI to restart it (or alternatively Alt-F2 and then | > | kdesktop). | > | > dep@dep-desktop:~$ kdesktop is already running! | > | > | If this brings everything back in order, please let us know because | > | we need some more advanced testing to understand why and where | > | kdesktop crashed. | > | > fwiw, top reports 3 zombies. | | have you tried to kill the running kdesktop beforehand (not the | defuncts)? I assume it runns under process number 3200. Thus: | $ kill -9 3200 | | and than launch kdesktop again?
this worked. i do not know if we learned anything from its having worked, but work it did.
thanks!
On Friday 02 January 2015, dep wrote:
said Gerhard Zintel: | > avahi 1973 0.0 0.0 32308 1732 ? S 2014 0:01 | > avahi-daemon: running [dep-desktop.local] | > dep 3200 0.0 0.1 252184 17972 ? Sl 2014 | > 1:04 /opt/trinity/bin/kdesktop | > dep 11289 0.0 0.0 0 0 ? Z 2014 0:02 | > [kdesktop_lock] <defunct> | > dep 29758 0.0 0.0 9388 904 pts/0 S+ 16:12 0:00 grep | > desktop | > | > nevertheless, it hasn't updated since 10:19:53 AM 26 December. and a | > rmb click on the desktop does not produce the expected menu. | > | > | If not, kdesktop has crashed. You can type: | > | kdesktop & from CLI to restart it (or alternatively Alt-F2 and then | > | kdesktop). | > | > dep@dep-desktop:~$ kdesktop is already running! | > | > | If this brings everything back in order, please let us know because | > | we need some more advanced testing to understand why and where | > | kdesktop crashed. | > | > fwiw, top reports 3 zombies. | | have you tried to kill the running kdesktop beforehand (not the | defuncts)? I assume it runns under process number 3200. Thus: | $ kill -9 3200 | | and than launch kdesktop again?
this worked. i do not know if we learned anything from its having worked, but work it did.
I have to restore kdesktop from time to time this way (about each week). Others seems to have the problem as well. Tried to give debug information to the list but obviously with too less information yet.
Have not written a bug report yet though.
Gerhard
BTW: I'm useing kmail. I just relized that I have to give Enter for line endings otherwise my mails are with very long lines in the list archives. That's very inconvenient especially when you do some edits before sending the mail. Kmail normally breaks down my line length automatically during writing. Why isn't this reflected in the archive? Can I tune this in the settings? Others seems not to have the problem.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 01/03/2015 07:53 AM, dep wrote:
said Gerhard Zintel: | On Friday 02 January 2015, dep wrote: | > said Michele Calgaro: | > | On 12/28/2014 08:15 AM, dep wrote: | > | > sorry to be such a bother, but as long as i'm bringing things up, | > | > here's one that has been an issue for a couple of years and | > | > survived into R14. | > | > | > | > my desktop crashes, but in such a way as to not even be noticeable | > | > at first. | > | > | > | > i have in lieu of wallpaper xplanet set up as a realtime moon | > | > phase indicator, updating hourly. the way i tell the desktop has | > | > crashed is that it doesn't update -- in this case it last | > | > refreshed at 10:30 a.m. yesterday. i believe that i was probably | > | > editing pictures at that time, though would not swear to it. | > | > | > | > after it crashes, a right click on the desktop does not produce | > | > the expected menu. as it happens, kicker and everything else |
| > continues to function as expected -- in fact, it was just now that | > | > i noticed that the desktop itself
had gone south. | > | > | > | > i thought i'd look in the x error log, bit i see that the one i | > | > have, ~/.xsession-errors, is of an unspecified file type and won't | > | > open in a text editor (it reports its size as 500.0 k). | > | > | > | > any idea if there's a log that might let me see what's going on | > | > here and if so what log it might be? bonus points, how i might | > | > restart the desktop without logging out and back in? extra bonus | > | > points, how i might fix it so it doesn't do this anymore? i'm | > | > running some flavor of ubuntu 12.04LTS -- i say some flavor | > | > because when i sought to upgrade a few days ago the ubuntu | > | > upgrader refused, citing third-party apps or a beta version of the | > | > opsys, or something; it didn't specify. i thought i had bog | > | > standard 12.04LTS on the machine but am apparently wrong. | > | | > | sorry for the late reply. The desktop behavior is controlled by the | > | kdesktop process. When your desktop stops updating, from CLI type: | > | ps aux | grep desktop | > | and see if there is something like: | > | username 8414 0.4 0.7 260192 28956 pts/8 Sl 12:50 0:00 | > | kdesktop | > | > avahi 1973 0.0 0.0 32308 1732 ? S 2014 0:01 | > avahi-daemon: running [dep-desktop.local] | > dep 3200 0.0 0.1 252184 17972 ? Sl 2014 |
1:04 /opt/trinity/bin/kdesktop | > dep 11289 0.0 0.0 0 0 ? Z 2014 0:02 | >
[kdesktop_lock] <defunct> | > dep 29758 0.0 0.0 9388 904 pts/0 S+ 16:12 0:00 grep | > desktop |
| > nevertheless, it hasn't updated since 10:19:53 AM 26 December. and a | > rmb click on the desktop does not
produce the expected menu. | > | > | If not, kdesktop has crashed. You can type: | > | kdesktop & from CLI to restart it (or alternatively Alt-F2 and then | > | kdesktop). | > | > dep@dep-desktop:~$ kdesktop is already running! | > | > | If this brings everything back in order, please let us know because | > | we need some more advanced testing to understand why and where | > | kdesktop crashed. | > | > fwiw, top reports 3 zombies. | | have you tried to kill the running kdesktop beforehand (not the | defuncts)? I assume it runns under process number 3200. Thus: | $ kill -9 3200 | | and than launch kdesktop again?
this worked. i do not know if we learned anything from its having worked, but work it did.
thanks!
kdesktop_lock died and has not been reaped, so I suspect that kdesktop may be waiting on some unreleased mutex, which would be the reason why the background does not update any more and the RMB click doesn't do anything. Something obviously went wrong. The next time you see the error, can you try the following: 1) ps aux | grep kdesktop -> this should give again kdesktop_lock <defunct> 2) take note of the kdesktop pid (not the kdesktop_lock) 3) from CLI (not within TDE, but from a tty), run: gdb --pid=<pid of kdesktop> --> you may try from a TDE console, but you may loose the keyboard. In such case you have to switch to a tty, kill the gdb instance and retry from there. 4) type: thread apply all bt Report what is printed out. This hopefully will provide some additional info. If it is not critical for you, please do not exit gdb and do not kill and restart kdesktop. Depending on what we find, we may have to run some other commands.
By the way, can you open a proper bug report on our bugszilla? It looks like there is something to fix here :-)
Cheers Michele
said Michele Calgaro: | On 01/03/2015 07:53 AM, dep wrote: | > said Gerhard Zintel: | On Friday 02 January 2015, dep wrote: | > said | > Michele Calgaro: | > | On 12/28/2014 08:15 AM, dep wrote: | > | > | > sorry to be such a bother, but as long as i'm bringing things up, | > | > | > here's one that has been an issue for a couple of years and | > | | > > survived into R14. | > | > | > | > my desktop crashes, but in such a | > way as to not even be noticeable | > | > at first. | > | > | > | > i | > have in lieu of wallpaper xplanet set up as a realtime moon | > | > | > phase indicator, updating hourly. the way i tell the desktop has | > | | > > crashed is that it doesn't update -- in this case it last | > | > | > refreshed at 10:30 a.m. yesterday. i believe that i was probably | > | | > > editing pictures at that time, though would not swear to it. | > | > | > | > | > after it crashes, a right click on the desktop does not | > produce | > | > the expected menu. as it happens, kicker and | > everything else | | > | > > | > continues to function as expected -- in fact, it was just now | > > | > that | > | > i noticed that the desktop itself | > | > had gone south. | > | > | > | > i thought i'd look in the x error log, | > bit i see that the one i | > | > have, ~/.xsession-errors, is of an | > unspecified file type and won't | > | > open in a text editor (it | > reports its size as 500.0 k). | > | > | > | > any idea if there's a | > log that might let me see what's going on | > | > here and if so what | > log it might be? bonus points, how i might | > | > restart the desktop | > without logging out and back in? extra bonus | > | > points, how i | > might fix it so it doesn't do this anymore? i'm | > | > running some | > flavor of ubuntu 12.04LTS -- i say some flavor | > | > because when i | > sought to upgrade a few days ago the ubuntu | > | > upgrader refused, | > citing third-party apps or a beta version of the | > | > opsys, or | > something; it didn't specify. i thought i had bog | > | > standard | > 12.04LTS on the machine but am apparently wrong. | > | | > | sorry for | > the late reply. | > | > The desktop behavior is controlled by the | > | kdesktop process. When your desktop stops updating, from CLI type: | > | > | ps aux | grep desktop | > | and see if there is something like: | > | > | | > | username 8414 0.4 0.7 260192 | > | > 28956 pts/8 Sl 12:50 0:00 | > | kdesktop | > | > avahi 1973 | > 0.0 0.0 32308 1732 ? S 2014 0:01 | > avahi-daemon: | > running [dep-desktop.local] | > dep 3200 0.0 0.1 252184 17972 | > ? Sl 2014 | | > | > > 1:04 /opt/trinity/bin/kdesktop | > dep 11289 0.0 0.0 0 | > > 0 ? Z 2014 0:02 | > | > | > [kdesktop_lock] <defunct> | > dep 29758 0.0 0.0 9388 904 | > pts/0 S+ 16:12 0:00 grep | > desktop | | > | > > | > nevertheless, it hasn't updated since 10:19:53 AM 26 December. | > > | > and a | > rmb click on the desktop does not | > | > produce the expected menu. | > | > | If not, kdesktop has crashed. You | > can type: | > | kdesktop & from CLI to restart it (or alternatively | > Alt-F2 and then | > | kdesktop). | > | > dep@dep-desktop:~$ kdesktop | > is already running! | > | > | If this brings everything back in order, | > please let us know because | > | we need some more advanced testing to | > understand why and where | > | kdesktop crashed. | > | > fwiw, top | > reports 3 zombies. | | have you tried to kill the running kdesktop | > beforehand (not the | defuncts)? I assume it runns under process | > number 3200. Thus: | $ kill -9 3200 | | and than launch kdesktop | > again? | > | > this worked. i do not know if we learned anything from its having | > worked, but work it did. | > | > thanks! | | kdesktop_lock died and has not been reaped, so I suspect that kdesktop | may be waiting on some unreleased mutex, which would be the reason why | the background does not update any more and the RMB click doesn't do | anything. Something obviously went wrong. | The next time you see the error, can you try the following: | 1) ps aux | grep kdesktop -> this should give again kdesktop_lock | <defunct> 2) take note of the kdesktop pid (not the kdesktop_lock) | 3) from CLI (not within TDE, but from a tty), run: gdb --pid=<pid of | kdesktop> --> you may try from a TDE console, but you may loose the | keyboard. In such case you have to switch to a tty, kill the gdb | instance and retry from there. 4) type: thread apply all bt | Report what is printed out. This hopefully will provide some additional | info. If it is not critical for you, please do not exit gdb and do not | kill and restart kdesktop. Depending on what we find, we may have to run | some other commands. | | By the way, can you open a proper bug report on our bugszilla? It looks | like there is something to fix here :-)
I shall create an account there and do so; it hath happened again. The results from your instructions:
dep@dep-desktop:~$ ps aux | grep kdesktop dep 11451 0.0 0.0 0 0 ? Z Jan08 3:19 [kdesktop_lock] <defunct> dep 30334 0.0 0.1 252428 18252 ? Sl Jan02 4:55 kdesktop dep 30724 0.0 0.0 9384 908 pts/0 S+ 11:37 0:00 grep kdesktop dep@dep-desktop:~$ gdb --pid=30334 GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/. Attaching to process 30334 Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. (gdb) thread apply all bt (gdb)
so tried again as root:
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/. Attaching to process 30334 Reading symbols from /opt/trinity/bin/kdesktop...(no debugging symbols found)...done. Reading symbols from /opt/trinity/lib/libtdeinit_kdesktop.so...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeinit_kdesktop.so Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 Reading symbols from /opt/trinity/lib/libkonq.so.4...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libkonq.so.4 Reading symbols from /opt/trinity/lib/libtdeutils.so.1...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeutils.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXrender.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXrender.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libX11.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libX11.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libXcursor.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXcursor.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXext.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXext.so.6 Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libXss.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXss.so.1 Reading symbols from /usr/lib/libdbus-1-tqt.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdbus-1-tqt.so.0 Reading symbols from /usr/lib/x86_64-linux-gnu/libXau.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXau.so.6 Reading symbols from /opt/trinity/lib/libtdeio.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeio.so.14 Reading symbols from /opt/trinity/lib/libtdeui.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeui.so.14 Reading symbols from /opt/trinity/lib/libtdesu.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdesu.so.14 Reading symbols from /opt/trinity/lib/libtdecore.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdecore.so.14 Reading symbols from /opt/trinity/lib/libDCOP.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libDCOP.so.14 Reading symbols from /opt/trinity/lib/libtdefx.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdefx.so.14 Reading symbols from /usr/lib/libtqt-mt.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libtqt-mt.so.3 Reading symbols from /usr/lib/x86_64-linux-gnu/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libgcc_s.so.1 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /opt/trinity/lib/libtdeparts.so.2...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeparts.so.2 Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libz.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libxcb.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libxcb.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXfixes.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Reading symbols from /lib/x86_64-linux-gnu/libdbus-1.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libdbus-1.so.3 Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7f5c62de7700 (LWP 30339)] Loaded symbols for /lib/x86_64-linux-gnu/libpthread.so.0 Reading symbols from /opt/trinity/lib/libtdewalletclient.so.1...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdewalletclient.so.1 Reading symbols from /usr/lib/libr.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libr.so.0 Reading symbols from /lib/x86_64-linux-gnu/libacl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libacl.so.1 Reading symbols from /usr/lib/libmagic.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libmagic.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 Reading symbols from /usr/lib/libtqt.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libtqt.so.4 Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libm.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libidn.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libidn.so.11 Reading symbols from /usr/lib/x86_64-linux-gnu/libXcomposite.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libICE.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libICE.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libSM.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libSM.so.6 Reading symbols from /lib/x86_64-linux-gnu/libudev.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libudev.so.0 Reading symbols from /usr/lib/libart_lgpl_2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libart_lgpl_2.so.2 Reading symbols from /lib/x86_64-linux-gnu/libuuid.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libuuid.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libaudio.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libaudio.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libjpeg.so.8...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libjpeg.so.8 Reading symbols from /lib/x86_64-linux-gnu/libpng12.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libpng12.so.0 Reading symbols from /lib/x86_64-linux-gnu/libglib-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libglib-2.0.so.0 Reading symbols from /usr/lib/x86_64-linux-gnu/libXi.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXi.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libXrandr.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXrandr.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libXinerama.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXinerama.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXft.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXft.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libfreetype.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libXdmcp.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 Reading symbols from /lib/x86_64-linux-gnu/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/librt.so.1 Reading symbols from /usr/lib/libbfd-2.22-system.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbfd-2.22-system.so Reading symbols from /lib/x86_64-linux-gnu/libattr.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libattr.so.1 Reading symbols from /lib/x86_64-linux-gnu/libexpat.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libexpat.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXt.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXt.so.6 Reading symbols from /lib/x86_64-linux-gnu/libpcre.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libpcre.so.3 Reading symbols from /lib/x86_64-linux-gnu/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_compat.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnsl.so.1 Reading symbols from /lib/x86_64-linux-gnu/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_nis.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_files.so.2 Reading symbols from /opt/trinity/lib/trinity/plugins/styles/asteroid.so... (no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/trinity/plugins/styles/asteroid.so Reading symbols from /usr/lib/tqt3/plugins/imageformats/libqmng.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/tqt3/plugins/imageformats/libqmng.so Reading symbols from /usr/lib/x86_64-linux-gnu/libmng.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libmng.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/liblcms.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/liblcms.so.1 0x00007f5c6cca1feb in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb)
Not sure that this is overarchingly helpful . . .
Many thanks, as always.
On Sunday 11 of January 2015 17:44:08 dep wrote:
said Michele Calgaro: | On 01/03/2015 07:53 AM, dep wrote: | > said Gerhard Zintel: | On Friday 02 January 2015, dep wrote: | > said | > Michele Calgaro: | > | On 12/28/2014 08:15 AM, dep wrote: | > | > | > sorry to be such a bother, but as long as i'm bringing things up, | > | > | > | > here's one that has been an issue for a couple of years and | > | | > > | > > survived into R14. | > | > | > | > my desktop crashes, but in such a | > | > way as to not even be noticeable | > | > at first. | > | > | > | > i | > have in lieu of wallpaper xplanet set up as a realtime moon | > | > | > phase indicator, updating hourly. the way i tell the desktop has | > | | > | > > crashed is that it doesn't update -- in this case it last | > | > | > | > refreshed at 10:30 a.m. yesterday. i believe that i was probably | > | | > | > > editing pictures at that time, though would not swear to it. | > | > | > > | > | > | > after it crashes, a right click on the desktop does not | > | > produce | > | > the expected menu. as it happens, kicker and | > everything else | | > | > > | > continues to function as expected -- in fact, it was just now | > > | > that | > | > i noticed that the desktop itself | > | > had gone south. | > | > | > | > i thought i'd look in the x error log, | > bit i see that the one i | > | > have, ~/.xsession-errors, is of an | > unspecified file type and won't | > | > open in a text editor (it | > reports its size as 500.0 k). | > | > | > | > any idea if there's a | > log that might let me see what's going on | > | > here and if so what | > log it might be? bonus points, how i might | > | > restart the desktop | > without logging out and back in? extra bonus | > | > points, how i | > might fix it so it doesn't do this anymore? i'm | > | > running some | > flavor of ubuntu 12.04LTS -- i say some flavor | > | > because when i | > sought to upgrade a few days ago the ubuntu | > | > upgrader refused, | > citing third-party apps or a beta version of the | > | > opsys, or | > something; it didn't specify. i thought i had bog | > | > standard | > 12.04LTS on the machine but am apparently wrong. | > | | > | sorry for | > the late reply. | > | > The desktop behavior is controlled by the | > | kdesktop process. When
your desktop stops updating, from CLI type: | > | > | ps aux | grep desktop | > | and see if there is something like: | > | > | | > | username 8414 0.4 0.7 260192 | > | > 28956 pts/8 Sl 12:50 0:00 | > | kdesktop | > | > avahi 1973 | > 0.0 0.0 32308 1732 ? S 2014 0:01 | > avahi-daemon: | > running [dep-desktop.local] | > dep 3200 0.0 0.1 252184 17972 | > ? Sl 2014 | | > | > > 1:04 /opt/trinity/bin/kdesktop | > dep 11289 0.0 0.0 0 | > > 0 ? Z 2014 0:02 | > | > | > [kdesktop_lock] <defunct> | > dep 29758 0.0 0.0 9388 904 | > pts/0 S+ 16:12 0:00 grep | > desktop | | > | > > | > nevertheless, it hasn't updated since 10:19:53 AM 26 December. | > > | > and a | > rmb click on the desktop does not | > | > produce the expected menu. | > | > | If not, kdesktop has crashed. You | > can type: | > | kdesktop & from CLI to restart it (or alternatively | > Alt-F2 and then | > | kdesktop). | > | > dep@dep-desktop:~$ kdesktop | > is already running! | > | > | If this brings everything back in order, | > please let us know because | > | we need some more advanced testing to | > understand why and where | > | kdesktop crashed. | > | > fwiw, top | > reports 3 zombies. | | have you tried to kill the running kdesktop | > beforehand (not the | defuncts)? I assume it runns under process | > number 3200. Thus: | $ kill -9 3200 | | and than launch kdesktop | > again? | > | > this worked. i do not know if we learned anything from its having | > worked, but work it did. | > | > thanks! | | kdesktop_lock died and has not been reaped, so I suspect that kdesktop | may be waiting on some unreleased mutex, which would be the reason why | the background does not update any more and the RMB click doesn't do | anything. Something obviously went wrong. | The next time you see the error, can you try the following: | 1) ps aux | grep kdesktop -> this should give again kdesktop_lock | <defunct> 2) take note of the kdesktop pid (not the kdesktop_lock) | 3) from CLI (not within TDE, but from a tty), run: gdb --pid=<pid of | kdesktop> --> you may try from a TDE console, but you may loose the | keyboard. In such case you have to switch to a tty, kill the gdb | instance and retry from there. 4) type: thread apply all bt | Report what is printed out. This hopefully will provide some additional | info. If it is not critical for you, please do not exit gdb and do not | kill and restart kdesktop. Depending on what we find, we may have to run | some other commands. | | By the way, can you open a proper bug report on our bugszilla? It looks | like there is something to fix here :-)
I shall create an account there and do so; it hath happened again. The results from your instructions:
dep@dep-desktop:~$ ps aux | grep kdesktop dep 11451 0.0 0.0 0 0 ? Z Jan08 3:19 [kdesktop_lock] <defunct> dep 30334 0.0 0.1 252428 18252 ? Sl Jan02 4:55 kdesktop dep 30724 0.0 0.0 9384 908 pts/0 S+ 11:37 0:00 grep kdesktop dep@dep-desktop:~$ gdb --pid=30334 GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/. Attaching to process 30334 Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation not permitted. (gdb) thread apply all bt (gdb)
so tried again as root:
GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". For bug reporting instructions, please see: http://bugs.launchpad.net/gdb-linaro/. Attaching to process 30334 Reading symbols from /opt/trinity/bin/kdesktop...(no debugging symbols found)...done. Reading symbols from /opt/trinity/lib/libtdeinit_kdesktop.so...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeinit_kdesktop.so Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 Reading symbols from /opt/trinity/lib/libkonq.so.4...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libkonq.so.4 Reading symbols from /opt/trinity/lib/libtdeutils.so.1...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeutils.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXrender.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXrender.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libX11.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libX11.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libXcursor.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXcursor.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXext.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXext.so.6 Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libXss.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXss.so.1 Reading symbols from /usr/lib/libdbus-1-tqt.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdbus-1-tqt.so.0 Reading symbols from /usr/lib/x86_64-linux-gnu/libXau.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXau.so.6 Reading symbols from /opt/trinity/lib/libtdeio.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeio.so.14 Reading symbols from /opt/trinity/lib/libtdeui.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeui.so.14 Reading symbols from /opt/trinity/lib/libtdesu.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdesu.so.14 Reading symbols from /opt/trinity/lib/libtdecore.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdecore.so.14 Reading symbols from /opt/trinity/lib/libDCOP.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libDCOP.so.14 Reading symbols from /opt/trinity/lib/libtdefx.so.14...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdefx.so.14 Reading symbols from /usr/lib/libtqt-mt.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libtqt-mt.so.3 Reading symbols from /usr/lib/x86_64-linux-gnu/libstdc++.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libgcc_s.so.1 Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /opt/trinity/lib/libtdeparts.so.2...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdeparts.so.2 Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libz.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libxcb.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libxcb.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXfixes.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXfixes.so.3 Reading symbols from /lib/x86_64-linux-gnu/libdbus-1.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libdbus-1.so.3 Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7f5c62de7700 (LWP 30339)] Loaded symbols for /lib/x86_64-linux-gnu/libpthread.so.0 Reading symbols from /opt/trinity/lib/libtdewalletclient.so.1...(no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/libtdewalletclient.so.1 Reading symbols from /usr/lib/libr.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libr.so.0 Reading symbols from /lib/x86_64-linux-gnu/libacl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libacl.so.1 Reading symbols from /usr/lib/libmagic.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libmagic.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libfontconfig.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 Reading symbols from /usr/lib/libtqt.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libtqt.so.4 Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libm.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libidn.so.11...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libidn.so.11 Reading symbols from /usr/lib/x86_64-linux-gnu/libXcomposite.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libICE.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libICE.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libSM.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libSM.so.6 Reading symbols from /lib/x86_64-linux-gnu/libudev.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libudev.so.0 Reading symbols from /usr/lib/libart_lgpl_2.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libart_lgpl_2.so.2 Reading symbols from /lib/x86_64-linux-gnu/libuuid.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libuuid.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libaudio.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libaudio.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libjpeg.so.8...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libjpeg.so.8 Reading symbols from /lib/x86_64-linux-gnu/libpng12.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libpng12.so.0 Reading symbols from /lib/x86_64-linux-gnu/libglib-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libglib-2.0.so.0 Reading symbols from /usr/lib/x86_64-linux-gnu/libXi.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXi.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libXrandr.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXrandr.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libXinerama.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXinerama.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXft.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXft.so.2 Reading symbols from /usr/lib/x86_64-linux-gnu/libfreetype.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Reading symbols from /usr/lib/x86_64-linux-gnu/libXdmcp.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 Reading symbols from /lib/x86_64-linux-gnu/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/librt.so.1 Reading symbols from /usr/lib/libbfd-2.22-system.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbfd-2.22-system.so Reading symbols from /lib/x86_64-linux-gnu/libattr.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libattr.so.1 Reading symbols from /lib/x86_64-linux-gnu/libexpat.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libexpat.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/libXt.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libXt.so.6 Reading symbols from /lib/x86_64-linux-gnu/libpcre.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libpcre.so.3 Reading symbols from /lib/x86_64-linux-gnu/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_compat.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnsl.so.1 Reading symbols from /lib/x86_64-linux-gnu/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_nis.so.2 Reading symbols from /lib/x86_64-linux-gnu/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libnss_files.so.2 Reading symbols from /opt/trinity/lib/trinity/plugins/styles/asteroid.so... (no debugging symbols found)...done. Loaded symbols for /opt/trinity/lib/trinity/plugins/styles/asteroid.so Reading symbols from /usr/lib/tqt3/plugins/imageformats/libqmng.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/tqt3/plugins/imageformats/libqmng.so Reading symbols from /usr/lib/x86_64-linux-gnu/libmng.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/libmng.so.1 Reading symbols from /usr/lib/x86_64-linux-gnu/liblcms.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/x86_64-linux-gnu/liblcms.so.1 0x00007f5c6cca1feb in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb)
Not sure that this is overarchingly helpful . . .
Many thanks, as always.
On the second try - as root - you did not enter in gdb command: thread apply all bt
Listing is unfortunately not useful.
said Slávek Banko: | On Sunday 11 of January 2015 17:44:08 dep wrote: | > said Michele Calgaro: | > | On 01/03/2015 07:53 AM, dep wrote: | > | > said Gerhard Zintel: | On Friday 02 January 2015, dep wrote: | > | > | > said Michele Calgaro: | > | On 12/28/2014 08:15 AM, dep wrote: | > | > | > | > sorry to be such a bother, but as long as i'm bringing things | > | > up, | > | > | > | > | > | > here's one that has been an issue for a couple of years and | | > | > | > > | | > | > > | > | > > survived into R14. | > | > | > | > my desktop crashes, but in | > | > > such a | > | > | > | > way as to not even be noticeable | > | > at first. | > | > | > | > | > | > i have in lieu of wallpaper xplanet set up as a realtime moon | > | > | > | > phase indicator, updating hourly. the way i tell the desktop | > | > has | > | | > | > | > | > > crashed is that it doesn't update -- in this case it last | > | | > | > > > | > | > | > | > refreshed at 10:30 a.m. yesterday. i believe that i was probably | | > | > > | | > | > | > | > > editing pictures at that time, though would not swear to it. | > | > | > > | > | > | > > | > | > | > | > after it crashes, a right click on the desktop does not | > | > | > | > produce | > | > the expected menu. as it happens, kicker and | > | > everything else | | > | > | > | > > | > continues to function as expected -- in fact, it was just | > | > > | > now that | > | > i noticed that the desktop itself | > | > | > | > had gone south. | > | > | > | > i thought i'd look in the x error | > | > log, bit i see that the one i | > | > have, ~/.xsession-errors, is | > | > of an unspecified file type and won't | > | > open in a text | > | > editor (it reports its size as 500.0 k). | > | > | > | > any idea | > | > if there's a log that might let me see what's going on | > | > | > | > here and if so what log it might be? bonus points, how i might | > | > | > | > restart the desktop without logging out and back in? extra | > | > bonus | > | > points, how i might fix it so it doesn't do this | > | > anymore? i'm | > | > running some flavor of ubuntu 12.04LTS -- i | > | > say some flavor | > | > because when i sought to upgrade a few | > | > days ago the ubuntu | > | > upgrader refused, citing third-party | > | > apps or a beta version of the | > | > opsys, or something; it | > | > didn't specify. i thought i had bog | > | > standard 12.04LTS on | > | > the machine but am apparently wrong. | > | | > | sorry for the | > | > late reply. | > | > | > | > The desktop behavior is controlled by the | > | kdesktop process. | > | > When | > | > your desktop stops updating, from CLI type: | > | > | > | ps aux | grep desktop | > | and see if there is something like: | > | > | > | | > | username 8414 0.4 0.7 260192 | > | > | > | > 28956 pts/8 Sl 12:50 0:00 | > | kdesktop | > | > avahi | > | > 1973 0.0 0.0 32308 1732 ? S 2014 0:01 | > | > | > avahi-daemon: running [dep-desktop.local] | > dep 3200 0.0 | > | > 0.1 252184 17972 ? Sl 2014 | | > | > | > | > > 1:04 /opt/trinity/bin/kdesktop | > dep 11289 0.0 0.0 | > | > > 0 0 ? Z 2014 0:02 | > | > | > | > | > [kdesktop_lock] <defunct> | > dep 29758 0.0 0.0 9388 | > | > 904 pts/0 S+ 16:12 0:00 grep | > desktop | | > | > | > | > > | > nevertheless, it hasn't updated since 10:19:53 AM 26 | > | > > | > December. and a | > rmb click on the desktop does not | > | > | > | > produce the expected menu. | > | > | If not, kdesktop has crashed. | > | > You can type: | > | kdesktop & from CLI to restart it (or | > | > alternatively Alt-F2 and then | > | kdesktop). | > | > | > | > dep@dep-desktop:~$ kdesktop is already running! | > | > | If this | > | > brings everything back in order, please let us know because | > | | > | > we need some more advanced testing to understand why and where | > | > | > | kdesktop crashed. | > | > fwiw, top reports 3 zombies. | | have | > | > you tried to kill the running kdesktop beforehand (not the | | > | > defuncts)? I assume it runns under process number 3200. Thus: | $ | > | > kill -9 3200 | | and than launch kdesktop again? | > | > | > | > this worked. i do not know if we learned anything from its having | > | > worked, but work it did. | > | > | > | > thanks! | > | | > | kdesktop_lock died and has not been reaped, so I suspect that | > | kdesktop may be waiting on some unreleased mutex, which would be the | > | reason why the background does not update any more and the RMB click | > | doesn't do anything. Something obviously went wrong. | > | The next time you see the error, can you try the following: | > | 1) ps aux | grep kdesktop -> this should give again kdesktop_lock | > | <defunct> 2) take note of the kdesktop pid (not the kdesktop_lock) | > | 3) from CLI (not within TDE, but from a tty), run: gdb --pid=<pid of | > | kdesktop> --> you may try from a TDE console, but you may loose the | > | keyboard. In such case you have to switch to a tty, kill the gdb | > | instance and retry from there. 4) type: thread apply all bt | > | Report what is printed out. This hopefully will provide some | > | additional info. If it is not critical for you, please do not exit | > | gdb and do not kill and restart kdesktop. Depending on what we find, | > | we may have to run some other commands. | > | | > | By the way, can you open a proper bug report on our bugszilla? It | > | looks like there is something to fix here :-) | > | > I shall create an account there and do so; it hath happened again. The | > results from your instructions: | > | > dep@dep-desktop:~$ ps aux | grep kdesktop | > dep 11451 0.0 0.0 0 0 ? Z Jan08 3:19 | > [kdesktop_lock] <defunct> | > dep 30334 0.0 0.1 252428 18252 ? Sl Jan02 4:55 | > kdesktop dep 30724 0.0 0.0 9384 908 pts/0 S+ 11:37 | > 0:00 grep kdesktop | > dep@dep-desktop:~$ gdb --pid=30334 | > GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 | > Copyright (C) 2012 Free Software Foundation, Inc. | > License GPLv3+: GNU GPL version 3 or later | > http://gnu.org/licenses/gpl.html | > This is free software: you are free to change and redistribute it. | > There is NO WARRANTY, to the extent permitted by law. Type "show | > copying" and "show warranty" for details. | > This GDB was configured as "x86_64-linux-gnu". | > For bug reporting instructions, please see: | > http://bugs.launchpad.net/gdb-linaro/. | > Attaching to process 30334 | > Could not attach to process. If your uid matches the uid of the | > target process, check the setting of | > /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. | > For more details, see /etc/sysctl.d/10-ptrace.conf ptrace: Operation | > not permitted. | > (gdb) thread apply all bt | > (gdb) | > | > so tried again as root: | > | > GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 | > Copyright (C) 2012 Free Software Foundation, Inc. | > License GPLv3+: GNU GPL version 3 or later | > http://gnu.org/licenses/gpl.html | > This is free software: you are free to change and redistribute it. | > There is NO WARRANTY, to the extent permitted by law. Type "show | > copying" and "show warranty" for details. | > This GDB was configured as "x86_64-linux-gnu". | > For bug reporting instructions, please see: | > http://bugs.launchpad.net/gdb-linaro/. | > Attaching to process 30334 | > Reading symbols from /opt/trinity/bin/kdesktop...(no debugging symbols | > found)...done. | > Reading symbols from /opt/trinity/lib/libtdeinit_kdesktop.so...(no | > debugging symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdeinit_kdesktop.so | > Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...(no debugging | > symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libc.so.6 | > Reading symbols from /opt/trinity/lib/libkonq.so.4...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libkonq.so.4 | > Reading symbols from /opt/trinity/lib/libtdeutils.so.1...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdeutils.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXrender.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXrender.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libX11.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libX11.so.6 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXcursor.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXcursor.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXext.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXext.so.6 | > Reading symbols from /lib/x86_64-linux-gnu/libdl.so.2...(no debugging | > symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libdl.so.2 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXss.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXss.so.1 | > Reading symbols from /usr/lib/libdbus-1-tqt.so.0...(no debugging | > symbols found)...done. | > Loaded symbols for /usr/lib/libdbus-1-tqt.so.0 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXau.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXau.so.6 | > Reading symbols from /opt/trinity/lib/libtdeio.so.14...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdeio.so.14 | > Reading symbols from /opt/trinity/lib/libtdeui.so.14...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdeui.so.14 | > Reading symbols from /opt/trinity/lib/libtdesu.so.14...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdesu.so.14 | > Reading symbols from /opt/trinity/lib/libtdecore.so.14...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdecore.so.14 | > Reading symbols from /opt/trinity/lib/libDCOP.so.14...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libDCOP.so.14 | > Reading symbols from /opt/trinity/lib/libtdefx.so.14...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdefx.so.14 | > Reading symbols from /usr/lib/libtqt-mt.so.3...(no debugging symbols | > found)...done. | > Loaded symbols for /usr/lib/libtqt-mt.so.3 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libstdc++.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libstdc++.so.6 | > Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libgcc_s.so.1 | > Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging | > symbols found)...done. | > Loaded symbols for /lib64/ld-linux-x86-64.so.2 | > Reading symbols from /opt/trinity/lib/libtdeparts.so.2...(no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdeparts.so.2 | > Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...(no debugging | > symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libz.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libxcb.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libxcb.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXfixes.so.3...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXfixes.so.3 | > Reading symbols from /lib/x86_64-linux-gnu/libdbus-1.so.3...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libdbus-1.so.3 | > Reading symbols from /lib/x86_64-linux-gnu/libpthread.so.0...(no | > debugging symbols found)...done. | > [Thread debugging using libthread_db enabled] | > Using host libthread_db library | > "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7f5c62de7700 | > (LWP 30339)] | > Loaded symbols for /lib/x86_64-linux-gnu/libpthread.so.0 | > Reading symbols from /opt/trinity/lib/libtdewalletclient.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /opt/trinity/lib/libtdewalletclient.so.1 | > Reading symbols from /usr/lib/libr.so.0...(no debugging symbols | > found)...done. | > Loaded symbols for /usr/lib/libr.so.0 | > Reading symbols from /lib/x86_64-linux-gnu/libacl.so.1...(no debugging | > symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libacl.so.1 | > Reading symbols from /usr/lib/libmagic.so.1...(no debugging symbols | > found)...done. | > Loaded symbols for /usr/lib/libmagic.so.1 | > Reading symbols from | > /usr/lib/x86_64-linux-gnu/libfontconfig.so.1...(no debugging symbols | > found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 | > Reading symbols from /usr/lib/libtqt.so.4...(no debugging symbols | > found)...done. | > Loaded symbols for /usr/lib/libtqt.so.4 | > Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...(no debugging | > symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libm.so.6 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libidn.so.11...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libidn.so.11 | > Reading symbols from | > /usr/lib/x86_64-linux-gnu/libXcomposite.so.1...(no debugging symbols | > found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libICE.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libICE.so.6 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libSM.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libSM.so.6 | > Reading symbols from /lib/x86_64-linux-gnu/libudev.so.0...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libudev.so.0 | > Reading symbols from /usr/lib/libart_lgpl_2.so.2...(no debugging | > symbols found)...done. | > Loaded symbols for /usr/lib/libart_lgpl_2.so.2 | > Reading symbols from /lib/x86_64-linux-gnu/libuuid.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libuuid.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libaudio.so.2...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libaudio.so.2 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libjpeg.so.8...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libjpeg.so.8 | > Reading symbols from /lib/x86_64-linux-gnu/libpng12.so.0...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libpng12.so.0 | > Reading symbols from /lib/x86_64-linux-gnu/libglib-2.0.so.0...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libglib-2.0.so.0 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXi.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXi.so.6 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXrandr.so.2...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXrandr.so.2 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXinerama.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXinerama.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXft.so.2...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXft.so.2 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libfreetype.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libfreetype.so.6 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXdmcp.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 | > Reading symbols from /lib/x86_64-linux-gnu/librt.so.1...(no debugging | > symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/librt.so.1 | > Reading symbols from /usr/lib/libbfd-2.22-system.so...(no debugging | > symbols found)...done. | > Loaded symbols for /usr/lib/libbfd-2.22-system.so | > Reading symbols from /lib/x86_64-linux-gnu/libattr.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libattr.so.1 | > Reading symbols from /lib/x86_64-linux-gnu/libexpat.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libexpat.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/libXt.so.6...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libXt.so.6 | > Reading symbols from /lib/x86_64-linux-gnu/libpcre.so.3...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libpcre.so.3 | > Reading symbols from /lib/x86_64-linux-gnu/libnss_compat.so.2...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libnss_compat.so.2 | > Reading symbols from /lib/x86_64-linux-gnu/libnsl.so.1...(no debugging | > symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libnsl.so.1 | > Reading symbols from /lib/x86_64-linux-gnu/libnss_nis.so.2...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libnss_nis.so.2 | > Reading symbols from /lib/x86_64-linux-gnu/libnss_files.so.2...(no | > debugging symbols found)...done. | > Loaded symbols for /lib/x86_64-linux-gnu/libnss_files.so.2 | > Reading symbols from | > /opt/trinity/lib/trinity/plugins/styles/asteroid.so... (no debugging | > symbols found)...done. | > Loaded symbols for /opt/trinity/lib/trinity/plugins/styles/asteroid.so | > Reading symbols from | > /usr/lib/tqt3/plugins/imageformats/libqmng.so...(no debugging symbols | > found)...done. | > Loaded symbols for /usr/lib/tqt3/plugins/imageformats/libqmng.so | > Reading symbols from /usr/lib/x86_64-linux-gnu/libmng.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/libmng.so.1 | > Reading symbols from /usr/lib/x86_64-linux-gnu/liblcms.so.1...(no | > debugging symbols found)...done. | > Loaded symbols for /usr/lib/x86_64-linux-gnu/liblcms.so.1 | > 0x00007f5c6cca1feb in ?? () from /lib/x86_64-linux-gnu/libc.so.6 | > (gdb) | > | > Not sure that this is overarchingly helpful . . . | > | > Many thanks, as always. | | On the second try - as root - you did not enter in gdb command: | thread apply all bt | | Listing is unfortunately not useful.
alas -- i am an idiot. here goes:
(gdb) thread apply all bt
Thread 2 (Thread 0x7f5c62de7700 (LWP 30339)): #0 0x00007f5c6801689c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007f5c68012065 in _L_lock_858 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x00007f5c68011eba in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x00007f5c6971f4ff in ?? () from /usr/lib/libtqt-mt.so.3 #4 0x00007f5c69493655 in TQEventLoop::hasPendingEvents() const () from /usr/lib/libtqt-mt.so.3 #5 0x00007f5c694931d5 in TQEventLoop::gsourceCheck(_GSource*) () from /usr/lib/libtqt-mt.so.3 #6 0x00007f5c69493243 in ?? () from /usr/lib/libtqt-mt.so.3 #7 0x00007f5c65897b03 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x00007f5c65897f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x00007f5c65898124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x00007f5c69492b68 in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3 #11 0x00007f5c694c2319 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3 ---Type <return> to continue, or q <return> to quit--- #12 0x00007f5c694c22a9 in TQEventLoop::exec() () from /usr/lib/libtqt-mt.so.3 #13 0x00007f5c694a970d in ?? () from /usr/lib/libtqt-mt.so.3 #14 0x00007f5c658b99b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x00007f5c6800fe9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #16 0x00007f5c6cc942ed in clone () from /lib/x86_64-linux-gnu/libc.so.6 #17 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7f5c6d413780 (LWP 30334)): #0 0x00007f5c6cca1feb in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007f5c6cc24f61 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007f5c6cc22c87 in malloc () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007f5c68fddded in operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x00007f5c6972fdde in TQGArray::newData() () from /usr/lib/libtqt-mt.so.3 #5 0x00007f5c6972fec7 in TQGArray::TQGArray() () from /usr/lib/libtqt-mt.so.3 #6 0x00007f5c69725809 in TQCString::TQCString(char const*) () from /usr/lib/libtqt-mt.so.3 #7 0x00007f5c69515ccc in TQSignal::connect(TQObject const*, char const*) () from /usr/lib/libtqt-mt.so.3 #8 0x00007f5c695218f4 in ?? () from /usr/lib/libtqt-mt.so.3 #9 0x00007f5c6cfbeccc in ?? () from /opt/trinity/lib/libtdeinit_kdesktop.so #10 0x00007f5c6cfbcd93 in ?? () from /opt/trinity/lib/libtdeinit_kdesktop.so #11 <signal handler called> #12 0x00007f5c6cc2406a in calloc () from /lib/x86_64-linux-gnu/libc.so.6 #13 0x00007f5c6a1586ee in NETWinInfo::NETWinInfo(_XDisplay*, unsigned long, unsigned long, unsigned long, NET::Role) () from /opt/trinity/lib/libtdecore.so.14 #14 0x00007f5c6a1b4922 in ?? () from /opt/trinity/lib/libtdecore.so.14 #15 0x00007f5c6a138ff0 in TDEApplication::x11EventFilter(_XEvent*) () from /opt/trinity/lib/libtdecore.so.14 #16 0x00007f5c6cfe5039 in ?? () from /opt/trinity/lib/libtdeinit_kdesktop.so #17 0x00007f5c6945b6f6 in TQApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libtqt-mt.so.3 #18 0x00007f5c69492d12 in TQEventLoop::processX11Events() () from /usr/lib/libtqt-mt.so.3 #19 0x00007f5c694934f6 in TQEventLoop::gsourceDispatch(_GSource*) () from /usr/lib/libtqt-mt.so.3 #20 0x00007f5c69493623 in ?? () from /usr/lib/libtqt-mt.so.3 #21 0x00007f5c65897d13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #22 0x00007f5c65898060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #23 0x00007f5c65898124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x00007f5c69492b68 in TQEventLoop::processEvents(unsigned int) () from /usr/lib/libtqt-mt.so.3 #25 0x00007f5c694c2319 in TQEventLoop::enterLoop() () from /usr/lib/libtqt-mt.so.3 #26 0x00007f5c694c22a9 in TQEventLoop::exec() () from /usr/lib/libtqt-mt.so.3 #27 0x00007f5c6cf973ec in kdemain () from /opt/trinity/lib/libtdeinit_kdesktop.so #28 0x00000000004007a4 in _start () (gdb)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
<snip>
| > | kdesktop_lock died and has not been reaped, so I suspect that | > | kdesktop may be waiting on some unreleased mutex, which would be the | > | reason why the background does not update any more and the RMB click | > | doesn't do anything. Something obviously went wrong. | > | The next time you see the error, can you try the following: | > | 1) ps aux | grep kdesktop -> this should give again kdesktop_lock | > | <defunct> 2) take note of the kdesktop pid (not the kdesktop_lock) | > | 3) from CLI (not within TDE, but from a tty), run: gdb --pid=<pid of | > | kdesktop> --> you may try from a TDE console, but you may loose the | > | keyboard. In such case you have to switch to a tty, kill the gdb | > | instance and retry from there. 4) type: thread apply all bt | > | Report what is printed out. This hopefully will provide some | > | additional info. If it is not critical for you, please do not exit | > | gdb and do not kill and restart kdesktop. Depending on what we find, | > | we may have to run some other commands. | > | | > | By the way, can you open a proper bug report on our bugszilla? It | > | looks like there is something to fix here :-) | > | > I shall create an account there and do so; it hath happened again. The |
results from your instructions: | >
<gdb output snip>
I have created bug 2311 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=2311) to serve as a info collection point for this problem. dep, if you do not have a bugszilla account, you can report info to the mailing list and later I will update the bug, although it would be better if you could report there :-)
Going back to the problem, as suspected kdesktop seems locked waiting on a mutex, which is probably related to the defunct kdesktop_lock process somehow. Can you try the following commands from gdb and report back?
1) info thread just for the sake of info
2) thread 2 Expect something like "switching to thread 2 blah blah blah"
frame 2 Expect something like "#2 hex-adress in pthread_mutex_lock()"
info reg This will print the registers' contents.
After this I will have more questions, but first I need the answers above. Again, please do not exit from gdb unless it is critical for you (for example you have to switch off your computer). If you have to exit and restart kdesktop, the next time you need to repeat the commands already typed + the new ones.
Cheers Michele
said Michele Calgaro:
| I have created bug 2311 | (http://bugs.pearsoncomputing.net/show_bug.cgi?id=2311) to serve as a | info collection point for this problem. | dep, if you do not have a bugszilla account, you can report info to the | mailing list and later I will update the bug, although it would be | better if you could report there :-) | | Going back to the problem, as suspected kdesktop seems locked waiting on | a mutex, which is probably related to the defunct kdesktop_lock process | somehow. Can you try the following commands from gdb and report back? | | 1) info thread | just for the sake of info
(gdb) info thread Id Target Id Frame 2 Thread 0x7f5c62de7700 (LWP 30339) "kdesktop" 0x00007f5c6801689c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0 * 1 Thread 0x7f5c6d413780 (LWP 30334) "kdesktop" 0x00007f5c6cca1feb in ?? () from /lib/x86_64-linux-gnu/libc.so.6
| 2) thread 2 | Expect something like "switching to thread 2 blah blah blah"
(gdb) thread 2 [Switching to thread 2 (Thread 0x7f5c62de7700 (LWP 30339))] #0 0x00007f5c6801689c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0
| frame 2 | Expect something like "#2 hex-adress in pthread_mutex_lock()"
(gdb) frame 2 #2 0x00007f5c68011eba in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0
| info reg | This will print the registers' contents.
(gdb) info reg rax 0xfffffffffffffe00 -512 rbx 0xda51f0 14307824 rcx 0xffffffffffffffff -1 rdx 0xda5230 14307888 rsi 0x80 128 rdi 0xda51f8 14307832 rbp 0xda5230 0xda5230 rsp 0x7f5c62de6c40 0x7f5c62de6c40 r8 0xda51f8 14307832 r9 0x7683 30339 r10 0x7f5c62de6a40 140034772462144 r11 0x202 514 r12 0x7f5c62de7700 140034772465408 r13 0x2 2 r14 0x7f5c69493200 140034880123392 r15 0x1 1 rip 0x7f5c68011eba 0x7f5c68011eba <pthread_mutex_lock+58> eflags 0x202 [ IF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0
| After this I will have more questions, but first I need the answers | above. Again, please do not exit from gdb unless it is critical for you | (for example you have to switch off your computer). If you have to exit | and restart kdesktop, the next time you need to repeat the commands | already typed + the new ones.
many thanks. i should note that the above began from gdb --pid=30334 without the additional command(s) done yesterday. should i go back and redo it? forgive me, but this is several levels beyond my understanding!
i now have gdb running in a console after the above commands, and shall leave it running per your explanation.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
<snip>
(gdb) info thread Id Target Id Frame 2 Thread 0x7f5c62de7700 (LWP 30339) "kdesktop" 0x00007f5c6801689c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0
- 1 Thread 0x7f5c6d413780 (LWP 30334) "kdesktop" 0x00007f5c6cca1feb
in ?? () from /lib/x86_64-linux-gnu/libc.so.6
| 2) thread 2 | Expect something like "switching to thread 2 blah blah blah"
(gdb) thread 2 [Switching to thread 2 (Thread 0x7f5c62de7700 (LWP 30339))] #0 0x00007f5c6801689c in __lll_lock_wait () from /lib/x86_64-linux-gnu/libpthread.so.0
| frame 2 | Expect something like "#2 hex-adress in pthread_mutex_lock()"
(gdb) frame 2 #2 0x00007f5c68011eba in pthread_mutex_lock () from /lib/x86_64-linux-gnu/libpthread.so.0
| info reg | This will print the registers' contents.
(gdb) info reg
<snip>
rsp 0x7f5c62de6c40 0x7f5c62de6c40 r8 0xda51f8 14307832 r9 0x7683 30339
<snip>
many thanks. i should note that the above began from gdb --pid=30334 without the additional command(s) done yesterday. should i go back and redo it? forgive me, but this is several levels beyond my understanding!
Thanks for the info, no need to rerun the previous commands since the thread IDs are the same. Register r8 should contain the address of the locked mutex. Please try this in the open gdb console.
(gdb) p *(pthread_mutex_t*)0xda51f8 Expect something like:
__data = { __lock = xxx, __count = yyy, __owner = thread_ID, ....
This should give the id of the thread which has locked the mutex. Please report back, then we take the next step. If gdb complains about pthread_mutex_t, please try this: print *((int*)(0xda51f8)+2)
Cheers Michele
said Michele Calgaro:
| Thanks for the info, no need to rerun the previous commands since the | thread IDs are the same. Register r8 should contain the address of the | locked mutex. Please try this in the open gdb console. | | (gdb) p *(pthread_mutex_t*)0xda51f8 | Expect something like: | | __data = { | __lock = xxx, | __count = yyy, | __owner = thread_ID, | .... | | This should give the id of the thread which has locked the mutex. Please | report back, then we take the next step. | If gdb complains about pthread_mutex_t, please try this: | print *((int*)(0xda51f8)+2)
(gdb) p *(pthread_mutex_t*)0xda51f8 No symbol table is loaded. Use the "file" command. (gdb) print *((int*)(0xda51f8)+2) $1 = 30334 (gdb)
that's all i got.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/01/13 12:00 PM, dep wrote:
(gdb) print *((int*)(0xda51f8)+2) $1 = 30334
That's good. It means the mutex is locked by thread 1 (LWP 30334).
I actually noticed just now (my fault) that you do not have the debug symbols installed for tdelibs, tdebase and tqt3. Can you install them, exit gdb, reattach to the kdesktop process and run again the thread apply all bt command? That should provide more detailed information (i.e. line numbers) about where each thread and frame is. - From a quick look at the current incomplete stack frame, thread 1 (which is blocking thread 2) is blocked inside a malloc() call, which as far as I can tell is usually a sign that the heap is corrupted (perhaps a pointer deallocated twice). Now we are kind of stretching to the limit of my knowledge as well, so I will need to guess/look up what's the best way to go.
By the way, when kdesktop_lock crashes do you have any crash report window popping up in your system?
In the mean time, can you try the following things:
1) install the debug symbols as said above and provide the updated stack frames
2) kill kdesktop and run it again (or reboot your system, even better). From CLI (outside TDE), run: ps aux |grep kdesktop Take note of the kdesktop_lock pid. Run: gdb --pid=<kdesktop_lock pid> After gdb attaches to the process, continue execution with: c At this stage kdesktop_lock should be running normally. Leave everything running until kdesktop_lock crashes again. At this point gdb should provide some info about the crash (perhaps a segmentation fault - SIGSEGV). When it happens you should be able to get the stack frame for kdesktop_lock (again thread apply all bt) since gdb is still attached to the process. Do not exit gdb after that, not sure what else we may need. All this is somehow experimental, if something doesn't go to plan, please let me know.
Cheers Michele
said Michele Calgaro: | On 2015/01/13 12:00 PM, dep wrote: | > (gdb) print *((int*)(0xda51f8)+2) $1 = 30334 | | That's good. It means the mutex is locked by thread 1 (LWP 30334). | | I actually noticed just now (my fault) that you do not have the debug | symbols installed for tdelibs, tdebase and tqt3. Can you install them, | exit gdb, reattach to the kdesktop process and run again the | thread apply all bt command?
(gdb) thread 2 [Switching to thread 2 (Thread 0x7f5c62de7700 (LWP 30339))] #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:132 132 ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S: No such file or directory. (gdb) frame 2 #2 0x00007f5c68011eba in __pthread_mutex_lock (mutex=0xda51f8) at pthread_mutex_lock.c:61 61 pthread_mutex_lock.c: No such file or directory. (gdb) p *(pthread_mutex_t*)0xda51f8 $1 = {__data = {__lock = 2, __count = 0, __owner = 30334, __nusers = 1, __kind = 0, __spins = 0, __list = {__prev = 0x0, __next = 0x0}}, __size = "\002\000\000\000\000\000\000\000~v\000\000\001", '\000' <repeats 26 times>, __align = 2} (gdb) thread apply all bt
Thread 2 (Thread 0x7f5c62de7700 (LWP 30339)): #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:132 #1 0x00007f5c68012065 in _L_lock_858 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x00007f5c68011eba in __pthread_mutex_lock (mutex=0xda51f8) at pthread_mutex_lock.c:61 #3 0x00007f5c6971f4ff in TQRecursiveMutexPrivate::lock (this=0xda51f0) at tools/qmutex_unix.cpp:251 #4 0x00007f5c69493655 in TQMutexLocker (m=0xd99660, this=<synthetic pointer>) at ../include/ntqmutex.h:102 #5 TQEventLoop::hasPendingEvents (this=<optimized out>) at kernel/qeventloop_x11_glib.cpp:633 #6 0x00007f5c694931d5 in TQEventLoop::gsourceCheck (this=0x7f5c5c001340, gs=<optimized out>) at kernel/qeventloop_x11_glib.cpp:507 #7 0x00007f5c69493243 in qt_gsource_check (source=0x7f5c5c002200) at kernel/qeventloop_x11_glib.cpp:105 #8 0x00007f5c65897b03 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x00007f5c65897f96 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x00007f5c65898124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007f5c69492b68 in TQEventLoop::processEvents (this=0x7f5c5c001340, flags=<optimized out>) at kernel/qeventloop_x11_glib.cpp:279 #12 0x00007f5c694c2319 in TQEventLoop::enterLoop (this=0x7f5c5c001340) at kernel/qeventloop.cpp:227 #13 0x00007f5c694c22a9 in TQEventLoop::exec (this=0x7f5c5c001340) at kernel/qeventloop.cpp:174 #14 0x00007f5c694a970d in TQThreadInstance::start (_arg=0xf4c5b8) at kernel/qthread_unix.cpp:142 #15 0x00007f5c658b99b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x00007f5c6800fe9a in start_thread (arg=0x7f5c62de7700) at pthread_create.c:308 #17 0x00007f5c6cc942ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #18 0x0000000000000000 in ?? ()
Thread 1 (Thread 0x7f5c6d413780 (LWP 30334)): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:93 #1 0x00007f5c6cc24f61 in _L_lock_10611 () at malloc.c:5249 #2 0x00007f5c6cc22c87 in __GI___libc_malloc (bytes=140034941749024) at malloc.c:2921 #3 0x00007f5c68fddded in operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ---Type <return> to continue, or q <return> to quit--- #4 0x00007f5c6972fdde in TQGArray::newData (this=<optimized out>) at tools/qgarray.cpp:819 #5 0x00007f5c6972fec7 in TQGArray::TQGArray (this=0x7fff3e582860) at tools/qgarray.cpp:118 #6 0x00007f5c69725809 in TQMemArray (this=0x7fff3e582860) at tools/ntqmemarray.h:61 #7 TQCString::TQCString (this=0x7fff3e582860, str=0x7f5c6d006c82 "1lockProcessWaiting()") at tools/qcstring.cpp:700 #8 0x00007f5c69515ccc in intSignature ( member=0x7f5c6d006c82 "1lockProcessWaiting()") at kernel/qsignal.cpp:134 #9 TQSignal::connect (this=0xdb3d70, receiver=0x7fff3e583670, member=0x7f5c6d006c82 "1lockProcessWaiting()") at kernel/qsignal.cpp:148 #10 0x00007f5c695218f4 in TQSingleShotTimer::start (this=0xdb3d20, msec=0, r=<optimized out>, m=<optimized out>) at kernel/qtimer.cpp:281 #11 0x00007f5c6cfbeccc in SaverEngine::slotLockProcessWaiting ( this=0x7fff3e583670) at /build/buildd/tdebase-trinity-14.0.0-r1865/kdesktop/lockeng.cc:548 #12 0x00007f5c6cfbcd93 in sigusr1_handler () at /build/buildd/tdebase-trinity-14.0.0-r1865/kdesktop/lockeng.cc:52 #13 <signal handler called> #14 0x00007f5c6cc2406a in __libc_calloc (n=2, elem_size=<optimized out>) at malloc.c:3291 #15 0x00007f5c6a1586ee in NETRArray (this=0xf402e0) at /build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/netwm.cpp:558 #16 NETWinInfoPrivate (this=0xf402c0) at /build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/netwm_p.h:122 #17 NETWinInfo::NETWinInfo (this=0x7fff3e582f60, display=0xd520d0, window=27263003, rootWindow=674, properties=0, role=<optimized out>) at /build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/netwm.cpp:2902 #18 0x00007f5c6a1b4922 in KWinModulePrivate::x11Event (this=0xdc5a80, ev=0x7fff3e583330)
at /build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/twinmodule.cpp:247 #19 0x00007f5c6a138ff0 in publicx11Event (e=0x7fff3e583330, this=<optimized out>)
at /build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/tdeapplication.cpp:1911 #20 TDEApplication::x11EventFilter (this=0xd50630, _event=0x7fff3e583330)
at /build/buildd/tdelibs-trinity-14.0.0-r1231/tdecore/tdeapplication.cpp:2189 #21 0x00007f5c6cfe5039 in KDesktopApp::x11EventFilter (this=0xd50630, xevent=0x7fff3e583330)
at /build/buildd/tdebase-trinity-14.0.0-r1865/kdesktop/kdesktopapp.cpp:90 #22 0x00007f5c6945b6f6 in TQApplication::x11ProcessEvent (this=0xd50630, event=0x7fff3e583330) at kernel/qapplication_x11.cpp:3435 #23 0x00007f5c69492d12 in TQEventLoop::processX11Events (this=0xda4be0) at kernel/qeventloop_x11_glib.cpp:353 #24 0x00007f5c694934f6 in TQEventLoop::gsourceDispatch (this=0xda4be0, gs=<optimized out>) at kernel/qeventloop_x11_glib.cpp:614 #25 0x00007f5c69493623 in qt_gsource_dispatch (source=0xda5c00, callback=<optimized out>, user_data=<optimized out>) at kernel/qeventloop_x11_glib.cpp:123 #26 0x00007f5c65897d13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f5c65898060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f5c65898124 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f5c69492b68 in TQEventLoop::processEvents (this=0xda4be0, flags=<optimized out>) at kernel/qeventloop_x11_glib.cpp:279 #30 0x00007f5c694c2319 in TQEventLoop::enterLoop (this=0xda4be0) at kernel/qeventloop.cpp:227 #31 0x00007f5c694c22a9 in TQEventLoop::exec (this=0xda4be0) at kernel/qeventloop.cpp:174 #32 0x00007f5c6cf973ec in kdemain (argc=1, argv=0x7fff3e583dc8) at /build/buildd/tdebase-trinity-14.0.0-r1865/kdesktop/main.cc:293 #33 0x00000000004007a4 in main (argc=1, argv=0x7fff3e583dc8)
at /build/buildd/tdebase-trinity-14.0.0-r1865/obj-x86_64-linux-gnu/kdesktop/kdesktop_tdeinit_executable.cpp:2 #34 0x00007f5c6cbc176d in __libc_start_main ( main=0x400784 <main(int, char**)>, argc=1, ubp_av=0x7fff3e583dc8, ---Type <return> to continue, or q <return> to quit--- init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3e583db8) at libc-start.c:226 #35 0x00000000004006c9 in _start () (gdb)
| That should provide more detailed information (i.e. line | numbers) about where each thread and frame is. | From a quick look at the current incomplete stack frame, thread 1 | (which is blocking thread 2) is blocked inside a malloc() call, which | as far as I can tell is usually a sign that the heap is corrupted | (perhaps a pointer deallocated twice). Now we are kind of stretching | to the limit of my knowledge as well, so I will need to guess/look up | what's the best way to go. | | By the way, when kdesktop_lock crashes do you have any crash report | window popping up in your system?
no. the only way i know it has happened is when i notice that the desktop program (xplanet set to refresh hourly) has stopped refreshing. nor does xerrors (or whatever it's called now) report anything.
| In the mean time, can you try the following things:
| 1) install the debug symbols as said above and provide the updated | stack frames
done, above.
| 2) kill kdesktop and run it again (or reboot your system, even | better). From CLI (outside TDE), run: | ps aux |grep kdesktop | Take note of the kdesktop_lock pid. Run: | gdb --pid=<kdesktop_lock pid> | After gdb attaches to the process, continue execution with: | c | At this stage kdesktop_lock should be running normally. Leave | everything running until kdesktop_lock crashes again. At this point | gdb should provide some info about the crash (perhaps a segmentation | fault - SIGSEGV). When it happens you should be able to get the stack | frame for kdesktop_lock (again thread apply all bt) since gdb is still | attached to the process. Do not exit gdb after that, not sure what | else we may need. All this is somehow experimental, if something | doesn't go to plan, please let me know.
will do. thanks very much for taking time to dig into this.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
<snip>
| In the mean time, can you try the following things:
| 1) install the debug symbols as said above and provide the updated | stack frames
done, above.
Thanks, it adds some more information, which may always come useful sooner or later.
| 2) kill kdesktop and run it again (or reboot your system, even | better). From CLI (outside TDE), run: | ps aux |grep kdesktop | Take note of the kdesktop_lock pid. Run: | gdb --pid=<kdesktop_lock pid> | After gdb attaches to the process, continue execution with: | c | At this stage kdesktop_lock should be running normally. Leave | everything running until kdesktop_lock crashes again. At this point | gdb should provide some info about the crash (perhaps a segmentation | fault - SIGSEGV). When it happens you should be able to get the stack | frame for kdesktop_lock (again thread apply all bt) since gdb is still | attached to the process. Do not exit gdb after that, not sure what | else we may need. All this is somehow experimental, if something | doesn't go to plan, please let me know.
will do.
Ok, let's take this as further step, see if we can find out what crashed kdesktop_lock first.
thanks very much for taking time to dig into this.
No problem, it's an interesting bug and may be a good way to learn something new, whether I am able to fix it or not :-)
Cheers Michele
-
dep -
Gerhard Zintel -
Michele Calgaro -
Slávek Banko