[frameworks-kconfig] [Bug 388184] wrong folder to store user settings under Windows
https://bugs.kde.org/show_bug.cgi?id=388184 caulier.gil...@gmail.com changed: What|Removed |Added Assignee|digikam-bugs-n...@kde.org |matt...@mjdsystems.ca CC||caulier.gil...@gmail.com, ||kdelibs-b...@kde.org Component|general |general Version|5.7.0 |5.36.0 Product|digikam |frameworks-kconfig --- Comment #1 from caulier.gil...@gmail.com --- This problem is relevant of low level KConfig library from KF5 framework used to manage digiKam config files in background. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388183] Windows installer is not HiDPI ready
https://bugs.kde.org/show_bug.cgi?id=388183 caulier.gil...@gmail.com changed: What|Removed |Added Latest Commit||https://commits.kde.org/dig ||ikam-software-compilation/a ||2e99b0cf9d6c645290544638891 ||8855d1bcfc9e Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Version Fixed In||5.8.0 --- Comment #2 from caulier.gil...@gmail.com --- Git commit a2e99b0cf9d6c6452905446388918855d1bcfc9e by Human Dynamo. Committed on 24/12/2017 at 07:23. Pushed by cgilles into branch 'master'. add support of hdpi screens with NSI 3.x FIXED-IN: 5.8.0 M +4-1project/bundles/mxe/installer/digikam.nsi https://commits.kde.org/digikam-software-compilation/a2e99b0cf9d6c6452905446388918855d1bcfc9e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388116] Add possibility to switch with the mouse between images in preview mode
https://bugs.kde.org/show_bug.cgi?id=388116 --- Comment #5 from caulier.gil...@gmail.com --- >From the keyboard only, Page Up/Down permit to switch between images too. This is not enough ? This prevent to switch between keyboard and mouse context with hands. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388191] New: Adesso M14 No Sensitivity
https://bugs.kde.org/show_bug.cgi?id=388191 Bug ID: 388191 Summary: Adesso M14 No Sensitivity Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: tablet support Assignee: krita-bugs-n...@kde.org Reporter: chev...@live.com Target Milestone: --- I'm running Win10, build 16299 and using Krita Gemini V2.9 Pre-Alpha off Steam. I'm using the Adesso M14 USB tablet. After modifying sensitivity settings in Settings > Configure Krita > Tablet Settings and in brush-specific settings, I still have no pressure sensitivity. It's still all, nothing, or sporadic dots because the pressure is on or off, no in-between. I just. Really am not sure where to proceed from here? Nor really what other information you may need, but I'll be more than happy to collect what's necessary and update this with it - just tell me everything to find and I'll share it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388183] Windows installer is not HiDPI ready
https://bugs.kde.org/show_bug.cgi?id=388183 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Bundle-Windows -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388183] Windows installer is not HiDPI ready
https://bugs.kde.org/show_bug.cgi?id=388183 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- The new 5.8.0 bundle use already NSIS 3.x. So it will not a problem to patch the option for Hdpi support. See here : https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388190] no baloo settings
https://bugs.kde.org/show_bug.cgi?id=388190 caulier.gil...@gmail.com changed: What|Removed |Added Platform|openSUSE RPMs |Appimage Component|Bundle-AppImage |Database-Baloo -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388190] no baloo settings
https://bugs.kde.org/show_bug.cgi?id=388190 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from caulier.gil...@gmail.com --- Baloo support is optional and voluntary disabled with all bundle, because the service do not work well with bundle application process. Baloo is also considerated as unstable, as we seen all reports in bugzilla about this interface. There is no plan around Baloo support. I will said more : the plan is to remove baloo support in the future if nothing change to improve the stability of this engine. We have more important tasks to do and we need to reduce complexity if we can. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 377880] Gwenview There are two actions (Cut, Delete)
https://bugs.kde.org/show_bug.cgi?id=377880 NIlesh Prasad changed: What|Removed |Added CC||prasadniles...@gmail.com --- Comment #35 from NIlesh Prasad --- I've been facing the same issue. On Ubuntu 16.04 KDE PLasma Version 5.8.8 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388190] New: no baloo settings
https://bugs.kde.org/show_bug.cgi?id=388190 Bug ID: 388190 Summary: no baloo settings Product: digikam Version: 5.7.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Bundle-AppImage Assignee: digikam-bugs-n...@kde.org Reporter: philippe.roub...@free.fr Target Milestone: --- in digikam settings > metadata there is no baloo settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 375000] Meta-to-open-menu stops working quickly after reboot on specific keyboard model
https://bugs.kde.org/show_bug.cgi?id=375000 tuxflo changed: What|Removed |Added CC||flo.hen...@gmail.com --- Comment #14 from tuxflo --- I think this is still relevant on the latest version of the plasmashell (KDE Neon user edition, 5.11.4). Starting Computer, super key works fine (toggles Menu) After a while: nothing happens when pressing the super key. Restart kwin (killall kwin_x11 && kstart5 kwin_x11): Super key is working again. In my tests it had nothing to do with the Alt+Tab shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 388189] New: KGet Crashes on application start
https://bugs.kde.org/show_bug.cgi?id=388189 Bug ID: 388189 Summary: KGet Crashes on application start Product: kget Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@kde.org Reporter: jdogzi...@hotmail.com CC: wba...@tmo.at Target Milestone: --- Application: kget (2.14.34) KDE Platform Version: 4.14.34 Qt Version: 4.8.7 Operating System: Linux 4.13.0-17-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: started kget from KDE Menu. Copied a link from Chrome to download The crash can be reproduced every time. -- Backtrace: Application: KGet (kget), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 0x55f628c931a4 in () #7 0x55f628c93b65 in () #8 0x7f8a23693f70 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #9 0x7f8a22f0ef8f in QHeaderView::sectionCountChanged(int, int) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #10 0x7f8a22f12c36 in QHeaderView::initializeSections(int, int) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #11 0x7f8a22f14c5d in QHeaderView::initializeSections() () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #12 0x7f8a22f18ad2 in QHeaderView::setModel(QAbstractItemModel*) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #13 0x7f8a22f4bd9f in QTreeView::setModel(QAbstractItemModel*) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #14 0x55f628c933b0 in () #15 0x55f628c98dc2 in () #16 0x55f628d086a1 in () #17 0x55f628d09b9d in () #18 0x7f8a2490714e in () at /usr/lib/libkdeui.so.5 #19 0x7f8a249071fd in () at /usr/lib/libkdeui.so.5 #20 0x7f8a24907451 in () at /usr/lib/libkdeui.so.5 #21 0x7f8a23a0bfc5 in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #22 0x7f8a23a0d5ab in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #23 0x7f8a23a0e23d in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #24 0x7f8a23a0e43b in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #25 0x7f8a23699d11 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #26 0x7f8a229ca7ef in QApplication::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #27 0x7f8a229c503c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x7f8a229cbf76 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #29 0x7f8a2490004a in KApplication::notify(QObject*, QEvent*) () at /usr/lib/libkdeui.so.5 #30 0x7f8a2367f8ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #31 0x7f8a23683366 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #32 0x7f8a236b009e in () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #33 0x7f8a1e443fb7 in g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7f8a1e4441f0 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7f8a1e44427c in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #36 0x7f8a236b020e in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #37 0x7f8a22a72666 in () at /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #38 0x7f8a2367e12f in QEventLoop::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #39 0x7f8a2367e495 in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #40 0x7f8a0bfe5972 in () at /usr/lib/kde4/kget_metalinkfactory.so #41 0x7f8a0bfceaa5 in () at /usr/lib/kde4/kget_metalinkfactory.so #42 0x7f8a25975140 in KGet::createTransfers(QList const&) () at /usr/lib/libkgetcore.so.4 #43 0x7f8a25976833 in KGet::addTransfers(QList const&, QString const&) () at /usr/lib/libkgetcore.so.4 #44 0x7f8a2598ef14 in TransferGroup::load(QDomElement const&) () at /usr/lib/libkgetcore.so.4 #45 0x7f8a25972e99 in KGet::load(QString) () at /usr/lib/libkgetcore.so.4 #46 0x55f628d075d2 in () #47 0x55f628d0875e in () #48 0x55f628d09b9d in () #49 0x7f8a2490714e in () at /usr/lib/libkdeui.so.5 #50 0x7f8a249071fd in () at /usr/lib/libkdeui.so.5 #51 0x7f8a24907451 in () at /usr/lib/libkdeui.so.5 #52 0x7f8a23a0bfc5 in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #53 0x7f8a23a0d51c in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #54 0x7f8a23a0e23d in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #55 0x7f8a23a0e43b in () at /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 #56 0x7f8a23699d11 in QObje
[plasmashell] [Bug 385814] Kate icon removed from the favorites list is back when plasma session is restarted
https://bugs.kde.org/show_bug.cgi?id=385814 Chris Holland changed: What|Removed |Added CC||zrenf...@gmail.com --- Comment #9 from Chris Holland --- https://www.reddit.com/r/kde/comments/7lqt3u/discover_keeps_returning_in_my_favorites/ /u/RASQ37 has this issue with Kate /u/Astroniglio (Arch Linux) has this issue with Discover -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 256561] Katepart scrolls per paragraph rather than what is set globally (e.g. 3 lines)
https://bugs.kde.org/show_bug.cgi?id=256561 --- Comment #27 from Michael D --- A fix for 2018? Still my favorite worst editor the year. Great to use until you have to scroll -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 387672] Baloo File Extraction Error
https://bugs.kde.org/show_bug.cgi?id=387672 --- Comment #6 from marty --- Created attachment 109497 --> https://bugs.kde.org/attachment.cgi?id=109497&action=edit New crash information added by DrKonqi baloo_file_extractor (5.40.0) using Qt 5.9.2 - What I was doing when the application crashed: Logging in after powering up laptop - Unusual behavior I noticed: Laptop fan and hard drive loads spike after trying to resart app, and temperature spikes on laptop soon afterward. -- Backtrace (Reduced): #8 0x7f1c722dbb22 in mdb_assert_fail.constprop () from /lib64/liblmdb.so.0.0.0 #9 0x7f1c722d0b85 in mdb_page_dirty () from /lib64/liblmdb.so.0.0.0 #10 0x7f1c722d1d8b in mdb_page_alloc.isra () from /lib64/liblmdb.so.0.0.0 #11 0x7f1c722d1ff9 in mdb_page_touch () from /lib64/liblmdb.so.0.0.0 #12 0x7f1c722d3c24 in mdb_cursor_touch () from /lib64/liblmdb.so.0.0.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 388188] continuing...
https://bugs.kde.org/show_bug.cgi?id=388188 --- Comment #2 from gerald.da...@gmx.com --- Created attachment 109496 --> https://bugs.kde.org/attachment.cgi?id=109496&action=edit more wlan0 connection screenshot information. screenshot during & after "continuing" bugreport. Note in second screenshot missing wlan0 (linksys usb) connection information & the list of local IP numbers that are NEVER shown anywhere using my wlp3s0b3 wpa2 connection. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 388188] continuing...
https://bugs.kde.org/show_bug.cgi?id=388188 --- Comment #1 from gerald.da...@gmx.com --- Created attachment 109495 --> https://bugs.kde.org/attachment.cgi?id=109495&action=edit screenshot after connecting to wlan0 with wpa2 on home wifi screenshot during & after connecting with wlan0 wpa2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 388188] New: continuing...
https://bugs.kde.org/show_bug.cgi?id=388188 Bug ID: 388188 Summary: continuing... Product: konsole Version: 16.12.3 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: gerald.da...@gmx.com Target Milestone: --- Application: konsole (16.12.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.56-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: bugreport popup; please see backtrace. Was online with wifi using drakconnect to setup wlp3s0b1 on house 5G wifi using wpa2. Viewed contents of htop and noticed under /sbin/init/| |-sbin/ifplugd -I -b -i wlp3s0b1 -c /etc/wpa_supplicant.conf -D wext I use drakconnect to setup & then takedown interfaces each time as they seem to be populated with settings that I do not choose or use in my house wifi connection, and the strange settings that reappear constantly seem to increase with the amount of time I am online & typically appear if I forget them unattended for any length of time. I do not use any wext extensions. After viewing this in htop I then tried connecting using a linksys usb (uses ndiswrapper), used drakconnect to set up connection. Opened and found 5G connection populated, (typically only uses 2.4G, (but thats another looping story), pressed connect & DrK popped up, asking for a bug report. Took screenshot of htop, please see attached, and promptly reported. drakconnect reports a successful 2.4G connection... may I LOL here..? ;) -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa7ad486800 (LWP 14519))] Thread 3 (Thread 0x7fa78989f700 (LWP 14528)): #0 0x7fa7a6186c4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa7914b2e2b in util_queue_thread_func () from /usr/lib64/dri/nouveau_dri.so #2 0x7fa7914b2b97 in impl_thrd_routine () from /usr/lib64/dri/nouveau_dri.so #3 0x7fa7a618166d in start_thread () from /lib64/libpthread.so.0 #4 0x7fa7acf3ed4d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fa7929b5700 (LWP 14527)): #0 0x7fa7acf32f0d in poll () from /lib64/libc.so.6 #1 0x7fa7a5c5ec94 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #2 0x7fa7a5c5ed9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7fa7a9b0fe2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7fa7a9abb49a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7fa7a98f53bc in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7fa7ad557635 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7fa7a98f9ff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7fa7a618166d in start_thread () from /lib64/libpthread.so.0 #9 0x7fa7acf3ed4d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fa7ad486800 (LWP 14519)): [KCrash Handler] #6 0x7fa7a928f1a9 in KNotification::id() () from /lib64/libKF5Notifications.so.5 #7 0x7fa7a92917c9 in KNotificationManager::notifyPluginFinished(KNotification*) () from /lib64/libKF5Notifications.so.5 #8 0x7fa7a9291bdc in KNotificationManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libKF5Notifications.so.5 #9 0x7fa7a9ae8859 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7fa7a92bb49f in KNotificationPlugin::finished(KNotification*) () from /lib64/libKF5Notifications.so.5 #11 0x7fa7a92a351c in NotifyByPopup::onPassivePopupDestroyed() () from /lib64/libKF5Notifications.so.5 #12 0x7fa7a9ae8859 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7fa7a9ae8f6f in QObject::destroyed(QObject*) () from /lib64/libQt5Core.so.5 #14 0x7fa7aa6a10c1 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #15 0x7fa7a9293319 in KPassivePopup::~KPassivePopup() () from /lib64/libKF5Notifications.so.5 #16 0x7fa7a9ae93e0 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7fa7aa6a54b3 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7fa7aa79efbe in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7fa7aa662d0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7fa7aa667e76 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7fa7a9abd628 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7fa7a9abf44b in QCoreApplicationPrivate::sendPostedEv
[systemsettings] [Bug 388187] New: Crash do aplicativo Configurações do sistema (systemsettings5)
https://bugs.kde.org/show_bug.cgi?id=388187 Bug ID: 388187 Summary: Crash do aplicativo Configurações do sistema (systemsettings5) Product: systemsettings Version: 5.11.4 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: moisescar...@hotmail.com Target Milestone: --- Application: systemsettings5 (5.11.4) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.10.0-42-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: Ao pesquisar as categorias do aplicativo, o crash aconteceu. Neste momento, estava aberto aplicativo Konsole (konsole) e duas janelas do Dolphin (dolphin). The crash can be reproduced sometimes. -- Backtrace: Application: Configurações do Sistema (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1bb171b8c0 (LWP 8555))] Thread 5 (Thread 0x7f1b7f3af700 (LWP 8560)): #0 0x7f1bad41570d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1ba73b138c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1ba73b149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1badd3c6cb in QEventDispatcherGlib::processEvents (this=0x7f1b780008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f1badce4e2a in QEventLoop::exec (this=this@entry=0x7f1b7f3aece0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #5 0x7f1badb0d8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #6 0x7f1babbc2d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f1badb12709 in QThreadPrivate::start (arg=0x24e51c0) at thread/qthread_unix.cpp:368 #8 0x7f1ba92396ba in start_thread (arg=0x7f1b7f3af700) at pthread_create.c:333 #9 0x7f1bad4213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f1b88e88700 (LWP 8559)): #0 0x7f1ba73b1381 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1ba73b149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1badd3c6cb in QEventDispatcherGlib::processEvents (this=0x7f1b840008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #3 0x7f1badce4e2a in QEventLoop::exec (this=this@entry=0x7f1b88e87ce0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #4 0x7f1badb0d8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #5 0x7f1babbc2d25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f1badb12709 in QThreadPrivate::start (arg=0x217d790) at thread/qthread_unix.cpp:368 #7 0x7f1ba92396ba in start_thread (arg=0x7f1b88e88700) at pthread_create.c:333 #8 0x7f1bad4213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 3 (Thread 0x7f1b9530f700 (LWP 8557)): #0 0x7f1ba73f5a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f1ba73b0910 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f1ba73b12bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f1ba73b149c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f1badd3c6cb in QEventDispatcherGlib::processEvents (this=0x7f1b98c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f1badce4e2a in QEventLoop::exec (this=this@entry=0x7f1b9530ecd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:212 #6 0x7f1badb0d8f4 in QThread::exec (this=) at thread/qthread.cpp:515 #7 0x7f1bae1bb315 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7f1badb12709 in QThreadPrivate::start (arg=0x7f1bae42fd40) at thread/qthread_unix.cpp:368 #9 0x7f1ba92396ba in start_thread (arg=0x7f1b9530f700) at pthread_create.c:333 #10 0x7f1bad4213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 2 (Thread 0x7f1b9e210700 (LWP 8556)): #0 0x7f1bad41570d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f1ba9aafc62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f1ba9ab18d7 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f1ba07671f9 in QXcbEventReader::run (this=0x1dc41f0) at qxcbconnection.cpp:1330 #4 0x7f1badb12709 in QThreadPrivate::start (arg=0x1dc41f0) at thread/qthread_unix.cpp:368 #5 0x7f1ba92396ba in start_thread (arg=0x7f1b9e210700) at pthread_create.c:333 #6 0x7f1bad4213dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f1bb171b8c0 (LWP 8555)): [KCrash Handler] #6 0x7f1badcf03a0 in QMetaObject::inherits (this=0x2452db8, metaObject=metaObject@entry=0x7f1baffa1540 ) at kernel/qmetaobject.cpp:339
[kate] [Bug 387358] Kate reloads files from disk without confirmation
https://bugs.kde.org/show_bug.cgi?id=387358 --- Comment #4 from nfx...@gmail.com --- I'm still disliking this very much. Just because a file is git managed, it doesn't mean you can't lose parts of its contents. For example, this clears the undo stack. I'd also like more control over this whole thing (this automatism and bugs like #388186 aren't very confidence inducing). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 388186] New: Kate fails to reload files from disk as they disappear/reappear (and other cases)
https://bugs.kde.org/show_bug.cgi?id=388186 Bug ID: 388186 Summary: Kate fails to reload files from disk as they disappear/reappear (and other cases) Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: nfx...@gmail.com Target Milestone: --- I have this reproducible with 2 git branches, where one branch adds a new file: - checkout the other branch (which lacks the new file) - confirm reloading (will show an empty editor window when you select the file) - checkout the first branch again - the file is not reloaded, and still shows an empty editor window, even though the file definitely has content on disk Using "Reload All" gives you the file back. I think this also happened when the file was not empty. Then it contained an old version of the file, different from the on disk version. This is even more evil, but I can't reproduce it. But I had some embarrassing bugs due to editing a file during a rebase, and accidentally restoring some old edits (can't tell if the file was removed and recreated at some point during all the reloading). This probably happened in slightly older kate versions too (before #387358 happened), but not in even older versions. Sorry, I don't know at which versions this was, and have no easy way to test. Kate 17.08.3, Project Plugin enabled. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 388180] Error after all packages built successfully
https://bugs.kde.org/show_bug.cgi?id=388180 --- Comment #3 from Michael Pyne --- Git commit b0f4b638c7cb4fa0033ddfb86d393a25f8c90eb8 by Michael Pyne. Committed on 24/12/2017 at 00:26. Pushed by mpyne into branch 'testing-restructure'. test: Add unit test for bug 388180 first-use persistent options. Fails without the bugfix, passes afterwards. A +53 -0t/persistent-storage.t https://commits.kde.org/kdesrc-build/b0f4b638c7cb4fa0033ddfb86d393a25f8c90eb8 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 388185] No Description field in Qt5WebKitWidgets.pc
https://bugs.kde.org/show_bug.cgi?id=388185 --- Comment #1 from Alex --- This is using version 5.212.0~alpha2-6+16.04+xenial+build30 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 388185] No Description field in Qt5WebKitWidgets.pc
https://bugs.kde.org/show_bug.cgi?id=388185 Alex changed: What|Removed |Added Platform|Other |Neon Packages CC||alexander.sch...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 388185] New: No Description field in Qt5WebKitWidgets.pc
https://bugs.kde.org/show_bug.cgi?id=388185 Bug ID: 388185 Summary: No Description field in Qt5WebKitWidgets.pc Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: alexander.sch...@yahoo.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- I ran into this issue while attempting to build the VERGE cryptocurrency wallet. When running ./configure, it doesn't see the Qt dependencies required for the GUI client. The log notes that the Description field is missing for Qt5WebkitWidgets. Adding a line beginning with "Description: ..." solves to Qt5WebkitWidgets.pc (part of libqt5webkit5-dev) this problem. I saw Qt5Core.pc has such a line. Therefore, I think Qt5WebkitWidgets.pc should have a description as well. Sorry if this already has been reported. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 388181] As Yet Unknown Cause
https://bugs.kde.org/show_bug.cgi?id=388181 --- Comment #1 from gerald.da...@gmx.com --- Created attachment 109494 --> https://bugs.kde.org/attachment.cgi?id=109494&action=edit New crash information added by DrKonqi konsole (16.12.3) using Qt 5.6.2 - What I was doing when the application crashed: Fillling out the previous bug report "As Yet Unknown Cause". The main difference between this & the last report is: Thread 2 (Thread 0x7f38c913c700 (LWP 11908)): #0 0x7f38dc42a959 in g_mutex_lock () from /lib64/libglib-2.0.so.0 If I keep getting conitinous crash reports with only slight differences between them I can see it being a waiste of resources re time spent reading by developers/bug triage folks. If I save the diff's from each report and build a "trail" of sorts, then this would address that difficulty; on the other hand, if the reports are that serious in nature & my box is comprimised then overkill also has it's merrits. I would appreciate some direction if I am to be of any use here and not waisting peoples valuable time. Seeking the opportunity to contribute & learn :) -- Backtrace (Reduced): #4 0x7f38dfa161a9 in KNotification::id() () from /lib64/libKF5Notifications.so.5 #5 0x7f38dfa187c9 in KNotificationManager::notifyPluginFinished(KNotification*) () from /lib64/libKF5Notifications.so.5 #6 0x7f38dfa18bdc in KNotificationManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libKF5Notifications.so.5 [...] #8 0x7f38dfa4249f in KNotificationPlugin::finished(KNotification*) () from /lib64/libKF5Notifications.so.5 #9 0x7f38dfa2a51c in NotifyByPopup::onPassivePopupDestroyed() () from /lib64/libKF5Notifications.so.5 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 388181] As Yet Unknown Cause
https://bugs.kde.org/show_bug.cgi?id=388181 gerald.da...@gmx.com changed: What|Removed |Added CC||gerald.da...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387025] KMail crashes when launched
https://bugs.kde.org/show_bug.cgi?id=387025 --- Comment #5 from Allan Sandfeld --- I downgraded to neon user instead of dev stable, so I don't know if it still happens there. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 388180] Error after all packages built successfully
https://bugs.kde.org/show_bug.cgi?id=388180 Michael Pyne changed: What|Removed |Added Version Fixed In||18.01 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kde ||src-build/25e7bfc26fbacbfeb ||3875e75df02fa9409571d4e --- Comment #2 from Michael Pyne --- Git commit 25e7bfc26fbacbfeb3875e75df02fa9409571d4e by Michael Pyne. Committed on 23/12/2017 at 23:13. Pushed by mpyne into branch 'master'. persistence: Fix regression in saving options. The move to JSON storage of persistent opts break first-time users, since the refactored code never actually gets around to setting a persistent_options key in the build context object. This seemed to work previously with Data::Dumper, but JSON::PP is not happy with being asked to serialize an undef. On the other hand I had always thought that sub setPersistentOption would have 'autovivified' the needed hash table, and the reporter's build process should have resulted in many calls to setPersistentOption over the build. FIXED-IN:18.01 M +1-1modules/ksb/BuildContext.pm https://commits.kde.org/kdesrc-build/25e7bfc26fbacbfeb3875e75df02fa9409571d4e -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 355755] Konsole doesn't follow system settings for natural scrolling
https://bugs.kde.org/show_bug.cgi?id=355755 --- Comment #5 from Kurt Hindenburg --- Doing a search shows that 1) libinput has to be removed and 2) have to restart Konsole (and some other KDE) apps after changing the scrolling. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388184] New: wrong folder to store user settings under Windows
https://bugs.kde.org/show_bug.cgi?id=388184 Bug ID: 388184 Summary: wrong folder to store user settings under Windows Product: digikam Version: 5.7.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: uwesto...@web.de Target Milestone: --- digiKam uses the folder C:\Users\\AppData\Local\digikam to store the suer settings. This is not wrong but is annoying if you login on another PC in your network. Therefore the folder to store user settings should be C:\Users\\AppData\Roaming\digikam See e.g. https://www.howtogeek.com/318177/what-is-the-appdata-folder-in-windows/ for a short explanation of the difference between the Local and the Roaming folder. Most programs use therefore the Roaming folder. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388116] Add possibility to switch with the mouse between images in preview mode
https://bugs.kde.org/show_bug.cgi?id=388116 --- Comment #4 from bug...@tuta.io --- This is it, thanks! Is there / is there going to be a possibility to switch between the pictures only with the mouse (without using the for this purpose provided buttons on the upper left of the preview canvas)? When I add face tags to my pictures, the left hand is on the number pad to which the names of the persons are mapped and the right hand is, of course, on the mouse. When working on many hundreds of pictures, it would take me a significant amount of extra time to always move the left hand from the number pad to SHIFT and back. When not zoomed into the picture, scrolling the mouse wheel does nothing, so mapping next picture and previous picture to the mouse wheel would not collide with other functions. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388183] New: Windows installer is not HiDPI ready
https://bugs.kde.org/show_bug.cgi?id=388183 Bug ID: 388183 Summary: Windows installer is not HiDPI ready Product: digikam Version: 5.7.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: uwesto...@web.de Target Milestone: --- The Win installer of digiKam 5.7 looks blurred on HiDPI screens. The reason is that it uses the old NSIS 2.5. To fix this bug, simply upgrade to NSIS 3.x and use the new command ManifestDPIAware: http://nsis.sourceforge.net/Reference/ManifestDPIAware p.s. NSIS 3.x comes with full Unicode support. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 388180] Error after all packages built successfully
https://bugs.kde.org/show_bug.cgi?id=388180 --- Comment #1 from Michael Pyne --- I bet this is related to a first-use bug, let me see if I can reproduce. Thanks for the report as well! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388182] New: Plasma breaks when taking a screenshot of chromium
https://bugs.kde.org/show_bug.cgi?id=388182 Bug ID: 388182 Summary: Plasma breaks when taking a screenshot of chromium Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: altgu...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Taking an active window screenshot of a web page in Chromium often causes Plasma to break in a number of ways - any hidden toolbars will become permanently visible, many windows will loose their window decoration and become unable to be moved, clicking on a different window doesn't change window focus and bring it to the forefront, various widgets stop working, etc. etc. This seems to only happen with Chromium window screenshots - I can't recreate the bug with screenshots of any other application or web browser. The link below is a video of the bug: https://youtu.be/_mrwpKCwZ2Y -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 386546] bad textarea width for rename file if filename too short
https://bugs.kde.org/show_bug.cgi?id=386546 David Edmundson changed: What|Removed |Added Severity|major |normal CC||k...@davidedmundson.co.uk --- Comment #7 from David Edmundson --- Updating based on phabricator status: - patch needs some rework to not break RTL support. You can test with plasmashell --reverse. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 388181] New: As Yet Unknown Cause
https://bugs.kde.org/show_bug.cgi?id=388181 Bug ID: 388181 Summary: As Yet Unknown Cause Product: konsole Version: 16.12.3 Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: gerald.da...@gmx.com Target Milestone: --- Application: konsole (16.12.3) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.9.56-desktop-1.mga6 x86_64 Distribution: "Mageia 6" -- Information about the crash: - What I was doing when the application crashed: running first time user & install of ddd-gui to try to learn & understand why system keeps crashing. This was a response to bugreports popping up prompting to report said crashes & bugs. I setup this account, installed gdb, found it slightly beyong my abilities and grabbed the ddd-gui. I am running as root using ICEwm, and the system keeps crashing while doing various things in the terminal. The information in the bug reports generated seem to bare little resemblance to the processes related to the few things Im running ie: terminal, browser, wifi etc, and more to do with what's going on with the underlying methods of transport being utilised by the kernel. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f577f1df800 (LWP 4789))] Thread 3 (Thread 0x7f575e052700 (LWP 4800)): #0 0x7f5777edfc4f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f575ed1ae2b in util_queue_thread_func () from /usr/lib64/dri/nouveau_dri.so #2 0x7f575ed1ab97 in impl_thrd_routine () from /usr/lib64/dri/nouveau_dri.so #3 0x7f5777eda66d in start_thread () from /lib64/libpthread.so.0 #4 0x7f577ec97d4d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f575700 (LWP 4798)): #0 0x7f57779b4e20 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #1 0x7f57779b71cb in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #2 0x7f57779b7bc3 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #3 0x7f57779b7d9c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #4 0x7f577b868e2b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7f577b81449a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7f577b64e3bc in QThread::exec() () from /lib64/libQt5Core.so.5 #7 0x7f577f2b0635 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #8 0x7f577b652ff9 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7f5777eda66d in start_thread () from /lib64/libpthread.so.0 #10 0x7f577ec97d4d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f577f1df800 (LWP 4789)): [KCrash Handler] #4 0x7f577afe81a9 in KNotification::id() () from /lib64/libKF5Notifications.so.5 #5 0x7f577afea7c9 in KNotificationManager::notifyPluginFinished(KNotification*) () from /lib64/libKF5Notifications.so.5 #6 0x7f577afeabdc in KNotificationManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libKF5Notifications.so.5 #7 0x7f577b841859 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f577b01449f in KNotificationPlugin::finished(KNotification*) () from /lib64/libKF5Notifications.so.5 #9 0x7f577affc51c in NotifyByPopup::onPassivePopupDestroyed() () from /lib64/libKF5Notifications.so.5 #10 0x7f577b841859 in QMetaObject::activate(QObject*, int, int, void**) () from /lib64/libQt5Core.so.5 #11 0x7f577b841f6f in QObject::destroyed(QObject*) () from /lib64/libQt5Core.so.5 #12 0x7f577c3fa0c1 in QWidget::~QWidget() () from /lib64/libQt5Widgets.so.5 #13 0x7f577afec319 in KPassivePopup::~KPassivePopup() () from /lib64/libKF5Notifications.so.5 #14 0x7f577b8423e0 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #15 0x7f577c3fe4b3 in QWidget::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #16 0x7f577c4f7fbe in QFrame::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f577c3bbd0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7f577c3c0e76 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #19 0x7f577b816628 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f577b81844b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #21 0x7f577b8689f3 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #22 0x7f57779b7ac7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #23 0x7f57779b7cf8 in g_main_context_iterate.isra ()
[plasmashell] [Bug 381608] Plasmashell use 100% cpu
https://bugs.kde.org/show_bug.cgi?id=381608 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #18 from David Edmundson --- >I am re-opening this ticket because I have some new information to provide. Thanks, I did read it. I can't do much else with this, we have N similar reports of "slow CPU " whcih is a very vague symptom. This "see also" section of the linked reports tracks specific technical areas. *** This bug has been marked as a duplicate of bug 378010 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 --- Comment #64 from David Edmundson --- *** Bug 381608 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 377748] Plasma crashed when I'm changed the window focus
https://bugs.kde.org/show_bug.cgi?id=377748 David Edmundson changed: What|Removed |Added CC||huanghaorui...@gmail.com --- Comment #8 from David Edmundson --- *** Bug 388173 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388173] Plasma crash on clicking desktop icon
https://bugs.kde.org/show_bug.cgi?id=388173 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from David Edmundson --- *** This bug has been marked as a duplicate of bug 377748 *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387979] Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387979 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Severity|critical|crash -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388116] Add possibility to switch with the mouse between images in preview mode
https://bugs.kde.org/show_bug.cgi?id=388116 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #3 from Maik Qualmann --- Shift + Mouse wheel... Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388116] Add possibility to switch with the mouse between images in preview mode
https://bugs.kde.org/show_bug.cgi?id=388116 --- Comment #2 from bug...@tuta.io --- I tried it, but CTRL + mouse wheel zooms in and out. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 386827] Errors in syntax definitions
https://bugs.kde.org/show_bug.cgi?id=386827 --- Comment #9 from Dominik Haumann --- @Gene Thomas: ping -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 367909] Pressing Backspace skips Arabic and Hebrew diacritics
https://bugs.kde.org/show_bug.cgi?id=367909 Safa Alfulaij changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Safa Alfulaij --- Fixed by https://cgit.kde.org/ktexteditor.git/commit/?id=c9b412d403342ce4b96632a1f6feaa61e37c2e64 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 387025] KMail crashes when launched
https://bugs.kde.org/show_bug.cgi?id=387025 --- Comment #4 from David Faure --- To remove drkonqi from the equation, simply export KDE_DEBUG=1. Either this is a miscompilation... or I did something wrong in terms of KConfigGroup lifetime in https://phabricator.kde.org/D8783 ... but the calling code is simply KConfigGroup grp(KernelIf->config(), "CollectionTreeOrder"); d->entityOrderProxy->setOrderConfig(grp); which should be fine... Does this still happen? -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 388180] New: Error after all packages built successfully
https://bugs.kde.org/show_bug.cgi?id=388180
Bug ID: 388180
Summary: Error after all packages built successfully
Product: kdesrc-build
Version: unspecified
Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: mp...@kde.org
Reporter: kde...@posteo.de
Target Milestone: ---
I used kdesrc-build to build the kde-pim group in a fresh kdepim-docker
container. See https://community.kde.org/KDE_PIM/Docker for details on this
Neon-based image; I had to install libyaml-libyaml-perl inside the container
manually.
After all 58 packages built successfully, I got the following (error?) message:
Encountered an error in the execution of the script.
The error reported was hash- or arrayref expected (not a simple scalar, use
allow_nonref to allow this) at
/home/neon/kdesrc-build/modules/ksb/BuildContext.pm line 829.
at /usr/share/perl/5.22/JSON/PP.pm line 504.
JSON::PP::encode_error("hash- or arrayref expected (not a simple
scalar, use allow_no"...) called at /usr/share/perl/5.22/JSON/PP.pm line 289
JSON::PP::PP_encode_json(JSON::PP=HASH(0x47577a0), undef) called at
/usr/share/perl/5.22/JSON/PP.pm line 143
JSON::PP::encode(JSON::PP=HASH(0x47577a0), undef) called at
/home/neon/kdesrc-build/modules/ksb/BuildContext.pm line 829
ksb::BuildContext::storePersistentOptions(ksb::BuildContext=HASH(0x26b2100))
called at /home/neon/kdesrc-build/modules/ksb/Application.pm line 740
ksb::Application::finish(ksb::Application=HASH(0x3ef8b50), 0) called at
./kdesrc-build line 288
eval {...} called at ./kdesrc-build line 271
Please submit a bug against kdesrc-build on https://bugs.kde.org/
--
You are receiving this mail because:
You are watching all bug changes.
[gwenview] [Bug 340667] Add "sort By" rating option
https://bugs.kde.org/show_bug.cgi?id=340667 Andrew Travneff changed: What|Removed |Added CC||travn...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 388179] New: KRunner loses keypresses on wayland
https://bugs.kde.org/show_bug.cgi?id=388179 Bug ID: 388179 Summary: KRunner loses keypresses on wayland Product: krunner Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: fab...@ritter-vogt.de Target Milestone: --- When starting a plasma wayland session, krunner is only half-loaded. "Alt-F2 kons" in this state results in either "s" or an empty krunner prompt. Successive invocations work fine. Probably easiler to reproduce on a slower machine, but I get a 100% failure rate in a VM. openQA found that even keypresses after krunner is shown completely get lost. Workaround: "krunner -platform xcb". -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 377331] typwriter effect is missing since 15.04. bounty 60€
https://bugs.kde.org/show_bug.cgi?id=377331 --- Comment #8 from Eckard Gerlach --- When will be there a first linux version with typwriter? -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 373743] Inserting columns crash
https://bugs.kde.org/show_bug.cgi?id=373743 Tomas Mecir changed: What|Removed |Added CC||tracy.hetr...@gmail.com --- Comment #2 from Tomas Mecir --- *** Bug 371910 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 381072] Crash after insert new row
https://bugs.kde.org/show_bug.cgi?id=381072 Tomas Mecir changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||mec...@gmail.com --- Comment #1 from Tomas Mecir --- *** This bug has been marked as a duplicate of bug 373743 *** -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 371910] Calligra crashed when reducing column width
https://bugs.kde.org/show_bug.cgi?id=371910 Tomas Mecir changed: What|Removed |Added CC||mec...@gmail.com Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Tomas Mecir --- *** This bug has been marked as a duplicate of bug 373743 *** -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 373743] Inserting columns crash
https://bugs.kde.org/show_bug.cgi?id=373743 Tomas Mecir changed: What|Removed |Added CC||n...@qakq.com --- Comment #3 from Tomas Mecir --- *** Bug 381072 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 387979] Plasmashell and latte dock crashes due abnormal behavior of kactivitymanagerd
https://bugs.kde.org/show_bug.cgi?id=387979 --- Comment #8 from Ivan Bordoni --- Ok I've solved ! The problem, it comes from the database ~/.local/share/kactivitymanagerd/resources/database it was corrupt ...I have not tried to empty it but I simply deleted it: ~/.local/share/kactivitymanagerd/ and now everything works correctly ...but now I can not explain why this kind of problem, here are the things I was doing before the problem: - after a login I found the latte-dock of the primary display, strangely out of position and on the 55-inch TV secondary display - I played on the management of the displays to reposition the latte-dock - I restarted and here appears the problem described above Thanks so much guys for support -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 388178] New: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault - ArchiveJob::~ArchiveJob() (this=0x24b1080, __in_chrg=)
https://bugs.kde.org/show_bug.cgi?id=388178 Bug ID: 388178 Summary: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault - ArchiveJob::~ArchiveJob() (this=0x24b1080, __in_chrg=) Product: Akonadi Version: 5.5.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: Archive Mail Agent Assignee: kdepim-b...@kde.org Reporter: bugrprt21...@online.de Target Milestone: --- Application: akonadi_archivemail_agent (5.5.2) Qt Version: 5.6.2 Frameworks Version: 5.32.0 Operating System: Linux 4.4.103-36-default x86_64 Distribution: "openSUSE Leap 42.3" -- Information about the crash: - What I was doing when the application crashed: Letting the automatic e-Mail Archive run as planned -- noticed this crash when I returned to the machine. -- Backtrace: Application: Agent zur E-Mail-Archivierung (akonadi_archivemail_agent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3a02c52940 (LWP 32612))] Thread 9 (Thread 0x7f39c6d42700 (LWP 336)): #0 0x7f39fdebb555 in clock_gettime () at /lib64/libc.so.6 #1 0x7f39fe86fa46 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f39fe9d5809 in QTimerInfoList::updateCurrentTime() () at /usr/lib64/libQt5Core.so.5 #3 0x7f39fe9d5d85 in QTimerInfoList::timerWait(timespec&) () at /usr/lib64/libQt5Core.so.5 #4 0x7f39fe9d6f7e in () at /usr/lib64/libQt5Core.so.5 #5 0x7f39f729895d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #6 0x7f39f7299230 in () at /usr/lib64/libglib-2.0.so.0 #7 0x7f39f729942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #8 0x7f39fe9d71ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #9 0x7f39fe984bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #10 0x7f39fe7bff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #11 0x7f39fe7c4a29 in () at /usr/lib64/libQt5Core.so.5 #12 0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0 #13 0x7f39fdeaeaad in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7f39c7543700 (LWP 32742)): #0 0x7f39fe7bd44a in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7f39fe9d77c5 in () at /usr/lib64/libQt5Core.so.5 #2 0x7f39f7298da1 in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f39f72992a8 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f39f729942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f39fe9d71ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7f39fe984bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7f39fe7bff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7f39fe7c4a29 in () at /usr/lib64/libQt5Core.so.5 #9 0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0 #10 0x7f39fdeaeaad in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f39c7d44700 (LWP 32736)): #0 0x7f39f7298efb in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #1 0x7f39f7299388 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f39f729942c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f39fe9d71ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f39fe984bfb in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f39fe7bff5a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f3a00014295 in () at /usr/lib64/libQt5DBus.so.5 #7 0x7f39fe7c4a29 in () at /usr/lib64/libQt5Core.so.5 #8 0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0 #9 0x7f39fdeaeaad in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f39c8c39700 (LWP 32714)): #0 0x7f39f81720bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f39d6383b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f39d63838c7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f39fdeaeaad in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f39c943a700 (LWP 32713)): #0 0x7f39f81720bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f39d6383b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f39d63838c7 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7f39f816d744 in start_thread () at /lib64/libpthread.so.0 #4 0x7f39fdeaeaad in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f39c9c3b700 (LWP 32712)): #0 0x7f39f81720bf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f39d6383b4b in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7f39d63838c7 in () at /usr/lib
[konsole] [Bug 350001] Konsole mistakenly believes it is non-visible when not focused
https://bugs.kde.org/show_bug.cgi?id=350001 Kurt Hindenburg changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kon ||sole/3e7981a2917dd3f5a175f3 ||e5be04a5000841a4f1 --- Comment #2 from Kurt Hindenburg --- Git commit 3e7981a2917dd3f5a175f3e5be04a5000841a4f1 by Kurt Hindenburg. Committed on 23/12/2017 at 17:39. Pushed by hindenburg into branch 'master'. Use "focused" instead of "visible" and "hidden" in notifications Patch by ahmadsamir Differential Revision: https://phabricator.kde.org/D9471 M +21 -21 desktop/konsole.notifyrc https://commits.kde.org/konsole/3e7981a2917dd3f5a175f3e5be04a5000841a4f1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388176] I cant see the layers
https://bugs.kde.org/show_bug.cgi?id=388176 Boudewijn Rempt changed: What|Removed |Added Platform|Other |MS Windows CC||b...@valdyas.org Component|Layer Stack |OpenGL Canvas Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Boudewijn Rempt --- That probably means your system is suffering from this problem: https://docs.krita.org/KritaFAQ#Krita_starts_with_a_black_or_blank_canvas_and_nothing_changes_when_you_try_to_draw.2Fshows_a_black_or_blank_screen_on_my_Windows_system_with_an_Intel_GPU *** This bug has been marked as a duplicate of bug 360601 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 360601] [INTEL] Various issues caused by buggy Intel drivers.
https://bugs.kde.org/show_bug.cgi?id=360601 Boudewijn Rempt changed: What|Removed |Added CC||lithingw...@gmail.com --- Comment #87 from Boudewijn Rempt --- *** Bug 388176 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388177] I cant see the layers
https://bugs.kde.org/show_bug.cgi?id=388177 Alvin Wong changed: What|Removed |Added CC||alvinhoc...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Alvin Wong --- *** This bug has been marked as a duplicate of bug 388176 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388176] I cant see the layers
https://bugs.kde.org/show_bug.cgi?id=388176 --- Comment #1 from Alvin Wong --- *** Bug 388177 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388177] New: I cant see the layers
https://bugs.kde.org/show_bug.cgi?id=388177 Bug ID: 388177 Summary: I cant see the layers Product: krita Version: 3.3.2 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: lithingw...@gmail.com Target Milestone: --- If I open Krita and if I make a new file, I cant see the window with the layers. I reinstalled Krita 3 times the problem is still there. ( I'm German, so sorry for the bad English.) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388176] New: I cant see the layers
https://bugs.kde.org/show_bug.cgi?id=388176 Bug ID: 388176 Summary: I cant see the layers Product: krita Version: 3.3.2 Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: lithingw...@gmail.com Target Milestone: --- If I open Krita and if I make a new file, I cant see the window with the layers. I reinstalled Krita 3 times the problem is still there. ( I'm German, so sorry for the bad English.) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 348478] Missing menu entries after closing a detached tab
https://bugs.kde.org/show_bug.cgi?id=348478 Kurt Hindenburg changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://commits.kde.org/kon ||sole/52185790cb4b18b42a9f95 ||dd1b7335e00202e1ba Status|UNCONFIRMED |RESOLVED --- Comment #1 from Kurt Hindenburg --- Git commit 52185790cb4b18b42a9f95dd1b7335e00202e1ba by Kurt Hindenburg. Committed on 23/12/2017 at 17:05. Pushed by hindenburg into branch 'master'. Fix menus after closing a detaching tab Patch by ahmadsamir Differential Revision: https://phabricator.kde.org/D9448 M +6-3src/ViewManager.cpp https://commits.kde.org/konsole/52185790cb4b18b42a9f95dd1b7335e00202e1ba -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 388175] New: core dump while opening a specific PDF document
https://bugs.kde.org/show_bug.cgi?id=388175 Bug ID: 388175 Summary: core dump while opening a specific PDF document Product: okular Version: 1.3.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: jeckfer...@gmail.com Target Milestone: --- Okular dumps core with a PDF document. It didn't crash. It keep working normally. But coredumpctl says otherwise. The system is with the latest updates as of this writing. I would send that specified PDF but how? Ask me more. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388174] valgrind with Wine quits with "Assertion 'cfsi_fits' failed"
https://bugs.kde.org/show_bug.cgi?id=388174 Konstantin Kharlamov changed: What|Removed |Added Component|callgrind |general -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388174] New: valgrind with Wine quits with "Assertion 'cfsi_fits' failed"
https://bugs.kde.org/show_bug.cgi?id=388174
Bug ID: 388174
Summary: valgrind with Wine quits with "Assertion 'cfsi_fits'
failed"
Product: valgrind
Version: 3.13.0
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: callgrind
Assignee: josef.weidendor...@gmx.de
Reporter: hi-an...@yandex.ru
Target Milestone: ---
Created attachment 109493
--> https://bugs.kde.org/attachment.cgi?id=109493&action=edit
The output of valgrind --trace-children=yes -v -v -v -d -d -d wine ./a.exe
Steps to reproduce in terms of terminal commands:
$ cat test2.cpp
#include
int main() {
puts("hello!");
}
$ x86_64-w64-mingw32-g++ test2.cpp -o a.exe -Wall -Wextra -g3 -O3
$ valgrind --trace-children=yes wine ./a.exe
==19314== Memcheck, a memory error detector
==19314== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==19314== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright
info
==19314== Command: wine ./a.exe
==19314==
==19314== Memcheck, a memory error detector
==19314== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==19314== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright
info
==19314== Command: /usr/bin/wine-preloader /usr/bin/wine ./a.exe
==19314==
preloader: Warning: failed to reserve range 0011-6800
preloader: Warning: failed to reserve range 7f00-8200
==19314== Warning: set address range perms: large range [0x8049000,
0x47669000) (noaccess)
==19314== Warning: set address range perms: large range [0x8049000,
0x47669000) (noaccess)
==19314== Warning: set address range perms: large range [0x8049000,
0x27b59000) (noaccess)
==19314== Warning: set address range perms: large range [0x8049000,
0x27b59000) (noaccess)
==19314== Warning: set address range perms: large range [0x9faf,
0xbf60) (noaccess)
==19314== Warning: set address range perms: large range [0x8049000,
0x47669000) (noaccess)
==19314== Warning: set address range perms: large range [0x8049000,
0x47669000) (noaccess)
==19314== Warning: set address range perms: large range [0xbf60,
0xdf11) (noaccess)
==19314== Warning: set address range perms: large range [0x8049000,
0x27b59000) (noaccess)
==19314== Warning: set address range perms: large range [0x8049000,
0x27b59000) (noaccess)
valgrind: m_debuginfo/debuginfo.c:551 (check_CFSI_related_invariants):
Assertion 'cfsi_fits' failed.
host stacktrace:
==19314==at 0x5803A708: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x5803A83D: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x5803A937: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x5806FDEA: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x5809D366: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x580D8ADA: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x58099856: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x58095D7D: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x58097716: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
==19314==by 0x580A884A: ??? (in /usr/lib/valgrind/memcheck-x86-linux)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable (lwpid 19314)
==19314==at 0x401A480: mmap (in /usr/lib32/ld-2.26.so)
==19314==by 0x4005F5D: _dl_map_object_from_fd (in
/usr/lib32/ld-2.26.so)
==19314==by 0x4008838: _dl_map_object (in /usr/lib32/ld-2.26.so)
==19314==by 0x40138F4: dl_open_worker (in /usr/lib32/ld-2.26.so)
==19314==by 0x4363114: _dl_catch_error (in /usr/lib32/libc-2.26.so)
==19314==by 0x40133F8: _dl_open (in /usr/lib32/ld-2.26.so)
==19314==by 0x4468C64: ??? (in /usr/lib32/libdl-2.26.so)
==19314==by 0x4363114: _dl_catch_error (in /usr/lib32/libc-2.26.so)
==19314==by 0x446936D: ??? (in /usr/lib32/libdl-2.26.so)
==19314==by 0x4468CED: dlopen (in /usr/lib32/libdl-2.26.so)
==19314==by 0x404B014: wine_init (in /usr/lib32/libwine.so.1.0)
==19314==by 0x7C000CDD: main (in /usr/bin/wine)
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
Output of running with -vvv -ddd is too big,
[Akonadi] [Bug 336581] accidental database loss causes Akonadi / KMail to silently break correct folder assignments
https://bugs.kde.org/show_bug.cgi?id=336581 Kai Maerzhaeuser changed: What|Removed |Added CC||ka...@freenet.de --- Comment #11 from Kai Maerzhaeuser --- A short comment on this, since Martin perfectly summarizes my frustration. A user's opinion, I am not a developer. Since introduction of akonadi, I experience broken database issue about 1-2 times a Year (last time some days ago) and none of the proposed solutions anywhere in posts resolves my given issues. Because I don't have the time for extensive investigations I have to delete ~/.local/share/akonadi which then totally mixes up folder associations with the described impacts on filters etc. as described above. Email is among the most critical applications for daily use and this weakness in architecture (as I learned from above) is a total mess. This is not a bug, but a totally broken architecture !!! Martin's suggestions seem already very reasonable to me, and promising. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #34 from Urs Joss --- Thanks Fabian. The patch (via archlinux ksmtp-17.12.0-2) solves the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388173] New: Plasma crash on clicking desktop icon
https://bugs.kde.org/show_bug.cgi?id=388173 Bug ID: 388173 Summary: Plasma crash on clicking desktop icon Product: plasmashell Version: 5.11.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: huanghaorui...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.11.4) Qt Version: 5.9.3 Frameworks Version: 5.41.0 Operating System: Linux 4.10.0-38-generic x86_64 Distribution: KDE neon User Edition 5.11 -- Information about the crash: - What I was doing when the application crashed: I'm clicking a desktop icon (a png file). I can't reproduce it. Maybe a duplicate of https://bugs.kde.org/show_bug.cgi?id=377748 -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8c9a5a38c0 (LWP 21764))] Thread 8 (Thread 0x7f8bccbd3700 (LWP 22397)): #0 0x7f8c93c7c70d in poll () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f8c8eb4238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8c8eb4249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8c945a36cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f8c9454be2a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8c943748f4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8c974cbd25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f8c94379709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f8c932206ba in start_thread (arg=0x7f8bccbd3700) at pthread_create.c:333 #9 0x7f8c93c883dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 7 (Thread 0x7f8be00ae700 (LWP 22126)): #0 __libc_enable_asynccancel () at ../sysdeps/unix/sysv/linux/x86_64/cancellation.S:65 #1 0x7f8c93c7c702 in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0x7f8c8eb4238c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8c8eb4249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8c945a36cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8c9454be2a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8c943748f4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8c9806b046 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f8c94379709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f8c932206ba in start_thread (arg=0x7f8be00ae700) at pthread_create.c:333 #10 0x7f8c93c883dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 6 (Thread 0x7f8c6f3a2700 (LWP 22045)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f8c99d22d04 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #2 0x7f8c99d22d49 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #3 0x7f8c932206ba in start_thread (arg=0x7f8c6f3a2700) at pthread_create.c:333 #4 0x7f8c93c883dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 5 (Thread 0x7f8c7997e700 (LWP 21986)): #0 0x7f8c8eb3f434 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8c8eb418bb in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8c8eb422bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8c8eb4249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f8c945a36cb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f8c9454be2a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f8c943748f4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f8c974cbd25 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f8c94379709 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f8c932206ba in start_thread (arg=0x7f8c7997e700) at pthread_create.c:333 #10 0x7f8c93c883dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 4 (Thread 0x7f8c7bbf2700 (LWP 21932)): #0 0x7f8c8eb41464 in g_main_context_release () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f8c8eb42346 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f8c8eb4249c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f8c945a36cb in QEventDispatcherGlib::processEvents(QFlags) () from /u
[krita] [Bug 388166] Photoshop Shear for Krita
https://bugs.kde.org/show_bug.cgi?id=388166 --- Comment #2 from reptilli...@live.com --- I'll try not to do that again. At the time, I had forgotten about the wish thing. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388169] Cropped Images Contain Meaningless Face Tags
https://bugs.kde.org/show_bug.cgi?id=388169 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Component|ImageEditor |Faces-Engine -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 359580] High CPU usage
https://bugs.kde.org/show_bug.cgi?id=359580 Jaime Torres changed: What|Removed |Added CC||jtam...@gmail.com --- Comment #9 from Jaime Torres --- One of my sessions has high cpu also, a constant 20% cpu ussage. Launching plasmashell using callgrid, I see that the problem is in Qt calling fontconfig again and again. From previous investigations, my guess is that this only happens in QtQuick and only when personal fonts are available, because last time I moved the personal fonts to the global fonts directory the high cpu was gone after plasmashell restart. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388161] selecting onion skin lightbulb makes Krita unresponsive
https://bugs.kde.org/show_bug.cgi?id=388161 --- Comment #3 from wolthera --- Alright, probably caused by this commit somehow: https://phabricator.kde.org/R37:36e9e0d5f878e163b169457f42944a0ebdfe392b#change-82il1okkk5tm I don't know the animation code enough to fix it though... -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 388161] selecting onion skin lightbulb makes Krita unresponsive
https://bugs.kde.org/show_bug.cgi?id=388161
--- Comment #2 from wolthera ---
For what it is worth, when doing cntrl+c in gdb when this issue pops up gives
the following data:
^C
Thread 1 "krita" received signal SIGINT, Interrupt.
KisNode::setDirtyDontResetAnimationCache (this=0x12eb6b90, rect=...)
at /home/wolthera/krita/src/libs/image/kis_node.cpp:611
611 {
(gdb)
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 388161] selecting onion skin lightbulb makes Krita unresponsive
https://bugs.kde.org/show_bug.cgi?id=388161 wolthera changed: What|Removed |Added Ever confirmed|0 |1 CC||griffinval...@gmail.com Status|UNCONFIRMED |CONFIRMED --- Comment #1 from wolthera --- Yeah, same here. Seems almost as if an un-exitable for loop was entered. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388170] Often in kmail the information bar shows a hanging message about synchronizing the trash folder of a specific IMAP account
https://bugs.kde.org/show_bug.cgi?id=388170 --- Comment #2 from Freek de Kruijf --- I checked the number of messages in the Trash folder on the dovecot server. The number there was 10 more than what was shown in kmail. So I decided to lower the number of days messages should be kept. This lowered the number in kmail to 2304, however nothing happened on the dovecot server. I still have the original amount 2375. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388170] Often in kmail the information bar shows a hanging message about synchronizing the trash folder of a specific IMAP account
https://bugs.kde.org/show_bug.cgi?id=388170 --- Comment #1 from Freek de Kruijf --- After the description in #1 I logged out and in again to start akonadi fresh. Before starting kontact I did a "akonadictl fsck" and "akonadictl vacuum"; both finished OK. However fsck reported a few duplicated messages in that trash folder. I decided use akonadiconsole. I selected the IMAP account with the problematic trash folder and activated Settings...->Configure Natively. Selecting tab Advanced I noticed that the field for the Trash folder was empty. Trying to configure the Trash folder of that account, which should have been there, I got nothing to choose from. I canceled the configuration action. Pressed Restart went back to Settings...->Configure Natively, and found that field for the Trash folder contained the Trash folder of the IMAP account, as it should have. Currently, a few minutes after the Restart, it shows Folder Trash being synchronized (149%). A Restart at the bottom of the console does not work. Toggling off and on does work and shows the account connected. However the configuration again shows an empty Trash folder field. Using the context menu I restarted the agent and it shows Ready and the field shows again the right Trash folder. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 388172] New: ksmtp: sending email broken, include patch from #388068 / D9476
https://bugs.kde.org/show_bug.cgi?id=388172 Bug ID: 388172 Summary: ksmtp: sending email broken, include patch from #388068 / D9476 Product: neon Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: m...@bearsh.org CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- see https://bugs.kde.org/show_bug.cgi?id=388068 https://phabricator.kde.org/D9476 -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 388160] ksmtp EHLO sends server hostname as domain parameter by default
https://bugs.kde.org/show_bug.cgi?id=388160 --- Comment #3 from kzi --- Thank you, Fabian! localhost.invalid and foo.localnet make up nice domain names, too. :) -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 388171] New: umbrello5 does not display any files using default file pattern
https://bugs.kde.org/show_bug.cgi?id=388171 Bug ID: 388171 Summary: umbrello5 does not display any files using default file pattern Product: umbrello Version: 2.24.1 (KDE Applications 17.12.1) Platform: Other OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: umbrello-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- The open file dialog does not show any file if the default file pattern is selected. To see xmi files the dedicated xmi file type needs to be selected. How to reproduce: 1. Download umbrello5 from https://download.opensuse.org/repositories/home:/rhabacker:/branches:/windows:/mingw:/win32:/KF5Apps/ (look into available noarch sub dirs for a package named 'mingw32-umbrello5-portable') und pack with 7zip 2. enter bin dir inside unpackaged folder and start umbrello5 3. Add some classes to a diagram 4. save file 5. Press File->Open and select directory of file created in step 4 What happens ? The file is not displayed in the dialog What is expected ? The file should be displayed also with the default file pattern selected -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 388171] umbrello5 does not display any files using default file pattern
https://bugs.kde.org/show_bug.cgi?id=388171 Ralf Habacker changed: What|Removed |Added Blocks||380136 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=380136 [Bug 380136] Fix KF5 issues on Windows -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 380136] Fix KF5 issues on Windows
https://bugs.kde.org/show_bug.cgi?id=380136 Ralf Habacker changed: What|Removed |Added Depends on||388171 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=388171 [Bug 388171] umbrello5 does not display any files using default file pattern -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 388160] ksmtp EHLO sends server hostname as domain parameter by default
https://bugs.kde.org/show_bug.cgi?id=388160 Fabian Vogt changed: What|Removed |Added CC||fab...@ritter-vogt.de Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #2 from Fabian Vogt --- Fixed by https://phabricator.kde.org/D9485. It simply does the exact same in ksmtp now as kmailtransport's smtp kio slave used to (it worked, so why change). The version in bugzilla does not match ksmtp as there is no ksmtp component in bugzilla (yet). FYI: Patch got added to KDE:Applications for openSUSE - I assume other distros will pick it soon as well. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388142] digikam crash when clicing on map tool
https://bugs.kde.org/show_bug.cgi?id=388142 Maik Qualmann changed: What|Removed |Added Version Fixed In||5.8.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 387996] Impossible to extract ZIP compressed with LZMA method
https://bugs.kde.org/show_bug.cgi?id=387996 --- Comment #2 from Dr. Chapatin --- Created attachment 109492 --> https://bugs.kde.org/attachment.cgi?id=109492&action=edit test archive -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Fabian Vogt changed: What|Removed |Added Latest Commit||https://commits.kde.org/ksm ||tp/5199ed07428a03f1aa340da3 ||ae99fcfa62ba2751 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED FIXED Latest Commit||https://commits.kde.org/ksm ||tp/ec2afd27c790fbde63a9c2bd ||d1f97a59fe04b18e Status|CONFIRMED |RESOLVED --- Comment #32 from Fabian Vogt --- Git commit 5199ed07428a03f1aa340da3ae99fcfa62ba2751 by Fabian Vogt. Committed on 23/12/2017 at 12:09. Pushed by fvogt into branch 'Applications/17.12'. Send the correct hostname with the HELO/EHLO command Summary: It sent the server's hostname previously, which some reject. Test Plan: Ran nc as smtp server, uses the right hostname for EHLO now. Reviewers: mlaurent, dvratil Subscribers: #kde_pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D9485 M +13 -1src/session.cpp https://commits.kde.org/ksmtp/5199ed07428a03f1aa340da3ae99fcfa62ba2751 --- Comment #33 from Fabian Vogt --- Git commit ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e by Fabian Vogt. Committed on 23/12/2017 at 12:09. Pushed by fvogt into branch 'Applications/17.12'. Fix duplicate authentication Summary: The response to EHLO triggers an authentication command, but with TLS two EHLOs are sent: For the 220 from the server and after TLS negotiation. However, sending it twice results in an unexpected "503 already authenticated" response which ends up getting parsed by the SendJob, causing confusion. By leaving the EHLO-resending to the SessionPrivate, the state can be properly tracked. Related: bug 388068 Reviewers: mlaurent, dvratil Subscribers: lbeltrame, cgiboudeaux Differential Revision: https://phabricator.kde.org/D9476 M +19 -10 src/session.cpp M +1-0src/session_p.h M +0-1src/sessionthread.cpp https://commits.kde.org/ksmtp/ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388068] With the kmail version 5.7 can no longer send mails.
https://bugs.kde.org/show_bug.cgi?id=388068 Fabian Vogt changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/ksm ||tp/ec2afd27c790fbde63a9c2bd ||d1f97a59fe04b18e --- Comment #20 from Fabian Vogt --- Git commit ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e by Fabian Vogt. Committed on 23/12/2017 at 12:09. Pushed by fvogt into branch 'Applications/17.12'. Fix duplicate authentication Summary: The response to EHLO triggers an authentication command, but with TLS two EHLOs are sent: For the 220 from the server and after TLS negotiation. However, sending it twice results in an unexpected "503 already authenticated" response which ends up getting parsed by the SendJob, causing confusion. By leaving the EHLO-resending to the SessionPrivate, the state can be properly tracked. Related: bug 387926 Reviewers: mlaurent, dvratil Subscribers: lbeltrame, cgiboudeaux Differential Revision: https://phabricator.kde.org/D9476 M +19 -10 src/session.cpp M +1-0src/session_p.h M +0-1src/sessionthread.cpp https://commits.kde.org/ksmtp/ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Fabian Vogt changed: What|Removed |Added Latest Commit||https://commits.kde.org/ksm ||tp/5199ed07428a03f1aa340da3 ||ae99fcfa62ba2751 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED FIXED Latest Commit||https://commits.kde.org/ksm ||tp/ec2afd27c790fbde63a9c2bd ||d1f97a59fe04b18e Status|CONFIRMED |RESOLVED --- Comment #32 from Fabian Vogt --- Git commit 5199ed07428a03f1aa340da3ae99fcfa62ba2751 by Fabian Vogt. Committed on 23/12/2017 at 12:09. Pushed by fvogt into branch 'Applications/17.12'. Send the correct hostname with the HELO/EHLO command Summary: It sent the server's hostname previously, which some reject. Test Plan: Ran nc as smtp server, uses the right hostname for EHLO now. Reviewers: mlaurent, dvratil Subscribers: #kde_pim Tags: #kde_pim Differential Revision: https://phabricator.kde.org/D9485 M +13 -1src/session.cpp https://commits.kde.org/ksmtp/5199ed07428a03f1aa340da3ae99fcfa62ba2751 --- Comment #33 from Fabian Vogt --- Git commit ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e by Fabian Vogt. Committed on 23/12/2017 at 12:09. Pushed by fvogt into branch 'Applications/17.12'. Fix duplicate authentication Summary: The response to EHLO triggers an authentication command, but with TLS two EHLOs are sent: For the 220 from the server and after TLS negotiation. However, sending it twice results in an unexpected "503 already authenticated" response which ends up getting parsed by the SendJob, causing confusion. By leaving the EHLO-resending to the SessionPrivate, the state can be properly tracked. Related: bug 388068 Reviewers: mlaurent, dvratil Subscribers: lbeltrame, cgiboudeaux Differential Revision: https://phabricator.kde.org/D9476 M +19 -10 src/session.cpp M +1-0src/session_p.h M +0-1src/sessionthread.cpp https://commits.kde.org/ksmtp/ec2afd27c790fbde63a9c2bdd1f97a59fe04b18e -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386354] Can change keyboard settings without authentication
https://bugs.kde.org/show_bug.cgi?id=386354 jokubas.lekevic...@gmail.com changed: What|Removed |Added Version|5.11.2 |5.11.4 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388170] New: Often in kmail the information bar shows a hanging message about synchronizing the trash folder of a specific IMAP account
https://bugs.kde.org/show_bug.cgi?id=388170 Bug ID: 388170 Summary: Often in kmail the information bar shows a hanging message about synchronizing the trash folder of a specific IMAP account Product: kmail2 Version: 5.7.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: freekdekru...@kde.nl Target Milestone: --- I have quite large IMAP account on a server with dovecot (~12000 messages) . After starting kontact/kmail and after a while the information bar at the bottom of the window shows a message indicating that the trash folder of that IMAP account is being synchronized. The progress shown is not 100%, it varies, but it does not change anymore. A click on the arrow to show more info shows only the progress bar of synchronizing the trash folder of that particular IMAP account at 100%. However it stays that way. I tried command "akonadictl fsck", which sometimes shows irregular things, but a second time, these are gone. Currently "akonadictl vacuum" hangs after showing "optimizing table CollectionTable..." Also kontact/kmail does not show new messages. It shows turning dots in front of the inbox. After quite a while I give the command "akonadictl stop", which sometimes shows a bug report, but even after installing the requested debug package, it shows a that the bug report is not usable. akonadiserver crashed with a Segmentation fault (11). Now akonadi vacuum continues but hangs in "optimizing table PartTable...". "akonadictl status" shows "stopped". The bApplication: akonadiserver (5.7.0) Qt Version: 5.9.3 Frameworks Version: 5.40.0 Operating System: Linux 4.14.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: The crash can be reproduced every time. -- Backtrace: A useful backtrace could not be generatedug report is: akonadictl vacuum still hangs. In kmail I can start akonadi again and things look normal apart from the message in the messages bar where only the filter agent hangs. After deleting some messages in the inbox of that IMAP acount I have the situation back where the message bar shows 59% progress, but clicking the arrow on that bar shows 100% progress on synchronizing the trash folder. The number of messages in the trash folder is not updated after deleting the messages in the inbox. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 388017] Callgrind produces empty log for pulseaudio
https://bugs.kde.org/show_bug.cgi?id=388017 Philippe Waroquiers changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Philippe Waroquiers --- (In reply to Konstantin Kharlamov from comment #2) > (In reply to Philippe Waroquiers from comment #1) > > Several things can be tried to get some more info. > > > > * I suppose pulseaudio will daemonize itself. > > So, you should run with --trace-children=yes > > Also, to be sure that the output goes to a known place, you should use > > --log-file=/some/abs/filename%p > >(you should use %p to have filenames containing the pid) > > > > * Try with other tools, e.g. --tool=none and memchec, and use from a shell > >the command 'vgdb v.info scheduler' > > to check what is happening > > > > * Run with -v -v -v -d -d -d --trace-syscalls=yes --trace-signals=yes > > Amazing, thanks, the `--trace-children=yes` did the trick! I guess, this bug > can be closed, not sure about the wording — "RESOLVED"? "NOTABUG"? Closing the bug now as INVALID. > > On an irrelevant note, I also tried running under valgrind and Wine a PE > binary compiled with MinGW — it resulted in valgrind quitting with these > lines: > > preloader: Warning: failed to reserve range 0011-6800 > preloader: Warning: failed to reserve range 7f00-8200 > > valgrind: m_debuginfo/debuginfo.c:551 (check_CFSI_related_invariants): > Assertion 'cfsi_fits' failed. > > …and then stacktrace follows. I'm wondering if it's something known or > should it be reported. That looks like a bug, yes. So, better to report it as a new bug, with some more info. Someone more knowledgeable about wine/windows/... might then jump on it. E.g. attach the output of running the above with -v -v -v -d -d -d (i.e. the general debugging of valgrind). Possibly other debug --trace-cfi=yes --trace-symtab ... might give some hints but these will produce a lot more info. Thanks -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388169] New: Cropped Images Contain Meaningless Face Tags
https://bugs.kde.org/show_bug.cgi?id=388169 Bug ID: 388169 Summary: Cropped Images Contain Meaningless Face Tags Product: digikam Version: 5.8.0 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal Priority: NOR Component: ImageEditor Assignee: digikam-bugs-n...@kde.org Reporter: hardy.pub...@gmail.com Target Milestone: --- If an image with multiple face tags is cropped and saved as a new image, all face regions are retained in the metadata giving meaningless face tags in the new image. Expected Behaviour == Minimum: All regions should be deleted from the metadata in the new image. Ideal: If technically possible, whole face regions within the boundaries of the new cropped image should be rescaled and retained. All other regions should be deleted from the metadata. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 387996] Impossible to extract ZIP compressed with LZMA method
https://bugs.kde.org/show_bug.cgi?id=387996 --- Comment #1 from Elvis Angelaccio --- Can you attach a test archive? -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 387995] Dolphin KIO gdrive unknown error
https://bugs.kde.org/show_bug.cgi?id=387995 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO Product|dolphin |kio-gdrive Component|general |general Version|unspecified |1.2.0 Assignee|dolphin-bugs-n...@kde.org |elvis.angelac...@kde.org --- Comment #1 from Elvis Angelaccio --- Please show the output of 'journalctl -b | grep kdeinit5' after you get the error (use pastebin if it's too large). -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 387855] Okular does not open PDF files on GDrive
https://bugs.kde.org/show_bug.cgi?id=387855 Elvis Angelaccio changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Elvis Angelaccio --- Please run 'kdeinit5' in Konsole and try again. Then copy-paste here the output of kdeinit5. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 322060] Synced swapping on double buffered nvidia GPUs cause high CPU load
https://bugs.kde.org/show_bug.cgi?id=322060 leh...@tutanota.com changed: What|Removed |Added CC|leh...@tutanota.com | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388092] Dolphin crashing on emptying the recycle bin
https://bugs.kde.org/show_bug.cgi?id=388092 Elvis Angelaccio changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Elvis Angelaccio --- *** This bug has been marked as a duplicate of bug 371507 *** -- You are receiving this mail because: You are watching all bug changes.
[phonon-backend-vlc] [Bug 371507] libvlc loads Qt4 plugin in a Qt5 application [ArchLinux]
https://bugs.kde.org/show_bug.cgi?id=371507 Elvis Angelaccio changed: What|Removed |Added CC||frontier...@gmail.com --- Comment #39 from Elvis Angelaccio --- *** Bug 388092 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
