[kontact] [Bug 361794] New: Crash when attempting to read mail from the notification
https://bugs.kde.org/show_bug.cgi?id=361794 Bug ID: 361794 Summary: Crash when attempting to read mail from the notification Product: kontact Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: aux...@gmail.com Application: kontact (5.1.90 rc) Qt Version: 5.6.0 Frameworks Version: 5.21.0 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: When I attempt to read the email from the new mail notification, kontact crashes. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9f0471e7c0 (LWP 5713))] Thread 32 (Thread 0x7f9ee7588700 (LWP 5714)): #0 0x7f9f013a1bbd in poll () at /lib64/libc.so.6 #1 0x7f9efab48422 in () at /usr/lib64/libxcb.so.1 #2 0x7f9efab4a00f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7f9ee9f0d979 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7f9f01cb5079 in () at /usr/lib64/libQt5Core.so.5 #5 0x7f9ef9596754 in () at /usr/X11R6/lib64/libGL.so.1 #6 0x7f9efa7250a4 in start_thread () at /lib64/libpthread.so.0 #7 0x7f9f013a9fed in clone () at /lib64/libc.so.6 Thread 31 (Thread 0x7f9edea08700 (LWP 5715)): #0 0x7f9f013a1bbd in poll () at /lib64/libc.so.6 #1 0x7f9ef9f07e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9ef9f07f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9f01ec63fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9f01e7404b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9f01cb05da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f9f005ef095 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f9f01cb5079 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f9ef9596754 in () at /usr/X11R6/lib64/libGL.so.1 #9 0x7f9efa7250a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7f9f013a9fed in clone () at /lib64/libc.so.6 Thread 30 (Thread 0x7f9edd5f0700 (LWP 5716)): #0 0x7f9efa72903f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9efecae753 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f9efecae779 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f9ef9596754 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f9efa7250a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f9f013a9fed in clone () at /lib64/libc.so.6 Thread 29 (Thread 0x7f9e93ebd700 (LWP 5717)): #0 0x7f9f013a1bbd in poll () at /lib64/libc.so.6 #1 0x7f9ef9f07e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9ef9f07f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9f01ec63fb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f9f01e7404b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f9f01cb05da in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f9f01cb5079 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f9ef9596754 in () at /usr/X11R6/lib64/libGL.so.1 #8 0x7f9efa7250a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f9f013a9fed in clone () at /lib64/libc.so.6 Thread 28 (Thread 0x7f9e92516700 (LWP 5718)): #0 0x7f9efa72903f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9efe9ba5ed in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f9efecdd221 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f9ef9596754 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f9efa7250a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f9f013a9fed in clone () at /lib64/libc.so.6 Thread 27 (Thread 0x7f9e91ce6700 (LWP 5719)): #0 0x7f9efa72903f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9efe9bb5c3 in () at /usr/lib64/libQt5WebKit.so.5 #2 0x7f9efecdd221 in () at /usr/lib64/libQt5WebKit.so.5 #3 0x7f9ef9596754 in () at /usr/X11R6/lib64/libGL.so.1 #4 0x7f9efa7250a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f9f013a9fed in clone () at /lib64/libc.so.6 Thread 26 (Thread 0x7f9e7d2c9700 (LWP 5720)): #0 0x7f9f0139dc8d in read () at /lib64/libc.so.6 #1 0x7f9ef959573c in () at /usr/X11R6/lib64/libGL.so.1 #2 0x7f9ef095fbf7 in () at /usr/lib64/tls/libnvidia-tls.so.304.128 #3 0x7f9ef9f48b60 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f9ef9f07999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #5 0x7f9ef9f07df8 in () at /usr/lib64/libglib-2.0.so.0 #6 0x7f9ef9f07f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #7 0x7f9f01ec63fb in Q
[i18n] [Bug 361795] New: ki18n5.js installed by both ki18n and kde-l10n
https://bugs.kde.org/show_bug.cgi?id=361795 Bug ID: 361795 Summary: ki18n5.js installed by both ki18n and kde-l10n Product: i18n Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: aa...@kde.org Reporter: aro...@archlinux.org The files usr/share/locale/*/LC_SCRIPTS/ki18n5/ki18n5.js are installed by both ki18n and the kde-l10n-* packages, causing file conflicts. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 359887] Neon packages change DISTRIB_ID in /etc/lsb-release
https://bugs.kde.org/show_bug.cgi?id=359887 --- Comment #8 from Laurent Bonnaud --- Here is another side effect of neon packages messing with /etc/lsb-release: Unpacking base-files (9.4ubuntu4) over (9.4ubuntu3+p16.04+git20160414.1434) ... Processing triggers for plymouth-theme-kubuntu-text (1:16.04ubuntu2) ... dpkg: warning: version '/etc/lsb-release' has bad syntax: version number does not start with digit update-initramfs: deferring update (trigger activated) Processing triggers for plymouth-theme-ubuntu-gnome-text (16.04.4) ... dpkg: warning: version '/etc/lsb-release' has bad syntax: version number does not start with digit -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361793] View/Headers menu does not show choices
https://bugs.kde.org/show_bug.cgi?id=361793 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from Laurent Montel --- Install kdepim-addons too. Regards -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346967] Crash on picking a color (either through the Color Picker or the Advanced Color Selector)
https://bugs.kde.org/show_bug.cgi?id=346967 --- Comment #15 from Douglas --- There are 56117 lines and it overflows the text buffer. How do I output it and send it to you? On Fri, Apr 15, 2016 at 8:58 AM, Boudewijn Rempt via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #14 from Boudewijn Rempt --- > You don't need the mail, just click on the link for the bug, and there it > is > :-) > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361325] Immense problems and inconsistencies in shortcut dialog, new schemes created by users are not loaded.
https://bugs.kde.org/show_bug.cgi?id=361325 --- Comment #8 from Raghavendra kamath --- The shortcuts are now saved thanks boud for fixing those Now the problem is with saving and loading new shortcut schemes. they seem to get saved in /.local/share/krita/shortcuts but they don't show up in the drop-down list. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 359887] Neon packages change DISTRIB_ID in /etc/lsb-release
https://bugs.kde.org/show_bug.cgi?id=359887 --- Comment #9 from Francesco Chicchiriccò --- (In reply to Laurent Bonnaud from comment #8) > Here is another side effect of neon packages messing with /etc/lsb-release: > > Unpacking base-files (9.4ubuntu4) over (9.4ubuntu3+p16.04+git20160414.1434) > ... > Processing triggers for plymouth-theme-kubuntu-text (1:16.04ubuntu2) ... > dpkg: warning: version '/etc/lsb-release' has bad syntax: version number > does not start with digit > update-initramfs: deferring update (trigger activated) > Processing triggers for plymouth-theme-ubuntu-gnome-text (16.04.4) ... > dpkg: warning: version '/etc/lsb-release' has bad syntax: version number > does not start with digit Yep, I had the same trouble: had to manually set it via echo 9.4 > /etc/postgresql-common/supported_versions -- You are receiving this mail because: You are watching all bug changes.
[frameworks-bluez-qt] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 David Rosca changed: What|Removed |Added Latest Commit||http://commits.kde.org/blue ||devil/9c5fda0232bc181484300 ||44b2f73617b6cef12e1 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from David Rosca --- Git commit 9c5fda0232bc18148430044b2f73617b6cef12e1 by David Rosca. Committed on 15/04/2016 at 07:22. Pushed by drosca into branch 'Plasma/5.6'. Restore adapter powered state after 1s delay Workaround issue in bluez-qt. M +6-1src/kded/devicemonitor.cpp http://commits.kde.org/bluedevil/9c5fda0232bc18148430044b2f73617b6cef12e1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346967] Crash on picking a color (either through the Color Picker or the Advanced Color Selector)
https://bugs.kde.org/show_bug.cgi?id=346967 --- Comment #16 from Boudewijn Rempt --- You can go to the bugzilla web interface and add it as an attachement. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361784] Launch an application on a second monitor when launching from app launcher on panel on that monitor
https://bugs.kde.org/show_bug.cgi?id=361784 --- Comment #2 from hrvo...@jankovci.net --- Yes, this is the behavior I want. However, it does not work as expected with Teamviewer and Chrome. I clicked on Chrome on second monitor application launcher and it opened a window on a first screen. Please see video attached. https://www.youtube.com/watch?v=OrOloe4GJv4&feature=youtu.be -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361783] Add "Show Rulers" checkbox to "Grid and Guides" docker
https://bugs.kde.org/show_bug.cgi?id=361783 --- Comment #2 from Amir Adar --- I didn't get the impression that it was cluttered, but it could be just me. At any rate, in my opinion, "Show Rulers" is the one option painfully missing from it. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353654] Extend Kate's session to stash unsaved documents / changes
https://bugs.kde.org/show_bug.cgi?id=353654 yes456 changed: What|Removed |Added CC||yes...@gmail.com --- Comment #3 from yes456 --- +1 must have -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 353654] Extend Kate's session to stash unsaved documents / changes
https://bugs.kde.org/show_bug.cgi?id=353654 yes456 changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from yes456 --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361793] View/Headers menu does not show choices
https://bugs.kde.org/show_bug.cgi?id=361793 --- Comment #2 from Ian --- (In reply to Laurent Montel from comment #1) > Install kdepim-addons too. > Regards I've never had to do this before, is this new? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361784] Launch an application on a second monitor when launching from app launcher on panel on that monitor
https://bugs.kde.org/show_bug.cgi?id=361784
Thomas Lübking changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Thomas Lübking ---
They'll demand a specific position.
Create custom window/application settings to ignore geometry requests ("apply
initially" will likely do)
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 355399] make # of recent files configurable
https://bugs.kde.org/show_bug.cgi?id=355399 caminost...@gmail.com changed: What|Removed |Added CC||caminost...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359127] Desktop theme KCM 'details' and editing tab no longer present/functional
https://bugs.kde.org/show_bug.cgi?id=359127 franceso florian changed: What|Removed |Added CC||francesco.florian94@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361796] New: update doesn't install for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=361796 Bug ID: 361796 Summary: update doesn't install for unknown reasons Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PackageKit Assignee: aleix...@kde.org Reporter: sit...@kde.org I have a pending update that just won't install after running update multiple times. Discover doesn't tell me why exactly it fails to upgrade, it really pretends all is fine I'd say :/ No relevant output on stdout except for > muondiscover(10885)/(default) unknown: update finished! 1 415 which I guess doesn't help much Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361796] update doesn't install for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=361796 --- Comment #1 from Harald Sitter --- Created attachment 98402 --> https://bugs.kde.org/attachment.cgi?id=98402&action=edit screenshot -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361796] update doesn't install for unknown reasons
https://bugs.kde.org/show_bug.cgi?id=361796 --- Comment #2 from Harald Sitter --- Possibly a result of a failing resolution path involving downgrades see bug #361797 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361797] New: upgrade doesn't downgrade
https://bugs.kde.org/show_bug.cgi?id=361797 Bug ID: 361797 Summary: upgrade doesn't downgrade Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PackageKit Assignee: aleix...@kde.org Reporter: sit...@kde.org My system wants to downgrade the Qt stack, discover doesn't show that in the update UI, it doesn't actually show it anywhere, it pretends those downgrades aren't pending at all. Apt about the transactions it wants to conduct > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > libxcb-xinerama0 linux-headers-4.2.0-30 linux-headers-4.2.0-30-generic > linux-image-4.2.0-30-generic > linux-image-extra-4.2.0-30-generic > Use 'sudo apt autoremove' to remove them. > The following packages will be REMOVED: > qt5-qmltooling-plugins > The following packages will be upgraded: > plasma-integration > The following packages will be DOWNGRADED: > frameworkintegration kpackagelauncherqml libkf5calendarevents5 > libkf5declarative-data libkf5declarative-dev > libkf5declarative5 libkf5plasma5 libkf5plasmaquick5 libkf5quickaddons5 > libkf5style-dev libkf5style5 > libqgsttools-p1 libqt5clucene5 libqt5concurrent5 libqt5core5a libqt5dbus5 > libqt5designer5 > libqt5designercomponents5 libqt5gui5 libqt5help5 libqt5multimedia5 > libqt5multimedia5-plugins > libqt5multimediaquick-p5 libqt5multimediawidgets5 libqt5network5 > libqt5opengl5 libqt5opengl5-dev > libqt5printsupport5 libqt5qml5 libqt5quick5 libqt5quickparticles5 > libqt5quicktest5 libqt5quickwidgets5 > libqt5script5 libqt5scripttools5 libqt5sql5 libqt5sql5-mysql > libqt5sql5-sqlite libqt5svg5 libqt5svg5-dev > libqt5test5 libqt5waylandclient5 libqt5webkit5 libqt5webkit5-dev > libqt5widgets5 libqt5x11extras5 libqt5xml5 > libqt5xmlpatterns5 plasma-framework plasma-framework-dev qdbus-qt5 > qml-module-org-kde-draganddrop > qml-module-org-kde-kcoreaddons qml-module-org-kde-kio > qml-module-org-kde-kquickcontrols > qml-module-org-kde-kquickcontrolsaddons qml-module-org-kde-kwindowsystem > qml-module-qt-labs-folderlistmodel > qml-module-qt-labs-settings qml-module-qtgraphicaleffects > qml-module-qtmultimedia qml-module-qtquick-controls > qml-module-qtquick-dialogs qml-module-qtquick-layouts > qml-module-qtquick-privatewidgets > qml-module-qtquick-window2 qml-module-qtquick-xmllistmodel > qml-module-qtquick2 qml-module-qtwebkit qt5-qmake > qtbase5-dev qtbase5-dev-tools qtdeclarative5-dev > qtdeclarative5-kf5declarative qtscript5-dev qttools5-dev > qttools5-dev-tools qtwayland5 > 1 upgraded, 0 newly installed, 78 downgraded, 1 to remove and 0 not upgraded. > Need to get 38,7 MB of archives. > After this operation, 564 kB disk space will be freed. > Do you want to continue? [Y/n] N > Abort. the plasma-integration upgarde isn't even shown in pkcon, it is shown in discover though. it does however fail to install in discover so maybe that is why it isn't shown (also see bug #361796) > $ pkcon --allow-downgrade --allow-reinstall update > Getting updates [=] > Finished [=] > Loading cache [=] > Testing changes [=] > Finished [=] > Updating packages [=] > Waiting for authentication[=] > Loading cache [=] > Finished [=] > There are no updates available at this time. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[calligragemini] [Bug 361798] New: Calligra Gemini
https://bugs.kde.org/show_bug.cgi?id=361798 Bug ID: 361798 Summary: Calligra Gemini Product: calligragemini Version: unspecified Platform: Slackware Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: franci...@protonmail.com Application: calligragemini (2.9.11) KDE Platform Version: 4.14.18 Qt Version: 4.8.7 Operating System: Linux 4.4.6 x86_64 Distribution (Platform): Slackware Packages -- Information about the crash: Nothing unusual observed prior to the crash. Double-clicked an .odt file from a directory on a different drive (ext4)and the program opened. The document did not open however so I had to manually click on the "icon/preview". It was just after opening the file when Calligra crashed. I tried this a couple of times with the same result. The crash can be reproduced every time. -- Backtrace: Application: Calligra Gemini (calligragemini), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f9d4b2097c0 (LWP 1554))] Thread 6 (Thread 0x7f9d29498700 (LWP 1555)): #0 0x7f9d447f936f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9d438635aa in () at /usr/lib64/qt/lib/libQtScript.so.4 #2 0x7f9d438635d9 in () at /usr/lib64/qt/lib/libQtScript.so.4 #3 0x7f9d447f3684 in start_thread () at /lib64/libpthread.so.0 #4 0x7f9d43c8fefd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f9ca3835700 (LWP 1556)): #0 0x7f9d447f9718 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9d499338b2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7f9d49926e7f in () at /usr/lib64/qt/lib/libQtCore.so.4 #3 0x7f9d499333bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #4 0x7f9d447f3684 in start_thread () at /lib64/libpthread.so.0 #5 0x7f9d43c8fefd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f9ca3034700 (LWP 1557)): #0 0x7f9d447f9718 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9d499338b2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7f9d49926e7f in () at /usr/lib64/qt/lib/libQtCore.so.4 #3 0x7f9d499333bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #4 0x7f9d447f3684 in start_thread () at /lib64/libpthread.so.0 #5 0x7f9d43c8fefd in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f9ca2833700 (LWP 1558)): #0 0x7f9d447f9718 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f9d499338b2 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/qt/lib/libQtCore.so.4 #2 0x7f9d49926e7f in () at /usr/lib64/qt/lib/libQtCore.so.4 #3 0x7f9d499333bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #4 0x7f9d447f3684 in start_thread () at /lib64/libpthread.so.0 #5 0x7f9d43c8fefd in clone () at /lib64/libc.so.6 Thread 2 (Thread 0x7f9ca2032700 (LWP 1559)): #0 0x7f9d43c8430d in poll () at /lib64/libc.so.6 #1 0x7f9d4271e954 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f9d4271ea5c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f9d49a670ce in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #4 0x7f9d49a375d1 in QEventLoop::processEvents(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #5 0x7f9d49a378e5 in QEventLoop::exec(QFlags) () at /usr/lib64/qt/lib/libQtCore.so.4 #6 0x7f9d49930c39 in QThread::exec() () at /usr/lib64/qt/lib/libQtCore.so.4 #7 0x7f9d4aba954e in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #8 0x7f9d499333bc in () at /usr/lib64/qt/lib/libQtCore.so.4 #9 0x7f9d447f3684 in start_thread () at /lib64/libpthread.so.0 #10 0x7f9d43c8fefd in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f9d4b2097c0 (LWP 1554)): [KCrash Handler] #6 0x7f9d48b43f54 in KoPart::document() const () at /usr/lib64/libkomain.so.14 #7 0x7f9ca3e69e02 in () at /usr/lib64/calligra/imports/org/calligra/CalligraComponents/libcalligraqtquickcomponentsplugin.so #8 0x7f9ca3e628e4 in () at /usr/lib64/calligra/imports/org/calligra/CalligraComponents/libcalligraqtquickcomponentsplugin.so #9 0x7f9ca3e6095d in () at /usr/lib64/calligra/imports/org/calligra/CalligraComponents/libcalligraqtquickcomponentsplugin.so #10 0x7f9ca3e60b77 in () at /usr/lib64/calligra/imports/org/calligra/CalligraComponents/libcalligraqtquickcomponentsplugin.so #11 0x7f9d4ac556e8 in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #12 0x7f9d4ad0262e in () at /usr/lib64/qt/lib/libQtDeclarative.so.4 #13 0x7f9d438e1cf6 in () at /usr/lib64/qt/lib/libQtScript.so.4 #14 0x7f9d437ac628 in () at /usr/lib64/qt/lib/libQtScript.so.4 #15 0x7f9ca8c0b9
[krita] [Bug 346967] Crash on picking a color (either through the Color Picker or the Advanced Color Selector)
https://bugs.kde.org/show_bug.cgi?id=346967 --- Comment #17 from Douglas --- That is not the problem. How do I get it out of GDB? Can you pipe somehow? On Fri, Apr 15, 2016 at 9:30 AM, Boudewijn Rempt via KDE Bugzilla < bugzilla_nore...@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=346967 > > --- Comment #16 from Boudewijn Rempt --- > You can go to the bugzilla web interface and add it as an attachement. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361784] Launch an application on a second monitor when launching from app launcher on panel on that monitor
https://bugs.kde.org/show_bug.cgi?id=361784 --- Comment #4 from hrvo...@jankovci.net --- Thank you! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] New: Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 Bug ID: 361799 Summary: Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen Product: kwin Version: 5.5.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: xrandr Assignee: kwin-bugs-n...@kde.org Reporter: hawk...@tiscali.it When using the fixDisplay.sh script I get a working extended desktop on my laptop's HDMI-attached external screen. The three (related ?) problems I get are: As soon as I run the script I (sometimes) in one random case of the following: 1) end up with an Xorg crash (problem1) 2) end up with some of the open windows disappearing (not on any display/desktop/activity), but the processes are still running and it is still possible to list the x window ID 3) kwin works ok for a while (problem2) While kwin is working I get reversible and temporary visual corruptions (expecially in konsole) while scrolling. I have a patched Xorg xorg-server-1.17.2 (because of a bug related to randr and scaling) xrandr -q Screen 0: minimum 8 x 8, current 7680 x 4320, maximum 32767 x 32767 eDP1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 3840x2160 60.00*+ 48.00 3200x1800 60.00 2880x1620 60.00 2560x1440 60.00 2048x1536 60.00 1920x1440 60.00 1856x1392 60.01 1792x1344 60.01 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0059.93 1600x1200 60.00 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1440x900 59.89 1280x960 60.00 1368x768 60.00 1360x768 59.8059.96 1152x864 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 HDMI1 connected 3840x2160+3840+0 (normal left inverted right x axis y axis) 443mm x 249mm 1600x900 60.00*+ 1280x1024 60.02 1440x900 59.90 1280x720 60.00 1024x768 60.00 800x600 60.32 640x480 60.00 720x400 70.08 VIRTUAL1 disconnected (normal left inverted right x axis y axis) Reproducible: Sometimes Steps to Reproduce: 1. run the patched xorg (not sure this prerequisite is ncessary) 2. attach a secondary screen 3. run the script Actual Results: crash/corruption/visual problems Expected Results: The external screen should just work after just running xrandr, without the need to kill kwin and kwin should not present the described problems. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361800] New: Account Wizard from Kmail crashes setting up an e-mail account
https://bugs.kde.org/show_bug.cgi?id=361800 Bug ID: 361800 Summary: Account Wizard from Kmail crashes setting up an e-mail account Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: en...@softastur.org Trying to setting up an IMAP account on Kmail's Account Wizard, it crashes. I'm using OpenSUSE Tumbleweed Reproducible: Always Steps to Reproduce: 1. Open Account Wizard from Kmail 2. Fill up all personal information 3. Click Next when you done, and wait for the crash Actual Results: Account wizard crashes setting up an account Expected Results: Account wizard should not crash setting up an account Backtrace: https://paste.kde.org/pyjpt5arf -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361157] Akonadi does not work properly after Update to KDE FW 5.20, Plasma 5.6 and Qt5.6 on Opensuse Leap 42.1
https://bugs.kde.org/show_bug.cgi?id=361157 Torsten Bielen changed: What|Removed |Added CC||bie...@gmx.de --- Comment #3 from Torsten Bielen --- My system: opensuse Leap (64 bit) Yesterday I've updated my system in the same way (Qt 5.6.0 from KDE:Qt5, KDE Frameworks 5.20.0 from KDE:Frameworks5, Akonadi and KDEPIM5 from KDE:Applications 16.03) and it worked fine. Today I installed the suggested updates and system stops working. Same behavior as described here. If I call 'akonadi_ctrl stop' nothing happens. If I start a single applications instead of kontact the same behavior. If I start kmail using the konsole I got the error klauchner failed due to unknown protocol 'cid'. I'm not sure if this is related to cited error. I checked if there is no package mismatch and all seems to be okay. At the end all programs using akonadi don't start. For me this seems to be a very fragile combination of KDEPIM and akonadi in opensuse leap. The following packages installed today: kdgantt2|16.03.90-4.1 libKF5Libkdepim5|16.03.90-5.1 libkleo|16.03.90-3.1 libKF5KDGantt2-5|16.03.90-4.1 libkdepim|16.03.90-5.1 libKF5Libkleo5|16.03.90-3.1 libKF5MailImporter5|16.03.90-3.1 kleopatra5|16.03.90-4.6 libavutil55|3.0.1-66.1 libpostproc54|3.0.1-66.1 libswresample2|3.0.1-66.1 libavresample3|3.0.1-66.1 libswscale4|3.0.1-66.1 libavcodec57|3.0.1-66.1 libavformat57|3.0.1-66.1 libavfilter6|3.0.1-66.1 libopencv3_1|3.1.0-83.7 handbrake-gtk|0.10.5-1.6 libavdevice57|3.0.1-66.1 ffmpeg|3.0.1-66.1|x86_64 grantlee5|5.0.0-7.2|x86_64 libKF5PimCommon5|16.03.90-4.1 grantleetheme|16.03.90-3.1 knotes5|16.03.90-58.5|x86_64 libksieve|16.03.90-5.1|x86_64 libKF5Gravatar5|16.03.90-3.1 libKF5GrantleeTheme5|16.03.90-3.1 kdepim-apps-libs|16.03.90-3.1 kontact5|16.03.90-58.5|x86_64 kaddressbook5|16.03.90-58.5 messagelib|16.03.90-6.1 akregator5|16.03.90-58.5 libKF5MailCommon5|16.03.90-3.1 korganizer5|16.03.90-58.5 kmail5|16.03.90-58.5 akonadi_resources|16.03.90-58.5 kdepim-addons|16.03.90-8.1 kdepim|16.03.90-58.5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #1 from Thomas Lübking --- (In reply to Vincenzo Di Massa from comment #0) > When using the fixDisplay.sh script What fixDisplay.sh script? > 1) end up with an Xorg crash (problem1) Xorg bug, check /var/log/Xorg.*.log for possible backtraces. > 2) end up with some of the open windows disappearing (not on any > display/desktop/activity), but the processes are still running and it is > still possible to list the x window ID Qt5 is completely broken on randr events, see bug #341497 > While kwin is working I get reversible and temporary visual corruptions > (expecially in konsole) while scrolling. What makes you believe this is a bug in KWin? Does it happen with suspended compositor as well (SHIFT+Alt+F12) Please attach the output of "qdbus org.kde.KWin /KWin supportInformation" and /var/log/Xorg.0.log nb. that multiscreen is completely dysfunctional and that will remain at least until Qt5.6 & Plasma 5.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #2 from Vincenzo Di Massa --- Created attachment 98404 --> https://bugs.kde.org/attachment.cgi?id=98404&action=edit xorg patch I'mk using to fix mouse cursor problems https://bugs.freedesktop.org/attachment.cgi?id=94929 https://bugs.freedesktop.org/show_bug.cgi?id=39949 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #3 from Vincenzo Di Massa --- Created attachment 98405 --> https://bugs.kde.org/attachment.cgi?id=98405&action=edit script to setup an external (non HIGH DPI monitor) using xrandr The script scales the resolution of my laptop monitor down to the resolution of the attached monitor using xrandr -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #4 from Vincenzo Di Massa --- Created attachment 98406 --> https://bugs.kde.org/attachment.cgi?id=98406&action=edit qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #5 from Vincenzo Di Massa --- Created attachment 98407 --> https://bugs.kde.org/attachment.cgi?id=98407&action=edit xorg log -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361793] View/Headers menu does not show choices
https://bugs.kde.org/show_bug.cgi?id=361793 --- Comment #3 from Laurent Montel --- yep it's new in 5.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 361800] Account Wizard from Kmail crashes setting up an e-mail account
https://bugs.kde.org/show_bug.cgi?id=361800 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Application: Account Assistant (accountwizard), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f451d69d900 (LWP 4754))] Thread 6 (Thread 0x7f44f12bb700 (LWP 4756)): #0 0x7f451237807f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f44f861cd23 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f44f861c537 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f45123724a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4517deeded in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7f44f03da700 (LWP 4758)): #0 0x7f4517de649d in poll () from /lib64/libc.so.6 #1 0x7f4511e53374 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4511e5347c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f451891143b in QEventDispatcherGlib::processEvents (this=0x7f44e80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f45188bb52a in QEventLoop::exec (this=this@entry=0x7f44f03d9cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f45186e7acc in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f45186ec90f in QThreadPrivate::start (arg=0x1ae9770) at thread/qthread_unix.cpp:331 #7 0x7f45123724a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f4517deeded in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f44ef555700 (LWP 4759)): #0 0x7f4517de649d in poll () from /lib64/libc.so.6 #1 0x7f4511e53374 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f4511e5347c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7f451891143b in QEventDispatcherGlib::processEvents (this=0x7f44e8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #4 0x7f45188bb52a in QEventLoop::exec (this=this@entry=0x7f44ef554cd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #5 0x7f45186e7acc in QThread::exec (this=) at thread/qthread.cpp:503 #6 0x7f45186ec90f in QThreadPrivate::start (arg=0x1c5e410) at thread/qthread_unix.cpp:331 #7 0x7f45123724a4 in start_thread () from /lib64/libpthread.so.0 #8 0x7f4517deeded in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f44ee313700 (LWP 4763)): #0 0x7f451237807f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f4516ff3a84 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f45172daea0 ) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f4516ff3ac9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f45123724a4 in start_thread () from /lib64/libpthread.so.0 #4 0x7f4517deeded in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f44eed54700 (LWP 4764)): #0 0x7f4512378428 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f45186ed9c6 in QWaitConditionPrivate::wait_relative (time=3, this=0x7f44e0005350) at thread/qwaitcondition_unix.cpp:126 #2 QWaitConditionPrivate::wait (time=3, this=0x7f44e0005350) at thread/qwaitcondition_unix.cpp:134 #3 QWaitCondition::wait (this=this@entry=0x7f44e0005070, mutex=mutex@entry=0x7f44e0004dd0, time=3) at thread/qwaitcondition_unix.cpp:208 #4 0x7f45186e965b in QThreadPoolThread::run (this=0x7f44e0005060) at thread/qthreadpool.cpp:127 #5 0x7f45186ec90f in QThreadPrivate::start (arg=0x7f44e0005060) at thread/qthread_unix.cpp:331 #6 0x7f45123724a4 in start_thread () from /lib64/libpthread.so.0 #7 0x7f4517deeded in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f451d69d900 (LWP 4754)): [KCrash Handler] #6 QScopedPointer >::data (this=0x8) at ../../src/corelib/tools/qscopedpointer.h:135 #7 qGetPtrHelper > (p=...) at ../../src/corelib/global/qglobal.h:983 #8 QDBusAbstractInterface::d_func (this=0x0) at qdbusabstractinterface.h:148 #9 QDBusAbstractInterface::asyncCallWithArgumentList (this=0x0, method=..., args=...) at qdbusabstractinterface.cpp:502 #10 0x7f451c1e4ad6 in OrgKdeKWalletInterface::isOpen (wallet=..., this=) at /usr/src/debug/kwallet-5.21.0/build/src/api/KWallet/kwallet_interface.h:146 #11 KWallet::Wallet::isOpen (name=...) at /usr/src/debug/kwallet-5.21.0/src/api/KWallet/kwallet.cpp:366 #12 0x00438666 in SetupManager::openWallet (this=0x1b22f60) at /usr/src/debug/kdepim-15.12.3/accountwizard/setupmanager.cpp:223 #13 0x
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 Martin Gräßlin changed: What|Removed |Added Attachment #98407|text/x-log |text/plain mime type|| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #6 from Martin Gräßlin --- (In reply to Vincenzo Di Massa from comment #5) > Created attachment 98407 [details] > xorg log that doesn't contain an xorg crash. You have to look into the old log after a crash. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #7 from Vincenzo Di Massa --- (In reply to Thomas Lübking from comment #1) > (In reply to Vincenzo Di Massa from comment #0) > What fixDisplay.sh script? Really fast answer, I have now made it an attachment. > > 1) end up with an Xorg crash (problem1) > Xorg bug, check /var/log/Xorg.*.log for possible backtraces. I'll attach next crash log. > > 2) end up with some of the open windows disappearing (not on any > > display/desktop/activity), but the processes are still running and it is > > still possible to list the x window ID > > Qt5 is completely broken on randr events, see bug #341497 I suspected this. Anyways it is working "sort of ok" except that in my setup (when none or all of the displays are HIGH dpi, and thus I'm not scaling. > > While kwin is working I get reversible and temporary visual corruptions > > (expecially in konsole) while scrolling. > > What makes you believe this is a bug in KWin? Kwin often crashes, its output spawns (cryptic for me) errors. (see attached file). I have windows listed by X that kwin does not render (I'm not sure I get how compositing works BTW). > Does it happen with suspended compositor as well (SHIFT+Alt+F12) > Please attach the output of "qdbus org.kde.KWin /KWin supportInformation" > and /var/log/Xorg.0.log Done, I'll try disablin the compositor and report back. > > nb. that multiscreen is completely dysfunctional and that will remain at > least until Qt5.6 & Plasma 5.7 Great news! I'm really looking forward. Do you reccomend any workaround to make kwin/kde apps play nicely with my monitors in the meantime? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #8 from Vincenzo Di Massa --- Whooops, I realize just now that in the description I did not tell that that kwin also crashes may times a day, but ONLY in this setup. BTW you, and the kde people, rock! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361801] New: discover should show error when no appstream data
https://bugs.kde.org/show_bug.cgi?id=361801 Bug ID: 361801 Summary: discover should show error when no appstream data Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Apt Back-end Assignee: aleix...@kde.org Reporter: j...@jriddell.org Using plasma-discover from KDE neon git-unstable today I run discover and it shows lots of empty panels http://weegie.edinburghlinux.co.uk/~jr/tmp/discover1.png The problem is in appstream as when I use cli I get >appstreamcli get org.kde.dolphin.desktop --details Unable to find component with id 'org.kde.dolphin.desktop'! but discover should show an error message rather than just carry on regardless Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361802] New: digikam crash when tyring to fuse 3 pics
https://bugs.kde.org/show_bug.cgi?id=361802 Bug ID: 361802 Summary: digikam crash when tyring to fuse 3 pics Product: digikam Version: 4.12.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: digikam-de...@kde.org Reporter: p...@free.fr Application: digikam (4.12.0) KDE Platform Version: 4.14.15 Qt Version: 4.8.6 Operating System: Linux 4.2.0-35-lowlatency x86_64 Distribution: Ubuntu 15.10 -- Information about the crash: - What I was doing when the application crashed: I selected 3 pics then go to tool, fuse pics - Unusual behavior I noticed: when the tool tries to start the fuse, digikam crashes. The crash can be reproduced every time. -- Backtrace: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2b1d25cb40 (LWP 19292))] Thread 13 (Thread 0x7f2af85f3700 (LWP 19293)): #0 0x7f2b164b388d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f2b0262812c in () at /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x7f2b139cb6aa in start_thread (arg=0x7f2af85f3700) at pthread_create.c:333 #3 0x7f2b164bee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f2af4078700 (LWP 19294)): #0 0x7f2b139d0da0 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2b17019286 in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x28fedb0) at thread/qwaitcondition_unix.cpp:86 #2 0x7f2b17019286 in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x28fecb8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x005fffb4 in () #4 0x7f2b17018d1c in QThreadPrivate::start(void*) (arg=0x28fea30) at thread/qthread_unix.cpp:349 #5 0x7f2b139cb6aa in start_thread (arg=0x7f2af4078700) at pthread_create.c:333 #6 0x7f2b164bee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f2af3877700 (LWP 19295)): #0 0x7f2b0ffaa884 in g_mutex_unlock (mutex=0x7f2ae40009a0) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gthread-posix.c:1350 #1 0x7f2b0ff66306 in g_main_context_iteration (context=0x7f2ae40009a0, may_block=may_block@entry=1) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3902 #2 0x7f2b1715920e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f2ae40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #3 0x7f2b171270d1 in QEventLoop::processEvents(QFlags) (this=this@entry=0x7f2af3876a40, flags=...) at kernel/qeventloop.cpp:149 #4 0x7f2b17127445 in QEventLoop::exec(QFlags) (this=this@entry=0x7f2af3876a40, flags=...) at kernel/qeventloop.cpp:204 #5 0x7f2b170164f9 in QThread::exec() (this=this@entry=0x28a2140) at thread/qthread.cpp:538 #6 0x7f2b17107133 in QInotifyFileSystemWatcherEngine::run() (this=0x28a2140) at io/qfilesystemwatcher_inotify.cpp:265 #7 0x7f2b17018d1c in QThreadPrivate::start(void*) (arg=0x28a2140) at thread/qthread_unix.cpp:349 #8 0x7f2b139cb6aa in start_thread (arg=0x7f2af3877700) at pthread_create.c:333 #9 0x7f2b164bee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 10 (Thread 0x7f2af3076700 (LWP 19335)): #0 0x7f2b139d0da0 in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f2b17019286 in QWaitCondition::wait(QMutex*, unsigned long) (time=18446744073709551615, this=0x3b145a0) at thread/qwaitcondition_unix.cpp:86 #2 0x7f2b17019286 in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x2c45d78, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x7f2b1b396f02 in () at /usr/lib/digikam/libdigikamcore.so.4.12.0 #4 0x7f2b17018d1c in QThreadPrivate::start(void*) (arg=0x2c45d60) at thread/qthread_unix.cpp:349 #5 0x7f2b139cb6aa in start_thread (arg=0x7f2af3076700) at pthread_create.c:333 #6 0x7f2b164bee9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 9 (Thread 0x7f2ada2f5700 (LWP 19336)): #0 0x7f2b0ff65bd4 in g_main_context_check (context=context@entry=0x7f2ad40009a0, max_priority=, fds=fds@entry=0x7f2ad4003210, n_fds=n_fds@entry=1) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3751 #1 0x7f2b0ff66190 in g_main_context_iterate (context=context@entry=0x7f2ad40009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3837 #2 0x7f2b0ff662fc in g_main_context_iteration (context=0x7f2ad40009a0, may_block=may_block@entry=1) at /build/glib2.0-MuyBSS/glib2.0-2.46.2/./glib/gmain.c:3901 #3 0x7f2b1715920e in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f2ad40
[digikam] [Bug 361802] digikam crash when tyring to fuse 3 pics
https://bugs.kde.org/show_bug.cgi?id=361802 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 354364 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354364] Crash of DNG converter
https://bugs.kde.org/show_bug.cgi?id=354364 caulier.gil...@gmail.com changed: What|Removed |Added CC||p...@free.fr --- Comment #35 from caulier.gil...@gmail.com --- *** Bug 361802 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361803] New: Plasma 5 crashes when a new application shortcut is manually created in KDE Menu Editor
https://bugs.kde.org/show_bug.cgi?id=361803 Bug ID: 361803 Summary: Plasma 5 crashes when a new application shortcut is manually created in KDE Menu Editor Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cezar.tiga...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: Just created a new application shortcut in KDE Menu editor. Mor specifically I was setting its icon from a local png file - Custom settings of the application: I only have the KDE panel on top of the screen, containing some downloaded pasmoids: places, popup + stock plasmoids: Applications menu, icons-only task manager, Konsole profiles, two folder views, desktop pager, system tray, clock/calendar, wastebin, window list The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc84bef97c0 (LWP 10927))] Thread 7 (Thread 0x7fc82eb46700 (LWP 10937)): #0 0x7fc841b2fd08 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fc841aed4b9 in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc841aedd80 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc841aedf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fc845d3ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc845ce1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fc845b0361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fc848e15df8 in () at /usr/lib64/libQt5Qml.so.5 #8 0x7fc845b0832f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fc844c190a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fc845417fed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fc82142e700 (LWP 10938)): #0 0x7fc84540fbbd in poll () at /lib64/libc.so.6 #1 0x7fc841aede64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc841aedf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc845d3ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc845ce1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc845b0361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc848e15df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc845b0832f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc844c190a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc845417fed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fc81bc0d700 (LWP 10939)): #0 0x7fc84540fbbd in poll () at /lib64/libc.so.6 #1 0x7fc841aede64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc841aedf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc845d3ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc845ce1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc845b0361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc848e15df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fc845b0832f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc844c190a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc845417fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fc81a1d6700 (LWP 10940)): #0 0x7fc844c1d03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fc84b5e486b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fc84b5e4899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fc844c190a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fc845417fed in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7fc793501700 (LWP 10941)): #0 0x7fc84540fbbd in poll () at /lib64/libc.so.6 #1 0x7fc841aede64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fc841aedf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fc845d3ad8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fc845ce1d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fc845b0361a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fc8499b1282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7fc845b0832f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fc844c190a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fc845417fed in clone () at /lib64/libc.so.6 Thread 2 (Thread
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #9 from Thomas Lübking --- for kwin crashes, please attach the developer informations from the crash dialog (backtrace) (reg. xorg.0.log, i wanted to check for egl/dri3 - xorg.1.log will contain x11 backtraces only directly after an xorg server crash) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 346967] Crash on picking a color (either through the Color Picker or the Advanced Color Selector)
https://bugs.kde.org/show_bug.cgi?id=346967 --- Comment #18 from Douglas --- Two things. I got the dump and I found out why Krita will not start in the debugger. It fails to fully start up when it tries to load an autosave file. So no autosave files and it starts up just fine! Guess this should be a new bug report. http://www.pasteall.org/68156 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361804] New: plasma 5 crashed afer launching system-help
https://bugs.kde.org/show_bug.cgi?id=361804 Bug ID: 361804 Summary: plasma 5 crashed afer launching system-help Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cezar.tiga...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: system-help launched from a popul plasmoid installed in the KDE panel -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbfb510b7c0 (LWP 11035))] Thread 16 (Thread 0x7fbf9eb43700 (LWP 11038)): #0 0x7fbfae621bbd in poll () at /lib64/libc.so.6 #1 0x7fbfb3571422 in () at /usr/lib64/libxcb.so.1 #2 0x7fbfb357300f in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fbfa0c943c9 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fbfaed1a32f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fbfade2b0a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fbfae629fed in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7fbf97dfa700 (LWP 11045)): #0 0x7fbfae61dc8d in read () at /lib64/libc.so.6 #1 0x7fbfaad40b60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbfaacff999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbfaacffdf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbfaacfff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fbfaef4cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fbfaeef3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fbfaed1561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fbfb2027df8 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fbfaed1a32f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fbfade2b0a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fbfae629fed in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7fbf8a726700 (LWP 11048)): #0 0x7fbfaacff47e in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #1 0x7fbfaacffd80 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbfaacfff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbfaef4cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fbfaeef3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbfaed1561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fbfb2027df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fbfaed1a32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fbfade2b0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fbfae629fed in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fbf88e3c700 (LWP 11049)): #0 0x7fbfaad41cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fbfaacffe4a in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbfaacfff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbfaef4cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fbfaeef3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbfaed1561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fbfb2027df8 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fbfaed1a32f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fbfade2b0a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fbfae629fed in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fbf833d7700 (LWP 11050)): #0 0x7fbfade2f03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fbfb47f686b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fbfb47f6899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fbfade2b0a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fbfae629fed in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fbefbfff700 (LWP 11051)): #0 0x7fbfaad41cf9 in g_mutex_lock () at /usr/lib64/libglib-2.0.so.0 #1 0x7fbfaacff8fc in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbfaacffdf8 in () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbfaacfff7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbfaef4cd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fbfaeef3d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fbfaed1561a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #7 0x7fbfb2bc3282 in () at /usr/lib64/libQt5Q
[kdevelop] [Bug 361805] New: cmake project manager should call cmake without any arguments on imported pre-existing build directories (and maybe not auto-call at all)
https://bugs.kde.org/show_bug.cgi?id=361805 Bug ID: 361805 Summary: cmake project manager should call cmake without any arguments on imported pre-existing build directories (and maybe not auto-call at all) Product: kdevelop Version: git master Platform: Compiled Sources OS: All Status: UNCONFIRMED Severity: normal Priority: NOR Component: Build tools: CMake Assignee: kdevelop-bugs-n...@kde.org Reporter: rjvber...@gmail.com The CMake project manager can import pre-existing/configured build directories. It will then disable the fields of the wizard that would otherwise allow to specific the install prefix, build type and other, additional cmake arguments. That is fine, but at least the build type remains set and is given to cmake if that command is executed automatically. That is not necessary in the best case and should not happen in the worst case (when the build is under control of an external configure/build system and the IDE is only used for navigating and editing the source). It should also be possible to select an environment profile in the importer wizard. Ensuring that the external configure system generates and maintains a compile_commands.json file will limit automatic invocation of cmake, but apparently not eliminated it completely. There should probably be a control for disabling that feature so that the user can decide is s/he prefers to work with potentially out-of-date project information in the IDE or have an IDE with up-to-date information on a potentially misconfigured project. There could be a visual indication when the project information is supposedly out of date, though. Reproducible: Always Steps to Reproduce: 1. prepare a cmake-based project with a pre-configured build directory 2. Import a new project in KDevelop; select the project's CMakeLists.txt file 3. Point the importer wizard to the pre-configured build directory without touching any of the other fields Actual Results: Under certain conditions cmake will be called with at least KDevelop's default CMAKE_BUILD_TYPE passed as an argument Expected Results: If cmake is called at all it in this kind of scenario, should be called without arguments, and with the appropriate environment (if that is not the current environment). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361803] Plasma 5 crashes when a new application shortcut is manually created in KDE Menu Editor
https://bugs.kde.org/show_bug.cgi?id=361803 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 342763 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342763] Crash In Task Manager Item Changed
https://bugs.kde.org/show_bug.cgi?id=342763 --- Comment #186 from David Edmundson --- *** Bug 361803 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 342763] Crash In Task Manager Item Changed
https://bugs.kde.org/show_bug.cgi?id=342763 --- Comment #186 from David Edmundson --- *** Bug 361803 has been marked as a duplicate of this bug. *** --- Comment #187 from David Edmundson --- *** Bug 361804 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361804] plasma 5 crashed afer launching system-help
https://bugs.kde.org/show_bug.cgi?id=361804 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 342763 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361806] New: plasmashell crasheds om every boots
https://bugs.kde.org/show_bug.cgi?id=361806 Bug ID: 361806 Summary: plasmashell crasheds om every boots Product: plasmashell Version: 5.4.3 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rrcr...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.4.0-1-amd64 x86_64 Distribution: Kali GNU/Linux Rolling -- Information about the crash: plasma doesn't start whit sddm and crashes if I use startx in a shell. using plasma in Debian Testing or Sid whit repos of Kali and Mint Debian Edition The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbb5a3eb940 (LWP 2666))] Thread 7 (Thread 0x7fbb439d2700 (LWP 2668)): #0 0x7fbb54b3de4d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fbb58bf0382 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7fbb58bf1ff7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7fbb45719789 in QXcbEventReader::run (this=0xfa7b20) at qxcbconnection.cpp:1230 #4 0x7fbb552227fe in QThreadPrivate::start (arg=0xfa7b20) at thread/qthread_unix.cpp:331 #5 0x7fbb54346454 in start_thread (arg=0x7fbb439d2700) at pthread_create.c:334 #6 0x7fbb54b46ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7fbb3bfff700 (LWP 2669)): #0 0x7fbb518e9414 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fbb55459a5b in QEventDispatcherGlib::processEvents (this=0x7fbb340008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #2 0x7fbb55400d6a in QEventLoop::exec (this=this@entry=0x7fbb3bffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #3 0x7fbb5521d854 in QThread::exec (this=) at thread/qthread.cpp:503 #4 0x7fbb57ab0105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7fbb552227fe in QThreadPrivate::start (arg=0x108f210) at thread/qthread_unix.cpp:331 #6 0x7fbb54346454 in start_thread (arg=0x7fbb3bfff700) at pthread_create.c:334 #7 0x7fbb54b46ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7fbb326aa700 (LWP 2672)): #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7fbb54348b82 in __GI___pthread_mutex_lock (mutex=0x7fbb50f8e880) at ../nptl/pthread_mutex_lock.c:116 #2 0x7fbb50d0ae90 in ?? () from /usr/lib/libGL.so.1 #3 0x7fbb50d0e41e in ?? () from /usr/lib/libGL.so.1 #4 0x7fbb50d0e878 in ?? () from /usr/lib/libGL.so.1 #5 0x7fbb4d6c5fd1 in ?? () from /usr/lib/tls/libnvidia-tls.so.340.96 #6 0x7fbb5192c6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fbb518e8e14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fbb518e92d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fbb518e943c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7fbb55459a5b in QEventDispatcherGlib::processEvents (this=0x7fbb2c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #11 0x7fbb55400d6a in QEventLoop::exec (this=this@entry=0x7fbb326a9c60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #12 0x7fbb5521d854 in QThread::exec (this=) at thread/qthread.cpp:503 #13 0x7fbb57ab0105 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fbb552227fe in QThreadPrivate::start (arg=0x135ba60) at thread/qthread_unix.cpp:331 #15 0x7fbb54346454 in start_thread (arg=0x7fbb326aa700) at pthread_create.c:334 #16 0x7fbb54b46ecd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7fbb2bfff700 (LWP 2675)): #0 0x7fbb54b39e2d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7fbb4d6c5f45 in ?? () from /usr/lib/tls/libnvidia-tls.so.340.96 #2 0x7fbb5192c6f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbb518e8e14 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbb518e92d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbb518e943c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fbb55459a5b in QEventDispatcherGlib::processEvents (this=0x7fbb240008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:420 #7 0x7fbb55400d6a in QEventLoop::exec (this=this@entry=0x7fbb2bffec60, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #8 0x7fbb5521d854 in QThread::exec (this=) at thread/qthread.cpp:503 #9 0x7fbb57ab0105 in ?? () from /usr/lib/x86_6
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #10 from Vincenzo Di Massa --- I tried to get such logs, but the system becomes unresponsive in such cases. I have to terminate kwin from a vt like this. killall -9 kwin_x11 && sleep 1 ; kwin_x11 --replace & chvt 7 I realze I should s/crashes/hungs/g on my prevoius sentences. notice that sending sigterm (or just calling kwin --replace ) does not work, thus I use sigkill. I could run kwin into a debugger to backtrace where it crashes, would this help? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 361789] Запустил обновление системы
https://bugs.kde.org/show_bug.cgi?id=361789 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 321711 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 321711] Crash
https://bugs.kde.org/show_bug.cgi?id=321711 --- Comment #10 from Christoph Feck --- *** Bug 361789 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 361807] New: Description in details page is draggable
https://bugs.kde.org/show_bug.cgi?id=361807 Bug ID: 361807 Summary: Description in details page is draggable Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: thomas.pfeif...@kde.org The description text in the details page can be dragged around on both axes even though it fits perfectly on the page. Even if it doesn't, the whole page should scroll, not the description individually. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 333843] Brush freezes after lifting stylus pen away from tablet while cursor is on canvas
https://bugs.kde.org/show_bug.cgi?id=333843 freshkonig changed: What|Removed |Added CC||pajtim...@gmail.com --- Comment #26 from freshkonig --- Hello. I'm having the same problem with my wacom intuos art medium tablet (CTH-690AK) on Linux Mint 17.3. This line of tablets doesn't seem to be recognized by Linux yet. Mine works but when I open Graphics Tablet it says 'No tablet detected' so maybe the bug is related to the wacom model. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 354400] In Kmail 5.0.2 autocompletion only shows recent email addresses but not stored emails in Kaddressbook
https://bugs.kde.org/show_bug.cgi?id=354400 Florian changed: What|Removed |Added CC||floesc...@gmx.net -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 357993] Kmail initial account setup wizard flashes error message too quick to read
https://bugs.kde.org/show_bug.cgi?id=357993 Valeriy Malov changed: What|Removed |Added CC||jazzv...@gmail.com --- Comment #1 from Valeriy Malov --- Same happens with KMail 4.14.10 with kdelibs 4.14.16 on Gentoo -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 361778] 4k default wallpaper
https://bugs.kde.org/show_bug.cgi?id=361778 Sebastian Kügler changed: What|Removed |Added Severity|wishlist|normal Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Assignee|plasma-de...@kde.org|verme...@gmail.com CC||se...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 beojan changed: What|Removed |Added Version|5.5.1 |5.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355935] Font kerning is incorrect
https://bugs.kde.org/show_bug.cgi?id=355935 --- Comment #5 from beojan --- I've changed the version to 5.6.2, as it continues to exist in the latest release. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 361808] New: plasma-nm crashes Plasma upon switching WiFI network
https://bugs.kde.org/show_bug.cgi?id=361808 Bug ID: 361808 Summary: plasma-nm crashes Plasma upon switching WiFI network Product: plasma-nm Version: 5.6.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: lu...@kde.org Reporter: madc...@atlas.cz CC: jgrul...@redhat.com Whenever I switch from one WiFi network to another, plasma-nm takes down the whole plasma with the backtrace below. Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f819d5fa800 (LWP 882))] Thread 9 (Thread 0x7f8186317700 (LWP 892)): #0 0x7f8196aa2c3d in poll () from /usr/lib/libc.so.6 #1 0x7f819baa3ae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f819baa5757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f8187c39a99 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f8197191de8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f81962a5424 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f8196aabcbd in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f817700 (LWP 900)): #0 0x7f8197189ee9 in QMutex::lock() () from /usr/lib/libQt5Core.so.5 #1 0x7f81973ba4a9 in ?? () from /usr/lib/libQt5Core.so.5 #2 0x7f8192f22b31 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f8192f230a0 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f8192f2320c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f81973bacab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f81973636fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f819718cfe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f819814da55 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f8197191de8 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f81962a5424 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f8196aabcbd in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f817edee700 (LWP 916)): #0 0x7f8192f67879 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7f8192f230e2 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8192f2320c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f81973bacab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f81973636fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f819718cfe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f819a531915 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7f8197191de8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f81962a5424 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f8196aabcbd in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f8175704700 (LWP 926)): #0 0x7f8192f67894 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f8192f22680 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #2 0x7f8192f2302b in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f8192f2320c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f81973bacab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f81973636fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f819718cfe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f819a531915 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7f8197191de8 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f81962a5424 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f8196aabcbd in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f816ba50700 (LWP 931)): #0 0x7f8196aa2c3d in poll () from /usr/lib/libc.so.6 #1 0x7f8192f230fc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f8192f2320c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f81973bacab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f81973636fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f819718cfe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f819a531915 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7f8197191de8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f81962a5424 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f8196aabcbd in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f816a20a700 (LWP 945)): #0 0x7f81962ab03f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f819cd8c134 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f819cd8c179 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f81962a5424 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f8196aabcbd in clone () from /usr
[kmail2] [Bug 358679] kmail5 crash on reload when config to empty trash on exit
https://bugs.kde.org/show_bug.cgi?id=358679 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #5 from Laurent Montel --- backtrace please as it's too different bug as first comment Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 361808] plasma-nm crashes Plasma upon switching WiFI network
https://bugs.kde.org/show_bug.cgi?id=361808 --- Comment #1 from madc...@atlas.cz --- Relevant software versions: Plasma 5.6.2 KF libraries 5.21.0 NetworkManager 1.0.12 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 353102] Support for XF86AudioMicMute events
https://bugs.kde.org/show_bug.cgi?id=353102 --- Comment #1 from Elvis Angelaccio --- It looks like we can now close this wish? http://davidrosca.blogspot.it/2016/04/audio-volume-improvements-in-plasma-57.html -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361566] Panel auto-hide is completely broken
https://bugs.kde.org/show_bug.cgi?id=361566 Stephen Kraemer changed: What|Removed |Added Status|NEEDSINFO |UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #8 from Stephen Kraemer --- Is there any more information I can provide to help this bug investigation? It is quite frustrating, and I haven't been able to find a workaround yet. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 361794] Crash when attempting to read mail from the notification
https://bugs.kde.org/show_bug.cgi?id=361794 --- Comment #1 from aux...@gmail.com --- Perhaps the missing kdepim-addons caused this, as I cannot reproduce it after installing the aforementioned package. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 361757] Archive view should not show the horizontal header when aborting opening a corrupt archive
https://bugs.kde.org/show_bug.cgi?id=361757 Elvis Angelaccio changed: What|Removed |Added Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361809] New: Migration failed from SQLite to MySQL
https://bugs.kde.org/show_bug.cgi?id=361809 Bug ID: 361809 Summary: Migration failed from SQLite to MySQL Product: digikam Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Database Assignee: digikam-de...@kde.org Reporter: swatilodh...@gmail.com Migration tool failed. Although digiKam is started but after this error: Failed to open the database. You cannot use digiKam without a working database. digiKam will attempt to start now, but it will not be functional. Please check the database settings in the configuration menu. Reproducible: Always Steps to Reproduce: 1.Remove digikamrc file from your home directory. 2.Use SQLite for database. 3.After digiKam launches, from Settings->Configure database, migrate from SQLite to MySQL Internal. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 361809] Migration failed from SQLite to MySQL
https://bugs.kde.org/show_bug.cgi?id=361809 caulier.gil...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||caulier.gil...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from caulier.gil...@gmail.com --- *** This bug has been marked as a duplicate of bug 350574 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 350574] MIGRATION: MySQL to SQLite fails
https://bugs.kde.org/show_bug.cgi?id=350574 caulier.gil...@gmail.com changed: What|Removed |Added CC||swatilodh...@gmail.com --- Comment #2 from caulier.gil...@gmail.com --- *** Bug 361809 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 361612] gtk3 Breeze theme contains lots of deprecation errors
https://bugs.kde.org/show_bug.cgi?id=361612 Francis Herne changed: What|Removed |Added CC||francis.he...@yahoo.co.uk --- Comment #1 from Francis Herne --- Duplicate of https://bugs.kde.org/show_bug.cgi?id=361066 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361810] New: valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810 Bug ID: 361810 Summary: valgrind duplicate stdin after fork Product: valgrind Version: 3.11.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: rjo...@redhat.com Created attachment 98408 --> https://bugs.kde.org/attachment.cgi?id=98408&action=edit forktest.c It's probably best to just look at the attached C program and attached C script (you have to use both). The script is a minimal reproducer from a much larger program (libguestfs). $ gcc -Wall -O2 forktest.c -o forktest $ chmod +x forktest.sh $ ./forktest.sh mask 2 buf abc mask 2 buf def mask 2 buf ghi mask 2 buf abc mask 2 buf def mask 2 buf ghi mask 2 buf abc mask 2 buf def mask 2 buf ghi [etc forever] In other words, stdin of the program is duplicated somehow. It's presumably something to do with the fork() operation. valgrind-3.11.0-1.fc23.x86_64 glibc-2.22.90-36.fc24.x86_64 kernel 4.4.4-301.fc23.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361810] valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #1 from Richard Jones --- Created attachment 98409 --> https://bugs.kde.org/attachment.cgi?id=98409&action=edit forktest.sh -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] New: Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811
Bug ID: 361811
Summary: Krita forces use of Fusion theme even in a KDE session
Product: krita
Version: git master
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: krita-bugs-n...@kde.org
Reporter: beo...@gmail.com
Even in a KDE (Plasma 5) session, Krita forces use of the Fusion style instead
of the style selected in System Settings.
Reproducible: Always
Steps to Reproduce:
Start Krita in a Plasma session.
Actual Results:
Krita uses the fusion style
Expected Results:
Krita should use style selected in System Settings (e.g. Breeze).
Patch to fix this is below:
diff --git a/libs/ui/KisApplication.cpp b/libs/ui/KisApplication.cpp
index 2e21901..4374951 100644
--- a/libs/ui/KisApplication.cpp
+++ b/libs/ui/KisApplication.cpp
@@ -154,7 +154,7 @@ KisApplication::KisApplication(const QString &key, int
&argc, char **argv)
QString version = CalligraVersionWrapper::versionString(true);
setApplicationVersion(version);
setWindowIcon(KisIconUtils::loadIcon("calligrakrita"));
-
+if (qgetenv("KDE_FULL_SESSION").isEmpty()) {
QStringList styles = QStringList() << "Fusion" << "Plastique";
if (!styles.contains(style()->objectName())) {
Q_FOREACH (const QString & style, styles) {
@@ -167,6 +167,7 @@ KisApplication::KisApplication(const QString &key, int
&argc, char **argv)
}
}
}
+}
KisOpenGL::initialize();
}
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 elk...@yahoo.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from elk...@yahoo.com --- Not a Krita issue. Updating to the latest Nvidia driver resolved this issue. (At least on Win 7, will try Mint later. These things take time on low end DSL) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 --- Comment #1 from Boudewijn Rempt --- Yes, that's by design. It's pretty much the only theme that is not really broken one way or another. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 361812] New: Password field in applet is hardcoded to 200px width
https://bugs.kde.org/show_bug.cgi?id=361812 Bug ID: 361812 Summary: Password field in applet is hardcoded to 200px width Product: plasma-nm Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: k...@privat.broulik.de CC: lu...@kde.org This makes the input field super tiny eg on a phone. It should use a width based on units.gridUnit Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 --- Comment #2 from beojan --- Perhaps it could check for some other environment variable (say KRITA_USE_SYSTEM_THEME) and only force fusion if that variable isn't set, or otherwise allow the forcing of Fusion to be switched off? I'm using it with QtCurve and don't have any issues. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361811] Krita forces use of Fusion theme even in a KDE session
https://bugs.kde.org/show_bug.cgi?id=361811 --- Comment #3 from beojan --- Perhaps it could check for some other environment variable (say KRITA_USE_SYSTEM_THEME) and only force fusion if that variable isn't set, or otherwise allow the forcing of Fusion to be switched off? I'm using it with QtCurve and don't have any issues. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361709] With more than 1 curve based assistant, zooming in will black screen part or all of the drawing window
https://bugs.kde.org/show_bug.cgi?id=361709 elk...@yahoo.com changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from elk...@yahoo.com --- Spoke to soon, Open GL was turned off in preferences. When re-enabled the issue still exists. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361813] New: Wacom CTL-460/Intuos Pro Small+Krita 2.9.11: Stylus Side Buttons Not Working with Click-Based Shortcuts
https://bugs.kde.org/show_bug.cgi?id=361813 Bug ID: 361813 Summary: Wacom CTL-460/Intuos Pro Small+Krita 2.9.11: Stylus Side Buttons Not Working with Click-Based Shortcuts Product: krita Version: 2.9.11 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: nub...@mailinator.com I am using a Wacom Bamboo Pen (CTL-460). Everything seems to be working fine, except two, personally major, issues. I generally assign the Color Picker (Ctrl in Krita) to the lower side button, and Drag Brush Size (Shift in Krita) to the upper side button. When I use these function on the keyboard (press and hold the shift key and drag with the stylus, or press and hold the ctrl key and tap on a color), they work fine and dandy. When these functions are mapped to the Wacom stylus, however, they cease to function altogether. I'm running Windows 7 64-bit (Home). The issue apparently seems to effect new intuos pro models as well. This issue seems to carry over to color picker as well. Reproducible: Always Steps to Reproduce: 1. In Wacom Preferences, create a new "Modifier" for a Pen Button shortcut 2. Select "Shift" only (Or shift+click, neither seem to work) 3. Shift is the shortcut for being able to drag the brush size by default in Krita 2.9.11. One must press and hold shift, then click and drag. 4. Assigning shift to a Pen Button does not produce the desired effect, it seems. Actual Results: The brush drag resize function fails to initiate. Expected Results: Initiate the brush drag function (shift) in Krita, and then drag the brush size by pressing the pen tip to the wacom surface and dragging. I have tested this across different versions of Krita. It seems to be prevalent across the versions I have tried. Other painting/art software I have tested does not exhibit this issue (Manga Studio, Mischief.) -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 357130] Not able to enable or add todo collection (existing (sub)calendar on ownCloud server)
https://bugs.kde.org/show_bug.cgi?id=357130 Alex Ander changed: What|Removed |Added CC||aalexand...@gmail.com --- Comment #2 from Alex Ander --- I used a 0.3.1 (hope, it's a release), and in the Akonadi's "collectiontable" all "enabled" are set to 1 (I haven't changed nothing, it was so), but I still can't add no own collection. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 354364] Crash of DNG converter
https://bugs.kde.org/show_bug.cgi?id=354364 Tom changed: What|Removed |Added CC|t...@tombaxter.me.uk | -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 361814] New: Hold shift + drag to change brush size to snap to whole numbers
https://bugs.kde.org/show_bug.cgi?id=361814 Bug ID: 361814 Summary: Hold shift + drag to change brush size to snap to whole numbers Product: krita Version: 3.0 Alpha Platform: unspecified OS: other Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: krita-bugs-n...@kde.org Reporter: tob...@johansson-tobias.com I love that you scale a brush by holding down shift and left mouse dragging. However, as I'm now doing pixel art I'm started to feel that I miss one thing with that tool. It would be great if you could change so the brush size snaps to the nearest full number. Like 1px, 2px, 3px and so on. At the moment it doesn't snap to any specific size, but it snaps to for example 1.34 and then 2.45 and so on. Reproducible: Always Steps to Reproduce: 1. Hold shift and drag the left mouse to change scale of the brush. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 361799] Crashes/visual curruption/lost windows on HIGH-dpi (4k) scaled multiscreen
https://bugs.kde.org/show_bug.cgi?id=361799 --- Comment #11 from Thomas Lübking --- You may run into bug #353428 (is the kwin process stopped?) And yes, a backtrace would be tremendously helpful, TIA =) -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361810] valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment #2 from Mark Wielaard --- I can replicate this, but only with redirected input, like in the shell script or when putting the input in a file and running with valgrind ./forktest < input_file. When stdin isn't redirected from some (here) file, but comes direct or through a pipe (cat input | valgrind ./forktest) it works as intended. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361815] New: Plasma shell crashed while repositioning plasmoid underneath existing window
https://bugs.kde.org/show_bug.cgi?id=361815 Bug ID: 361815 Summary: Plasma shell crashed while repositioning plasmoid underneath existing window Product: plasmashell Version: 5.5.5 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mike...@gmail.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.1.15-gentoo-r1 x86_64 Distribution: "NAME=Gentoo" -- Information about the crash: - What I was doing when the application crashed: Attempting to move plasmoid from upper right corner of desktop to lower left corner. There happened to be a window between the source and destination points. - Unusual behavior I noticed: I have three displays. I tried moving a plasmoid from the leftmost display to the rightmost display, and it disappeared, though the plasmoid counter indicated it was still...somewhere. Also, for the life of me, I cannot seem to get a panel to *stay* on the right edge of this rightmost display. Log out and back in, and it reappears on the right edge of my leftmost display. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f25f4bc57c0 (LWP 31125))] Thread 34 (Thread 0x7f25da3f5700 (LWP 31133)): #0 0x7f25ef3c411d in read () from /lib64/libc.so.6 #1 0x7f25eb4a6550 in g_wakeup_acknowledge () from /usr/lib64/libglib-2.0.so.0 #2 0x7f25eb46399c in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f25eb463e90 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7f25eb463ffc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f25efc2a66c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f25efbdc22a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f25efa2e4e4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f25f2234695 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #9 0x7f25efa32e92 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f25eebd1444 in start_thread () from /lib64/libpthread.so.0 #11 0x7f25ef3d112d in clone () from /lib64/libc.so.6 Thread 33 (Thread 0x7f25d0e36700 (LWP 31172)): #0 0x7f25efa2bd82 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5 #1 0x7f25efc2a3eb in postEventSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #2 0x7f25eb4638f1 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f25eb463e90 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #4 0x7f25eb463ffc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f25efc2a66c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f25efbdc22a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #7 0x7f25efa2e4e4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #8 0x7f25f2234695 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #9 0x7f25efa32e92 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #10 0x7f25eebd1444 in start_thread () from /lib64/libpthread.so.0 #11 0x7f25ef3d112d in clone () from /lib64/libc.so.6 Thread 32 (Thread 0x7f25cad92700 (LWP 31173)): #0 0x7f25efc2a3c3 in postEventSourcePrepare(_GSource*, int*) () from /usr/lib64/libQt5Core.so.5 #1 0x7f25eb46342d in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x7f25eb463e18 in g_main_context_iterate.isra () from /usr/lib64/libglib-2.0.so.0 #3 0x7f25eb463ffc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x7f25efc2a66c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/libQt5Core.so.5 #5 0x7f25efbdc22a in QEventLoop::exec(QFlags) () from /usr/lib64/libQt5Core.so.5 #6 0x7f25efa2e4e4 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x7f25f2234695 in QQmlThreadPrivate::run() () from /usr/lib64/libQt5Qml.so.5 #8 0x7f25efa32e92 in QThreadPrivate::start(void*) () from /usr/lib64/libQt5Core.so.5 #9 0x7f25eebd1444 in start_thread () from /lib64/libpthread.so.0 #10 0x7f25ef3d112d in clone () from /lib64/libc.so.6 Thread 31 (Thread 0x7f25c943e700 (LWP 31177)): #0 0x7f25eebd700f in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x7f25f461e6e4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQt5Script.so.5 #2 0x7f25f461e729 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQt5Script.so.5 #3 0x7f25
[akregator] [Bug 361816] New: Akregator crashes at the begining
https://bugs.kde.org/show_bug.cgi?id=361816 Bug ID: 361816 Summary: Akregator crashes at the begining Product: akregator Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: saldi...@yahoo.es Application: akregator (4.14.10) KDE Platform Version: 4.14.18 Qt Version: 4.8.6 Operating System: Linux 4.1.20-11-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: Application: Akregator (akregator), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5e2df1d800 (LWP 3885))] Thread 11 (Thread 0x7f5e0c1a8700 (LWP 3896)): #0 0x7f5e260dc03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5e13070eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f5e13070ee9 in () at /usr/lib64/libQtWebKit.so.4 #3 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f5dcac5b700 (LWP 3899)): #0 0x7f5e2a9e6c8d in read () at /lib64/libc.so.6 #1 0x7f5e252fdb60 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f5e252bc999 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f5e252bcdf8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f5e252bcf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f5e2c33bfde in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #6 0x7f5e2c30dd4f in QEventLoop::processEvents(QFlags) () at /usr/lib64/libQtCore.so.4 #7 0x7f5e2c30e045 in QEventLoop::exec(QFlags) () at /usr/lib64/libQtCore.so.4 #8 0x7f5e2c20b4df in QThread::exec() () at /usr/lib64/libQtCore.so.4 #9 0x7f5e2c20dbbf in () at /usr/lib64/libQtCore.so.4 #10 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f5dc96bd700 (LWP 3930)): #0 0x7f5e260dc03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5e12de3b3d in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4 #2 0x7f5e13098a06 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4 #3 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f5dc3fff700 (LWP 3955)): #0 0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f5e2c201bda in () at /usr/lib64/libQtCore.so.4 #3 0x7f5e2c20dbbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f5dc37fe700 (LWP 3956)): #0 0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f5e2c201bda in () at /usr/lib64/libQtCore.so.4 #3 0x7f5e2c20dbbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f5dc2ffd700 (LWP 3957)): #0 0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f5e2c201bda in () at /usr/lib64/libQtCore.so.4 #3 0x7f5e2c20dbbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f5dc27fc700 (LWP 3958)): #0 0x7f5e260dc3e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5e2c20e084 in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQtCore.so.4 #2 0x7f5e2c201bda in () at /usr/lib64/libQtCore.so.4 #3 0x7f5e2c20dbbf in () at /usr/lib64/libQtCore.so.4 #4 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #5 0x7f5e2a9f2fed in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f5d9dd9e700 (LWP 3973)): #0 0x7f5e260dc03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f5d9de05d79 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #2 0x7f5d9de06819 in () at /usr/lib64/java-1_8_0-openjdk-plugin/lib/IcedTeaPlugin.so #3 0x7f5e260d80a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f5e2a9f2fed in clone () at /lib64/li
[valgrind] [Bug 361810] valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #3 from Richard Jones --- For reference here is the actual test that fails for us: https://github.com/libguestfs/libguestfs/blob/master/fish/test-find0.sh#L25-L30 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #13 from Thomas Lübking --- Might have relation to bug #351112 The question is whether the keyboard grab fails after randr events or it is released afterwards. Does this also happen if you trigger present windows via a screen corner (run "kcmshell5 kwinscreenedges" for configuration)? -- You are receiving this mail because: You are watching all bug changes.
[zanshin] [Bug 357130] Not able to enable or add todo collection (existing (sub)calendar on ownCloud server)
https://bugs.kde.org/show_bug.cgi?id=357130 --- Comment #3 from Kevin Ottens --- Right, adding collections is a different thing and not supported yet. Clearly a missing feature (I'm not reopening just because it's tracked on our roadmap, it'll appear at some point and I'd like this report to be more about the enable/disable issue you had initially). -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361810] valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #4 from Tom Hughes ---
Frankly it makes no sense at all. Here's an strace of that valgrind, from the
first read on fd 0 to the second:
read(0, "abc\ndef\nghi\n", 4096)= 12
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "J", 1) = 1
pipe2([4, 5], O_CLOEXEC)= 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x60262190) = 3115
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
gettid()= 3114
write(1029, "K", 1) = 1
sched_yield() = 0
gettid()= 3114
read(1028, "K", 1) = 1
close(5)= 0
gettid()= 3114
write(1029, "L", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
read(4, "\2\0\0\0", 4) = 4
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "L", 1) = 1
close(4)= 0
gettid()= 3114
write(1029, "M", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
wait4(3115, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 3115
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3115, si_uid=2067,
si_status=0, si_utime=1, si_stime=0} ---
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "M", 1) = 1
fstat(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
mmap(0x60224000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x60224000
gettid()= 3114
write(1029, "N", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
write(1, "mask 2 buf abc\n", 15)= 15
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "N", 1) = 1
pipe2([4, 5], O_CLOEXEC)= 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x60262190) = 3116
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
gettid()= 3114
write(1029, "O", 1) = 1
sched_yield() = 0
gettid()= 3114
read(1028, "O", 1) = 1
close(5)= 0
gettid()= 3114
write(1029, "P", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
read(4, "\2\0\0\0", 4) = 4
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "P", 1) = 1
close(4)= 0
gettid()= 3114
write(1029, "Q", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
wait4(3116, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 3116
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3116, si_uid=2067,
si_status=0, si_utime=1, si_stime=0} ---
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "Q", 1) = 1
gettid()= 3114
write(1029, "R", 1) = 1
rt_sigprocmask(SIG_SETMASK, [], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
write(1, "mask 2 buf def\n", 15)= 15
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()= 3114
read(1028, "R", 1) = 1
pipe2([4, 5], O_CLOEXEC)= 0
rt_sigprocmask(SIG_SETMASK, ~[], ~[ILL TRAP BUS FPE KILL SEGV STOP], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x60262190) = 3117
rt_sigprocmask(SIG_SETMASK, ~[ILL TRAP BUS FPE KILL SEGV STOP], NULL, 8) = 0
gettid()
[plasma-nm] [Bug 361808] plasma-nm crashes Plasma upon switching WiFI network
https://bugs.kde.org/show_bug.cgi?id=361808 --- Comment #2 from madc...@atlas.cz --- Updated backtrace with debugging symbols installed for plasma-nm and networkmanager-qt Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0105243800 (LWP 881))] Thread 10 (Thread 0x7f00edf60700 (LWP 891)): #0 0x7f00fe6ebc3d in poll () from /usr/lib/libc.so.6 #1 0x7f01036ecae2 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f01036ee757 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f00ef882a99 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6 Thread 9 (Thread 0x7f00e7fff700 (LWP 895)): #0 0x7f00fe6ebc3d in poll () from /usr/lib/libc.so.6 #1 0x7f00fab6c0fc in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f00fab6c20c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f00ff003cab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f00fefac6fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f00ffd96a55 in ?? () from /usr/lib/libQt5DBus.so.5 #7 0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f00e69c8700 (LWP 908)): #0 0x7f00fabb0879 in g_mutex_lock () from /usr/lib/libglib-2.0.so.0 #1 0x7f00fab6b090 in g_main_context_acquire () from /usr/lib/libglib-2.0.so.0 #2 0x7f00fab6bfb5 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f00fab6c20c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f00ff003cab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f00fefac6fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f010217a915 in ?? () from /usr/lib/libQt5Qml.so.5 #8 0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f00dd4a1700 (LWP 919)): #0 0x7f00fab6b708 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #1 0x7f00fab6c02b in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f00fab6c20c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f00ff003cab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #4 0x7f00fefac6fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #6 0x7f010217a915 in ?? () from /usr/lib/libQt5Qml.so.5 #7 0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5 #8 0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f00d3848700 (LWP 923)): #0 0x7f00fe6e7c0d in read () from /usr/lib/libc.so.6 #1 0x7f00fabaf4f0 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f00fab6bbe4 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #3 0x7f00fab6c0a0 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0x7f00fab6c20c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #5 0x7f00ff003cab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f00fefac6fa in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #7 0x7f00fedd5fe4 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #8 0x7f010217a915 in ?? () from /usr/lib/libQt5Qml.so.5 #9 0x7f00feddade8 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f00d1f40700 (LWP 938)): #0 0x7f00fdef403f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f01049d5134 in ?? () from /usr/lib/libQt5Script.so.5 #2 0x7f01049d5179 in ?? () from /usr/lib/libQt5Script.so.5 #3 0x7f00fdeee424 in start_thread () from /usr/lib/libpthread.so.0 #4 0x7f00fe6f4cbd in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f004b20e700 (LWP 943)): #0 0x7f00fabaf4d2 in ?? () from /usr/lib/libglib-2.0.so.0 #1 0x7f00fab6bbe4 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #2 0x7f00fab6c0a0 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f00fab6c20c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f00ff003cab in QEventDispatcherGlib::processEvents(QFlags) () from /usr/li
[valgrind] [Bug 361810] valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #5 from Tom Hughes --- Ah, if you add the childs you will see each one do: 3992 lseek(0, -8, SEEK_CUR)= 4 for some reason... -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 359159] File Indexer Monitor: "Start File Indexer" button has no effect
https://bugs.kde.org/show_bug.cgi?id=359159
franz.berges...@gmail.com changed:
What|Removed |Added
CC||franz.berges...@gmail.com
--- Comment #1 from franz.berges...@gmail.com ---
I have the same problem on openSUSE Tumbleweed (20160412) (x86_64) with
Qt: 5.5.1
KDE Frameworks: 5.21.0
~> kcmshell5 kcm_fileindexer
Error loading plugin "kcm_fileindexermonitor" "The shared library was not
found."
Plugin search paths are ("/usr/lib64/qt5/plugins", "/usr/bin")
The environment variable QT_PLUGIN_PATH might be not correctly set
fetched suspend state
Trying to use rootObject before initialization is completed, whilst using
setInitializationDelayed. Forcing completion
KInit could not launch 'khelpcenter5'.
~>
The File Indexer Monitor is fired up, but show only some button, as shown in
the attachment.
A "File Indexer Monitor" app is visible both in the application dashboard and
krunner, but nothing happens.
The "File Indexer Monitor" in KInfoCenter freezes the GUI for about a minute
before showing it and there what it looks like a progress bar, but I'm not sure
it makes sense, given the issues just described
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 360841] Unable to unshow/unpresent windows using the same keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=360841 --- Comment #14 from vpiotr --- This also happens when "present windows" is triggered via a screen corner. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361810] valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #7 from Tom Hughes --- I think the problem is that __libc_freeres calls (among many other things) the _IO_unbuffer_write to free the buffers for stdio streams. That "unbuffers" each file by calling _IO_SETBUF (fp, NULL, 0) to drop the buffer, but that (which is just the internal implementation of setbuf/setvbuf) rewinds the stream over any data which has been read into the buffer but not yet consumed. Of course when the buffer is shared between multiple processes the question of what has been consumed is something of an open one... -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 361810] valgrind duplicate stdin after fork
https://bugs.kde.org/show_bug.cgi?id=361810 --- Comment #8 from Tom Hughes --- Of course the buffer isn't really shared (this is fork, not threads...) but the file position is. -- You are receiving this mail because: You are watching all bug changes.
