[Bug 463920] [NEW] evolution crashes when composing a message pressing space
Public bug reported: Binary package hint: evolution When composing a message as soon as I hit space evolution crashes. Backtrace attached. It seems to be a problem with spell checking being triggered. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- evolution crashes when composing a message pressing space https://bugs.launchpad.net/bugs/463920 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 463920] Re: evolution crashes when composing a message pressing space
** Attachment added: gdb-evolution.txt http://launchpadlibrarian.net/34635232/gdb-evolution.txt -- evolution crashes when composing a message pressing space https://bugs.launchpad.net/bugs/463920 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 267828] Re: switch user does not work
Have not noticed this problem in Jaunty. -- switch user does not work https://bugs.launchpad.net/bugs/267828 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 267828] Re: switch user does not work
I get the same error message (after a few seconds) when trying to switch user for the first time. The second time (after the error message) works. I have a Geforce 6800 Ultra, using the nvidia binary driver. -- switch user does not work https://bugs.launchpad.net/bugs/267828 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
Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
On Thu, 2007-11-22 at 10:28 +, Pjotr12345 wrote: Possibly the bad guy is Tracker. Tracker is a plugin in Deskbar applet. An hour ago, I've completely removed Tracker from my system with Synaptic, and I'm curious if the problem is over now. Maybe you could try this, too, and report here if it has been a success? I do not have Tracker installed and still experience the problem. -- [Gutsy] high processor activity after logging out and then logging in again https://bugs.launchpad.net/bugs/150471 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
Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
On Thu, 2007-11-22 at 21:25 +, Pjotr12345 wrote: @doclist: I would like some clarification from you, because this is an important matter. Tracker is installed in the standard installation, so everybody has tracker automatically. So if I understand you correctly, you already removed tracker before, and still have the problem? That's right. -- [Gutsy] high processor activity after logging out and then logging in again https://bugs.launchpad.net/bugs/150471 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
Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
On Nov 7, 2007 8:12 AM, Luiz Alberto Medaets [EMAIL PROTECTED] wrote: Tracker is a desktop search tool, part of Gnome, and is loaded when you start (Disable Tracker on System – Preferences – Sessions and the problem will end.) or when you ask for file search. Open System - Administration -System Monitor. Look for Trackerd on process tab to see if it's running . If it is, right click and stop then right click and kill. Megahertz I know what Tracker is. I could have been clearer: I uninstalled Tracker soon after upgrading to Gutsy. -- [Gutsy] high processor activity after logging out and then logging in again https://bugs.launchpad.net/bugs/150471 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
Re: [Bug 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
On Nov 6, 2007 6:06 AM, Luiz Alberto Medaets [EMAIL PROTECTED] wrote: Disable Tracker on System – Preferences – Sessions and the problem will end. Tracker is a desktop search tool, it has a bug, and it is launched every time you make a search on file browser (Nautilus). Luiz I don't have tracker installed at all (and haven't since the first day of installing Gutsy) and still experience the problem. -- [Gutsy] high processor activity after logging out and then logging in again https://bugs.launchpad.net/bugs/150471 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 150471] Re: [Gutsy] high processor activity after logging out and then logging in again
I also experience 100% CPU usage from Nautilus after logging in userA, logging in userB, logging out userB. The offending process is owned by userB. This is new (for me) in Gutsy. I can't seem to get a proper backtrace. This is what I get immediately after attaching through GDB. = #0 0xb727d45f in fputs () from /lib/tls/i686/cmov/libc.so.6 #1 0x080e27c8 in write_string (filename=0x0, file=0x8905b48, str=0x1 Address 0x1 out of bounds, error=0x0) at nautilus-debug-log.c:446 #2 0x080e28ab in nautilus_debug_log_dump ( filename=0x89058f0 /home/USER/nautilus-debug-log.txt, error=0x0) at nautilus-debug-log.c:508 #3 0x0807e776 in dump_debug_log () at nautilus-main.c:213 #4 0x0807e7bf in sigfatal_handler (sig=11) at nautilus-main.c:258 #5 signal handler called #6 0xb7657af6 in gconf_client_remove_dir () from /usr/lib/libgconf-2.so.4 #7 0xb5c2e9cd in ?? () from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so #8 0xe509 in ?? () #9 0xb5c32d74 in ?? () from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so #10 0x in ?? () = Trying to 'continue' in GDB gives the following: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1228183888 (LWP 22236)] 0xb7657af6 in gconf_client_remove_dir () from /usr/lib/libgconf-2.so.4 -- [Gutsy] high processor activity after logging out and then logging in again https://bugs.launchpad.net/bugs/150471 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 27109] Re: nautilus uses 100% cpu after closing a ssh session
I am still experiencing this in Feisty. What seems to regularly reproduce the problem for me is to delete a file on the ssh server (from Nautilus). Shortly after Nautilus goes to 100% CPU. I would guess that the bug stems from Nautilus assuming that the deleted files are still there and doing an operation based on that incorrect assumption, resulting in a spin-lock. -- nautilus uses 100% cpu after closing a ssh session https://bugs.launchpad.net/bugs/27109 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81857] Critical bug in gnome-applets postinstall script
Public bug reported: Binary package hint: gnome-applets The postinstall script for gnome-applets version 2.16.1-0ubuntu4 contains a compileall.py directive which tries to compile /usr/lib/python2.4/site-packages/py-0.8.0_alpha2-py2.4.egg/py/test/testing/data/syntax_error.py among others. However, 'syntax_error.py' is test function designed to be malformed, invalid python (and thus uncompilable). This is on Edgy Eft. Workaround I used was to temporarily comment out the one line in syntax_error.py. Temporarily moving it somewhere else would also probably work. Output of apt-get install -- Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking, 0B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up gnome-applets (2.16.1-0ubuntu4) ... Compiling /usr/lib/python2.4/site-packages/py-0.8.0_alpha2-py2.4.egg/py/test/testing/data/syntax_error.py ... File /usr/lib/python2.4/site-packages/py-0.8.0_alpha2-py2.4.egg/py/test/testing/data/syntax_error.py, line 3 this is really not python ^ SyntaxError: invalid syntax dpkg: error processing gnome-applets (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: gnome-applets E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: Unconfirmed -- Critical bug in gnome-applets postinstall script https://launchpad.net/bugs/81857 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 81857] Re: Critical bug in gnome-applets postinstall script
Should mention that this is Edgy. ** Description changed: Binary package hint: gnome-applets The postinstall script for gnome-applets version 2.16.1-0ubuntu4 contains a compileall.py directive which tries to compile /usr/lib/python2.4/site-packages/py-0.8.0_alpha2-py2.4.egg/py/test/testing/data/syntax_error.py among others. However, 'syntax_error.py' is test function designed to be malformed, invalid python (and thus uncompilable). + + This is on Edgy Eft. Workaround I used was to temporarily comment out the one line in syntax_error.py. Temporarily moving it somewhere else would also probably work. Output of apt-get install -- Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking, 0B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up gnome-applets (2.16.1-0ubuntu4) ... Compiling /usr/lib/python2.4/site-packages/py-0.8.0_alpha2-py2.4.egg/py/test/testing/data/syntax_error.py ... File /usr/lib/python2.4/site-packages/py-0.8.0_alpha2-py2.4.egg/py/test/testing/data/syntax_error.py, line 3 this is really not python ^ SyntaxError: invalid syntax dpkg: error processing gnome-applets (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: gnome-applets E: Sub-process /usr/bin/dpkg returned an error code (1) -- Critical bug in gnome-applets postinstall script https://launchpad.net/bugs/81857 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 26618] Re: Only the foreground user should be able to trigger suspends
I am also waiting for this bug to be addressed. -- Only the foreground user should be able to trigger suspends https://launchpad.net/bugs/26618 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57781] Default option should be 'restore' on user switching
Public bug reported: When logging in and a previous session already exists for that user the default option should be restore the previous session and not to start a new one. So if I should be able enter my password and then bash the enter key and end up in a pre-existing session if there is one. Conversely, accidently pressing the enter key twice should not throw me into a new session. ** Affects: gdm (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Default option should be 'restore' on user switching https://launchpad.net/bugs/57781 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
