[Bug 60394] Re: screensaver starts but shows only a black screen
I'm having the same problem on my laptop running Hardy. Screensaver previews work fine, but when I lock the screen, or when the screensaver activates when the machine is idle or when I run gnome-screensaver- command -a I only get a blank screen. At first I thought the problem was due to some misconfiguration in my user account, so I created a new user, but when I log in using that new account the problem persists. I chose the "pictures folder" screensaver in the screensaver properties dialog and tried doing: gnome-screensaver-command -a && ps ax I would have expected to see some mention of /usr/lib/gnome-screensaver/gnome-screensaver/slideshow in the output, but it's not there (i tried the same with various different screensavers all with the same result). For what it's worth, my graphics card is an Intel 82852/855GM Integrated Graphics Device (rev 02) using the i810 driver (the newer intel driver is rather buggy) and I have all desktop effects disabled. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I forgot to mention, I've been running Ubuntu on this laptop for a bit over two years, never had this problem when I was running Dapper, Edgy, Fiesty or Gutsy... -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I think I know what's going on. I managed to turn on gnome-screensaver debugging on login (I had to rename /usr/bin/gnome-screensaver and replace it with a script that launches gnome-screensaver with debugging enabled. Comparing the debug output from when the screensaver worked to when it doesn't I noticed that when the screensaver wasn't working the output contained lines like: [listener_add_ref_entry] gs-listener-dbus.c:723 (13:48:37): adding throttler from Power screensaver for reason 'On battery power' on connection :1.6 and [manager_maybe_start_job_for_window] gs-manager.c:215 (13:48:53):Not starting job because throttled There is no mention of throttling in the debug output when the screensaver does work correctly. So it seems that gnome-screensaver is only blanking the screen because it thinks the machine is running on battery power (it's not - i'm running on AC). I tried pulling out the power cable and plugging it back in, after which the screensaver was worked correctly. This would seem to indicate that the problem is not with gnome- screensaver but somewhere else. Perhaps in gnome-power-manager. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I thought I'd try to get to the bottom of this by killing gnome-screensaver, running gnome-screensaver --no-daemon --debug > screensaver.debug 2>&1 and then doing gnome-screensaver-command -a but when I did that, the screensaver worked correctly. I did some more experimentation and found that if I kill gnome-screensaver and start it again manually, then it works correctly. If I can find out where gnome-screensaver gets started on login I could change that to enable debugging and see if that gets me any closer to an anwer. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] Re: Nautilus crashes on symlink loops
** Description changed: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) + + to duplicate: + $ mkdir test + $ cd test + $ ln -s s1 s2 + $ ln -s s2 s1 + + Open the directory test in Nautilus -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] [NEW] Nautilus crashes on symlink loops
Public bug reported: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247921] Re: nautilus crashed with SIGSEGV in pthread_mutex_lock()
I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/16775063/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/247921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] Re: Nautilus crashes on symlink loops
** Description changed: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) + + to duplicate: + $ mkdir test + $ cd test + $ ln -s s1 s2 + $ ln -s s2 s1 + + Open the directory test in Nautilus -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] [NEW] Nautilus crashes on symlink loops
Public bug reported: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247921] Re: nautilus crashed with SIGSEGV in pthread_mutex_lock()
I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/16775063/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/247921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I'm having the same problem on my laptop running Hardy. Screensaver previews work fine, but when I lock the screen, or when the screensaver activates when the machine is idle or when I run gnome-screensaver- command -a I only get a blank screen. At first I thought the problem was due to some misconfiguration in my user account, so I created a new user, but when I log in using that new account the problem persists. I chose the "pictures folder" screensaver in the screensaver properties dialog and tried doing: gnome-screensaver-command -a && ps ax I would have expected to see some mention of /usr/lib/gnome-screensaver/gnome-screensaver/slideshow in the output, but it's not there (i tried the same with various different screensavers all with the same result). For what it's worth, my graphics card is an Intel 82852/855GM Integrated Graphics Device (rev 02) using the i810 driver (the newer intel driver is rather buggy) and I have all desktop effects disabled. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I forgot to mention, I've been running Ubuntu on this laptop for a bit over two years, never had this problem when I was running Dapper, Edgy, Fiesty or Gutsy... -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I think I know what's going on. I managed to turn on gnome-screensaver debugging on login (I had to rename /usr/bin/gnome-screensaver and replace it with a script that launches gnome-screensaver with debugging enabled. Comparing the debug output from when the screensaver worked to when it doesn't I noticed that when the screensaver wasn't working the output contained lines like: [listener_add_ref_entry] gs-listener-dbus.c:723 (13:48:37): adding throttler from Power screensaver for reason 'On battery power' on connection :1.6 and [manager_maybe_start_job_for_window] gs-manager.c:215 (13:48:53):Not starting job because throttled There is no mention of throttling in the debug output when the screensaver does work correctly. So it seems that gnome-screensaver is only blanking the screen because it thinks the machine is running on battery power (it's not - i'm running on AC). I tried pulling out the power cable and plugging it back in, after which the screensaver was worked correctly. This would seem to indicate that the problem is not with gnome- screensaver but somewhere else. Perhaps in gnome-power-manager. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I thought I'd try to get to the bottom of this by killing gnome-screensaver, running gnome-screensaver --no-daemon --debug > screensaver.debug 2>&1 and then doing gnome-screensaver-command -a but when I did that, the screensaver worked correctly. I did some more experimentation and found that if I kill gnome-screensaver and start it again manually, then it works correctly. If I can find out where gnome-screensaver gets started on login I could change that to enable debugging and see if that gets me any closer to an anwer. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] Re: Nautilus crashes on symlink loops
** Description changed: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) + + to duplicate: + $ mkdir test + $ cd test + $ ln -s s1 s2 + $ ln -s s2 s1 + + Open the directory test in Nautilus -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] [NEW] Nautilus crashes on symlink loops
Public bug reported: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247921] Re: nautilus crashed with SIGSEGV in pthread_mutex_lock()
I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/16775063/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/247921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I'm having the same problem on my laptop running Hardy. Screensaver previews work fine, but when I lock the screen, or when the screensaver activates when the machine is idle or when I run gnome-screensaver- command -a I only get a blank screen. At first I thought the problem was due to some misconfiguration in my user account, so I created a new user, but when I log in using that new account the problem persists. I chose the "pictures folder" screensaver in the screensaver properties dialog and tried doing: gnome-screensaver-command -a && ps ax I would have expected to see some mention of /usr/lib/gnome-screensaver/gnome-screensaver/slideshow in the output, but it's not there (i tried the same with various different screensavers all with the same result). For what it's worth, my graphics card is an Intel 82852/855GM Integrated Graphics Device (rev 02) using the i810 driver (the newer intel driver is rather buggy) and I have all desktop effects disabled. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I forgot to mention, I've been running Ubuntu on this laptop for a bit over two years, never had this problem when I was running Dapper, Edgy, Fiesty or Gutsy... -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I think I know what's going on. I managed to turn on gnome-screensaver debugging on login (I had to rename /usr/bin/gnome-screensaver and replace it with a script that launches gnome-screensaver with debugging enabled. Comparing the debug output from when the screensaver worked to when it doesn't I noticed that when the screensaver wasn't working the output contained lines like: [listener_add_ref_entry] gs-listener-dbus.c:723 (13:48:37): adding throttler from Power screensaver for reason 'On battery power' on connection :1.6 and [manager_maybe_start_job_for_window] gs-manager.c:215 (13:48:53):Not starting job because throttled There is no mention of throttling in the debug output when the screensaver does work correctly. So it seems that gnome-screensaver is only blanking the screen because it thinks the machine is running on battery power (it's not - i'm running on AC). I tried pulling out the power cable and plugging it back in, after which the screensaver was worked correctly. This would seem to indicate that the problem is not with gnome- screensaver but somewhere else. Perhaps in gnome-power-manager. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I thought I'd try to get to the bottom of this by killing gnome-screensaver, running gnome-screensaver --no-daemon --debug > screensaver.debug 2>&1 and then doing gnome-screensaver-command -a but when I did that, the screensaver worked correctly. I did some more experimentation and found that if I kill gnome-screensaver and start it again manually, then it works correctly. If I can find out where gnome-screensaver gets started on login I could change that to enable debugging and see if that gets me any closer to an anwer. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] Re: Nautilus crashes on symlink loops
** Description changed: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) + + to duplicate: + $ mkdir test + $ cd test + $ ln -s s1 s2 + $ ln -s s2 s1 + + Open the directory test in Nautilus -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] [NEW] Nautilus crashes on symlink loops
Public bug reported: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247921] Re: nautilus crashed with SIGSEGV in pthread_mutex_lock()
I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/16775063/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/247921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I'm having the same problem on my laptop running Hardy. Screensaver previews work fine, but when I lock the screen, or when the screensaver activates when the machine is idle or when I run gnome-screensaver- command -a I only get a blank screen. At first I thought the problem was due to some misconfiguration in my user account, so I created a new user, but when I log in using that new account the problem persists. I chose the "pictures folder" screensaver in the screensaver properties dialog and tried doing: gnome-screensaver-command -a && ps ax I would have expected to see some mention of /usr/lib/gnome-screensaver/gnome-screensaver/slideshow in the output, but it's not there (i tried the same with various different screensavers all with the same result). For what it's worth, my graphics card is an Intel 82852/855GM Integrated Graphics Device (rev 02) using the i810 driver (the newer intel driver is rather buggy) and I have all desktop effects disabled. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I forgot to mention, I've been running Ubuntu on this laptop for a bit over two years, never had this problem when I was running Dapper, Edgy, Fiesty or Gutsy... -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I think I know what's going on. I managed to turn on gnome-screensaver debugging on login (I had to rename /usr/bin/gnome-screensaver and replace it with a script that launches gnome-screensaver with debugging enabled. Comparing the debug output from when the screensaver worked to when it doesn't I noticed that when the screensaver wasn't working the output contained lines like: [listener_add_ref_entry] gs-listener-dbus.c:723 (13:48:37): adding throttler from Power screensaver for reason 'On battery power' on connection :1.6 and [manager_maybe_start_job_for_window] gs-manager.c:215 (13:48:53):Not starting job because throttled There is no mention of throttling in the debug output when the screensaver does work correctly. So it seems that gnome-screensaver is only blanking the screen because it thinks the machine is running on battery power (it's not - i'm running on AC). I tried pulling out the power cable and plugging it back in, after which the screensaver was worked correctly. This would seem to indicate that the problem is not with gnome- screensaver but somewhere else. Perhaps in gnome-power-manager. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I thought I'd try to get to the bottom of this by killing gnome-screensaver, running gnome-screensaver --no-daemon --debug > screensaver.debug 2>&1 and then doing gnome-screensaver-command -a but when I did that, the screensaver worked correctly. I did some more experimentation and found that if I kill gnome-screensaver and start it again manually, then it works correctly. If I can find out where gnome-screensaver gets started on login I could change that to enable debugging and see if that gets me any closer to an anwer. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] Re: Nautilus crashes on symlink loops
** Description changed: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) + + to duplicate: + $ mkdir test + $ cd test + $ ln -s s1 s2 + $ ln -s s2 s1 + + Open the directory test in Nautilus -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] [NEW] Nautilus crashes on symlink loops
Public bug reported: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247921] Re: nautilus crashed with SIGSEGV in pthread_mutex_lock()
I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/16775063/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/247921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I'm having the same problem on my laptop running Hardy. Screensaver previews work fine, but when I lock the screen, or when the screensaver activates when the machine is idle or when I run gnome-screensaver- command -a I only get a blank screen. At first I thought the problem was due to some misconfiguration in my user account, so I created a new user, but when I log in using that new account the problem persists. I chose the "pictures folder" screensaver in the screensaver properties dialog and tried doing: gnome-screensaver-command -a && ps ax I would have expected to see some mention of /usr/lib/gnome-screensaver/gnome-screensaver/slideshow in the output, but it's not there (i tried the same with various different screensavers all with the same result). For what it's worth, my graphics card is an Intel 82852/855GM Integrated Graphics Device (rev 02) using the i810 driver (the newer intel driver is rather buggy) and I have all desktop effects disabled. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I forgot to mention, I've been running Ubuntu on this laptop for a bit over two years, never had this problem when I was running Dapper, Edgy, Fiesty or Gutsy... -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I think I know what's going on. I managed to turn on gnome-screensaver debugging on login (I had to rename /usr/bin/gnome-screensaver and replace it with a script that launches gnome-screensaver with debugging enabled. Comparing the debug output from when the screensaver worked to when it doesn't I noticed that when the screensaver wasn't working the output contained lines like: [listener_add_ref_entry] gs-listener-dbus.c:723 (13:48:37): adding throttler from Power screensaver for reason 'On battery power' on connection :1.6 and [manager_maybe_start_job_for_window] gs-manager.c:215 (13:48:53):Not starting job because throttled There is no mention of throttling in the debug output when the screensaver does work correctly. So it seems that gnome-screensaver is only blanking the screen because it thinks the machine is running on battery power (it's not - i'm running on AC). I tried pulling out the power cable and plugging it back in, after which the screensaver was worked correctly. This would seem to indicate that the problem is not with gnome- screensaver but somewhere else. Perhaps in gnome-power-manager. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I thought I'd try to get to the bottom of this by killing gnome-screensaver, running gnome-screensaver --no-daemon --debug > screensaver.debug 2>&1 and then doing gnome-screensaver-command -a but when I did that, the screensaver worked correctly. I did some more experimentation and found that if I kill gnome-screensaver and start it again manually, then it works correctly. If I can find out where gnome-screensaver gets started on login I could change that to enable debugging and see if that gets me any closer to an anwer. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] Re: Nautilus crashes on symlink loops
** Description changed: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) + + to duplicate: + $ mkdir test + $ cd test + $ ln -s s1 s2 + $ ln -s s2 s1 + + Open the directory test in Nautilus -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247644] [NEW] Nautilus crashes on symlink loops
Public bug reported: Binary package hint: nautilus I have a directory in which I created a symlink loop (to test a script I'm working on for finding and cleaning up duplicate files). Today I (accidentally) opened this directory with nautilus, causing it to crash trying to resolve the symlinks. I would have expected Nautilus to be able to detect the loop and display the links as broken symlinks. This happens both on AMD64 Gutsy (nautilus version 1:2.20.0-0ubuntu7.1) and on 32bit Hardy (nautilus version 1:2.22.3-0ubuntu2) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Nautilus crashes on symlink loops https://bugs.launchpad.net/bugs/247644 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 247921] Re: nautilus crashed with SIGSEGV in pthread_mutex_lock()
I couldn't get a complete backtrace. Nautilus seems to go into an infinite recursion before the crash and gdb crashes after printing the first 58203 stack frames. So, instead of uploading an 11MB file here, I just printed the innermost 21 frames. The pattern that can be seen here continues all the way down the stack (or at least as far as gdb will go). I tried to get the outermost few stack frames as well, but that also causes gdb to crash. ** Attachment added: "gdb-nautilus.txt" http://launchpadlibrarian.net/16775063/gdb-nautilus.txt -- nautilus crashed with SIGSEGV in pthread_mutex_lock() https://bugs.launchpad.net/bugs/247921 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I'm having the same problem on my laptop running Hardy. Screensaver previews work fine, but when I lock the screen, or when the screensaver activates when the machine is idle or when I run gnome-screensaver- command -a I only get a blank screen. At first I thought the problem was due to some misconfiguration in my user account, so I created a new user, but when I log in using that new account the problem persists. I chose the "pictures folder" screensaver in the screensaver properties dialog and tried doing: gnome-screensaver-command -a && ps ax I would have expected to see some mention of /usr/lib/gnome-screensaver/gnome-screensaver/slideshow in the output, but it's not there (i tried the same with various different screensavers all with the same result). For what it's worth, my graphics card is an Intel 82852/855GM Integrated Graphics Device (rev 02) using the i810 driver (the newer intel driver is rather buggy) and I have all desktop effects disabled. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I forgot to mention, I've been running Ubuntu on this laptop for a bit over two years, never had this problem when I was running Dapper, Edgy, Fiesty or Gutsy... -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I think I know what's going on. I managed to turn on gnome-screensaver debugging on login (I had to rename /usr/bin/gnome-screensaver and replace it with a script that launches gnome-screensaver with debugging enabled. Comparing the debug output from when the screensaver worked to when it doesn't I noticed that when the screensaver wasn't working the output contained lines like: [listener_add_ref_entry] gs-listener-dbus.c:723 (13:48:37): adding throttler from Power screensaver for reason 'On battery power' on connection :1.6 and [manager_maybe_start_job_for_window] gs-manager.c:215 (13:48:53):Not starting job because throttled There is no mention of throttling in the debug output when the screensaver does work correctly. So it seems that gnome-screensaver is only blanking the screen because it thinks the machine is running on battery power (it's not - i'm running on AC). I tried pulling out the power cable and plugging it back in, after which the screensaver was worked correctly. This would seem to indicate that the problem is not with gnome- screensaver but somewhere else. Perhaps in gnome-power-manager. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60394] Re: screensaver starts but shows only a black screen
I thought I'd try to get to the bottom of this by killing gnome-screensaver, running gnome-screensaver --no-daemon --debug > screensaver.debug 2>&1 and then doing gnome-screensaver-command -a but when I did that, the screensaver worked correctly. I did some more experimentation and found that if I kill gnome-screensaver and start it again manually, then it works correctly. If I can find out where gnome-screensaver gets started on login I could change that to enable debugging and see if that gets me any closer to an anwer. -- screensaver starts but shows only a black screen https://bugs.launchpad.net/bugs/60394 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
