[Bug 481053] Re: A while after login, mouse and keyboard events go only to a single window
Dug more here, and it's not metacity at fault at all. Reproducion steps: graphical bootup disabled,It also happens in the first GDM login session.If you click a name to start with, then the accessibility button is no longer interactive for clicks for some reason, and vice-versa, if you start by clicking the accessibility options, mouse clicks are afterwards not directed to the name list. Once you log in like this, the events only go to the top panel, no matter what WM I use. Attaching strace to metactiy shows events on the socket (fd/11) during mouse clicks, but no response happens. -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 481053] Re: A while after login, mouse and keyboard events go only to a single window
Checked: Compiz bugs out as well, so I'd assume it's in the xorg layer. I I'm fast in getting a terminal open I can manage a compiz --replace or metacity --replace, and it still fails to function properly. Attached is the xorg.log ** Attachment added: Xorg log file http://launchpadlibrarian.net/35743621/xorg.bugged -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 481053] Re: A while after login, mouse and keyboard events go only to a single window
Testing for tomorrow morning -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 481053] [NEW] A while after login, mouse and keyboard events go only to a single window
Public bug reported: Binary package hint: metacity This has started to crop up recently after fresh boots on my Karmic system. On separate accounts, so it's not a local configruation issue for the user. Logon, start a few programs, and after a while you can no longer alt+tab or change the focused window. If you hit numlock it lights up, you can still switch out of the VT by ctrl+alt+F1 or similar. But no matter what you do in the X session you cannot switch focus to another window. If you start terminals you can launch applications from there ( the panel doesn't respond either, becuase it doesn't get focus) and starting an `xev` gives it focus, but it doesn't register any mouse clicks even when you click the window repeatedly. It does however register keyboard events. however, if you kill gnome-session (thus terminating your login session) and re-login, it suddenly works again and doesn't fark out. This leads me to believe that something is afoul in the original X session that is started, and it is fixed by restarting the X server. However, I cannot prove this hypothesis, so I'm still filing the bug against metacity, because alt tab doesn't work. ProblemType: Bug Architecture: amd64 Date: Thu Nov 12 01:34:04 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: metacity 1:2.28.0-0ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/zsh ProcVersionSignature: Ubuntu 2.6.31-15.50-generic SourcePackage: metacity Uname: Linux 2.6.31-15-generic x86_64 ** Affects: metacity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 481053] Re: A while after login, mouse and keyboard events go only to a single window
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/3562/Dependencies.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/3563/XsessionErrors.txt -- A while after login, mouse and keyboard events go only to a single window https://bugs.launchpad.net/bugs/481053 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
No, can't seem to reproduce it anymore. Good to close this. -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 189192] Re: gdmsetup dialog is to big for 1024 x 768 resolution
Still an issue with the current version of Jaunty, (9.04, beta release) on a netbook (1024x768) with the jaunty netbook remix. This version also released with window clamping enabled, so I can not move the window above the top of the screen, it is thus impossible to correctly click the buttons in gdmsetup. -- gdmsetup dialog is to big for 1024 x 768 resolution https://bugs.launchpad.net/bugs/189192 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
Thought I did, *sigh* Repeatable quite often, simply by playing an album to the end. Reinstalling debug symbols and I'll see once more. Do I have to file a new report for apport to automatically updload stacktrace, or will it attach the new traces if I add to this? -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
(gdb) bt full #0 0x7f6228d8a610 in ?? () No symbol table info available. #1 0x7f624a67c459 in start_thread () from /lib/libpthread.so.0 No symbol table info available. #2 0x7f624317dfcd in clone () from /lib/libc.so.6 No symbol table info available. #3 0x in ?? () No symbol table info available. (gdb) info registers rax0x7f6228d8a610 140059568809488 rbx0xb0 176 rcx0x3 3 rdx0x30 48 rsi0x7f622c898950 140059630733648 rdi0x24effe038731744 rbp0x7f624a88c330 0x7f624a88c330 rsp0x7f622c898008 0x7f622c898008 r8 0x251b19038908304 r9 0x1 1 r100x3a98 15000 r110x7f6243112200 140060008718848 r120x7f622c898a20 140059630733856 r130x0 0 r140x7f624a88c280 140060133999232 r150x0 0 rip0x7f6228d8a610 0x7f6228d8a610 eflags 0x10202 [ IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 ---Type return to continue, or q return to quit--- gs 0x0 0 fctrl 0x37f895 fstat 0x20 32 ftag 0x 65535 fiseg 0x7f62 32610 fioff 0x45e6e047 1172758599 foseg 0x7f62 32610 fooff 0x2c8967c8 747202504 fop0x51f1311 mxcsr 0x1fa4 [ ZE PE IM DM ZM OM UM PM ] (gdb) thread apply all backtrace Thread 9 (Thread 0x7f622c898950 (LWP 23552)): #0 0x7f6228d8a610 in ?? () #1 0x7f624a67c459 in start_thread () from /lib/libpthread.so.0 #2 0x7f624317dfcd in clone () from /lib/libc.so.6 #3 0x in ?? () Thread 7 (Thread 0x7f622d099950 (LWP 23550)): #0 0x7f624a6802e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7f6243a8a67c in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f6243a8aa32 in g_async_queue_pop () from /usr/lib/libglib-2.0.so.0 #3 0x7f624af89255 in action_thread_main (db=0x2978140) at rhythmdb.c:2865 #4 0x7f6243ad7c74 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0x7f624a67c3ba in start_thread () from /lib/libpthread.so.0 #6 0x7f624317dfcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 1 (Thread 0x7f624b3b1800 (LWP 23541)): #0 0x7f6243174496 in poll () from /lib/libc.so.6 #1 0x7f6243ab170f in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f6243ab1d3d in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #3 0x7f6246b32937 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #4 0x00422e41 in main (argc=value optimized out, argv=value optimized out) at main.c:330 #0 0x7f6228d8a610 in ?? () Erm.. or maybe rhythmbox-dbg and rhythmbox-dbgsym aren't the same and the package repo is... Annoying? -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
again with rhythmbox-dbgsym and glib's debug symbols: (gdb) bt full #0 0x7fca01f76610 in ?? () No symbol table info available. #1 0x7fca23861459 in start_thread () from /lib/libpthread.so.0 No symbol table info available. #2 0x7fca1c362fcd in clone () from /lib/libc.so.6 No symbol table info available. #3 0x in ?? () No symbol table info available. (gdb) thread apply all backtrace Thread 36 (Thread 0x7fca1059f950 (LWP 24020)): #0 0x7fca2386556d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1d486675 in g_cond_timed_wait_posix_impl (cond=0x7fca080008c4, entered_mutex=0x7fca1cf1d748, abs_time=value optimized out) at /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c:242 #2 0x7fca1cc6f6bb in g_async_queue_pop_intern_unlocked (queue=0x2068780, try=0, end_time=0x7fca1059ef90) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:365 #3 0x7fca1ccbe209 in g_thread_pool_thread_proxy (data=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gthreadpool.c:220 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x35b5fc0) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 35 (Thread 0x7fca011ab950 (LWP 24019)): #0 0x7fca2386556d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1d486675 in g_cond_timed_wait_posix_impl (cond=0x7fca080008c4, entered_mutex=0x7fca1cf1d748, abs_time=value optimized out) at /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c:242 #2 0x7fca1cc6f6bb in g_async_queue_pop_intern_unlocked (queue=0x2068780, try=0, end_time=0x7fca011aaf90) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:365 #3 0x7fca1ccbe209 in g_thread_pool_thread_proxy (data=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gthreadpool.c:220 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x7fca09182070) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 34 (Thread 0x7fca019ac950 (LWP 24018)): #0 0x7fca2386556d in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1d486675 in g_cond_timed_wait_posix_impl (cond=0x7fca080008c4, entered_mutex=0x7fca1cf1d748, abs_time=value optimized out) at /build/buildd/glib2.0-2.19.10/gthread/gthread-posix.c:242 #2 0x7fca1cc6f6bb in g_async_queue_pop_intern_unlocked (queue=0x2068780, try=0, end_time=0x7fca019abf90) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:365 #3 0x7fca1ccbe209 in g_thread_pool_thread_proxy (data=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gthreadpool.c:220 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x7fca091970f0) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 16 (Thread 0x7fca06ae6950 (LWP 23860)): #0 0x7fca01f76610 in ?? () #1 0x7fca23861459 in start_thread () from /lib/libpthread.so.0 ---Type return to continue, or q return to quit--- #2 0x7fca1c362fcd in clone () from /lib/libc.so.6 #3 0x in ?? () Thread 7 (Thread 0x7fca062e5950 (LWP 23846)): #0 0x7fca238652e9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x7fca1cc6f67c in g_async_queue_pop_intern_unlocked (queue=0x1f6c1a0, try=0, end_time=0x0) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:358 #2 0x7fca1cc6fa32 in IA__g_async_queue_pop (queue=0x1f6c1a0) at /build/buildd/glib2.0-2.19.10/glib/gasyncqueue.c:398 #3 0x7fca2416e255 in action_thread_main (db=0x21a0140) at rhythmdb.c:2865 #4 0x7fca1ccbcc74 in g_thread_create_proxy (data=0x2ff0810) at /build/buildd/glib2.0-2.19.10/glib/gthread.c:635 #5 0x7fca238613ba in start_thread () from /lib/libpthread.so.0 #6 0x7fca1c362fcd in clone () from /lib/libc.so.6 #7 0x in ?? () Thread 1 (Thread 0x7fca24596800 (LWP 23837)): #0 0x7fca1c359496 in poll () from /lib/libc.so.6 #1 0x7fca1cc9670f in g_main_context_iterate (context=0x1e2ca00, block=1, dispatch=1, self=value optimized out) at /build/buildd/glib2.0-2.19.10/glib/gmain.c:2761 #2 0x7fca1cc96d3d in IA__g_main_loop_run (loop=0x2ce9d50) at /build/buildd/glib2.0-2.19.10/glib/gmain.c:2656 #3 0x7fca1fd17937 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #4 0x00422e41 in main (argc=value optimized out, argv=value optimized out) at main.c:330 #0 0x7fca01f76610 in ?? () (gdb) info registers rax0x7fca01f76610 140505593112080 rbx0xb0 176 rcx
[Bug 337294] Re: rhythmbox crashed with SIGSEGV in start_thread()
Attached stacktrace. (Can't filter out sig33 since playback doesn't work then) ** Attachment added: gdb-rhythmbox.txt http://launchpadlibrarian.net/23426687/gdb-rhythmbox.txt -- rhythmbox crashed with SIGSEGV in start_thread() https://bugs.launchpad.net/bugs/337294 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 223400] Re: When right-clicking on a Raw image, I cannot open it in the Gimp
Yes, it is a bit elitistic, but we are talking about a Fair bit more than simple jpeg compression error, you lose 4 bits per pixel channel of information as well. -- When right-clicking on a Raw image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 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 223400] Re: When right-clicking on a Raw image, I cannot open it in the Gimp
Intrepid still does not have the right Mime-types. The Develop in UF-raw is _not_ an option for real use as it involves a meta-stage that is very lossy in comparison. (RAW-Jpeg-Edit is a _bad_ move compared to RAW-Edit) and frankly, even suggesting such a workflow shows an obvious lack of insight into why a photographer would use RAW to begin with. Also, Do note that while f-spot might expect a distinct copy, it should be fully acceptable to use F-spot as the launcher for further editing in the Gimp and not be expected to save the files in the exact same place and work location. For example, Editing would commonly involve changing format to the gimp's internal state so you can keep track of layers/channels, and then exports from that format to others. Now, Just what from this log is it that you expect to see, the page after page of [Debug 14:35:54.816] open uri = file:///media/store/ ..? -- When right-clicking on a Raw image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 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 218812] Re: evince crashed with SIGSEGV in gdk_cairo_set_source_pixbuf()
Unfortunately, Nope. I didn't keep it for tests. -- evince crashed with SIGSEGV in gdk_cairo_set_source_pixbuf() https://bugs.launchpad.net/bugs/218812 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 192457] Re: nautilus crashed with SIGSEGV
messages.0:May 5 09:45:52 Waves kernel: [164588.388120] nautilus[31854]: segfault at 0001 eip 0812f2b8 esp bfa7c620 error 4 Aye, I still do at least. -- nautilus crashed with SIGSEGV https://bugs.launchpad.net/bugs/192457 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 223400] Re: When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp
Hardy Heron 32bit ** Attachment added: example image. http://launchpadlibrarian.net/14358768/IMG_3994.CR2 -- When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 223400] [NEW] When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp
Public bug reported: I have a mix of jpeg and RAW (.CR2, canon) images. When browsing with Nautilus, I can double-click an .CR2 image and it opens in The Gimp, ( meaning: my mime types are configured correctly) but from inside f-spot, it will only recognize UFRaw, and will not let me open it in the Gimp. With normal JPEG's, I'm allowed to use the Gimp from inside f-spot. ** Affects: f-spot (Ubuntu) Importance: Undecided Status: New -- When right-clicking on a CR2 (Raw) image, I cannot open it in the Gimp https://bugs.launchpad.net/bugs/223400 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 179659] Re: evince crashed with SIGSEGV in TextLine::visitSelection()
http://www.cs.yale.edu/homes/aspnes/skip-graphs-journal.pdf Did it for me, I was randomly selecting/Clicking things as a distraction while reading, so doing repeated select/unselect movements. -- evince crashed with SIGSEGV in TextLine::visitSelection() https://bugs.launchpad.net/bugs/179659 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
