[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
** Changed in: gnome-panel (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235944 Title: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/235944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
** Changed in: gnome-panel Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/235944 Title: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
** Changed in: gnome-panel Importance: Unknown => Medium -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
Same problem here on a Dell Latitude E6400: xorg.conf (generated by nvidia-settings tool): # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 1.0 (bui...@crested) Sun Feb 1 20:25:37 UTC 2009 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "Module" Load "dbe" Load "extmod" Load "type1" Load "freetype" Load "glx" EndSection Section "ServerFlags" Option "Xinerama" "0" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor0" VendorName "Unknown" ModelName "DELL E228WFP" HorizSync 30.0 - 83.0 VertRefresh 56.0 - 75.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "Quadro NVS 160M" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 Option "TwinView" "1" Option "metamodes" "CRT: nvidia-auto-select +1440+0, DFP: nvidia-auto-select +0+0" SubSection "Display" Depth 24 EndSubSection EndSection -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
I got here from another bug. I get this when I click on button launchers on the panel in screen 1 from my NVIDIA graphics card. It doesn't seem to occur if I run applications from the applications menu. A blank error dialog pops up (usually in screen 0) that I can't close and it uses 100% CPU. ctrl-alt-backspace or killing gnome-panel from a terminal seem to be the only options. ctrl-alt-backspace doesn't kill the offending gnome-panel process, so once X restarts I still have to manually kill it from a terminal. This reproduces pretty readily on my clean Intrepid Install. -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
I have the same problem since upgrading to intrepid from hardy. Ubuntu: 8.10 Metacity: 1:2.24.0-0ubuntu1 gnome-panel: 1:2.24.1-0ubuntu2.1 Dual Monitors An interesting side note is that if you enable assistive technologies gnome-panel restarts instead of locking up. This behavior I find easier to deal with. Clicking on launch buttons in the second display sometimes works. This is really annoying. -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
I am not sure it is the same problem but the gnome-panel freezes on me too after a while... not sure how and why? Here is what I do so I am able to work. I can work if I only opened all my windows before the freeze occurs after this I cannot even open any app via the terminal. I still can use all apps that are open. 1) restart computer (kill gdm or doing a crtl-alt-backspace both have a negative outcome) 2) quickly open all apps I need I have hardy with backports on a dell d620 with a digital screen above my laptop using xrandr. gnome-panel version is 1:2.22.2-0ubuntu-1 I did try a lot of things to overcome this problem, it did at least cost me a lot of wasted working hours unfortunatly... Removing all .gconf* and .gnome* folders (a few times) Reinstalling gnome-panel and nautilus Disable compiz Moved the gnome-panel on both screens but on both screens this problem occures using only the laptop screen ... but none solved it. Cheers -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
** Changed in: gnome-panel Status: Unknown => New -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
Thanks for the report and strace! I have forwarded your information upstream. You may follow the upstream report here: http://bugzilla.gnome.org/show_bug.cgi?id=535664 ** Bug watch added: GNOME Bug Tracker #535664 http://bugzilla.gnome.org/show_bug.cgi?id=535664 ** Also affects: gnome-panel via http://bugzilla.gnome.org/show_bug.cgi?id=535664 Importance: Unknown Status: Unknown ** Changed in: gnome-panel (Ubuntu) Importance: Undecided => Low Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs) Status: New => Triaged -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235944] Re: Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu
Here's part of the output of strace, it is a bit hard to tell where the loop begins and ends, it seems it is 2 processes interacting. (...) [pid 7459] 20:20:45.468638 <... writev resumed> ) = 2999 [pid 16613] 20:20:45.468680 futex(0x810b4e8, 0x80 /* FUTEX_??? */, 2 [pid 7459] 20:20:45.468712 futex(0x810b4e8, 0x81 /* FUTEX_??? */, 1 [pid 16613] 20:20:45.468734 <... futex resumed> ) = 0 [pid 7459] 20:20:45.468748 <... futex resumed> ) = 1 [pid 16613] 20:20:45.468768 futex(0x810b4e8, 0x81 /* FUTEX_??? */, 1) = 0 [pid 16613] 20:20:45.468803 read(11, "GIOP\1\2\1\1$\0\0\0", 12) = 12 [pid 16613] 20:20:45.468849 read(11, "\360-\252\277\0\0\0\0\1\0\0\0\1\0\0\0\f\0\0\0\1\1\1\1\1"..., 36) = 36 [pid 16613] 20:20:45.468948 poll( [pid 7459] 20:20:45.469276 select(4, [3], [3], NULL, NULL) = 2 (in [3], out [3]) [pid 7459] 20:20:45.469354 read(3, "[EMAIL PROTECTED]"..., 4096) = 192 [pid 7459] 20:20:45.469419 writev(3, [{"\22\0\n\0\347\227\341\1F\1\0\0\6\0\0\0 \0\0\0\4\0\0\0\0"..., 284}], 1) = 284 [pid 7459] 20:20:45.470074 select(4, [3], [], NULL, NULL) = 1 (in [3]) [pid 7459] 20:20:45.470795 read(3, "\34\257\26\317\347\227\341\1F\1\0\0\365\224\217\26\0\31"..., 4096) = 224 [pid 7459] 20:20:45.470891 read(3, 0x80e01fc, 4096) = -1 EAGAIN (Resource temporarily unavailable) [pid 7459] 20:20:45.480372 gettimeofday({1212002445, 480420}, NULL) = 0 [pid 7459] 20:20:45.480498 gettimeofday({1212002445, 480513}, NULL) = 0 [pid 7459] 20:20:45.480631 writev(11, [{"GIOP\1\2\1\0\243\v\0\0", 12}, {"\320-\252\277\3\0\0\0\0\0\0\0\34\0\0\0\0\0\0\0\337\304"..., 2036}, {"ROLE_TOOL_BAR\0\0\0\16\0\0\0ROLE_TOOL_TI"..., 943}], 3 [pid 16613] 20:20:45.481081 <... poll resumed> [{fd=41, events=POLLIN}, {fd=38, events=POLLIN|POLLPRI}, {fd=37, events=POLLIN|POLLPRI}, {fd=36, events=POLLIN|POLLPRI}, {fd=35, events=POLLIN|POLLPRI}, {fd=33, events=POLLIN|POLLPRI}, {fd=32, events=POLLIN|POLLPRI}, {fd=31, events=POLLIN|POLLPRI}, {fd=30, events=POLLIN|POLLPRI}, {fd=28, events=POLLIN|POLLPRI}, {fd=27, events=POLLIN|POLLPRI}, {fd=26, events=POLLIN|POLLPRI}, {fd=25, events=POLLIN|POLLPRI}, {fd=24, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|POLLPRI}, {fd=16, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=11, events=POLLIN|POLLPRI, revents=POLLIN}, {fd=12, events=POLLIN|POLLPRI}, {fd=43, events=POLLIN|POLLPRI}, {fd=45, events=POLLIN|POLLPRI}, {fd=46, events=POLLIN|POLLPRI}, {fd=29, events=POLLIN|POLLPRI}, {fd=34, events=POLLIN|POLLPRI}], 27, -1) = 1 [pid 7459] 20:20:45.481208 <... writev resumed> ) = 2991 [pid 16613] 20:20:45.481251 futex(0x810b4e8, 0x80 /* FUTEX_??? */, 2 [pid 7459] 20:20:45.481284 futex(0x810b4e8, 0x81 /* FUTEX_??? */, 1 [pid 16613] 20:20:45.481306 <... futex resumed> ) = 0 [pid 7459] 20:20:45.481320 <... futex resumed> ) = 1 [pid 16613] 20:20:45.481341 futex(0x810b4e8, 0x81 /* FUTEX_??? */, 1) = 0 [pid 16613] 20:20:45.481375 read(11, "GIOP\1\2\1\1$\0\0\0", 12) = 12 [pid 16613] 20:20:45.481420 read(11, "\320-\252\277\0\0\0\0\1\0\0\0\1\0\0\0\f\0\0\0\1\1\1\1\1"..., 36) = 36 [pid 16613] 20:20:45.481517 poll( [pid 7459] 20:20:45.481729 gettimeofday({1212002445, 481755}, NULL) = 0 [pid 7459] 20:20:45.481824 gettimeofday({1212002445, 481839}, NULL) = 0 [pid 7459] 20:20:45.481952 writev(11, [{"GIOP\1\2\1\0\253\v\0\0", 12}, {"\360-\252\277\3\0\0\0\0\0\0\0\34\0\0\0\0\0\0\0\337\304"..., 2044}, {"ROLE_TOOL_BAR\0\0\0\16\0\0\0ROLE_TOOL_TI"..., 943}], 3 [pid 16613] 20:20:45.482590 <... poll resumed> [{fd=41, events=POLLIN}, {fd=38, events=POLLIN|POLLPRI}, {fd=37, events=POLLIN|POLLPRI}, {fd=36, events=POLLIN|POLLPRI}, {fd=35, events=POLLIN|POLLPRI}, {fd=33, events=POLLIN|POLLPRI}, {fd=32, events=POLLIN|POLLPRI}, {fd=31, events=POLLIN|POLLPRI}, {fd=30, events=POLLIN|POLLPRI}, {fd=28, events=POLLIN|POLLPRI}, {fd=27, events=POLLIN|POLLPRI}, {fd=26, events=POLLIN|POLLPRI}, {fd=25, events=POLLIN|POLLPRI}, {fd=24, events=POLLIN|POLLPRI}, {fd=23, events=POLLIN|POLLPRI}, {fd=17, events=POLLIN|POLLPRI}, {fd=18, events=POLLIN|POLLPRI}, {fd=16, events=POLLIN|POLLPRI}, {fd=15, events=POLLIN|POLLPRI}, {fd=14, events=POLLIN|POLLPRI}, {fd=11, events=POLLIN|POLLPRI, revents=POLLIN}, {fd=12, events=POLLIN|POLLPRI}, {fd=43, events=POLLIN|POLLPRI}, {fd=45, events=POLLIN|POLLPRI}, {fd=46, events=POLLIN|POLLPRI}, {fd=29, events=POLLIN|POLLPRI}, {fd=34, events=POLLIN|POLLPRI}], 27, -1) = 1 [pid 7459] 20:20:45.482720 <... writev resumed> ) = 2999 (...) ** Attachment added: "strace-gnome-panel_hang-0805282010.log" http://launchpadlibrarian.net/14809442/strace-gnome-panel_hang-0805282010.log -- Hardy: opening a drawer can randomly make gnome-panel hang using 100% cpu https://bugs.launchpad.net/bugs/235944 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailma