[frameworks-baloo] [Bug 370024] New: baloo crashes on login
https://bugs.kde.org/show_bug.cgi?id=370024 Bug ID: 370024 Summary: baloo crashes on login Product: frameworks-baloo Version: 5.24.0 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: pinak.ah...@gmail.com Reporter: j...@vandenoever.info Application: baloo_file_extractor (5.24.0) Qt Version: 5.6.1 Frameworks Version: 5.24.0 Operating System: Linux 4.4.23 x86_64 -- Information about the crash: - What I was doing when the application crashed: Logged into Plasma. This problem happens every time when I log in, unless the file search is disabled. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault Using host libthread_db library "/nix/store/jm1n87rp8vr90j9ahcrfzr57nc2r8vgf-glibc-2.24/lib/libthread_db.so.1". To enable execution of this file add add-auto-load-safe-path /nix/store/djd2r4cnbcx4vfbj1qalg85vjbcslwxv-gcc-5.4.0-lib/lib/libstdc++.so.6.0.21-gdb.py line to your configuration file "/home/oever/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/oever/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" [Current thread is 1 (Thread 0x7fc03b765800 (LWP 2965))] Thread 3 (Thread 0x7fc018eb5700 (LWP 2967)): #0 0x7fc038674dad in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc03447988c in g_main_context_iterate.isra () from /nix/store/jjllibpjpidb4r1amgc3q1760f3iwxqk-glib-2.48.2/lib/libglib-2.0.so.0 #2 0x7fc03447999c in g_main_context_iteration () from /nix/store/jjllibpjpidb4r1amgc3q1760f3iwxqk-glib-2.48.2/lib/libglib-2.0.so.0 #3 0x7fc039472abb in QEventDispatcherGlib::processEvents(QFlags) () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Core.so.5 #4 0x7fc03942336a in QEventLoop::exec(QFlags) () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Core.so.5 #5 0x7fc0392851a4 in QThread::exec() () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Core.so.5 #6 0x7fc03b887755 in ?? () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5DBus.so.5 #7 0x7fc0392895ac in ?? () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Core.so.5 #8 0x7fc037be11f4 in start_thread (arg=0x7fc018eb5700) at pthread_create.c:333 #9 0x7fc03867e12f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 2 (Thread 0x7fc0273eb700 (LWP 2966)): #0 0x7fc038674dad in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fc0337df1d2 in _xcb_conn_wait () from /nix/store/29ni6dkyc46z73cla82431pg8pran369-libxcb-1.12/lib/libxcb.so.1 #2 0x7fc0337e0fd7 in xcb_wait_for_event () from /nix/store/29ni6dkyc46z73cla82431pg8pran369-libxcb-1.12/lib/libxcb.so.1 #3 0x7fc02997ebf9 in ?? () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/qt5/plugins/platforms/../../../libQt5XcbQpa.so.5 #4 0x7fc0392895ac in ?? () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Core.so.5 #5 0x7fc037be11f4 in start_thread (arg=0x7fc0273eb700) at pthread_create.c:333 #6 0x7fc03867e12f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:105 Thread 1 (Thread 0x7fc03b765800 (LWP 2965)): [KCrash Handler] #6 __memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:292 #7 0x7fc03ab27483 in Baloo::PostingCodec::decode(QByteArray const&) () from /nix/store/r5dwdwsfbaihzy1k8ajh6x0pl8db2x08-baloo-5.24.0/lib/libKF5BalooEngine.so.5 #8 0x7fc03ab11fe4 in Baloo::PostingDB::get(QByteArray const&) () from /nix/store/r5dwdwsfbaihzy1k8ajh6x0pl8db2x08-baloo-5.24.0/lib/libKF5BalooEngine.so.5 #9 0x7fc03ab245dd in Baloo::WriteTransaction::commit() () from /nix/store/r5dwdwsfbaihzy1k8ajh6x0pl8db2x08-baloo-5.24.0/lib/libKF5BalooEngine.so.5 #10 0x7fc03ab1aee2 in Baloo::Transaction::commit() () from /nix/store/r5dwdwsfbaihzy1k8ajh6x0pl8db2x08-baloo-5.24.0/lib/libKF5BalooEngine.so.5 #11 0x0040917c in Baloo::App::processNextFile() () #12 0x7fc039457a96 in ?? () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Core.so.5 #13 0x7fc03944ca6b in QObject::event(QEvent*) () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Core.so.5 #14 0x7fc039d21a5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /nix/store/w7mcna6qc1b9c55ph95zf960448lcg70-qtbase-5.6.1-1/lib/libQt5Widgets.so.5 #15 0x7fc039d26f20 in QApplication::notify(QObject*, QEvent*) () from /nix/store/w7mcna6
[plasmashell] [Bug 365422] New: digital clock takes up too little width on the horizontal plasma panel
https://bugs.kde.org/show_bug.cgi?id=365422 Bug ID: 365422 Summary: digital clock takes up too little width on the horizontal plasma panel Product: plasmashell Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Digital Clock Assignee: mklape...@kde.org Reporter: j...@vandenoever.info CC: plasma-b...@kde.org The digital clock on a horizontal plasma panel takes up too little width. The time is rendered outside of the space that is taken up by the clock. The time is drawn on top of other widgets. Removing the panel and adding a new default panel does not help. Changing the font does not help. Adding seconds or date to the display does not help. On a vertical plasma panel, the digital clock is fine. Reproducible: Always Steps to Reproduce: 1. start KDE in a default setup Actual Results: Digital clock is shown wrong on the horizontal panel. Part of the clock is outside of the display. Expected Results: Digital clock takes up enough space so that it renders only in the space that it takes up. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365422] digital clock takes up too little width on the horizontal plasma panel
https://bugs.kde.org/show_bug.cgi?id=365422 --- Comment #1 from Jos van den Oever --- Created attachment 100022 --> https://bugs.kde.org/attachment.cgi?id=100022&action=edit bad digital clock -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365422] digital clock takes up too little width on the horizontal plasma panel
https://bugs.kde.org/show_bug.cgi?id=365422 --- Comment #2 from Jos van den Oever --- Created attachment 100023 --> https://bugs.kde.org/attachment.cgi?id=100023&action=edit bad digital clock -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 365594] New: Use 7z instead of unrar
https://bugs.kde.org/show_bug.cgi?id=365594 Bug ID: 365594 Summary: Use 7z instead of unrar Product: ark Version: 16.04.3 Platform: Other URL: http://www.7-zip.org/history.txt OS: All Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: plugins Assignee: rthoms...@gmail.com Reporter: j...@vandenoever.info CC: elvis.angelac...@kdemail.net Ark uses the unfree program unrar. 7z can also open RAR files. Since version 15.12 (november 2015), it can open RARv5 files too. So Ark can drop the need for unrar and use 7z instead. Unarchiver also supports opening RAR files. It has a command-line version called unar which is .e.g. packaged by Debian. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 365594] Use 7z instead of unrar
https://bugs.kde.org/show_bug.cgi?id=365594 --- Comment #2 from Jos van den Oever --- Excellent! I should have read the README.packagers more carefully. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 285603] xrandr --scale as option Settings/Display and Monitor for laptops
https://bugs.kde.org/show_bug.cgi?id=285603 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #1 from Jos van den Oever --- The dialog 'Display and Monitor' from 'System Settings' has an option 'Scale Display' that allows you to scale up for use on high resolution displays. There is no option to scale down: the slider has magnification factors from 1 to 3, but not lower than 1. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #48 from Jos van den Oever --- Confirming. konversation blinking icon eats a lot of CPU time. When konversation stops blinking, the CPU usages is reduced immediately. X.org 1.17.4, Plasma 5.7, KF 16.04.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #49 from Jos van den Oever --- To be more precise, the CPU usages is caused by the animated konversation icon in the system tray. A highlighted konversation in the taskbar does not affect CPU usage. When konversation starts blinking CPU usage goes to 30% and stays there. CPU usage immediately disappears when konversation stops blinking. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #51 from Jos van den Oever --- One of the advantages of QML is to show animations efficiently with low CPU usage. So something very strange must be going on here. I'm not familiar with profiling QML applications, but could try it if someone points me to description of how to do it. I'd prefer to connect the profiler to the running plasmashell. I've no debug symbols installed for Plasma. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 356479] plasmashell uses 100% CPU when there is an animation in the task bar
https://bugs.kde.org/show_bug.cgi?id=356479 --- Comment #52 from Jos van den Oever --- I noticed this commit in the Plasma 5.7.2 which may alleviate the problem a bit: https://quickgit.kde.org/?p=plasma-workspace.git&a=commit&h=1caec23e0e9201e7353e15267f9ea28d9c3653f1 -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 366297] New: Z-index is not indepenent of layers.
https://bugs.kde.org/show_bug.cgi?id=366297 Bug ID: 366297 Summary: Z-index is not indepenent of layers. Product: karbon Version: 2.9.8 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: opendocument Assignee: ja...@gmx.net Reporter: j...@vandenoever.info Created attachment 100394 --> https://bugs.kde.org/attachment.cgi?id=100394&action=edit drawing with boxes with different z-index. The boxes should be stacked. In ODF, they layer to which a drawing object belongs should not affect the z-index. Nevertheless, the UI can modify the z-index for all object at once. Karbon does not respect the z-index of objects if they are in different layers when an ODG file with objects with different z-index per layer is loaded. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 366297] Z-index is not indepenent of layers.
https://bugs.kde.org/show_bug.cgi?id=366297 --- Comment #1 from Jos van den Oever --- Created attachment 100395 --> https://bugs.kde.org/attachment.cgi?id=100395&action=edit Screenshot of how the boxes should look. Each box shows the name of the layer to which it belongs. -- You are receiving this mail because: You are watching all bug changes.
[karbon] [Bug 366297] Z-index is not indepenent of layers.
https://bugs.kde.org/show_bug.cgi?id=366297 --- Comment #2 from Jos van den Oever --- Created attachment 100396 --> https://bugs.kde.org/attachment.cgi?id=100396&action=edit screenshot of karbon with wrong ordering of boxes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365422] digital clock takes up too little width on the horizontal plasma panel
https://bugs.kde.org/show_bug.cgi?id=365422 --- Comment #4 from Jos van den Oever --- I've not upgraded to 16.08 yet, waiting on the distro. On 16.04, it's still the case. Is there a reason to think it's fixed? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365422] digital clock takes up too little width on the horizontal plasma panel
https://bugs.kde.org/show_bug.cgi?id=365422 --- Comment #8 from Jos van den Oever --- Created attachment 100730 --> https://bugs.kde.org/attachment.cgi?id=100730&action=edit plasma configuration -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365422] digital clock takes up too little width on the horizontal plasma panel
https://bugs.kde.org/show_bug.cgi?id=365422 --- Comment #9 from Jos van den Oever --- Created attachment 100731 --> https://bugs.kde.org/attachment.cgi?id=100731&action=edit lower edge panel plasma configuration which as clock with overlapping text This is the buggy configuration. The previous configuration was for a vertical panel which has no bugs. -- You are receiving this mail because: You are watching all bug changes.
[kde-cli-tools] [Bug 363459] New: kde-cli-tools tools hang after running
https://bugs.kde.org/show_bug.cgi?id=363459 Bug ID: 363459 Summary: kde-cli-tools tools hang after running Product: kde-cli-tools Version: 5.6.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: j...@vandenoever.info On my machine most kde-cli-tools hang in the destructor, even after running with no argument or running with --help. $ kioclient/kde-open5 kde-open5: Syntax error, not enough arguments Attaching with gdb gives this backtrace: (gdb) bt #0 0x7f5c3bdfb02f in pthread_cond_wait@@GLIBC_2.3.2 () from /nix/store/68gvzfvm4886b4ni6wfl1j5n9di69zid-glibc-2.23/lib/libpthread.so.0 #1 0x7f5c3dca253b in QWaitCondition::wait(QMutex*, unsigned long) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #2 0x7f5c3dc9b9eb in QSemaphore::acquire(int) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #3 0x7f5c3de8eecf in QMetaObject::activate(QObject*, int, int, void**) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #4 0x7f5c3de8f5ef in QObject::destroyed(QObject*) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #5 0x7f5c3de960d5 in QObject::~QObject() () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #6 0x7f5c29714509 in Breeze::Style::~Style() () from /nix/store/gjm8yzbapdz9glipbzjbrq8k140khmwz-breeze-qt5-5.6.4/lib/qt5/plugins/styles/breeze.so #7 0x7f5c3de8efbe in QMetaObject::activate(QObject*, int, int, void**) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #8 0x7f5c3de8f5ef in QObject::destroyed(QObject*) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #9 0x7f5c3de960d5 in QObject::~QObject() () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #10 0x7f5c29727237 in Breeze::StylePlugin::~StylePlugin() () from /nix/store/gjm8yzbapdz9glipbzjbrq8k140khmwz-breeze-qt5-5.6.4/lib/qt5/plugins/styles/breeze.so #11 0x7f5c3de59bf9 in ?? () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #12 0x7f5c3de4fe12 in ?? () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #13 0x7f5c3de4ff49 in ?? () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #14 0x7f5c3de964b7 in QObject::~QObject() () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #15 0x7f5c3de4f0b9 in QFactoryLoader::~QFactoryLoader() () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #16 0x7f5c3e7dbce9 in ?? () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Widgets.so.5 #17 0x7f5c3cff6d78 in __run_exit_handlers () from /nix/store/68gvzfvm4886b4ni6wfl1j5n9di69zid-glibc-2.23/lib/libc.so.6 #18 0x7f5c3cff6dc5 in exit () from /nix/store/68gvzfvm4886b4ni6wfl1j5n9di69zid-glibc-2.23/lib/libc.so.6 #19 0x00403bcb in checkArgumentCount (count=0, min=1, max=0) at /home/oever/src/kde-cli-tools/kioclient/kioclient.cpp:193 #20 0x004044b7 in ClientApp::doIt (this=0x7ffec64af2f0, parser=...) at /home/oever/src/kde-cli-tools/kioclient/kioclient.cpp:284 #21 0x00403a60 in main (argc=1, argv=0x7ffec64af548) at /home/oever/src/kde-cli-tools/kioclient/kioclient.cpp:174 I thought perhaps breeze was the problem. After uninstalling breeze, I get: (gdb) bt #0 0x7fc0ae21402f in pthread_cond_wait@@GLIBC_2.3.2 () from /nix/store/68gvzfvm4886b4ni6wfl1j5n9di69zid-glibc-2.23/lib/libpthread.so.0 #1 0x7fc0b00bb53b in QWaitCondition::wait(QMutex*, unsigned long) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #2 0x7fc0b00b49eb in QSemaphore::acquire(int) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #3 0x7fc0b02a7ecf in QMetaObject::activate(QObject*, int, int, void**) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #4 0x7fc0b02a85ef in QObject::destroyed(QObject*) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #5 0x7fc0b02af0d5 in QObject::~QObject() () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #6 0x7fc09bb0a4d7 in Oxygen::Style::~Style() () from /nix/store/i5fv6qbrv7pj20lqzk80kbc3jgvv5hz8-oxygen-5.6.4/lib/qt5/plugins/styles/oxygen.so #7 0x7fc0b02a7fbe in QMetaObject::activate(QObject*, int, int, void**) () from /nix/store/pwbrmrmhwik1apnbw104gaikp3w1j63b-qtbase-5.6.0-dev/lib/libQt5Core.so.5 #8 0x7fc0b02a8
[frameworks-kservice] [Bug 352756] Database corruption upon upgrading to 5.14.0
https://bugs.kde.org/show_bug.cgi?id=352756
Jos van den Oever changed:
What|Removed |Added
CC||j...@vandenoever.info
--- Comment #12 from Jos van den Oever ---
I'm seeing something similar with 5.19.0. Did the mentioned patch make it into
master?
$ kbuildsycoca5 --version
kbuildsycoca5 5.19.0
$ kbuildsycoca5 --noincremental --global
kbuildsycoca5 running...
kbuildsycoca5(3331)/default unknown: Recreating ksycoca file
("/home/oever/.local/share/ksycoca/ksycoca5_en", version 303)
kbuildsycoca5(3331)/default unknown: Menu "applications-kmenuedit.menu" not
found.
kbuildsycoca5(3331)/default unknown: Saving
$ kcminit
kcminit(3336)/kf5.kservice.sycoca unknown: ERROR: KSycoca database corruption!
kcminit(3336)/kf5.kservice.sycoca unknown: ERROR: KSycoca database corruption!
kcminit(3336)/kf5.kservice.sycoca unknown: ERROR: KSycoca database corruption!
kcminit(3336)/kf5.kservice.sycoca unknown: ERROR: KSycoca database corruption!
kcminit(3336)/default unknown: Recreating ksycoca file
("/home/oever/.cache/ksycoca5_en_ZDaXpKg+fqgYRYEHHfhMEXeSCyc=", version 303)
kcminit(3336)/default unknown: Menu "applications-kmenuedit.menu" not found.
kcminit(3336)/default unknown: Saving
kcminit(3336)/kf5.kservice.sycoca unknown: ERROR: KSycoca database corruption!
kcminit(3336)/default unknown: Initializing "kded_touchpad" :
"kcminit_touchpad"
kcminit(3336)/default unknown: Width: 3852 height: 3046
kcminit(3336)/default unknown: Approx. resX: 42 resY: 60
kcminit(3336)/default unknown: Touchpad resolution: x: 53 y: 55
kcminit(3336)/default unknown: Final resolution x: 53 y: 55
kcminit(3336)/default unknown: Initializing "kcm_style" : "kcminit_style"
kcminit(3336)/default unknown: QFile::copy: Empty or null file name
kcminit(3336)/default unknown: Initializing "kcm_input" : "kcminit_mouse"
kcminit(3336)/default unknown: Initializing "kcm_access" : "kcminit_access"
--
You are receiving this mail because:
You are watching all bug changes.
[kontact] [Bug 353761] Kmail crashing on folder change
https://bugs.kde.org/show_bug.cgi?id=353761 Jos van den Oever changed: What|Removed |Added CC||j...@vandenoever.info --- Comment #4 from Jos van den Oever --- I can confirm the crash with KMail 4.14.3, KDE Development Platform 4.14.18 running on Plasma 5 desktop. The crash happens when a new folder is opened for which communication with akonadi is needed. When using the oxygen icon theme the crash does not happen. It happens with breezy and breezy-dark. There must be a pixmap missing and the absence is not handled nicely. Thread 1 "kmail" received signal SIGSEGV, Segmentation fault. 0x7ff8756c4b77 in QPixmap::copy(QRect const&) const () from /nix/store/p814jwfc6anwkr044zcvlgqkrxywyq5i-qt-4.8.7/lib/libQtGui.so.4 (gdb) back #0 0x7ff8756c4b77 in QPixmap::copy(QRect const&) const () from /nix/store/p814jwfc6anwkr044zcvlgqkrxywyq5i-qt-4.8.7/lib/libQtGui.so.4 #1 0x7ff8756c5832 in QPixmap::QPixmap(QPixmap const&) () from /nix/store/p814jwfc6anwkr044zcvlgqkrxywyq5i-qt-4.8.7/lib/libQtGui.so.4 #2 0x7ff87a7cd6f8 in KPixmapSequence::frameAt(int) const () from /nix/store/fppffg4ck2pb06gnx9jrqirdsf6kvq73-kdelibs-4.14.18/lib/libkdeui.so.5 #3 0x7ff8778e9c05 in Akonadi::DelegateAnimator::sequenceFrame(QModelIndex const&) () from /nix/store/dsppv8rzmg1hnvsfv4m3g0k6z0jfp37q-kdepimlibs-4.14.3/lib/libakonadi-kde.so.4 #4 0x7ff877843c34 in Akonadi::CollectionStatisticsDelegate::initStyleOption(QStyleOptionViewItem*, QModelIndex const&) const () from /nix/store/dsppv8rzmg1hnvsfv4m3g0k6z0jfp37q-kdepimlibs-4.14.3/lib/libakonadi-kde.so.4 #5 0x7ff875b7a63c in QStyledItemDelegate::paint(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /nix/store/p814jwfc6anwkr044zcvlgqkrxywyq5i-qt-4.8.7/lib/libQtGui.so.4 #6 0x7ff877843dcc in Akonadi::CollectionStatisticsDelegate::paint(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /nix/store/dsppv8rzmg1hnvsfv4m3g0k6z0jfp37q-kdepimlibs-4.14.3/lib/libakonadi-kde.so.4 #7 0x7ff875b189e5 in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /nix/store/p814jwfc6anwkr044zcvlgqkrxywyq5i-qt-4.8.7/lib/libQtGui.so.4 #8 0x7ff875b1c170 in QTreeView::drawTree(QPainter*, QRegion const&) const () from /nix/store/p814jwfc6anwkr044zcvlgqkrxywyq5i-qt-4.8.7/lib/libQtGui.so.4 #9 0x7ff875b1fbef in QTreeView::paintEvent(QPaintEvent*) () -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 362277] New: Dr Konqi shows two 'Help' buttons in one dialog
https://bugs.kde.org/show_bug.cgi?id=362277 Bug ID: 362277 Summary: Dr Konqi shows two 'Help' buttons in one dialog Product: drkonqi Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: j...@vandenoever.info Reproducible: Didn't try Steps to Reproduce: 1. Get some software that used Dr. Konqi to have a crash 2. Get an error in sending the bug report 3. End up in a dialog with two Help buttons Actual Results: A dialog with two help buttons. The dialog title is 'Sending the Crash Report'. In the lower left are two buttons labelled 'Help'. Expected Results: At most one button labelled 'Help'. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 362277] Dr Konqi shows two 'Help' buttons in one dialog
https://bugs.kde.org/show_bug.cgi?id=362277 --- Comment #1 from Jos van den Oever --- Created attachment 98604 --> https://bugs.kde.org/attachment.cgi?id=98604&action=edit Screenshot of the dialog. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362636] New: konsole, kwrite and konversation windows often disappear when disconnecting monitor
https://bugs.kde.org/show_bug.cgi?id=362636 Bug ID: 362636 Summary: konsole, kwrite and konversation windows often disappear when disconnecting monitor Product: kwin Version: 5.6.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: j...@vandenoever.info Created attachment 98761 --> https://bugs.kde.org/attachment.cgi?id=98761&action=edit picture of tabbox with empty entries for konsole windows (artist impression) Connecting / disconnecting a monitor confuses kwin_x11. The applications konsole 16.04.0, kwrite (16.04.0) and konversation (1.6) with (kf 5.21.0) can get lost when disconnecting an external monitor from a laptop. Both screens are 1920x1080. The applications still occupy a space in the tabbox, but that space is empty: not icon and no title. The windows also disappear from the task manager. The applications are still running. This is pretty weird. It gets weirder. It is possible to make KWin find the windows again. The applications are still running and can be controlled with dbus/qdbusviewer. By setting the QMainWindow widget to minimized and then putting it back to normal, the windows show up in kwin_x11 tabbox and the task manager again: dbus-send --session --dest=org.kde.konsole --type=method_call --print-reply /konsole/MainWindow_1 org.qtproject.Qt.QWidget.showMinimized dbus-send --session --dest=org.kde.konsole --type=method_call --print-reply /konsole/MainWindow_1 org.qtproject.Qt.QWidget.showNormal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362636] konsole, kwrite and konversation windows often disappear when disconnecting monitor
https://bugs.kde.org/show_bug.cgi?id=362636 --- Comment #2 from Jos van den Oever --- > Qt 5.6.0? No, Qt 5.5.1. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362636] konsole, kwrite and konversation windows often disappear when disconnecting monitor
https://bugs.kde.org/show_bug.cgi?id=362636 --- Comment #4 from Jos van den Oever --- > Qt5 clients are until today rather completely unreliable regarding screen > layout changes How is that even possible? The X clients are fundamental to a widget set. I've a script with the dbus commands I pasted above. Those make the issue barely bearable. KF5 really feels like an improvement if it were not for all the bugs. I will provide the output when the issues happens again. (probably tomorrow when I move to my work desk). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362636] konsole, kwrite and konversation windows often disappear when disconnecting monitor
https://bugs.kde.org/show_bug.cgi?id=362636 --- Comment #7 from Jos van den Oever --- Created attachment 98867 --> https://bugs.kde.org/attachment.cgi?id=98867&action=edit collated output from "xwininfo -tree -root", "xwininfo -id 0x12000e3" etc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362636] konsole, kwrite and konversation windows often disappear when disconnecting monitor
https://bugs.kde.org/show_bug.cgi?id=362636 --- Comment #6 from Jos van den Oever --- Here's what I'm doing: 1) Start from multihead config with external monitor as main screen 2) Run 'Display Configuration' and disable external monitor 3) Konversation, Konsole, KWrite disappear, xterm, firefox, kmail (qt4), gkrellm remain. Plasma and KRunner also still ok I'm putting the output of xwininfo as attachments. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362636] konsole, kwrite and konversation windows often disappear when disconnecting monitor
https://bugs.kde.org/show_bug.cgi?id=362636 --- Comment #8 from Jos van den Oever --- The coordinates of the qt5 widgets are far outside the screen. Perhaps the taskbar filters out windows that are outside its view. Minimizing and maximizing via dbus brings the windows back in view and in the task manager. -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 358638] New: KDE daemon crash after desktop startup
https://bugs.kde.org/show_bug.cgi?id=358638 Bug ID: 358638 Summary: KDE daemon crash after desktop startup Product: kdelibs Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: kded Assignee: unassigned-b...@kde.org Reporter: j...@vandenoever.info Application: kded4 (4.14.10) KDE Platform Version: 4.14.10 Qt Version: 4.8.7 Operating System: Linux 4.3.3 x86_64 -- Information about the crash: - What I was doing when the application crashed: I had just started up KDE and connected to the ethernet. This connection worked, but the network manager still showed an icon for not being connected. -- Backtrace: Application: KDE Daemon (kded4), signal: Segmentation fault Using host libthread_db library "/nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libthread_db.so.1". To enable execution of this file add add-auto-load-safe-path /nix/store/81gmdmvsi9a3iyhk4hnxamm8hg8d82sx-gcc-4.9.3/lib/libstdc++.so.6.0.20-gdb.py line to your configuration file "/home/oever/.gdbinit". To completely disable this security protection add set auto-load safe-path / line to your configuration file "/home/oever/.gdbinit". For more information about this security protection see the "Auto-loading safe path" section in the GDB manual. E.g., run from the shell: info "(gdb)Auto-loading safe path" [Current thread is 1 (Thread 0x7f6e89eb4780 (LWP 1260))] Thread 2 (Thread 0x7f6e62553700 (LWP 1277)): #0 0x7f6e86a614bd in poll () from /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libc.so.6 #1 0x7f6e8358d9c4 in g_main_context_iterate.isra () from /nix/store/vskixqm70apvvhpzizxyqq369lmfpv3b-glib-2.44.1/lib/libglib-2.0.so.0 #2 0x7f6e8358dacc in g_main_context_iteration () from /nix/store/vskixqm70apvvhpzizxyqq369lmfpv3b-glib-2.44.1/lib/libglib-2.0.so.0 #3 0x7f6e88854437 in QEventDispatcherGlib::processEvents(QFlags) () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #4 0x7f6e88825e81 in QEventLoop::processEvents(QFlags) () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #5 0x7f6e88826195 in QEventLoop::exec(QFlags) () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #6 0x7f6e88723a19 in QThread::exec() () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #7 0x7f6e888077e3 in ?? () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #8 0x7f6e8872622f in ?? () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #9 0x7f6e88485484 in start_thread () from /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libpthread.so.0 #10 0x7f6e86a6a05d in clone () from /nix/store/npfsi1d9ka8zwnxzn3sr08hbwvpapyk7-glibc-2.21/lib/libc.so.6 Thread 1 (Thread 0x7f6e89eb4780 (LWP 1260)): [KCrash Handler] #6 0x7f6e658f6b59 in Knm::Connection::setting(Knm::Setting::Type) const () from /nix/store/afnld464f81xlcm47cv1aji2pljvp7fa-networkmanagement-0.9.0.9/lib/libknminternals.so.4 #7 0x7f6e65b43518 in WirelessNetworkInterfaceActivatableProvider::handleAdd(Knm::Connection*) () from /nix/store/afnld464f81xlcm47cv1aji2pljvp7fa-networkmanagement-0.9.0.9/lib/libknmservice.so.4 #8 0x7f6e65b42759 in WirelessNetworkInterfaceActivatableProvider::networkAppeared(QString const&) () from /nix/store/afnld464f81xlcm47cv1aji2pljvp7fa-networkmanagement-0.9.0.9/lib/libknmservice.so.4 #9 0x7f6e8883ae8a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #10 0x7f6e656dd402 in Solid::Control::WirelessNetworkInterfaceEnvironment::networkAppeared(QString const&) () from /nix/store/afnld464f81xlcm47cv1aji2pljvp7fa-networkmanagement-0.9.0.9/lib/libsolidcontrolfuture.so #11 0x7f6e656dd89d in Solid::Control::WirelessNetworkInterfaceEnvironment::accessPointAppearedInternal(QString const&) () from /nix/store/afnld464f81xlcm47cv1aji2pljvp7fa-networkmanagement-0.9.0.9/lib/libsolidcontrolfuture.so #12 0x7f6e8883ae8a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/rffviirg2frs1hh0lqk4hsa8sldg4mls-qt-4.8.7/lib/libQtCore.so.4 #13 0x7f6e654c6f25 in Solid::Control::WirelessNetworkInterfaceNm09::accessPointAppeared(QString const&) () from /nix/store/afnld464f81xlcm47cv1aji2pljvp7fa-networkmanagement-0.9.0.9/lib/libsolidcontrolnm09.so.4 #14 0x7f6e654c716d in Solid::Control::WirelessNetworkInterfaceNm09::_k_accessPointAdded(QString const&) () from /nix/store/afnld464f81xlcm47cv1aji2pljvp7fa-networkmanagement-0.9.0.9/lib/libsolidcontrolnm09.so.4 #15 0x7f6e8883ae8a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /nix/store/rffviirg2frs1hh0l
