| Summary: | Dolphin unresponsive to clicks after opening a file in dual monitor | ||
|---|---|---|---|
| Product: | [Applications] dolphin | Reporter: | Horacio Sanson <hsanson> |
| Component: | general | Assignee: | Dolphin Bug Assignee <dolphin-bugs-null> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | major | CC: | elvis.angelaccio |
| Priority: | NOR | ||
| Version: | 16.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Horacio Sanson
2017-03-27 12:45:23 UTC
Just found an interesting behavior with this issue. Dolphin becomes unresponsive to clicks only when it is in the external screen. I can still drag the dolphin window between my main (laptop) screen and my external monitor. If I drag dolphin and put it in the main laptop screen I can click on any icons/places and everything works as normal. Once I drag the dolphin window to the external monitor screen I can no longer click on any icons or places. I cannot reproduce on my laptop + external monitor setup. If you can reproduce it reliably, please post a gdb backtrace after the freeze happens: - gdb dolphin - make it freeze - ctrl+c in gdb prompt - type 'backtrace' and copy here the output you get. Here is the backtrace. I must make clear that Dolphin is not freezing. I can click the window and move it around, resize it, click the menus and all that works fine. The file and directory icons/list in the files and the places panels are the ones I cannot click or highlight. It is like the mouse over/click event is not being registered in those places. To take the backtrace: - Installed dolphin-dbgsym package via apt-get - Started dolphin with "gdb dolphin" - Executed start/continue inside gdb. - In dolphin opened a PDF file by clicking on it. - Verified that I can no longer click on any other file. - Ctrl-c inside dbg - Executed backtrace (shown below). [~]> gdb dolphin GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1 Copyright (C) 2016 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". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from dolphin...Reading symbols from /usr/lib/debug/.build-id/be/77756e7b53dc825e81156fab3da004640499c9.debug...done. done. (gdb) start Temporary breakpoint 1 at 0x4006b0: file /workspace/build/obj-x86_64-linux-gnu/src/dolphin_dummy.cpp, line 3. Starting program: /usr/bin/dolphin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Temporary breakpoint 1, main (argc=1, argv=0x7fffffffd048) at /workspace/build/obj-x86_64-linux-gnu/src/dolphin_dummy.cpp:3 3 /workspace/build/obj-x86_64-linux-gnu/src/dolphin_dummy.cpp: No such file or directory. (gdb) continue Continuing. [New Thread 0x7fffe210a700 (LWP 25069)] [New Thread 0x7fffdbfff700 (LWP 25070)] Fontconfig warning: "/home/ryujin/.config/fontconfig/conf.d/69-language-selector-ja-jp.conf", line 172: Having multiple values in <test> isn't supported and may not work as expected [New Thread 0x7fffd2b85700 (LWP 25095)] Cannot creat accessible child interface for object: PlacesView(0xc7a650) index: 15 ^C Thread 1 "dolphin" received signal SIGINT, Interrupt. 0x00007ffff7832b5d in poll () at ../sysdeps/unix/syscall-template.S:84 84 ../sysdeps/unix/syscall-template.S: No such file or directory. (gdb) backtrace #0 0x00007ffff7832b5d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x00007fffec54838c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007fffec54849c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007ffff25c373f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007ffff256e0ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007ffff25766cc in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007ffff7b5dde6 in kdemain (argc=1, argv=<optimized out>) at /workspace/build/src/main.cpp:150 #7 0x00007ffff7758830 in __libc_start_main (main=0x4006b0 <main(int, char**)>, argc=1, argv=0x7fffffffd048, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffd038) at ../csu/libc-start.c:291 #8 0x00000000004006e9 in _start () Thanks, indeed the backtrace confirms that there is no freeze, just an idle process waiting for input events. Ah right, this sounds like a duplicate of bug 363548. Is your external monitor high dpi? Indeed this is a duplicate. Both my laptop screen and my external monitor are 2560x1440 resolution. I also found out that the clicks stop working only on the left side of the dolphin window as other people commented on the duplicate issue. Thanks for confirming. *** This bug has been marked as a duplicate of bug 363548 *** |