[ktouch] [Bug 373367] typos in de1 course
https://bugs.kde.org/show_bug.cgi?id=373367 Burkhard Lueck changed: What|Removed |Added Latest Commit||https://commits.kde.org/kto ||uch/7769aa81983b48e8a0fb550 ||d1ac8574eee57e1bf Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Burkhard Lueck --- Git commit 7769aa81983b48e8a0fb550d1ac8574eee57e1bf by Burkhard Lück. Committed on 07/12/2016 at 07:22. Pushed by lueck into branch 'master'. fix typo, thanks for spotting M +2-2data/courses/de1.xml https://commits.kde.org/ktouch/7769aa81983b48e8a0fb550d1ac8574eee57e1bf -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 137436] Adding support for cdrskin as an alternative to cdrecord/wodim
https://bugs.kde.org/show_bug.cgi?id=137436 --- Comment #71 from Leslie Zhai --- (In reply to Thomas Schmitt from comment #70) > > (I once spent two days with trying to find out why libburn failed with > a particular drive and DVD-RW where growisofs succeeded. On the third day > growisofs started to fail and libburn succeeded. It was just a matter of > luck on a flaky combination of hardware.) Hi Thomas, It is better to use Clang ThreadSanitizer to detect pthread related issue http://www.leetcode.cn/2016/11/analyzing-code-for-kde-qt-open-source-components.html#libburn I am analyzing code for K3b and other components via Clang Static Analyzer and Sanitizer ;-) Regards, Leslie Zhai -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 373376] Clicking on items in Help menu gives error
https://bugs.kde.org/show_bug.cgi?id=373376 Burkhard Lueck changed: What|Removed |Added CC||lu...@hube-lueck.de --- Comment #1 from Burkhard Lueck --- Kubuntu 16.04 partitionmanager 1.2.1 -> works Neon devedition git unstable partitionmanager 3.0.0 build from sources -> works partitionmanager master in frameworks/workspace master build from sources -> works Conclusion: Your installation is incomplete/broken (Distribution?, System?, Version of Partitionmanager?)) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 373378] New: Can't down-scale with nearest neighbor (Box)
https://bugs.kde.org/show_bug.cgi?id=373378 Bug ID: 373378 Summary: Can't down-scale with nearest neighbor (Box) Product: krita Version: 3.0.1.1 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: major Priority: NOR Component: transform Assignee: krita-bugs-n...@kde.org Reporter: bloodbath...@gmail.com Target Milestone: --- Created attachment 102656 --> https://bugs.kde.org/attachment.cgi?id=102656&action=edit upscaled 200% downscaled back by %50, supposed to be box but isn't Box scaling works when up-scaling but not down-scaling. The attached example shows an image that has been up-scaled to 200%, duplicated, and down-scaled to 50%. The down-scaled rendition shows no resemblance to nearest neighbor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358990] Make possible to move desktop icons freely again
https://bugs.kde.org/show_bug.cgi?id=358990 Aurélien Murith changed: What|Removed |Added Version|5.5.3 |master -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373111] Crash During Start Up After Login
https://bugs.kde.org/show_bug.cgi?id=373111 Sebastian Kuhne changed: What|Removed |Added CC||sebastiankuhne1@googlemail. ||com --- Comment #4 from Sebastian Kuhne --- I can confirm the same issue. To my knowledge this is new with 5.8.4. Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.10-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373377] kwin_x11 crashing
https://bugs.kde.org/show_bug.cgi?id=373377 Martin Gräßlin changed: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Gräßlin --- Unfortunately the backtrace is missing debug symbols. We see it's crashing but not where. If you are able to reproduce, please install debug packages provided by your distribution and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[user-manager] [Bug 372933] user manager is empty
https://bugs.kde.org/show_bug.cgi?id=372933 johann.jacobs...@directbox.com changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #2 from johann.jacobs...@directbox.com --- dnf install accountsservice-libs fixes this for me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367541] High memory usage when adding PIM Events in Digital Clock Widget
https://bugs.kde.org/show_bug.cgi?id=367541 --- Comment #19 from fl...@mailoo.org --- I can confirm that the bug is triggered by the presence of TODOs. To test this, I created 2 test calendars, one with TODOs, the other one without any. Without any surprise, only the former is triggering the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373377] New: kwin_x11 crashing
https://bugs.kde.org/show_bug.cgi?id=373377 Bug ID: 373377 Summary: kwin_x11 crashing Product: kwin Version: 5.8.4 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: mustaqim.ma...@live.com Target Milestone: --- Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.4.33-1-MANJARO x86_64 Distribution: "Manjaro Linux" -- Information about the crash: - What I was doing when the application crashed: Closed mpv media player that was in fullscreen mode, I often have to run kwin_x11 to restart the manager -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe855213840 (LWP 7881))] Thread 5 (Thread 0x7fe812715700 (LWP 7898)): #0 0x7fe84deeb10f in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 #1 0x7fe851241ac4 in () at /usr/lib/libQt5Script.so.5 #2 0x7fe851241b09 in () at /usr/lib/libQt5Script.so.5 #3 0x7fe84dee5454 in start_thread () at /usr/lib/libpthread.so.0 #4 0x7fe854c577df in clone () at /usr/lib/libc.so.6 Thread 4 (Thread 0x7fe81b145700 (LWP 7895)): #0 0x7fe854c4e551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe8522fbac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe8522fd3b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe8522aa23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe8520cd0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe84cc432d5 in () at /usr/lib/libQt5Qml.so.5 #6 0x7fe8520d1d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fe84dee5454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe854c577df in clone () at /usr/lib/libc.so.6 Thread 3 (Thread 0x7fe82fa76700 (LWP 7886)): #0 0x7fe854c4e551 in ppoll () at /usr/lib/libc.so.6 #1 0x7fe8522fbac9 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/libQt5Core.so.5 #2 0x7fe8522fd3b8 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #3 0x7fe8522aa23a in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe8520cd0f3 in QThread::exec() () at /usr/lib/libQt5Core.so.5 #5 0x7fe84be0de55 in () at /usr/lib/libQt5DBus.so.5 #6 0x7fe8520d1d78 in () at /usr/lib/libQt5Core.so.5 #7 0x7fe84dee5454 in start_thread () at /usr/lib/libpthread.so.0 #8 0x7fe854c577df in clone () at /usr/lib/libc.so.6 Thread 2 (Thread 0x7fe83aba2700 (LWP 7885)): #0 0x7fe854c4e48d in poll () at /usr/lib/libc.so.6 #1 0x7fe853d8e8e0 in () at /usr/lib/libxcb.so.1 #2 0x7fe853d90679 in xcb_wait_for_event () at /usr/lib/libxcb.so.1 #3 0x7fe83b64e449 in () at /usr/lib/libQt5XcbQpa.so.5 #4 0x7fe8520d1d78 in () at /usr/lib/libQt5Core.so.5 #5 0x7fe84dee5454 in start_thread () at /usr/lib/libpthread.so.0 #6 0x7fe854c577df in clone () at /usr/lib/libc.so.6 Thread 1 (Thread 0x7fe855213840 (LWP 7881)): [KCrash Handler] #6 0x7fe84cbda254 in () at /usr/lib/libQt5Qml.so.5 #7 0x7fe84cbd7eb2 in QQmlMetaType::qmlSingletonTypes() () at /usr/lib/libQt5Qml.so.5 #8 0x7fe84cbaf2d0 in QQmlEngine::~QQmlEngine() () at /usr/lib/libQt5Qml.so.5 #9 0x7fe84cbaf449 in QQmlEngine::~QQmlEngine() () at /usr/lib/libQt5Qml.so.5 #10 0x7fe854ba4990 in __run_exit_handlers () at /usr/lib/libc.so.6 #11 0x7fe854ba49ea in () at /usr/lib/libc.so.6 #12 0x7fe854c54f95 in () at /usr/lib/libc.so.6 #13 0x7fe854c550b7 in () at /usr/lib/libc.so.6 #14 0x7fe84d7da7e3 in () at /usr/lib/libepoxy.so.0 #15 0x7fe84d80063d in () at /usr/lib/libepoxy.so.0 #16 0x7fe851577e20 in () at /usr/lib/libkwin4_effect_builtins.so.1 #17 0x7fe851577ee9 in () at /usr/lib/libkwin4_effect_builtins.so.1 #18 0x7fe85481e501 in KWin::EffectsHandlerImpl::unloadAllEffects() () at /usr/lib/libkwin.so.5 #19 0x7fe85481e68c in KWin::EffectsHandlerImpl::~EffectsHandlerImpl() () at /usr/lib/libkwin.so.5 #20 0x7fe85481e7b9 in KWin::EffectsHandlerImpl::~EffectsHandlerImpl() () at /usr/lib/libkwin.so.5 #21 0x7fe8547dba09 in KWin::Compositor::finish() () at /usr/lib/libkwin.so.5 #22 0x7fe8547dc90c in KWin::Compositor::suspend(KWin::Compositor::SuspendReason) () at /usr/lib/libkwin.so.5 #23 0x7fe8522d84b9 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #24 0x7fe852f8be0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7fe852f93581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #26 0x7fe8522abde0 in QCoreApplication::notifyInternal2(QOb
[partitionmanager] [Bug 373376] New: Clicking on items in Help menu gives error
https://bugs.kde.org/show_bug.cgi?id=373376 Bug ID: 373376 Summary: Clicking on items in Help menu gives error Product: partitionmanager Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: raghavendr.ra...@gmail.com Target Milestone: --- When user clicks on some items of help menu like help, donate, launching bug report wizard etc or tries to access them by pressing shortcut. (for example F1 for help) partition manager displays and error stating "Could not start process Cannot talk to klauncher: Not connected to D-Bus server." So the above mentioned entries in the help menu are useless for the user. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 373375] New: Gwenview crashes when zoom is changed
https://bugs.kde.org/show_bug.cgi?id=373375 Bug ID: 373375 Summary: Gwenview crashes when zoom is changed Product: gwenview Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kdeb...@plast.id.au CC: myr...@kde.org Target Milestone: --- Application: gwenview (16.08.3) Qt Version: 5.7.0 Frameworks Version: 5.28.0 Operating System: Linux 4.8.11-1-ARCH x86_64 Distribution: "Arch Linux" -- Information about the crash: - What I was doing when the application crashed: Attempt to zoom a jpeg with Ctrl+[scroll wheel] or with the zoom slider Possibly related to https://bugs.kde.org/show_bug.cgi?id=362541 , but the backtrace looks different. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3613dde8c0 (LWP 29502))] Thread 3 (Thread 0x7f35fa84a700 (LWP 29504)): #0 0x7f3607124dd4 in g_mutex_unlock () from /usr/lib/libglib-2.0.so.0 #1 0x7f36070def89 in g_main_context_query () from /usr/lib/libglib-2.0.so.0 #2 0x7f36070df6f8 in ?? () from /usr/lib/libglib-2.0.so.0 #3 0x7f36070df89c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #4 0x7f360f06372b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #5 0x7f360f00d23a in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #6 0x7f360ee300f3 in QThread::exec() () from /usr/lib/libQt5Core.so.5 #7 0x7f360e3ece55 in ?? () from /usr/lib/libQt5DBus.so.5 #8 0x7f360ee34d78 in ?? () from /usr/lib/libQt5Core.so.5 #9 0x7f360872d454 in start_thread () from /usr/lib/libpthread.so.0 #10 0x7f360e74a7df in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f35fc608700 (LWP 29503)): #0 0x7f360e74148d in poll () from /usr/lib/libc.so.6 #1 0x7f36065338e0 in ?? () from /usr/lib/libxcb.so.1 #2 0x7f3606535679 in xcb_wait_for_event () from /usr/lib/libxcb.so.1 #3 0x7f35fdf1f449 in ?? () from /usr/lib/libQt5XcbQpa.so.5 #4 0x7f360ee34d78 in ?? () from /usr/lib/libQt5Core.so.5 #5 0x7f360872d454 in start_thread () from /usr/lib/libpthread.so.0 #6 0x7f360e74a7df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f3613dde8c0 (LWP 29502)): [KCrash Handler] #6 0x7f360e69504f in raise () from /usr/lib/libc.so.6 #7 0x7f360e69647a in abort () from /usr/lib/libc.so.6 #8 0x7f360e6d2c50 in __libc_message () from /usr/lib/libc.so.6 #9 0x7f360e6d8fe6 in malloc_printerr () from /usr/lib/libc.so.6 #10 0x7f360f5a069d in QImageData::~QImageData() () from /usr/lib/libQt5Gui.so.5 #11 0x7f360f5a0f17 in QImage::~QImage() () from /usr/lib/libQt5Gui.so.5 #12 0x7f360f5dd65c in QRasterPlatformPixmap::~QRasterPlatformPixmap() () from /usr/lib/libQt5Gui.so.5 #13 0x7f360f5dd679 in QRasterPlatformPixmap::~QRasterPlatformPixmap() () from /usr/lib/libQt5Gui.so.5 #14 0x7f360f5cef61 in QPixmap::~QPixmap() () from /usr/lib/libQt5Gui.so.5 #15 0x7f36135a23f0 in Gwenview::RasterImageView::updateFromScaler(int, int, QImage const&) () from /usr/lib/libgwenviewlib.so.5 #16 0x7f360f03a9ce in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQt5Core.so.5 #17 0x7f361361fa21 in Gwenview::ImageScaler::scaledRect(int, int, QImage const&) () from /usr/lib/libgwenviewlib.so.5 #18 0x7f36135ca58e in Gwenview::ImageScaler::scaleRect(QRect const&) () from /usr/lib/libgwenviewlib.so.5 #19 0x7f36135ca877 in Gwenview::ImageScaler::doScale() () from /usr/lib/libgwenviewlib.so.5 #20 0x7f36135a0eb4 in Gwenview::RasterImageView::updateBuffer(QRegion const&) () from /usr/lib/libgwenviewlib.so.5 #21 0x7f36135a1023 in Gwenview::RasterImageView::onZoomChanged() () from /usr/lib/libgwenviewlib.so.5 #22 0x7f3613591c26 in ?? () from /usr/lib/libgwenviewlib.so.5 #23 0x7f361359a5f7 in Gwenview::DocumentView::zoomIn(QPointF const&) () from /usr/lib/libgwenviewlib.so.5 #24 0x7f361359a828 in Gwenview::DocumentView::wheelEvent(QGraphicsSceneWheelEvent*) () from /usr/lib/libgwenviewlib.so.5 #25 0x7f36109e224e in QGraphicsItem::sceneEvent(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #26 0x7f3610a0a1a5 in QGraphicsScene::wheelEvent(QGraphicsSceneWheelEvent*) () from /usr/lib/libQt5Widgets.so.5 #27 0x7f3610a17300 in QGraphicsScene::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #28 0x7f36106fce0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #29 0x7f3610704581 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #30 0x7f360f00ede0 in QCoreApplication::notifyInternal2(QObject*, QEven
[korgac] [Bug 372653] korgac crash on startup (korgac version 5.3.3 )
https://bugs.kde.org/show_bug.cgi?id=372653 Weng Xuetian changed: What|Removed |Added Resolution|--- |UPSTREAM CC||wen...@gmail.com Status|UNCONFIRMED |RESOLVED --- Comment #4 from Weng Xuetian --- As fcitx/kde developer I don't think this is caused by fcitx. I have hit many qt dbus bug since 5.6. There're several qt dbus bug may trigger it (e.g. https://bugreports.qt.io/browse/QTBUG-52988), but so far we use following patch upstream qt patch on chakra and I can't reproduce the problem here. https://github.com/qt/qtbase/commit/494376f980e96339b6f1eff7c41336ca4d853065.patch -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 373374] Test failures with gnupg-2.1.16
https://bugs.kde.org/show_bug.cgi?id=373374 Jan Kundrát changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Jan Kundrát --- I'm having lots of fun so far. I did some debugging and it seems to me that my gpg-agent started deadlocking: (gdb) t a a bt Thread 3 (Thread 0x7fcaa700 (LWP 23673)): #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7fcab5369f65 in __GI___pthread_mutex_lock (mutex=0x7fcab5ecbd08 ) at ../nptl/pthread_mutex_lock.c:81 #2 0x0080 in ?? () #3 0x7fcaa8003aa0 in ?? () #4 0x7fcab60e6a20 in ?? () #5 0x7fcaafffeaf0 in ?? () #6 0x7fcab5c87b7a in _gcry_mpi_randomize (w=0x80, nbits=, level=) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/mpi/mpiutil.c:655 #7 0x in ?? () Thread 2 (Thread 0x7fcab4fb3700 (LWP 23657)): #0 0x7fcab536fb8b in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7fcab5782080 ) at ../sysdeps/unix/sysv/linux/futex-internal.h:205 #1 do_futex_wait (sem=sem@entry=0x7fcab5782080 , abstime=0x0) at sem_waitcommon.c:111 #2 0x7fcab536fc5c in __new_sem_wait_slow (sem=0x7fcab5782080 , abstime=0x0) at sem_waitcommon.c:181 #3 0x7fcab536fd0e in __new_sem_wait (sem=) at sem_wait.c:29 #4 0x7fcab557fdc1 in leave_npth () at /var/tmp/portage/dev-libs/npth-1.2/work/npth-1.2/src/npth.c:134 #5 0x7fcab558061c in npth_usleep (usec=) at /var/tmp/portage/dev-libs/npth-1.2/work/npth-1.2/src/npth.c:497 #6 0x7fcab5c7e302 in _gcry_rndlinux_gather_random (add=0x7fcab5c794e0 , origin=RANDOM_ORIGIN_SLOWPOLL, length=90, level=) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/random/rndlinux.c:205 #7 0x7fcab5c79092 in read_random_source (origin=origin@entry=RANDOM_ORIGIN_SLOWPOLL, length=length@entry=120, level=level@entry=1) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/random/random-csprng.c:1275 #8 0x7fcab5c7a184 in random_poll () at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/random/random-csprng.c:1101 #9 read_pool (level=0, length=, buffer=0x7fcab5ecc6a4 "") at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/random/random-csprng.c:995 #10 _gcry_rngcsprng_randomize (buffer=, length=, level=GCRY_WEAK_RANDOM) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/random/random-csprng.c:538 #11 0x7fcab5c78efb in _gcry_randomize (level=GCRY_WEAK_RANDOM, length=8, buffer=0x7fcab5ecc6a4 ) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/random/random.c:341 #12 _gcry_create_nonce (buffer=buffer@entry=0x7fcab60e6228, length=length@entry=128) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/random/random.c:466 #13 0x7fcab5c87b7a in _gcry_mpi_randomize (w=w@entry=0x7fcab0003ab0, nbits=nbits@entry=1024, level=level@entry=GCRY_WEAK_RANDOM) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/mpi/mpiutil.c:655 #14 0x7fcab5c49e2d in secret_blinded (output=0x7fcab0003a90, input=0x7fcab0001d70, sk=0x7fcab4fb2b90, nbits=1024) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/cipher/rsa.c:1067 #15 0x7fcab5c4a6d5 in rsa_decrypt (r_plain=0x7fcab4fb2d08, s_data=, keyparms=0x7fcab0003880) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/cipher/rsa.c:1365 #16 0x7fcab5bd451f in _gcry_pk_decrypt (r_plain=r_plain@entry=0x7fcab4fb2d08, s_data=s_data@entry=0x7fcab00030f0, s_skey=s_skey@entry=0x7fcab00031a0) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/cipher/pubkey.c:377 #17 0x7fcab5bbe0d6 in gcry_pk_decrypt (result=result@entry=0x7fcab4fb2d08, data=0x7fcab00030f0, skey=0x7fcab00031a0) at /var/tmp/portage/dev-libs/libgcrypt-1.7.3/work/libgcrypt-1.7.3/src/visibility.c:985 #18 0x55e5d82880e9 in agent_pkdecrypt (ctrl=ctrl@entry=0x55e5d89c7d60, desc_text=, ciphertext=0x7fcab0001ed0 "(7:enc-val(3:rsa(1:a129:", ciphertextlen=156, outbuf=outbuf@entry=0x7fcab4fb2d90, r_padding=r_padding@entry=0x7fcab4fb2d7c) at pkdecrypt.c:109 #19 0x55e5d8278412 in cmd_pkdecrypt (ctx=0x7fcab8f0, line=) at command.c:849 #20 0x7fcab578c60d in dispatch_command (ctx=0x7fcab8f0, line=, linelen=) at assuan-handler.c:675 #21 0x7fcab578ca7f in process_request (ctx=0x7fcab8f0) at assuan-handler.c:871 #22 assuan_process (ctx=0x7fcab8f0) at assuan-handler.c:894 #23 0x55e5d827b31b in start_command_handler (ctrl=0x55e5d89c7d60, listen_fd=, fd=) at command.c:3304 #24 0x55e5d82730b9 in do_start_connection_thread (ctrl=0x55e5d89c7d60) at gpg-agent.c:2601 #25 0x7fcab557febf in thread_start (startup_arg=) at /var/tmp/portage/dev-libs/npth-1.2/work/npth-1.2/src/npth.
[korgac] [Bug 372653] korgac crash on startup (korgac version 5.3.3 )
https://bugs.kde.org/show_bug.cgi?id=372653 --- Comment #3 from Sasasu --- korganizer 16.11.90-1 (korgac 5.3.90 beta1 in KDE-Unstable) have the same problem -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 370373] Please sort on saving index.xml
https://bugs.kde.org/show_bug.cgi?id=370373 --- Comment #4 from Johannes Zarl-Zierl --- Git commit d5f1ac71af2217f33df56b3c9739030ea2b60ae0 by Johannes Zarl-Zierl. Committed on 07/12/2016 at 01:16. Pushed by johanneszarl into branch 'master'. Make writing index.xml more deterministic. There were still a few QSet uses left that introduce non-determinism in file-writing. There is still some work to be done, but getting back diffable files seems viable. (Performance will also have to be checked, afterwards... M +9-2XMLDB/FileWriter.cpp M +2-3XMLDB/XMLCategory.cpp https://commits.kde.org/kphotoalbum/d5f1ac71af2217f33df56b3c9739030ea2b60ae0 -- You are receiving this mail because: You are watching all bug changes.
[korgac] [Bug 372653] korgac crash on startup (korgac version 5.3.3 )
https://bugs.kde.org/show_bug.cgi?id=372653 Sasasu changed: What|Removed |Added CC||lizhaolong0...@gmail.com --- Comment #2 from Sasasu --- Steps to reproduce the problem on archlinux: 1. install korganizer 16.08.3-1 and fcitx 4.2.9.1-2 and fcitx-qt5 1.0.6-1 2. export QT_IM_MODULE=fcitx 3. korgac -v 4. Application 'korgac' crashing log: Application: korgac (korgac), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6b2dba7900 (LWP 16625))] Thread 2 (Thread 0x7f6afedfb700 (LWP 16627)): [KCrash Handler] #6 0x7f6b282df9cf in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5 #7 0x7f6b28729530 in ?? () from /usr/lib/libQt5DBus.so.5 #8 0x7f6b28715f62 in ?? () from /usr/lib/libQt5DBus.so.5 #9 0x7f6b280d5d78 in ?? () from /usr/lib/libQt5Core.so.5 #10 0x7f6b1fc30454 in start_thread () from /usr/lib/libpthread.so.0 #11 0x7f6b277d47df in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f6b2dba7900 (LWP 16625)): #0 0x7f6b1fc3610f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x7f6b280d6c2b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5 #2 0x7f6b280d591e in QThread::wait(unsigned long) () from /usr/lib/libQt5Core.so.5 #3 0x7f6b28715cc6 in ?? () from /usr/lib/libQt5DBus.so.5 #4 0x7f6b28715d59 in ?? () from /usr/lib/libQt5DBus.so.5 #5 0x7f6b27721990 in __run_exit_handlers () from /usr/lib/libc.so.6 #6 0x7f6b277219ea in exit () from /usr/lib/libc.so.6 #7 0x7f6b280e53ee in QCommandLineParser::showVersion() () from /usr/lib/libQt5Core.so.5 #8 0x7f6b280e in QCommandLineParser::process(QStringList const&) () from /usr/lib/libQt5Core.so.5 #9 0x7f6b280e66cf in QCommandLineParser::process(QCoreApplication const&) () from /usr/lib/libQt5Core.so.5 #10 0x004119db in ?? () #11 0x7f6b2770c291 in __libc_start_main () from /usr/lib/libc.so.6 #12 0x00411c2a in _start () -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 372904] kded5 maxing one CPU core after search performed in Dolphin
https://bugs.kde.org/show_bug.cgi?id=372904 --- Comment #3 from Gerardo Exequiel Pozzi --- There is a flood of this messages on session bus, when this happens. signal time=1481071391.183634 sender=:1.147 -> destination=(null destination) serial=645086 path=/; interface=org.kde.KDirNotify; member=FilesAdded string "filenamesearch:?search=maze&url=file:///mnt/data" -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 370373] Please sort on saving index.xml
https://bugs.kde.org/show_bug.cgi?id=370373 --- Comment #3 from Johannes Zarl-Zierl --- How is fb60b996 for a change? I've refrained from sorting the tags and member-groups in the way you describe, because this would mean that numerical tag id's change every time I add a tag (and thus almost every image entry would change as well). -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 373374] Test failures with gnupg-2.1.16
https://bugs.kde.org/show_bug.cgi?id=373374 --- Comment #1 from Jan Kundrát --- OK, it seems that for those tests where validation should actually succeed, GnuPG::Context::decryptAndVerify never returns. Here's what remains running in the system after these failures (two test rows actually happen): jkt@kolibrik ~/work/prog/_trojita-build/qt5 $ ps -ef | grep gnupg jkt 11066 3509 0 01:37 pts/500:00:00 grep --colour=auto gnupg jkt@kolibrik ~/work/prog/_trojita-build/qt5 $ ps -ef | grep gpg jkt 8492 1 0 01:15 ?00:00:00 gpg-agent --homedir /home/jkt/work/prog/_trojita-build/qt5/keys --use-standard-socket --daemon jkt 11017 1 0 01:37 pts/500:00:00 gpg2 --enable-special-filenames --batch --no-sk-comments --status-fd 7 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0 --decrypt --output - -- -&10 jkt 11023 1 0 01:37 pts/500:00:00 gpg2 --enable-special-filenames --batch --no-sk-comments --status-fd 9 --no-tty --charset utf8 --enable-progress-filter --exit-on-status-write-error --display :0 --decrypt --output - -- -&12 jkt 11074 3509 0 01:37 pts/500:00:00 grep --colour=auto gpg jkt@kolibrik ~/work/prog/_trojita-build/qt5 $ lsof -p 8492 lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing Output information may be incomplete. COMMANDPID USER FD TYPE DEVICE SIZE/OFF NODE NAME gpg-agent 8492 jkt cwd DIR 254,0 24896 / gpg-agent 8492 jkt rtd DIR 254,0 24896 / gpg-agent 8492 jkt txt REG 254,0 414360 274454906 /usr/bin/gpg-agent gpg-agent 8492 jkt mem REG 254,0 1738328 410388282 /lib64/libc-2.22.so gpg-agent 8492 jkt mem REG 254,0 105272 410395864 /lib64/libpthread-2.22.so gpg-agent 8492 jkt mem REG 254,018248 269514259 /usr/lib64/libnpth.so.0.0.5 gpg-agent 8492 jkt mem REG 254,088112931164 /usr/lib64/libassuan.so.0.7.3 gpg-agent 8492 jkt mem REG 254,092128 134752584 /usr/lib64/libgpg-error.so.0.19.1 gpg-agent 8492 jkt mem REG 254,0 1166304 268688873 /usr/lib64/libgcrypt.so.20.1.3 gpg-agent 8492 jkt mem REG 254,0 148816 410388248 /lib64/ld-2.22.so gpg-agent 8492 jkt mem REG 254,0 1745248 268688934 /usr/lib64/locale/locale-archive gpg-agent 8492 jkt0r CHR1,3 0t0 2051 /dev/null gpg-agent 8492 jkt1w CHR1,3 0t0 2051 /dev/null gpg-agent 8492 jkt2w CHR1,3 0t0 2051 /dev/null gpg-agent 8492 jkt3u unix 0x88d6b3479800 0t0429639 /home/jkt/work/prog/_trojita-build/qt5/keys/S.gpg-agent type=STREAM gpg-agent 8492 jkt4u unix 0x88d6b3479c00 0t0429640 /home/jkt/work/prog/_trojita-build/qt5/keys/S.gpg-agent.extra type=STREAM gpg-agent 8492 jkt5u unix 0x88d6b3479400 0t0429641 /home/jkt/work/prog/_trojita-build/qt5/keys/S.gpg-agent.browser type=STREAM gpg-agent 8492 jkt6u unix 0x88d6b347a000 0t0429642 /home/jkt/work/prog/_trojita-build/qt5/keys/S.gpg-agent.ssh type=STREAM gpg-agent 8492 jkt7r a_inode 0,110 8449 inotify gpg-agent 8492 jkt8u unix 0x88d503b3e000 0t0429648 /home/jkt/work/prog/_trojita-build/qt5/keys/S.gpg-agent type=STREAM gpg-agent 8492 jkt9r CHR1,9 0t0 2056 /dev/urandom gpg-agent 8492 jkt 10u unix 0x88d9a0edf400 0t0427933 /home/jkt/work/prog/_trojita-build/qt5/keys/S.gpg-agent type=STREAM jkt@kolibrik ~/work/prog/_trojita-build/qt5 $ lsof -p 11017 lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME gpg211017 jkt cwdDIR 254,020480 174033037 /home/jkt/work/prog/_trojita-build/qt5 gpg211017 jkt rtdDIR 254,0 24896 / gpg211017 jkt txtREG 254,0 991856 274761284 /usr/bin/gpg2 gpg211017 jkt memREG 254,0 244416 402758332 /lib64/libtinfo.so.6.0 gpg211017 jkt memREG 254,0 1738328 410388282 /lib64/libc-2.22.so gpg211017 jkt memREG 254,088112931164 /usr/lib64/libassuan.so.0.7.3 gpg211017 jkt memREG 254,0 330624 135078460 /lib64/libreadline.so.6.3 gpg211017 jkt memREG 254,092128 134752584 /usr/lib64/libgpg-error.so.0.19.1 gpg211017 jkt memREG 254,0 1166304 268688873 /usr/lib64/libgcrypt.so.20.1.3 gpg211017 jkt memREG 254,070520 402976937 /lib64/libbz2.so.1.0.6 gpg211017 jkt memREG
[kphotoalbum] [Bug 370373] Please sort on saving index.xml
https://bugs.kde.org/show_bug.cgi?id=370373 --- Comment #2 from Johannes Zarl-Zierl --- Git commit fb60b9965e353e938507e1dd6c3c0ea636824235 by Johannes Zarl-Zierl. Committed on 07/12/2016 at 00:32. Pushed by johanneszarl into branch 'master'. Try harder to get minimal changes in the index.xml Scripts like kpa-backup require diff-able files if one wants human-readable change descriptions. This tweaks XMLCategory::addItem() so that it doesn't always change all numerical category ids, and sorts the blocklist before writing it to a file. M +4-1XMLDB/FileWriter.cpp M +2-2XMLDB/XMLCategory.cpp https://commits.kde.org/kphotoalbum/fb60b9965e353e938507e1dd6c3c0ea636824235 -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 373374] New: Test failures with gnupg-2.1.16
https://bugs.kde.org/show_bug.cgi?id=373374
Bug ID: 373374
Summary: Test failures with gnupg-2.1.16
Product: trojita
Version: git
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Cryptography
Assignee: trojita-b...@kde.org
Reporter: j...@kde.org
Target Milestone: ---
Continuing from https://bugzilla.redhat.com/show_bug.cgi?id=1401716 . It seems
that signature verification of our internal supposed-to-be-valid signature
doesn't conclude for some reason. Debug patch:
diff --git a/tests/Cryptography/test_Cryptography_PGP.cpp
b/tests/Cryptography/test_Cryptography_PGP.cpp
index 2d33a4d..bd9628c 100644
--- a/tests/Cryptography/test_Cryptography_PGP.cpp
+++ b/tests/Cryptography/test_Cryptography_PGP.cpp
@@ -110,6 +110,8 @@ void CryptographyPGPTest::testDecryption()
}
// allow for event processing, so that the model can retrieve the results
QCoreApplication::processEvents();
+// ensure that we're done now
+QVERIFY(!data.data(Imap::Mailbox::RolePartCryptoNotFinishedYet).toBool());
if (!qcaErrorSpy.isEmpty() && successful) {
qDebug() << "Unexpected failure in crypto";
jkt@kolibrik ~/work/prog/_trojita-build/qt5 $ ninja && ctest -R
test_Cryptography_PGP -VV
[53/53] Linking CXX executable test_Cryptography_PGP
UpdateCTestConfiguration from
:/home/jkt/work/prog/_trojita-build/qt5/DartConfiguration.tcl
UpdateCTestConfiguration from
:/home/jkt/work/prog/_trojita-build/qt5/DartConfiguration.tcl
Test project /home/jkt/work/prog/_trojita-build/qt5
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
test 24
Start 24: test_Cryptography_PGP
24: Test command: /home/jkt/work/prog/_trojita-build/qt5/test_Cryptography_PGP
24: Environment variables:
24: UBSAN_OPTIONS=suppressions=/home/jkt/work/prog/trojita/tests/ubsan.supp
24: Test timeout computed to be: 9.99988e+06
24: * Start testing of CryptographyPGPTest *
24: Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64
shared (dynamic) release build; by GCC 4.9.3)
24: PASS : CryptographyPGPTest::initTestCase()
24: FAIL! : CryptographyPGPTest::testDecryption(valid)
'!data.data(Imap::Mailbox::RolePartCryptoNotFinishedYet).toBool()' returned
FALSE. ()
24:Loc:
[/home/jkt/work/prog/trojita/tests/Cryptography/test_Cryptography_PGP.cpp(114)]
24: QDEBUG : CryptographyPGPTest::testDecryption(valid) We have 1 orphaned
crypto tasks
24: PASS : CryptographyPGPTest::testDecryption(invalid)
24: FAIL! : CryptographyPGPTest::testDecryption(expiredKey)
'!data.data(Imap::Mailbox::RolePartCryptoNotFinishedYet).toBool()' returned
FALSE. ()
24:Loc:
[/home/jkt/work/prog/trojita/tests/Cryptography/test_Cryptography_PGP.cpp(114)]
24: QDEBUG : CryptographyPGPTest::testDecryption(expiredKey) We have 1 orphaned
crypto tasks
24: PASS : CryptographyPGPTest::testDecryption(unknownKey)
24: PASS : CryptographyPGPTest::testDecryptWithoutEnvelope()
24: PASS : CryptographyPGPTest::testVerification(valid-me)
24: PASS :
CryptographyPGPTest::testVerification(my-signature-different-identity)
24: PASS : CryptographyPGPTest::testVerification(my-signature-different-data)
24: PASS :
CryptographyPGPTest::testVerification(invalid-implicit-content-type)
24: PASS : CryptographyPGPTest::testMalformed(signed-missing-protocol-micalg)
24: PASS :
CryptographyPGPTest::testMalformed(signed-ml-stripped-gpg-signature)
24: PASS : CryptographyPGPTest::testOffline(signed)
24: PASS : CryptographyPGPTest::testOffline(encrypted)
24: PASS : CryptographyPGPTest::cleanupTestCase()
24: Totals: 13 passed, 2 failed, 0 skipped, 0 blacklisted, 21125ms
24: * Finished testing of CryptographyPGPTest *
1/1 Test #24: test_Cryptography_PGP ***Failed 21.14 sec
0% tests passed, 1 tests failed out of 1
Total Test time (real) = 21.14 sec
The following tests FAILED:
24 - test_Cryptography_PGP (Failed)
Errors while running CTest
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 373373] New: Plasmashell crash when disconnecting or powering off monitors in multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=373373 Bug ID: 373373 Summary: Plasmashell crash when disconnecting or powering off monitors in multi-monitor setup Product: plasmashell Version: 5.8.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: spr...@redhat.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.11-300.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: Plasmashell pretty reliably crashes whenever a monitor is disconnected or (at least in my setup with Dell P2415Qs) when the monitors power off to go into a sleep mode. 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 0x7f357134e940 (LWP 4553))] Thread 19 (Thread 0x7f344f3f6700 (LWP 1250)): #0 0x7f357d542460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f357edff09a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3582a64ab5 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f3582a653aa in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f357edfea1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f357d53c6ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f357e1f1f6f in clone () at /lib64/libc.so.6 Thread 18 (Thread 0x7f3474fad700 (LWP 22410)): #0 0x7f357d542460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f357edff09a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3582a64ab5 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f3582a653aa in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f357edfea1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f357d53c6ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f357e1f1f6f in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f3480b40700 (LWP 21819)): #0 0x7f357e1e1bdd in read () at /lib64/libc.so.6 #1 0x7f3572f830d1 in pa_read () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #2 0x7f357381c33e in pa_mainloop_prepare () at /lib64/libpulse.so.0 #3 0x7f357381cdb0 in pa_mainloop_iterate () at /lib64/libpulse.so.0 #4 0x7f357381ce70 in pa_mainloop_run () at /lib64/libpulse.so.0 #5 0x7f357382ae99 in thread () at /lib64/libpulse.so.0 #6 0x7f3572fb2178 in internal_thread_func () at /usr/lib64/pulseaudio/libpulsecommon-9.0.so #7 0x7f357d53c6ca in start_thread () at /lib64/libpthread.so.0 #8 0x7f357e1f1f6f in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f34777bb700 (LWP 15960)): #0 0x7f357d542460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f357edff09a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3582a64ab5 in QSGRenderThread::processEventsAndWaitForMore() () at /lib64/libQt5Quick.so.5 #3 0x7f3582a653aa in QSGRenderThread::run() () at /lib64/libQt5Quick.so.5 #4 0x7f357edfea1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #5 0x7f357d53c6ca in start_thread () at /lib64/libpthread.so.0 #6 0x7f357e1f1f6f in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f3476377700 (LWP 9288)): #0 0x7f3576f7e1e0 in g_source_iter_next () at /lib64/libglib-2.0.so.0 #1 0x7f3576f8063b in g_main_context_prepare () at /lib64/libglib-2.0.so.0 #2 0x7f3576f8107b in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0 #3 0x7f3576f8126c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #4 0x7f357efebd8b in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #5 0x7f357ef9d0ba in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #6 0x7f357edfa643 in QThread::exec() () at /lib64/libQt5Core.so.5 #7 0x7f358206e735 in QQmlThreadPrivate::run() () at /lib64/libQt5Qml.so.5 #8 0x7f357edfea1a in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #9 0x7f357d53c6ca in start_thread () at /lib64/libpthread.so.0 #10 0x7f357e1f1f6f in clone () at /lib64/libc.so.6 Thread 14 (Thread 0x7f3481bed700 (LWP 9285)): #0 0x7f357d542460 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f357edff09a in QWaitCondition::wait(QMutex*, unsigned long) () at /lib64/libQt5Core.so.5 #2 0x7f3582a64ab5 in QSGR
[kphotoalbum] [Bug 359625] event always selected
https://bugs.kde.org/show_bug.cgi?id=359625 Johannes Zarl-Zierl changed: What|Removed |Added CC||johan...@zarl-zierl.at --- Comment #3 from Johannes Zarl-Zierl --- Sorry for the long (what an understatement) delay. Looking again at this bug, the only reason I can think of is that the tag "Tiere" is possibly set as you "untagged tag". To verify, look at the "Categories" page in the settings and check the "Untagged Images" settings (If you use the German locale, "Bilder ohne Stichwort"). If the tag appears there, it will be automatically applied to all new images. To change, simply select another tag or no tag at all. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 141244] aKregator updates feed even if configured to never do so
https://bugs.kde.org/show_bug.cgi?id=141244 --- Comment #12 from Ricardo J. Barberis --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 360796] Difficulties to compile with plugins and how to solve them
https://bugs.kde.org/show_bug.cgi?id=360796 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|CONFIRMED |RESOLVED --- Comment #2 from Johannes Zarl-Zierl --- The specific problems you encountered should be history now (simply because KPhotoAlbum is now ported to Qt5/KDE Frameworks. I'm marking this as resolved if you don't mind... -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 --- Comment #14 from Oliver Henshaw --- Just a note that IIRC xsmp first came about in the early 1990s - so it probably predates gtk. But I think the legacy session management is just what you get if you don't take advantage of the libraries in your toolkit that support xsmp. I think the main difference with Qt is that you would have to make an effort to opt out to avoid xsmp and fall back to the "legacy session management". -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 365873] When playing jpg's and mpeg's in Slideshow, the whole program exits without warning.
https://bugs.kde.org/show_bug.cgi?id=365873 Johannes Zarl-Zierl changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |REMIND --- Comment #3 from Johannes Zarl-Zierl --- Were you able to replicate the bug? -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 371233] Crash when adding category
https://bugs.kde.org/show_bug.cgi?id=371233 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED --- Comment #2 from Johannes Zarl-Zierl --- I'm closing this bug because there is not enough info to reproduce. Feel free to reopen with more information... -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 360876] Qt5/KF5 port of KPhotoAlbum
https://bugs.kde.org/show_bug.cgi?id=360876 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 362474] Copy To/Move To does not remember path any more
https://bugs.kde.org/show_bug.cgi?id=362474 peter_n...@web.de changed: What|Removed |Added CC||peter_n...@web.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373372] New: Crash of the plasma in the transition from the desktop menu items
https://bugs.kde.org/show_bug.cgi?id=373372 Bug ID: 373372 Summary: Crash of the plasma in the transition from the desktop menu items Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: kuznecov0...@yandex.ru CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.27-2-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: I open the desktop menu. Turn into one of the groups of applications, then the selected mouse, at some point and abruptly turn into another category. There hang, then drop. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8d3ddc7900 (LWP 2262))] Thread 18 (Thread 0x7f8c463b4700 (LWP 6962)): #0 0x7f8d36cfd0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8d37be965b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8c7ec6c42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8c7ec6fdea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8c7ec6a45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f8c7ec6da46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f8d37be89e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8d36cf8734 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8d374f7d3d in clone () at /lib64/libc.so.6 Thread 17 (Thread 0x7f8c46bb5700 (LWP 6961)): #0 0x7f8d36cfd0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8d37be965b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8c7ec6c42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8c7ec6fdea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8c7ec6a45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f8c7ec6fe32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f8c7ec6a45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7f8c7ec6fe32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7f8c7ec6a45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #9 0x7f8c7ec6fe32 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #10 0x7f8c7ec6a45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #11 0x7f8c7ec6da46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #12 0x7f8d37be89e9 in () at /usr/lib64/libQt5Core.so.5 #13 0x7f8d36cf8734 in start_thread () at /lib64/libpthread.so.0 #14 0x7f8d374f7d3d in clone () at /lib64/libc.so.6 Thread 16 (Thread 0x7f8c473b6700 (LWP 6960)): #0 0x7f8d36cfd0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8d37be965b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8c7ec6c42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8c7ec6fdea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8c7ec6a45b in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f8c7ec6da46 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f8d37be89e9 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f8d36cf8734 in start_thread () at /lib64/libpthread.so.0 #8 0x7f8d374f7d3d in clone () at /lib64/libc.so.6 Thread 15 (Thread 0x7f8c47bb7700 (LWP 6959)): #0 0x7f8d36cfd0af in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f8d37be965b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f8c7ec6c42f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f8c7ec6fdea in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f8c7ec6a45b in ThreadWeaver::Weaver::applyForWork(Thread
[plasmashell] [Bug 373222] [PATCH] switch from taskmanager to icontasks
https://bugs.kde.org/show_bug.cgi?id=373222 Eike Hein changed: What|Removed |Added CC||h...@kde.org Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Eike Hein --- No. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 373249] Ports on components are not aligned at component border
https://bugs.kde.org/show_bug.cgi?id=373249 clush...@gmx.net changed: What|Removed |Added Attachment #102618|0 |1 is obsolete|| --- Comment #4 from clush...@gmx.net --- Created attachment 102655 --> https://bugs.kde.org/attachment.cgi?id=102655&action=edit Place ports onto parent border Pins stay attached to outside shape. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 373371] New: Crash while calculating formula in Krunner
https://bugs.kde.org/show_bug.cgi?id=373371 Bug ID: 373371 Summary: Crash while calculating formula in Krunner Product: krunner Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: opensuse.lietuviu.ka...@gmail.com Target Milestone: --- Application: krunner (5.8.3) Qt Version: 5.6.1 Frameworks Version: 5.26.0 Operating System: Linux 4.4.27-2-default x86_64 Distribution: "openSUSE Leap 42.2" -- Information about the crash: - What I was doing when the application crashed: Press Alt+F2, enter mathematic expression. Notification about crash occured. -- Backtrace: Application: krunner (krunner), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 [Current thread is 1 (Thread 0x7f1b1ecef8c0 (LWP 3737))] Thread 13 (Thread 0x7f1aded76700 (LWP 4628)): #0 0x7f1b1a4f149d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1b177c3314 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7f1ac00043c0, timeout=-1, context=0x7f1ac990) at gmain.c:4135 #2 g_main_context_iterate (context=context@entry=0x7f1ac990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3835 #3 0x7f1b177c342c in g_main_context_iteration (context=0x7f1ac990, may_block=1) at gmain.c:3901 #4 0x7f1b1adfd32b in QEventDispatcherGlib::processEvents (this=0x7f1ac8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:419 #5 0x7f1b1adaafdb in QEventLoop::exec (this=this@entry=0x7f1aded75d10, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f1b1abe5f1a in QThread::exec (this=) at thread/qthread.cpp:500 #7 0x7f1b1abea9e9 in QThreadPrivate::start (arg=0x7f1ae0005100) at thread/qthread_unix.cpp:341 #8 0x7f1b1812a734 in start_thread (arg=0x7f1aded76700) at pthread_create.c:334 #9 0x7f1b1a4f9d3d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 12 (Thread 0x7f1ae4d72700 (LWP 25199)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1b1abeb65b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1c35480) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x1c573f0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f1af96a342b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x1c0d1c0, th=) at /usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:594 #4 0x7f1af96a442f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x1c0d1c0, th=th@entry=0x7f1ae0003610, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactive@entry=false, justReturning=justReturning@entry=false) at /usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:554 #5 0x7f1af96a7dea in ThreadWeaver::WorkingHardState::applyForWork (this=0x1c2d7a0, th=0x7f1ae0003610, wasBusy=) at /usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:66 #6 0x7f1af96a245b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f1ae0003610, wasBusy=) at /usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568 #7 0x7f1af96a7e32 in ThreadWeaver::WorkingHardState::applyForWork (this=0x1c2d7a0, th=0x7f1ae0003610, wasBusy=) at /usr/src/debug/threadweaver-5.26.0/src/workinghardstate.cpp:73 #8 0x7f1af96a245b in ThreadWeaver::Weaver::applyForWork (this=, th=0x7f1ae0003610, wasBusy=) at /usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:568 #9 0x7f1af96a5a46 in ThreadWeaver::Thread::run (this=0x7f1ae0003610) at /usr/src/debug/threadweaver-5.26.0/src/thread.cpp:103 #10 0x7f1b1abea9e9 in QThreadPrivate::start (arg=0x7f1ae0003610) at thread/qthread_unix.cpp:341 #11 0x7f1b1812a734 in start_thread (arg=0x7f1ae4d72700) at pthread_create.c:334 #12 0x7f1b1a4f9d3d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 11 (Thread 0x7f1ae5573700 (LWP 25198)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f1b1abeb65b in QWaitConditionPrivate::wait (time=18446744073709551615, this=0x1c35480) at thread/qwaitcondition_unix.cpp:136 #2 QWaitCondition::wait (this=, mutex=0x1c573f0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #3 0x7f1af96a342b in ThreadWeaver::Weaver::blockThreadUntilJobsAreBeingAssigned_locked (this=this@entry=0x1c0d1c0, th=) at /usr/src/debug/threadweaver-5.26.0/src/weaver.cpp:594 #4 0x7f1af96a442f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait (this=0x1c0d1c0, th=th@entry=0x39e9a20, threadWasBusy=threadWasBusy@entry=false, suspendIfInactive=suspendIfInactiv
[plasmashell] [Bug 373173] Recent Document Actions don't work after right clicking a search result
https://bugs.kde.org/show_bug.cgi?id=373173 Eike Hein changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/pla ||sma-desktop/0314f493185 ||57942e15bf9c980b8d7aa1fba --- Comment #4 from Eike Hein --- Git commit 0314f49318557942e15bf9c980b8d7aa1fba by Eike Hein. Committed on 06/12/2016 at 21:24. Pushed by hein into branch 'Plasma/5.8'. Fix running of recent docs actions for runner match entries. M +3-0applets/kicker/plugin/runnermatchesmodel.cpp https://commits.kde.org/plasma-desktop/0314f49318557942e15bf9c980b8d7aa1fba -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 372735] imposible dibujar
https://bugs.kde.org/show_bug.cgi?id=372735 Boudewijn Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373345] After return from preview view the album view scrolls the selected image to the top
https://bugs.kde.org/show_bug.cgi?id=373345 --- Comment #5 from Stas --- I am at Arch Linux and use the actual plasma framework (KDE5). -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 372777] no kwallet integration in 16.12
https://bugs.kde.org/show_bug.cgi?id=372777 --- Comment #3 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #2) > (In reply to Wolfgang Bauer from comment #1) > > With kwebkitpart and khtml Konqueror 16.12 can save and retrieve passwords > > to/from kwallet. > > Correction: apparently not any more, sorry. It definitely did work in the > past (with kde-baseapps frameworks branch) Please ignore my previous comment. It does still work (with 16.11.90), I just had kwallet disabled (I did some testing with kwallet disabled a while ago and forgot that I disabled it, sigh) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 339961] HUB : Add Windows Photo Gallery / Windows Explorer Hierarchical tags support
https://bugs.kde.org/show_bug.cgi?id=339961 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|FIXED |WONTFIX -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373369] keyboard battery status only shown for one keyboard when two are connected
https://bugs.kde.org/show_bug.cgi?id=373369 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Kai Uwe Broulik --- Can you provide the output of upower -d to see whether it actually properly tells us about both keyboards? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373370] New: Nvidia crashes Plasma!?!
https://bugs.kde.org/show_bug.cgi?id=373370 Bug ID: 373370 Summary: Nvidia crashes Plasma!?! 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: cmkit...@yahoo.com CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.5.5) (Compiled from sources) Qt Version: 5.5.1 Operating System: Linux 4.4.0-53-generic x86_64 Distribution: Ubuntu 16.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I had just rebooted the computer after updating all the software and system packages. I had also installed the nvidia-current driver because noveau had my screen locked at a very low resolution. - Unusual behavior I noticed: Well I first noticed unusual behavior when I found that the splash screen had been replaced by a text splash screen and plasma didn't even start, but let me to the crash manager program. - Custom settings of the application: Just barely installed the nvidia-current package on the system (BTW the system is Kubuntu 16.04.1 LTS, the graphics card is from Nvidia (i don't know the model :P ) 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 0x7ff93c253900 (LWP 1358))] Thread 8 (Thread 0x7ff8754eb700 (LWP 1626)): #0 0x7ff93372dac0 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff9336e8939 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff9336e92cb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff9336e94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff9372807eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff937227b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff937044834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff8779c97d7 in KCupsConnection::run() () from /usr/lib/x86_64-linux-gnu/libkcupslib.so #8 0x7ff9370497be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff932b43754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #10 0x7ff93613670a in start_thread (arg=0x7ff8754eb700) at pthread_create.c:333 #11 0x7ff93695f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7ff8865df700 (LWP 1420)): #0 0x7ff93694f69d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7ff932b4273c in ?? () from /usr/lib/nvidia-304/libGL.so.1 #2 0x7ff92f51dbf7 in ?? () from /usr/lib/nvidia-304/tls/libnvidia-tls.so.304.132 #3 0x7ff93372c740 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff9336e8e84 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff9336e9340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7ff9336e94ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7ff9372807eb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff937227b4a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7ff937044834 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff93a272ed6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7ff9370497be in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff932b43754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #13 0x7ff93613670a in start_thread (arg=0x7ff8865df700) at pthread_create.c:333 #14 0x7ff93695f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7ff90d1af700 (LWP 1409)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7ff93bc91bd4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7ff93bc91c19 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7ff932b43754 in ?? () from /usr/lib/nvidia-304/libGL.so.1 #4 0x7ff93613670a in start_thread (arg=0x7ff90d1af700) at pthread_create.c:333 #5 0x7ff93695f82d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7ff90ea61700 (LWP 1399)): #0 0x7ff93372dac9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff9336e8ddc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff9336e9340 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff9336e94ac in g_main_context_iteration () from /l
[konqueror] [Bug 372777] no kwallet integration in 16.12
https://bugs.kde.org/show_bug.cgi?id=372777 --- Comment #2 from Wolfgang Bauer --- (In reply to Wolfgang Bauer from comment #1) > With kwebkitpart and khtml Konqueror 16.12 can save and retrieve passwords > to/from kwallet. Correction: apparently not any more, sorry. It definitely did work in the past (with kde-baseapps frameworks branch) -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 372777] no kwallet integration in 16.12
https://bugs.kde.org/show_bug.cgi?id=372777 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #1 from Wolfgang Bauer --- Actually this seems to be a limitation of the new webenginepart. With kwebkitpart and khtml Konqueror 16.12 can save and retrieve passwords to/from kwallet. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373369] New: keyboard battery status only shown for one keyboard when two are connected
https://bugs.kde.org/show_bug.cgi?id=373369 Bug ID: 373369 Summary: keyboard battery status only shown for one keyboard when two are connected Product: plasmashell Version: 5.8.4 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Battery Monitor Assignee: k...@privat.broulik.de Reporter: enr...@pressmail.ch CC: plasma-b...@kde.org Target Milestone: 1.0 I have two wireless keyboards (Logitech k400 and K830) connected to my pc when both are connected only one will show the battery status in the widget. This is the same with two Logitech K400's at the same time. Sometimes low battery warnings appear for the keyboard of which the status is not shown. -- 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 Thomas Zell changed: What|Removed |Added CC||t.z...@gmx.de --- Comment #68 from Thomas Zell --- For me contact completion from the address book was not working at all. It was fixed by right clicking on "Personal Contacts" in the Akonadi Console (akonadiconsole) and selecting "Clear Akonadi Cache". I'm on openSUSE Leap 42.2 with KMail 5.3.0 and KDE Frameworks 5.26.0. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373368] New: Opening new message very slow and freezes KMail for several second each
https://bugs.kde.org/show_bug.cgi?id=373368 Bug ID: 373368 Summary: Opening new message very slow and freezes KMail for several second each Product: kmail2 Version: Git (master) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: renda.kr...@gmail.com Target Milestone: --- KMail 5.3.3 (QtWebEngine), OpenSUSE Tumbleweed, Linux (x86_64) release 4.8.12-1-default: Kmail is very slow when navigating between messages in the message list. I have two accounts - an IMAP account (Activated Download all messages for offline use) and a Local Folders account. To be sure this is no migration problem from KDE 4 I stopped KMail and Akonadi and removed the following folders and files: ~/.local/share/akonadi ~/.config/akonadi ~/.kde4/share/config/akonadi* After that I restarted Akonadi and resynchronized the account again. Thus, this should be a clean state. When having synchronized all messages after the above cleanup action the problem reoccurs again: I click on several messages in the message list, marking a new message in the message list freezes KMail for several seconds before the new message is shown in the message window. This behavior happened from my point of view since the QtWebEngine has been introduced as message viewer. Because I've read about multi-threading problems of Nouveau, I tried also the native NVidia driver, no change so far. -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 369350] Some applications (choqok) fail to autostart in 5.8 beta
https://bugs.kde.org/show_bug.cgi?id=369350 AJSlye changed: What|Removed |Added CC||ja...@nulogicsystems.com --- Comment #2 from AJSlye --- If this is not a bug then what caused it? There is a user running Maui reporting a similar issue with dropbox and pidgin. https://forums.mauilinux.org/showthread.php?tid=24149 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 373083] Bluetooth is marked as disabled, but I can connect from command line
https://bugs.kde.org/show_bug.cgi?id=373083 --- Comment #1 from Lorenzo --- Some extra context. The integrated bt was disabled by bios. After enabling it and removing the usb bt it started working as supposed. -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 373367] New: typos in de1 course
https://bugs.kde.org/show_bug.cgi?id=373367 Bug ID: 373367 Summary: typos in de1 course Product: ktouch Version: unspecified Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: reproducible Severity: normal Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: spiolli...@googlemail.com Target Milestone: --- Created attachment 102654 --> https://bugs.kde.org/attachment.cgi?id=102654&action=edit patch fixing the 2 typos I found I found 2 more typos in the de1.xml course, see attached patch -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 350586] typo in de1 course
https://bugs.kde.org/show_bug.cgi?id=350586 spiolli...@googlemail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=373367 -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 354473] Cannot login to Google account
https://bugs.kde.org/show_bug.cgi?id=354473 Wladimir Mangelardo changed: What|Removed |Added CC||wmangela...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 373366] New: Spectacle can't make screenshots after the first one
https://bugs.kde.org/show_bug.cgi?id=373366 Bug ID: 373366 Summary: Spectacle can't make screenshots after the first one Product: Spectacle Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: jacob...@gmail.com Target Milestone: --- I've tried to make set of screenshots. After the first one that was correct it wasn't possible to make the second, the third and so on. I clicked the button but I got the first picture every time. jacobtey@jacobtey-laptop ~ % spectacle qrc:/JobDialog.qml:67: TypeError: Cannot read property 'Layout' of null qrc:/JobDialog.qml:66: TypeError: Cannot read property 'Layout' of null -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 373365] New: WISHLIST: bulk import of image sequences
https://bugs.kde.org/show_bug.cgi?id=373365 Bug ID: 373365 Summary: WISHLIST: bulk import of image sequences Product: kdenlive Version: 16.08.2 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: ad...@djfun.de Target Milestone: --- If I project needs multiple animations in the form of image sequences from Natron, Blender, etc., importing these one by one gets tedious. There should be a function to import multiple image sequences at once. I imagine selecting multiple folders in a file dialog and after hitting an import button, each folder gets imported as its own image sequence clip with the clip name being the name of the folder. Post on this topic in the forums: https://forum.kde.org/viewtopic.php?f=265&t=137527 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373345] After return from preview view the album view scrolls the selected image to the top
https://bugs.kde.org/show_bug.cgi?id=373345 --- Comment #4 from caulier.gil...@gmail.com --- Which Window manager/desktop do you use ? Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373364] Desktop Icon text corrupted
https://bugs.kde.org/show_bug.cgi?id=373364 --- Comment #1 from Standa --- System:Host: standa-mint18 Kernel: 4.4.34-xanmod39 x86_64 (64 bit) Desktop: KDE Plasma 5.6.5 Distro: Linux Mint 18 Sarah Machine: Mobo: Gigabyte model: H55-UD3H v: x.x Bios: Award v: F10 date: 08/20/2010 CPU: Dual core Intel Core i3 540 (-HT-MCP-) cache: 4096 KB clock speeds: max: 3059 MHz 1: 1862 MHz 2: 3059 MHz 3: 1463 MHz 4: 1995 MHz Graphics: Card: NVIDIA GF108 [GeForce GT 630] Display Server: X.Org 1.18.4 drivers: nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@60.00hz GLX Renderer: GeForce GT 630/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 367.57 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373345] After return from preview view the album view scrolls the selected image to the top
https://bugs.kde.org/show_bug.cgi?id=373345 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- Strange, problem is also not reproducible here. Maik -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 362671] GTK applications are not restored in Plasma 5.6.x after relogin
https://bugs.kde.org/show_bug.cgi?id=362671 --- Comment #13 from Wolfgang Bauer --- (In reply to Oliver Henshaw from comment #10) > gtk2 applications need > libgnome and libgnomeui installed to register with xsmp; Well, I do have libgnome and libgnomeui installed (and also did when I wrote comment#2). But I just tried again, and gnucash and gvim (GTK2 applications) are still stored in the "LegacySession" section, same as gedit and gnome-chess btw (which are GTK3 applications). But I can confirm that Firefox 50 is now in the standard section indeed, thank you. Opera 12 still used Qt(3) for its GUI which may explain why this version did support XSMP. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373364] New: Desktop Icon text corrupted
https://bugs.kde.org/show_bug.cgi?id=373364 Bug ID: 373364 Summary: Desktop Icon text corrupted Product: plasmashell Version: 5.6.5 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: kacerna...@quick.cz Target Milestone: 1.0 Created attachment 102653 --> https://bugs.kde.org/attachment.cgi?id=102653&action=edit Desktop icon text corrupted After resume from suspend the text of desktop icons is corrupted. See attached picture. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 339961] HUB : Add Windows Photo Gallery / Windows Explorer Hierarchical tags support
https://bugs.kde.org/show_bug.cgi?id=339961 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||5.4.0 Resolution|WONTFIX |FIXED -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 332601] "search backwards" option not saved/restored
https://bugs.kde.org/show_bug.cgi?id=332601 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #6 from Kurt Hindenburg --- my commit message wasn't correct - this was committed 2b6b9c579bb7e79ea7dffac75318dc89bef5bb35 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373363] New: Kmail folder properties aren't shown after closing them
https://bugs.kde.org/show_bug.cgi?id=373363 Bug ID: 373363 Summary: Kmail folder properties aren't shown after closing them Product: Akonadi Version: 5.2.3 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libakonadi Assignee: kdepim-b...@kde.org Reporter: m...@debian.org Target Milestone: --- Created attachment 102652 --> https://bugs.kde.org/attachment.cgi?id=102652&action=edit Delete the dialog on close Hi, When closing the folder properties window with the X button it's no longer possible to show it again. This is due to the fact that the window is not deleted on close (as done in with the cancel button pressed signal). I'm attaching a patch that I'm planning to apply in the Debian packages. Happy hacking, -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 373288] are_valid_hwcaps VexArchAMD64 assert error
https://bugs.kde.org/show_bug.cgi?id=373288 --- Comment #1 from Philippe Waroquiers --- Is this really related to Valgrind version 3.8.0 ? This is obsolete/not maintained anymore. Please upgrade to the last release (3.12.0) and retry. Assuming you are using or have upgraded to 3.12.0 and problem still there, please provide more information: * which Linux distribution ? * cat /proc/cpuinfo * attach the output ofvalgrind -v -v -v -d -d -d date Thanks -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373313] Make From field in the composer read only
https://bugs.kde.org/show_bug.cgi?id=373313 --- Comment #4 from William L. Thomson Jr. --- I have hidden it. The only case it could be useful is in email spoofing. Which I do not think KDE would want to encourage that. I cannot see to many situations someone would want to compose an email in kmail using a different from address that was not associated with an account in kmail. Either way, it is up to you all. I have hidden it now for myself so I cannot make such mistake on accident. But others may use it on purpose. I would think KDE to want to limit things that could be abused for bad purposes like spoofing emails. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373255] Visual distractions: item highlight persists when mouse pointer is not over desktop
https://bugs.kde.org/show_bug.cgi?id=373255 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/7585f295363532e ||ff51f7e11ef6b62925117aba4 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.8.5 --- Comment #3 from Kai Uwe Broulik --- Git commit 7585f295363532eff51f7e11ef6b62925117aba4 by Kai Uwe Broulik. Committed on 06/12/2016 at 18:54. Pushed by broulik into branch 'Plasma/5.8'. [Folder View] Clear hover state when mouse leaves view This ensures there isn't a stray hovered item when moving the mouse from an item to an adjacent window. FIXED-IN: 5.8.5 Differential Revision: https://phabricator.kde.org/D3593 M +1-0containments/desktop/package/contents/ui/FolderView.qml https://commits.kde.org/plasma-desktop/7585f295363532eff51f7e11ef6b62925117aba4 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362061] Use popular shortcuts for Spectacle for sake of consistency with other environments
https://bugs.kde.org/show_bug.cgi?id=362061 --- Comment #10 from Gregor Mi --- @Sudhir: you are working on this? If yes, cool. :) ...Would you create a review request for this (on reviewboard or phabricator depending on the repository) with your current development state? Prefix the review request title with WIP to make it clear it is not finished yet and post the URL back to here. Code discussion is easier there than here. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 373288] are_valid_hwcaps VexArchAMD64 assert error
https://bugs.kde.org/show_bug.cgi?id=373288 Philippe Waroquiers changed: What|Removed |Added CC||philippe.waroquiers@skynet. ||be Summary|valgrind --version |are_valid_hwcaps ||VexArchAMD64 assert error -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362061] Use popular shortcuts for Spectacle for sake of consistency with other environments
https://bugs.kde.org/show_bug.cgi?id=362061 --- Comment #9 from Sudhir Khanger --- Shortcuts are defined in custom shortcuts using dbus specs. I do have two problems. 1. I am unable to set Alt+PrtSc as keyboard shortcuts. 2. I don't know what Arguments mean in dbus settings. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 372658] Opening file picker triggers "the process for file procotol is dead unexpectedly"
https://bugs.kde.org/show_bug.cgi?id=372658 Germano Massullo changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Germano Massullo --- I could not retrieve logs with the guide I followed because the affected application use KDE libs 4, not KDE Framework 5. I followed [1] and the moment I run kdeinit4 Konsole showed some messages about ~/. files, but I haven't paid attention to them. Suddenly the problem disappeared. I even tried to relogin, reboot the system, but there is no way to reproduce it again. This is very strange because I experienced it for ~ more than an entire week... Anyway, thanks to Rex Dieter and Pino Toscano [1]: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/Debugging_IOSlaves#GUI_.28Qt4.2Fkdelibs4_instructions.29 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 373355] Damaged partition table - file system type reported as empty
https://bugs.kde.org/show_bug.cgi?id=373355 Andrius Štikonas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Andrius Štikonas --- Ok, glad to hear that you fixed it. I'll close this bug then. -- You are receiving this mail because: You are watching all bug changes.
[ksnapshot] [Bug 373165] Completely black screenshots for KSnapshot in Fedora 25
https://bugs.kde.org/show_bug.cgi?id=373165 --- Comment #2 from Miguel Meza --- I was using the ksnapshot utility. I think the error might not be related directly with ksnapshot but with the new integration of Wayland or something else. At the end I had a lot of problems with video reproduction, programs crashing with the use of a mouse scrolling and more. I decided to downgrade to fedora 24 because it was really annoying. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 373355] Damaged partition table - file system type reported as empty
https://bugs.kde.org/show_bug.cgi?id=373355 --- Comment #2 from dreyerbe...@hotmail.de --- Good afternoon, great thanks Andrius. After I have modified a partition with Gparted, it took a bit longer, before, after recognition of the USB-drive, the volumes of the disk in question disappeared again in the Windows Explorer. So, I could start Testdisk and select the questionable disk in the USB-drive. After scanning, Testdisk found the boot sector of the fist partition being longer than expected. After that, I have written a new boot sector using the Testdisk tools and as a result all disk partitions are fully accessible now. Kindest regards Bernd Dreyer -Ursprüngliche Nachricht- Von: Andrius Štikonas [mailto:bugzilla_nore...@kde.org] Gesendet: Dienstag, 6. Dezember 2016 16:22 An: dreyerbe...@hotmail.de Betreff: [partitionmanager] [Bug 373355] Damaged partition table - file system type reported as empty https://bugs.kde.org/show_bug.cgi?id=373355 Andrius Štikonas changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Andrius Štikonas --- 8 MB gaps might be cause by partition alignment but it's nothing too serious. In the worse case you just loose a tiny amount of space an slight reduction in performance. Please be careful before proceeding, I'm not sure what Mini Tool has broken. Make sure you have backup of all your data. Changing fs in partition properties dialog would format that partition from scratch, this is not what you want, don't do it. But I would need more information to be able to help... E.g. what kind of partition table you have, maybe some screenshots what partition manager shows etc... Also if you have not enabled log output in kde partition manager (in view menu) then enable it, it can show useful errors. You can try to inspect what is your state of partition table with some tools, e.g. fdisk. If your hard drive is at /dev/sda, then run sudo fdisk /dev/sda and press p to show state of the hard drive. -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373358] Kwin Crash When Starting DE
https://bugs.kde.org/show_bug.cgi?id=373358 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 372114 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362061] Use popular shortcuts for Spectacle for sake of consistency with other environments
https://bugs.kde.org/show_bug.cgi?id=362061 --- Comment #8 from Peter Wu --- There were no changes made to Spectacle. I think these are handled by KWin, but not sure. If you are going to implement this, you probably have to interface with DBus (see dbus/org.kde.Spectacle.xml for the interface). -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373313] Make From field in the composer read only
https://bugs.kde.org/show_bug.cgi?id=373313 Laurent Montel changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #3 from Laurent Montel --- It's useful to make it editable. But if it's a problem you can hide this lineedit by default. I think it's the better solution. I will not add a new option for this line :) Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373356] drawing artifacts (not updated or transparent horizontal single-pixel lines)
https://bugs.kde.org/show_bug.cgi?id=373356 --- Comment #2 from Martin Gräßlin --- please provide output of: qdbus org.kde.KWin /KWin supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 372114] Kwin crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=372114 --- Comment #4 from Martin Gräßlin --- Better backtrace from duplicate: Application: kwin_x11 (5.8.4) Qt Version: 5.7.0 Frameworks Version: 5.27.0 Operating System: Linux 4.8.11-300.fc25.x86_64 x86_64 Distribution: "Fedora release 25 (Twenty Five)" -- Information about the crash: - What I was doing when the application crashed: I simply logged in from sddm after a reboot and kwin crashed and the abrt dialog appeared. kwin restarted by the time I processed this bug report. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fccc4cb1940 (LWP 1082))] Thread 7 (Thread 0x7fcca5245700 (LWP 1339)): #0 0x7fccd7e7c460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fccdd6c2bd4 in QTWTF::TCMalloc_PageHeap::scavengerThread() () from /lib64/libQt5Script.so.5 #2 0x7fccdd6c2c19 in QTWTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /lib64/libQt5Script.so.5 #3 0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0 #4 0x7fccd5054f6f in clone () from /lib64/libc.so.6 Thread 6 (Thread 0x7fcca6388700 (LWP 1246)): #0 0x7fccd7e7c460 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fcca713aad3 in radeon_drm_cs_emit_ioctl () from /usr/lib64/dri/r600_dri.so #2 0x7fcca713a217 in impl_thrd_routine () from /usr/lib64/dri/r600_dri.so #3 0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0 #4 0x7fccd5054f6f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fcca7fff700 (LWP 1239)): [KCrash Handler] #6 0x7fccd5da485f in QLockFilePrivate::tryLock_sys() () from /lib64/libQt5Core.so.5 #7 0x7fccd5d51a6d in QLockFile::tryLock(int) () from /lib64/libQt5Core.so.5 #8 0x7fccda841439 in KConfigIniBackend::lock() () from /lib64/libKF5ConfigCore.so.5 #9 0x7fccda82b0e0 in KConfig::sync() () from /lib64/libKF5ConfigCore.so.5 #10 0x7fccb7355ea5 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /usr/lib64/qt5/plugins/org.kde.kwin.platforms/KWinX11Platform.so #11 0x7fccd5e28326 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7fccd5e344d8 in QTimer::timerEvent(QTimerEvent*) () from /lib64/libQt5Core.so.5 #13 0x7fccd5e2908b in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7fccd664996c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7fccd665 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7fccd5e0112a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7fccd5e4e38b in QTimerInfoList::activateTimers() () from /lib64/libQt5Core.so.5 #18 0x7fccd5e4c710 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #19 0x7fccd5e000ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7fccd5c5d643 in QThread::exec() () from /lib64/libQt5Core.so.5 #21 0x7fccd5c61a1a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #22 0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0 #23 0x7fccd5054f6f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fccb6210700 (LWP 1220)): #0 0x7fccd50490d1 in ppoll () from /lib64/libc.so.6 #1 0x7fccd5e4b051 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7fccd5e4c566 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7fccd5e000ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fccd5c5d643 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7fccdc91a735 in QQmlThreadPrivate::run() () from /lib64/libQt5Qml.so.5 #6 0x7fccd5c61a1a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0 #8 0x7fccd5054f6f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fccb7d75700 (LWP 1174)): #0 0x7fccd50490d1 in ppoll () from /lib64/libc.so.6 #1 0x7fccd5e4b051 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /lib64/libQt5Core.so.5 #2 0x7fccd5e4c566 in QEventDispatcherUNIX::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #3 0x7fccd5e000ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fccd5c5d643 in QThread::exec() () from /lib64/libQt5Core.so.5 #5 0x7fccd79727a9 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #6 0x7fccd5c61a1a in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #7 0x7fccd7e766ca in start_thread () from /lib64/libpthread.so.0 #8 0x7fccd5054f6f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fccbd44d700 (LWP 1127)): #0 0x7fccd504900d in poll () from
[kwin] [Bug 372114] Kwin crashed unexpectedly
https://bugs.kde.org/show_bug.cgi?id=372114 Martin Gräßlin changed: What|Removed |Added CC||gtwilli...@gmail.com --- Comment #3 from Martin Gräßlin --- *** Bug 373358 has been marked as a duplicate of this bug. *** -- 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 Martin Gräßlin changed: What|Removed |Added Flags||Wayland-, X11+ -- 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 Martin Gräßlin changed: What|Removed |Added CC||to.roma.from.kdebug@qwertty ||.com --- Comment #29 from Martin Gräßlin --- *** Bug 373354 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373354] Escape key doesn’t exit kwin Present Windows and Desktop Grid effects
https://bugs.kde.org/show_bug.cgi?id=373354 Martin Gräßlin changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Martin Gräßlin --- *** This bug has been marked as a duplicate of bug 360841 *** -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362061] Use popular shortcuts for Spectacle for sake of consistency with other environments
https://bugs.kde.org/show_bug.cgi?id=362061 --- Comment #7 from Gregor Mi --- I checked the spectacle source log: https://cgit.kde.org/spectacle.git/log/. In the log messages on the first three pages I cannot see any keyboard shortcut related change. But I am not sure if the global shortcut settings are done in this repository or maybe somewhere else. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371877] key combos not being properly passed into keyboard-captured apps
https://bugs.kde.org/show_bug.cgi?id=371877 --- Comment #17 from Martin Gräßlin --- Option 4 is not possible. We don't have any hints about that an application/window grabbed the keyboard. Options 1-3 are all possible. For option 3 we do have a window rule which blocks global shortcuts and that also blocks the windows key triggering. We can also ship such rules by default, so that the user does not have to maintain them. But we will not be able to ship them to 5.8 users, that would have to go into Plasma 5.9. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371849] audio file sounds "clicky" when on project timeline; affects rendered file
https://bugs.kde.org/show_bug.cgi?id=371849 --- Comment #7 from S. Christian Collins --- I tried the melt command suggested in comment #4, but this did not create any artifacts. However, this does indeed seem to be related to the MLT issues posted by Martin in comment #5. Following the steps by ddennedy in the thread at https://github.com/mltframework/shotcut/issues/259#issuecomment-244806461 (this link will jump straight to his comment) solves the crackling issue, so it definitely seems to be related to the "combine" mixing method. Interestingly, the rate of crackling also changes with project framerate. It sounds like MLT is chopping the audio up per-frame, but not re-combining the audio with 100% accuracy. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373319] Plastik decoration hides buttons when a window is rolled up
https://bugs.kde.org/show_bug.cgi?id=373319 Martin Gräßlin changed: What|Removed |Added Component|decorations |aurorae -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373319] Plastik decoration hides buttons when a window is shaded
https://bugs.kde.org/show_bug.cgi?id=373319 Martin Gräßlin changed: What|Removed |Added Summary|Plastik decoration hides|Plastik decoration hides |buttons when a window is|buttons when a window is |rolled up |shaded -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 373268] Application dependent tearing with OpenGL
https://bugs.kde.org/show_bug.cgi?id=373268 Martin Gräßlin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from Martin Gräßlin --- I'm sorry, but such a setup is outside the scope of what we can support. The tearing is related to this setup with fake/dummy screens. This obviously breaks Vsync. Whether or not it's possible to specify to which screen to vsync is something I do not know and also not of relevance for KWin. That's something you need to check in the nvidia driver options. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 373362] New: krfb missing systray icon
https://bugs.kde.org/show_bug.cgi?id=373362 Bug ID: 373362 Summary: krfb missing systray icon Product: Breeze Version: 5.8.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: dfloger...@gmail.com CC: kain...@gmail.com Target Milestone: --- Using frameworks 5.26, and plasma-5.8.3 and krfb-16.04.3, there is not icon displayed in the systray when krfb is hidden. You can interact with the spot where the icon should be (ie. right click and get the krfb context menu) but the icon itself is missing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373361] New: iCal Calendar Folder - Digital Clock does not import Events
https://bugs.kde.org/show_bug.cgi?id=373361 Bug ID: 373361 Summary: iCal Calendar Folder - Digital Clock does not import Events Product: plasmashell Version: 5.8.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: bugrprt21...@online.de Target Milestone: 1.0 The following Digital Clock Modules are enabled: Holidays; PIM Events Plugin. The PIM Events Plugin has the following Calendars enabled: Birthdays & Anniversaries; Personal Calendar; Search: Open Invitations. If the Calendar items are stored in single files in a directory, instead of in a single flat file, the Digital Clock does not display Calendar Events and To-Do items. In addition, if an iCal Calendar File is used, the Digital Clock also displays any Birthdays and Anniversaries mentioned in the Kontact Contacts entries. If however the Calendar items are stored in single files in a directory, the Digital Clock stops displaying these dates. And, if the Events and To-Do Items are reverted back to singe flat file, the Digital Clock remains in the state that no Kontact items are displayed -- no Events, To-Do items, Birthdays or Anniversaries. -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 373349] KDevelop Crash on recent keywords (Python) [Python::PythonCodeCompletionContext::raiseItems, KDevelop::DUContext::findDeclarations]
https://bugs.kde.org/show_bug.cgi?id=373349 Sven Brauch changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED Latest Commit||https://commits.kde.org/kde ||v-python/1326aa448eab2b8b76 ||e6546c4e3160c98e817502 --- Comment #3 from Sven Brauch --- Git commit 1326aa448eab2b8b76e6546c4e3160c98e817502 by Sven Brauch. Committed on 06/12/2016 at 17:35. Pushed by brauch into branch '5.0'. fix crash when requesting raise items without the docfile being parsed If you hit this crash, just let the parser run through once before typing, then it should be gone. M +3-0codecompletion/context.cpp https://commits.kde.org/kdev-python/1326aa448eab2b8b76e6546c4e3160c98e817502 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 339961] HUB : Add Windows Photo Gallery / Windows Explorer Hierarchical tags support
https://bugs.kde.org/show_bug.cgi?id=339961 Antoine Chauveau changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #9 from Antoine Chauveau --- Thank you, configuring Digikam like you suggest (and also disabling reading and writing tags for all other namespaces) allows good interoperability with Explorer and Photo Gallery. Note that the example in attachment 102624 wasn't complete, I also had to set "Special Options" in this dialog to TAG_XMPBAG or nothing got written. It is rather inconvenient that such advanced configuration is needed for my use case, but the fault is in the lack of a widely adopted standard for hierarchical tags and not in Digikam. I understand that Digikam defaults to writing Xmp.dc.subject according to the MWG's standard (http://www.metadataworkinggroup.org/specs), and that seems like a reasonable choice. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 362061] Use popular shortcuts for Spectacle for sake of consistency with other environments
https://bugs.kde.org/show_bug.cgi?id=362061 --- Comment #6 from Sudhir Khanger --- Doesn't look like changes were made. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373173] Recent Document Actions don't work after right clicking a search result
https://bugs.kde.org/show_bug.cgi?id=373173 Eike Hein changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #3 from Eike Hein --- Oh I see - the problem is that execution isn't working, not that they don't show up. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 372161] okular crash on startup
https://bugs.kde.org/show_bug.cgi?id=372161 --- Comment #5 from Jean-Francois Ostiguy --- After spending way too much time on this, I came to a partial resolution. The problem seems to be related to EGL. The crash goes away by I disabling EGL support in Qt 4. I am running Mesa, Nouveau and GL3 Plasma backend. I suspect the issue arises somewhere in Mesa/Nouveau. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373173] Recent Document Actions don't work after right clicking a search result
https://bugs.kde.org/show_bug.cgi?id=373173 --- Comment #2 from Chris Holland --- Search for "Comix", then right click it for the recent docs. Clicking the item will do nothing (not launch the program). https://i.imgur.com/GuvFUYV.png However, if find Comix in category view and right click it, the context menu item will launch Comix. Also tested with Chrome + Kdenlive -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 373332] Akondai
https://bugs.kde.org/show_bug.cgi?id=373332 --- Comment #3 from HAJ --- I suspected that, in prior trouble shooting I did in fact run it down to and replaced the nouveau with the manufactures driver, which caused it's own problems. I no longer have a Gnome that functions and it appears that Wayland has been disabled, neither of these really bother me since I don't like the new Gnome and Wayland is not ready for prime time. But I no longer have a root login at the KDM prompt which is little more than an annoyance. But the aknodai crashes are driving me up a wall since Kmail and Akregator are my preferred email and RSS clients. -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 373308] Connection between activity and pin does not ends on pin
https://bugs.kde.org/show_bug.cgi?id=373308 Ralf Habacker changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/umb ||rello/95a1547793bba6519ca7f ||277ccc1d218f8d871d5 Version Fixed In||2.21.80 (KDE Applications ||17.03.80) Resolution|--- |FIXED --- Comment #2 from Ralf Habacker --- Git commit 95a1547793bba6519ca7f277ccc1d218f8d871d5 by Ralf Habacker. Committed on 06/12/2016 at 17:15. Pushed by habacker into branch 'master'. Fix 'Connection between activity and pin does not ends on pin'. FIXED-IN:2.21.80 (KDE Applications 17.03.80) M +2-2umbrello/toolbarstateassociation.cpp M +6-6umbrello/umlwidgets/associationwidget.cpp https://commits.kde.org/umbrello/95a1547793bba6519ca7f277ccc1d218f8d871d5 -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 373308] Connection between activity and pin does not ends on pin
https://bugs.kde.org/show_bug.cgi?id=373308 Ralf Habacker changed: What|Removed |Added Summary|Connection between activity |Connection between activity |and pin does not end on pin |and pin does not ends on ||pin -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373075] Changing Resolution hides programs in task manager
https://bugs.kde.org/show_bug.cgi?id=373075 Eike Hein changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 372450] colord-kde 0.5 does not show any monitor
https://bugs.kde.org/show_bug.cgi?id=372450 --- Comment #8 from darkba...@linuxsystems.it --- The cable is a standard Mini Displayport Cable (but even a Display Port one would be fine if you have a DP output instead of miniDP). To use MST (Multistream) you have to attach it to a monitor capable of handling MST with a miniDP or DP input and a miniDP or DP output. I will compile git version and attach logs from kded5 when attaching the external monitor. -- You are receiving this mail because: You are watching all bug changes.
