[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file
https://bugs.kde.org/show_bug.cgi?id=398342 Alexander Semke changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #7 from Alexander Semke --- (In reply to A. Wilcox (awilfox) from comment #6) > It is not possible to "mix" endians, unfortunately, so there is no way for > us to compile LabPlot in LE mode. > > I applied the attached patch to our tree and rebuilt. The exact same stack > trace was present; only the memory addresses were different, due to ASLR. Ok. We'll have a more deeper look into this. > Attempting to pass -DENABLE_LIBORIGIN=OFF to CMake resulted in a build error: > [...] I fixed the build issue with https://phabricator.kde.org/R262:d67faf643b2e69c017c21e9d9aaa1fe2d3de6b0e . Can you please try with this fix? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 398530] New: Kmail crashes after clicking new maildir in maildir list panel
https://bugs.kde.org/show_bug.cgi?id=398530 Bug ID: 398530 Summary: Kmail crashes after clicking new maildir in maildir list panel Product: kmail2 Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mat...@ant.gliwice.pl Target Milestone: --- Application: kmail (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: Started KMail. Clicked "check new mail". KMail starter processing, with unusuall hangs in displaying current mail lists. After while crash. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc1a9701b80 (LWP 2152))] Thread 35 (Thread 0x7fc0eaffd700 (LWP 4106)): #0 0x7fc19c0d4ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fc0eaffc7e0, expected=0, futex_word=0x7fc10c004414) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 __pthread_cond_wait_common (abstime=0x7fc0eaffc880, mutex=0x7fc10c0043c0, cond=0x7fc10c0043e8) at pthread_cond_wait.c:533 #2 __pthread_cond_timedwait (cond=0x7fc10c0043e8, mutex=0x7fc10c0043c0, abstime=0x7fc0eaffc880) at pthread_cond_wait.c:667 #3 0x7fc190fa4652 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc190f7a799 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc190f7acfb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc190f735eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc19c0ce6db in start_thread (arg=0x7fc0eaffd700) at pthread_create.c:463 #8 0x7fc1a67de88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7fc03b9b8700 (LWP 2863)): #0 0x7fc19c0d49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x562c1fd69f0c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562c1fd69eb8, cond=0x562c1fd69ee0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x562c1fd69ee0, mutex=0x562c1fd69eb8) at pthread_cond_wait.c:655 #3 0x7fc190f75c95 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc190f76177 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc190f76f11 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc190f735eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc19c0ce6db in start_thread (arg=0x7fc03b9b8700) at pthread_create.c:463 #8 0x7fc1a67de88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7fc03c1b9700 (LWP 2862)): #0 0x7fc19c0d49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x562c1fd69f0c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x562c1fd69eb8, cond=0x562c1fd69ee0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x562c1fd69ee0, mutex=0x562c1fd69eb8) at pthread_cond_wait.c:655 #3 0x7fc190f75c95 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fc190f76177 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fc190f76f11 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fc190f735eb in ?? () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fc19c0ce6db in start_thread (arg=0x7fc03c1b9700) at pthread_create.c:463 #8 0x7fc1a67de88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 32 (Thread 0x7fc0bd3ee700 (LWP 2861)): #0 0x7fc19c0d49f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7fc18d83efb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x7fc18d83ef68, cond=0x7fc18d83ef90) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x7fc18d83ef90, mutex=0x7fc18d83ef68) at pthread_cond_wait.c:655 #3 0x7fc18d5485f4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7fc18d548639 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7fc19c0ce6db in start_thread (arg=0x7fc0bd3ee700) at pthread_create.c:463 #6 0x7fc1a67de88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7fc0beca5700 (LWP 2832)): #0 0x7fc1a67cd0b4 in __GI___libc_read (fd=77, buf=0x7fc0beca4810, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7fc19a4bd980 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fc19a478f27 in g_main_context_check () from /
[akregator] [Bug 398516] UI - Akregator comments section font seems to be hard coded. Font is tiny on a 4k monitor
https://bugs.kde.org/show_bug.cgi?id=398516 --- Comment #1 from Christophe Giboudeaux --- What is the "comment section" ? mind posting a screenshot ? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398528] Transparent tiff file layer above fill layer makes it render black
https://bugs.kde.org/show_bug.cgi?id=398528 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Boudewijn Rempt --- Hi, I can reproduce this with 4.1.1, however with a build from the krita/4.1 and master branches, I cannot reproduce the issue anymore, so it has been fixed since the last release. But weirdly enough, the 4.1-based nightly build still shows the issue, while the master-based nightly build doesn't show the issue anymore. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398405] Session planner copies RA/DEC to Scheduler without fractional part
https://bugs.kde.org/show_bug.cgi?id=398405 --- Comment #7 from TallFurryMan --- Read some Qt docs, and found the problem: all of our arg() and number() calls basically ignore locale. To properly support that, we can use "%L1" instead of "%1" for a float number for instance, or use toString(), which uses the current locale but is not very flexible. That also raises the problem of portable XML files, in which we should better choose the right QLocale before reading and writing. Plenty of changes everywhere, apparently. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398529] New: Kwin crash after closing app
https://bugs.kde.org/show_bug.cgi?id=398529 Bug ID: 398529 Summary: Kwin crash after closing app Product: kwin Version: 5.13.5 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: andry.n...@outlook.com Target Milestone: --- Application: kwin_x11 (5.13.5) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: - What I was doing when the application crashed: I opened pdf document with Okular (in maximized window and BorderLess), then when I close Okular, Kwin crash. Sometimes the same issue happen at the first time opening any apps (when close it), but the issue gone at the second time opening any apps (when close it). The issue appears only when I try to close it. I use Window Active Control widget within Latte-Dock panel. and I activate Window Active Control's button only when I maximazed any windows' app with BorderLess. The crash can be reproduced sometimes. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f688d8b4840 (LWP 13414))] Thread 4 (Thread 0x7f68561ff700 (LWP 13457)): #0 0x7f68862579f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x7f68897f7fb8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f68862579f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x7f68897f7f68, cond=0x7f68897f7f90) at pthread_cond_wait.c:502 #2 0x7f68862579f3 in __pthread_cond_wait (cond=0x7f68897f7f90, mutex=0x7f68897f7f68) at pthread_cond_wait.c:655 #3 0x7f6889502954 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #4 0x7f6889502999 in () at /usr/lib/x86_64-linux-gnu/libQt5Script.so.5 #5 0x7f68862516db in start_thread (arg=0x7f68561ff700) at pthread_create.c:463 #6 0x7f688d21a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f68677fe700 (LWP 13446)): #0 0x7f688d20dcf6 in __GI_ppoll (fds=0x7f6858000d28, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f688a5f37a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f688a5f4eae in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f688a59bdea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f688a3c6b8a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6884cde8b5 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7f688a3d1aab in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f68862516db in start_thread (arg=0x7f68677fe700) at pthread_create.c:463 #8 0x7f688d21a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f686e571700 (LWP 13424)): #0 0x7f688d20dcf6 in __GI_ppoll (fds=0x7f686800e878, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39 #1 0x7f688a5f37a1 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f688a5f4eae in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f688a59bdea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f688a3c6b8a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f6883bd0e45 in () at /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7f688a3d1aab in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f68862516db in start_thread (arg=0x7f686e571700) at pthread_create.c:463 #8 0x7f688d21a88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f688d8b4840 (LWP 13414)): [KCrash Handler] #6 0x7f688ccd3572 in () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #7 0x7f688ccd38e0 in () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #8 0x7f688cd2fdb3 in KWin::Workspace::activateNextClient(KWin::AbstractClient*) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #9 0x7f688ccb3a0b in KWin::Client::releaseWindow(bool) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #10 0x7f688cd1152a in KWin::Client::unmapNotifyEvent(xcb_unmap_notify_event_t*) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #11 0x7f688cd14bab in KWin::Client::windowEvent(xcb_generic_event_t*) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #12 0x7f688cd15535 in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () at /usr/lib/x86_64-linux-gnu/libkwin.so.5 #13 0x7f688a59a97f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*)
[krita] [Bug 398528] New: Transparent tiff file layer above fill layer makes it render black
https://bugs.kde.org/show_bug.cgi?id=398528 Bug ID: 398528 Summary: Transparent tiff file layer above fill layer makes it render black Product: krita Version: 4.1.1 Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Layer Stack Assignee: krita-bugs-n...@kde.org Reporter: k...@tokiop.com Target Milestone: --- Created attachment 114911 --> https://bugs.kde.org/attachment.cgi?id=114911&action=edit Simple example tiff file layer makes fill layer render black Hi ! while debugging a old 3.3 file which renders black, I came across a curious minimal example. Fill layers seem to render as black if there is a transparent tiff loaded as file layer above it. Can anyone reproduce with attached file ? - open the file, it renders a violet fill above the transparent tiff - move "File layer TIFF" above "Fill layer" - save, close and reload file - the violet fill is now rendered black - move "File layer TIFF" under "Fill layer" - save, close and reload file - the violet fill is violet again With the png file-layer, the behaviour does not seem to appear. Thanks for this great software ! -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 385289] Kmail: Crash when moving or deleting imap folder (Wayland)
https://bugs.kde.org/show_bug.cgi?id=385289 k...@palkeo.com changed: What|Removed |Added CC||k...@palkeo.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 387313] Flickering on Wayland with Kmail or Systemsettings
https://bugs.kde.org/show_bug.cgi?id=387313 k...@palkeo.com changed: What|Removed |Added CC||k...@palkeo.com -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 373590] Amarok KF5 - Play/Pause global hotkey does not exist.
https://bugs.kde.org/show_bug.cgi?id=373590 k...@palkeo.com changed: What|Removed |Added CC||k...@palkeo.com --- Comment #4 from k...@palkeo.com --- Is it still the case? I'm not able to make a global shortcut for Play/Pause (the global column for that button doesn't exist in the configuration window). It works great for the other functions. Just Play/Pause isn't supported. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398527] New: Error on showing network/samba overview
https://bugs.kde.org/show_bug.cgi?id=398527 Bug ID: 398527 Summary: Error on showing network/samba overview Product: dolphin Version: 17.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: furzhim...@live.de CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 114910 --> https://bugs.kde.org/attachment.cgi?id=114910&action=edit tcpdump Interner Fehler Bitte senden Sie einen ausführlichen Problembericht an http://bugs.kde.org libsmbclient meldet einen Fehler ohne klare Zuordnung. Es könnte ein Netzwerkproblem vorliegen oder auch eines mit dem Client-Programm selbst. Wenn Sie uns bei der Fehleranalyse helfen möchten, erstellen Sie bitte einen tcpdump der Netzwerk-Schnittstelle, während Sie eine Verbindung aufzunehmen versuchen. (Beachten Sie jedoch, dass die Daten private Informationen enthalten könnten. Sie sollten sie also nicht öffentlich machen, sondern nur auf Anfrage an die Entwickler schicken.) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395580] Add an additional "Documentation" category to the Application menu
https://bugs.kde.org/show_bug.cgi?id=395580 Yuri Chornoivan changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #3 from Yuri Chornoivan --- The problem can be solved on the distribution level: https://bugs.mageia.org/show_bug.cgi?id=19532#c5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398479] DigiKam crashing at startup Thread 2 Crashed:: Digikam::ScanController
https://bugs.kde.org/show_bug.cgi?id=398479 --- Comment #10 from Maik Qualmann --- I can not reproduce the problem with my D5300 RAW files either. Neither with my native Linux version (Libraw-0.19) nor with the Windows version in VirtualBox. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398479] DigiKam crashing at startup Thread 2 Crashed:: Digikam::ScanController
https://bugs.kde.org/show_bug.cgi?id=398479 --- Comment #9 from caulier.gil...@gmail.com --- As libraw source code is integrated as well in digiKam source code as 3rdparty component, I recommend to report this dysfunction to Libraw project as UPSTREAM. Don't forget to provide a test RAW file to reproduce the crash using libraw command line tool. You can use the github page for the report : https://github.com/LibRaw/LibRaw/issues The libraw version integrated especially in digiKam PKG bundle 6.0.0 is the last stable 0.19.0 Thanks in advance Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 390488] Icons look fuzzy in info panel after I increase display scale
https://bugs.kde.org/show_bug.cgi?id=390488 Nate Graham changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[kopete] [Bug 398526] New: Crash when move contact to other metacontact
https://bugs.kde.org/show_bug.cgi?id=398526 Bug ID: 398526 Summary: Crash when move contact to other metacontact Product: kopete Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kopete-bugs-n...@kde.org Reporter: tonal.proms...@gmail.com Target Milestone: --- Application: kopete (1.13.0) Qt Version: 5.11.1 Frameworks Version: 5.50.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: KDE neon User Edition 5.13 -- Information about the crash: Crash Kopete when move contact to other metacontact. A open context menu from metacontact with 2 connected contacts. Selectet one and click to "move to other metacontact" The crash can be reproduced every time. -- Backtrace: Application: Kopete (kopete), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f63438d9cc0 (LWP 28252))] Thread 10 (Thread 0x7f62e35df700 (LWP 6458)): #0 0x7f633887c450 in __pthread_mutex_unlock_full (mutex=0x55e846c06f50, decr=1) at pthread_mutex_unlock.c:180 #1 0x7f633080458e in pa_mutex_unlock () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #2 0x7f633626e443 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f633625fe10 in pa_mainloop_poll () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f63362604a0 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f6336260530 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f633626e399 in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f63308052a8 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-11.1.so #8 0x7f63388786db in start_thread (arg=0x7f62e35df700) at pthread_create.c:463 #9 0x7f633e22f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f62f6252700 (LWP 6456)): #0 0x7f633692ad14 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f63368e5556 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f633eb62a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f633eb06dea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f633e931b8a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f62fdf29440 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/kopete_jabber.so #6 0x7f633e93caab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f63388786db in start_thread (arg=0x7f62f6252700) at pthread_create.c:463 #8 0x7f633e22f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7f62f6a53700 (LWP 6455)): #0 0x7f633eb62788 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f63368e4998 in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f63368e536b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f63368e554c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f633eb62a9b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f633eb06dea in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f62fd87f621 in QCA::SyncThread::run() () from /usr/lib/x86_64-linux-gnu/libqca-qt5.so.2 #7 0x7f633e93caab in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f63388786db in start_thread (arg=0x7f62f6a53700) at pthread_create.c:463 #9 0x7f633e22f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f630dc63700 (LWP 28273)): #0 0x7f633887e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e844ca6c78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e844ca6c28, cond=0x55e844ca6c50) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x55e844ca6c50, mutex=0x55e844ca6c28) at pthread_cond_wait.c:655 #3 0x7f63138ccd5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #4 0x7f63138ccbd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so #5 0x7f63388786db in start_thread (arg=0x7f630dc63700) at pthread_create.c:463 #6 0x7f633e22f88f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f630e464700 (LWP 28272)): #0 0x7f633887e9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55e844ca6b10) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55e844ca6ac0, cond=0x55e844ca6ae8) at pthread_cond_wait.c:502 #
[klipper] [Bug 378247] Applet doesn't close after selecting a clipboad entry with enter
https://bugs.kde.org/show_bug.cgi?id=378247 Sudhir Khanger changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||sud...@sudhirkhanger.com Version|5.9.4 |5.13.4 Ever confirmed|0 |1 --- Comment #1 from Sudhir Khanger --- This is a huge usability issue. The behavior of the clipboard manager is not consistent post-selection between mouse-click and enter key. If I press mouse-click on an item, it is selected and the widget is closed. If I press enter key then the item is selected and nothing is done to the widget. Now I first have to Esc to reach the un-filtered clipboard manager and then press Esc again. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 357667] ‘Previous tab’ only switches between last two used tabs
https://bugs.kde.org/show_bug.cgi?id=357667 Simon Depiets changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #8 from Simon Depiets --- You can comment the change review here, which should offer the flexibility for everyone https://phabricator.kde.org/D15444 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398525] New: kate: Add option to change default position/order for new document: LAST | FIRST
https://bugs.kde.org/show_bug.cgi?id=398525 Bug ID: 398525 Summary: kate: Add option to change default position/order for new document: LAST | FIRST Product: kate Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: moont...@139.com Target Milestone: --- Currently, if I opened a new document, kate will put the document at the first position of document tabs. I'd like to put it at the last position -- append to the document tabs, like many other text editors does. It would be nice if I can change the position for new document. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398479] DigiKam crashing at startup Thread 2 Crashed:: Digikam::ScanController
https://bugs.kde.org/show_bug.cgi?id=398479 caulier.gil...@gmail.com changed: What|Removed |Added Component|Bundle-MacOS|FilesIO-RAW -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 398524] New: NetworkManager is unable to get secrets after NetworkManager.service restart
https://bugs.kde.org/show_bug.cgi?id=398524 Bug ID: 398524 Summary: NetworkManager is unable to get secrets after NetworkManager.service restart Product: plasma-nm Version: 5.13.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: przemyslawada...@gmail.com Target Milestone: --- NetworkManager is not able to connect to password protected network after the NetworkManager.service is restarted (`service NetworkManager restart` or restart on failure). Here is how it looks from the point of view of the user. https://youtu.be/FlJIuNFkiYY - there is no prompt to unlock kdewallet either. Workaround: go to background services and restart "Plasma Networkmanagement module" - https://imgur.com/lbq5n8f relevant `journalctl -u NetworkManager.service` log: ``` Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8241] device (wlp3s0): Activation: starting connection 'Modem' () Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8242] audit: op="connection-activate" uuid="" name="Modem" pid=2650 uid=1000 result="success" Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8243] device (wlp3s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8246] manager: NetworkManager state is now CONNECTING Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8286] device (wlp3s0): set-hw-addr: reset MAC address to XX:XX:XX:XX:XX:XX (preserve) Sep 12 03:53:18 localhost.localdomain dhclient[25531]: receive_packet failed on wlp3s0: Network is down Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8335] device (wlp3s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8340] device (wlp3s0): Activation: (wifi) access point 'Modem' has security, but secrets are required. Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8341] device (wlp3s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8342] sup-iface[0x563e4b5e18d0,wlp3s0]: wps: type pbc start... Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8350] device (wlp3s0): No agents were available for this request. Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8828] device (wlp3s0): supplicant interface state: inactive -> disconnected Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8841] device (wlp3s0): supplicant interface state: disconnected -> inactive Sep 12 03:53:18 localhost.localdomain NetworkManager[5157]: [1536717198.8891] device (wlp3s0): supplicant interface state: inactive -> scanning Sep 12 03:53:49 localhost.localdomain NetworkManager[5157]: [1536717229.3755] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Sep 12 03:53:49 localhost.localdomain dhclient[25531]: receive_packet failed on wlp3s0: Network is down Sep 12 03:53:49 localhost.localdomain NetworkManager[5157]: [1536717229.3759] manager: NetworkManager state is now DISCONNECTED Sep 12 03:53:49 localhost.localdomain NetworkManager[5157]: [1536717229.3763] device (wlp3s0): Activation: failed for connection 'Modem' Sep 12 03:53:49 localhost.localdomain NetworkManager[5157]: [1536717229.3765] device (wlp3s0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') Sep 12 03:53:49 localhost.localdomain NetworkManager[5157]: [1536717229.3871] device (wlp3s0): set-hw-addr: set MAC address to XX:XX:XX:XX:XX:XX (scanning) Sep 12 03:53:49 localhost.localdomain NetworkManager[5157]: [1536717229.4306] device (wlp3s0): supplicant interface state: scanning -> disconnected Sep 12 03:53:49 localhost.localdomain NetworkManager[5157]: [1536717229.4383] device (wlp3s0): supplicant interface state: disconnected -> inactive ``` Tested on openSUSE Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398523] New: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4 0x0 0x0 0x89
https://bugs.kde.org/show_bug.cgi?id=398523 Bug ID: 398523 Summary: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4 0x0 0x0 0x89 Product: valgrind Version: 3.13.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: vex Assignee: jsew...@acm.org Reporter: bot...@gmx.de Target Milestone: --- vex amd64->IR: unhandled instruction bytes: 0x8F 0xEA 0x78 0x10 0xD0 0x8 0x4 0x0 0x0 0x89 vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0 vex amd64->IR: VEX=0 VEX.L=0 VEX.n=0x0 ESC=NONE vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0 ==24963== valgrind: Unrecognised instruction at address 0x4016c79. ==24963==[...] -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off
https://bugs.kde.org/show_bug.cgi?id=389585 --- Comment #44 from Nate Graham --- Awesome. Now we're down to two issues: - Fix High DPI - Fix individual KCMs that provide incorrect sizeHints. For this we should probably un-dupe any bugs for individual KCMs that still have a problem at 1x with current git master. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398472] No Pen Pressure
https://bugs.kde.org/show_bug.cgi?id=398472 cademedea...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from cademedea...@gmail.com --- Getting an older version of Wacom drivers fixed the issue, thanks! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcmutils] [Bug 389585] Window is too small when KCMs are opened standalone (e.g. using `kcmshell5), and contents get cut off
https://bugs.kde.org/show_bug.cgi?id=389585 --- Comment #43 from Valeriy Malov --- Git commit cc4ecfdcd48a52a67f60eb69ed69e91ca42ee405 by Valeriy Malov. Committed on 12/09/2018 at 02:20. Pushed by valeriymalov into branch 'master'. Manually resize KCMUtilDialog to sizeHint() Summary: Workaround for https://bugreports.qt.io/browse/QTBUG-3459 Currently adjustSize() is limited to 2/3 of the screen size for windows This adds unnecessary scrollbars on dialogs that would otherwise fit the screen Manually resize the window after adjustSize() happens to avoid this limitation Test Plan: Tested on a 1366x768 laptop, with this patch networkmanagement window opens in full screen height (respecting the panel) Reviewers: #frameworks, ngraham Reviewed By: ngraham Subscribers: davidedmundson, acrouthamel, kde-frameworks-devel Tags: #frameworks Differential Revision: https://phabricator.kde.org/D15406 M +13 -2src/kcmultidialog.cpp https://commits.kde.org/kcmutils/cc4ecfdcd48a52a67f60eb69ed69e91ca42ee405 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398522] New: Network monitor sometimes freezes
https://bugs.kde.org/show_bug.cgi?id=398522 Bug ID: 398522 Summary: Network monitor sometimes freezes Product: plasmashell Version: 5.12.6 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: System Monitor Assignee: notm...@gmail.com Reporter: kdeb...@cneufeld.ca Target Milestone: 1.0 When I have multiple network interfaces, sometimes the display for one interface freezes while the other continues to run. It can be restored by going into the settings and turning off then on again one of the interfaces, but it is annoying, and happens frequently (several times a day for me). It seems only the ppp0 interface is freezing for me, the other interface, into my internal network on enp8s0, always runs normally. It's not caused by my network interface being momentarily dropped, I've checked the logs, and the pppd is up and stable for many days at a time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398509] Request for Outline Tool
https://bugs.kde.org/show_bug.cgi?id=398509 --- Comment #3 from Kenneth Evans --- No, it's really a different thing. I saw it in a webinar by an inker for Marvel comics. For my example the mask might work, but for more elaborate inking it won't. With this tool you are drawing all the time, not doing UI things, which keeps your rhythm. Essentially you just need a pen and this fill tool. You probably have to see it to understand. The webimar is at https://youtu.be/adCeHwgIQi0. I will attach a screenshot from it. Again, it shouldn't be hard to do. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398521] New: Animation will not render
https://bugs.kde.org/show_bug.cgi?id=398521 Bug ID: 398521 Summary: Animation will not render Product: krita Version: 4.1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: bebobibo...@gmail.com Target Milestone: --- Created attachment 114909 --> https://bugs.kde.org/attachment.cgi?id=114909&action=edit log_encode.log Unfortunately every time i try to render my animation, it will not render. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398509] Request for Outline Tool
https://bugs.kde.org/show_bug.cgi?id=398509 --- Comment #2 from Kenneth Evans --- Created attachment 114908 --> https://bugs.kde.org/attachment.cgi?id=114908&action=edit Professional inking -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398520] New: KDE Discover crashes on launch
https://bugs.kde.org/show_bug.cgi?id=398520 Bug ID: 398520 Summary: KDE Discover crashes on launch Product: Discover Version: 5.13.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: aleix...@kde.org Reporter: david.landr...@gmx.com Target Milestone: --- Application: plasma-discover (5.13.4) Qt Version: 5.11.1 Frameworks Version: 5.49.0 Operating System: Linux 4.18.6-1-default x86_64 Distribution (Platform): openSUSE RPMs -- Information about the crash: - What I was doing when the application crashed: Every time I start the application it shows a window for a second with garbage in it, and then it crashes. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f1c4a767800 (LWP 6371))] Thread 12 (Thread 0x7f1c13624700 (LWP 6400)): #0 0x7f1c4f029d34 in read () at /lib64/libc.so.6 #1 0x7f1c4ca5d6f0 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f1c4ca18cdf in g_main_context_check () at /usr/lib64/libglib-2.0.so.0 #3 0x7f1c4ca191b0 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7f1c4ca1932c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7f1c4f7530bb in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f1c0b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f1c4f70009b in QEventLoop::exec(QFlags) (this=0x7f1c13623da0, flags=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f1c4f54ee96 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f1c4f558a67 in QThreadPrivate::start(void*) (arg=0x55bb145805f0) at thread/qthread_unix.cpp:367 #9 0x7f1c4dce0554 in start_thread () at /lib64/libpthread.so.0 #10 0x7f1c4f038ccf in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7f1c13fff700 (LWP 6392)): #0 0x7f1c4dce68c8 in pthread_cond_timedwait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f1c4f5590fc in QWaitConditionPrivate::wait_relative(unsigned long) (time=3, this=0x7f1c0c0059d0) at thread/qwaitcondition_unix.cpp:133 #2 0x7f1c4f5590fc in QWaitConditionPrivate::wait(unsigned long) (time=3, this=0x7f1c0c0059d0) at thread/qwaitcondition_unix.cpp:141 #3 0x7f1c4f5590fc in QWaitCondition::wait(QMutex*, unsigned long) (this=, mutex=0x7f1c0c005510, time=3) at thread/qwaitcondition_unix.cpp:215 #4 0x7f1c4f550f62 in QThreadPoolThread::run() (this=0x7f1c0c005780) at ../../include/QtCore/../../src/corelib/thread/qmutex.h:240 #5 0x7f1c4f558a67 in QThreadPrivate::start(void*) (arg=0x7f1c0c005780) at thread/qthread_unix.cpp:367 #6 0x7f1c4dce0554 in start_thread () at /lib64/libpthread.so.0 #7 0x7f1c4f038ccf in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7f1c22315700 (LWP 6385)): #0 0x7f1c4f033739 in syscall () at /lib64/libc.so.6 #1 0x7f1c4f54dad4 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:105 #2 0x7f1c4f54dad4 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 0x7f1c4f54dad4 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:221 #4 0x7f1c4f54dad4 in futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) (timeout=-1, n=, u=...) at thread/qsemaphore.cpp:264 #5 0x7f1c4f54dad4 in QSemaphore::acquire(int) (this=0x7f1c4e7c72e0, n=) at thread/qsemaphore.cpp:328 #6 0x7f1c4e708c44 in () at /usr/lib64/libQt5Network.so.5 #7 0x7f1c4f558a67 in QThreadPrivate::start(void*) (arg=0x7f1c4e7c72c0) at thread/qthread_unix.cpp:367 #8 0x7f1c4dce0554 in start_thread () at /lib64/libpthread.so.0 #9 0x7f1c4f038ccf in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7f1c22b16700 (LWP 6384)): #0 0x7f1c4f033739 in syscall () at /lib64/libc.so.6 #1 0x7f1c4f54dad4 in QtLinuxFutex::_q_futex(int*, int, int, unsigned long long, int*, int) (val3=0, addr2=0x0, val2=0, val=, op=0, addr=) at thread/qfutex_p.h:105 #2 0x7f1c4f54dad4 in QtLinuxFutex::futexWait >(QBasicAtomicInteger&, QBasicAtomicInteger::Type) (expectedValue=, futex=...) at thread/qfutex_p.h:107 #3 0x7f1c4f54dad4 in futexSemaphoreTryAcquire_loop(QBasicAtomicInteger&, unsigned long long, unsigned long long, int) (timeout=-1, nn=8589934593, curValue=, u=...) at thread/qsemaphore.cpp:221 #4 0x7f1c4f54dad4 in futexSemaphoreTryAcquire(QBasicAtomicInteger&, int, int) (timeout=-1, n=n@entry=1, u=...) at thread/qsemaphore.cpp:264 #5 0x7f1c4f54dad4 in QSemap
[Discover] [Bug 398464] Discover crashes when I try to launch it
https://bugs.kde.org/show_bug.cgi?id=398464 --- Comment #2 from katas...@gmail.com --- Created attachment 114907 --> https://bugs.kde.org/attachment.cgi?id=114907&action=edit New crash information added by DrKonqi plasma-discover (5.13.5) using Qt 5.11.1 - What I was doing when the application crashed: Just logged in and started browsing web using firefox. -- Backtrace (Reduced): #6 0x7f83c7e16428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f83c7e1802a in __GI_abort () at abort.c:89 [...] #9 0x7f83c7e5f9dc in malloc_printerr (ar_ptr=0x7f83c81a5b20 , ptr=0x2512460, str=0x7f83c7f6ec75 "corrupted size vs. prev_size", action=) at malloc.c:5006 #10 malloc_consolidate (av=av@entry=0x7f83c81a5b20 ) at malloc.c:4183 #11 0x7f83c7e62cde in _int_malloc (av=av@entry=0x7f83c81a5b20 , bytes=bytes@entry=4096) at malloc.c:3450 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398464] Discover crashes when I try to launch it
https://bugs.kde.org/show_bug.cgi?id=398464 katas...@gmail.com changed: What|Removed |Added CC||katas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398409] KMyMoney does not prompt for password when connecting to database
https://bugs.kde.org/show_bug.cgi?id=398409 --- Comment #12 from Eleazar --- After I reinstalled it using the KDE_INSTALL_PLUGINDIR tweak I opened KMM with -n, logged in to my DB backend. Closed KMM and reopened it and it prompted me for a Password. So I am guessing that it probably worked without the patch. I will use the tweak going forward to make sure it works correctly. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 398409] KMyMoney does not prompt for password when connecting to database
https://bugs.kde.org/show_bug.cgi?id=398409 --- Comment #11 from Eleazar --- They are in the same location /usr/lib/x86_64-linux-gnu/qt5/plugins/kcm_sddm.so /usr/lib/x86_64-linux-gnu/qt5/plugins/kmymoney/sqlstorage.so /usr/lib/x86_64-linux-gnu/plugins/kmymoney/sqlstorage.so I will uninstall and reinstall with the KDE_INSTALL_PLUGINDIR tweak and report back. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398469] Bad font rendering when display scaling factor is 1.2
https://bugs.kde.org/show_bug.cgi?id=398469 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- Here's the deal: The first attempt at fixing this upstream (https://bugreports.qt.io/browse/QTBUG-67007) failed and made the problem worse. We now have two options: - Fix it upstream correctly (tracked by https://bugreports.qt.io/browse/QTBUG-70481) - Work around it in KDE-land by using QtRendering instead of NativeRendering. This happens automatically for UIs that use QQC2 due to our theming. I suspect the issue is QQC1 controls here. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #5 from Stas Sergeev --- Think of the following use-case. Consider a very silly shm IPC that uses just one large struct with many input and output fields. Client fills in the output fields and copies the entire struct to the shm buffer. Server reads it, fills in the input fields and puts it back to shm. Client reads the struct back with all fields now properly initialized. valgrind in this scenario would still think some fields are uninitialized because it can't understand that server have already replaced the entire content in this buffer. This is what my test-case is trying to demonstrate. It doesn't matter whether the server is in the same process or another, as valgrind will behave the same way in both cases. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-sonnet] [Bug 398247] Spellchecking KCM should give more info on what "backend" is missing
https://bugs.kde.org/show_bug.cgi?id=398247 --- Comment #3 from Nate Graham --- +1, sounds like that may be the nudge they need. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 398519] New: konkeror crash report on kubuntu
https://bugs.kde.org/show_bug.cgi?id=398519 Bug ID: 398519 Summary: konkeror crash report on kubuntu Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: spr...@gmail.com Target Milestone: --- Application: kdeinit5 (5.0.97) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-34-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: just restarted the OS after Update and after I log in I encounter this error. -- Backtrace: Application: Konqueror (kdeinit5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fba72d2ce40 (LWP 7099))] Thread 21 (Thread 0x7fb9c7fff700 (LWP 7451)): #0 0x7fba6f1d59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558c89972a5c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fba6f1d59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558c89972a08, cond=0x558c89972a30) at pthread_cond_wait.c:502 #2 0x7fba6f1d59f3 in __pthread_cond_wait (cond=0x558c89972a30, mutex=0x558c89972a08) at pthread_cond_wait.c:655 #3 0x7fba35f6fc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fba35f70177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fba35f70f11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fba35f6d5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fba6f1cf6db in start_thread (arg=0x7fb9c7fff700) at pthread_create.c:463 #8 0x7fba70da188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 20 (Thread 0x7fb9f4ff9700 (LWP 7414)): #0 0x7fba6f1d5ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fb9f4ff8be0, expected=0, futex_word=0x7fba1c003410) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fba6f1d5ed9 in __pthread_cond_wait_common (abstime=0x7fb9f4ff8c80, mutex=0x7fba1c0033c0, cond=0x7fba1c0033e8) at pthread_cond_wait.c:533 #2 0x7fba6f1d5ed9 in __pthread_cond_timedwait (cond=0x7fba1c0033e8, mutex=0x7fba1c0033c0, abstime=0x7fb9f4ff8c80) at pthread_cond_wait.c:667 #3 0x7fba35f9e652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fba35f74799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fba35f74cfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fba35f6d5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fba6f1cf6db in start_thread (arg=0x7fb9f4ff9700) at pthread_create.c:463 #8 0x7fba70da188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7fb9f57fa700 (LWP 7413)): #0 0x7fba6f1d5ed9 in futex_reltimed_wait_cancelable (private=, reltime=0x7fb9f57f9be0, expected=0, futex_word=0x7fba1c003414) at ../sysdeps/unix/sysv/linux/futex-internal.h:142 #1 0x7fba6f1d5ed9 in __pthread_cond_wait_common (abstime=0x7fb9f57f9c80, mutex=0x7fba1c0033c0, cond=0x7fba1c0033e8) at pthread_cond_wait.c:533 #2 0x7fba6f1d5ed9 in __pthread_cond_timedwait (cond=0x7fba1c0033e8, mutex=0x7fba1c0033c0, abstime=0x7fb9f57f9c80) at pthread_cond_wait.c:667 #3 0x7fba35f9e652 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fba35f74799 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fba35f74cfb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fba35f6d5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fba6f1cf6db in start_thread (arg=0x7fb9f57fa700) at pthread_create.c:463 #8 0x7fba70da188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fb9f5ffb700 (LWP 7412)): #0 0x7fba6f1d59f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x558c89972a5c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7fba6f1d59f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x558c89972a08, cond=0x558c89972a30) at pthread_cond_wait.c:502 #2 0x7fba6f1d59f3 in __pthread_cond_wait (cond=0x558c89972a30, mutex=0x558c89972a08) at pthread_cond_wait.c:655 #3 0x7fba35f6fc95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7fba35f70177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7fba35f70f11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7fba35f6d5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7fba6f1cf6db in start_thread (arg=0x7fb9f5ffb700) at pthread_create.c:463 #8 0x7fba70da188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fb9f67fc70
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #4 from Stas Sergeev --- Created attachment 114906 --> https://bugs.kde.org/attachment.cgi?id=114906&action=edit 2 processes and VALGRIND_MAKE_MEM_DEFINED (In reply to Philippe Waroquiers from comment #3) > It is not very clear to me what is the reason > to map twice the same file. Mapping file twice may not be needed, but mapping shared memory twice (which is what my test-case does) allows you to create the mem aliases with different access rights. Consider writing the JIT. I am sure you, as a valgrind developer, write JIT every day actually. :) To trap self-modified code, you would execute the JITted code in PROT_EXEC window (no PROT_WRITE), and the JIT itself will access it via PROT_READ|PROT_WRITE window (very rough picture, it functions differently of course, but multiple windows with different perms are needed). But I would suggest to forget this exotic case and assume I use 2 processes as my second test-case does. This is because I simply don't see any difference. If you explain me why 2 processes+shmem are safe, I guess I'll deal with the rest on my own. Since valgrind doesn't know how the actions on shmem in one process affects another, it just exactly the same way doesn't know how writes within a single process can affect another mem window in the same process. > At my work, we are using shared memory between > several processes. We just declare the shared memory > as initialised just after mmap. See my next test-case where I did exactly that. I don't think it was needed, as AFAIK mmap()ed memory is always zeroed and valgrind knows this already, but I did that to follow your suggestion. > There is no concept of 'undefined error' and 'undefined warning', > and introducing this distinction seems not too desirable > (e.g. impact on suppression files, etc). Then you should at least document the possible sources of false-positives, including this one. I spent many hours trying to understand what valgrind is up to. A very long route was passed to track things back to the shared memory use (--track-origins just points to the stack allocation that didn't give me any clue). If that would have been documented, I would immediately understand that I hit exactly that case. > or disable error reporting for the mmap-ed address > range using > VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE Thanks. If nothing else, I can do that. But since I don't want to deal with valgrind instrumentation headers, I can as well add an extra initializers just to silence down the errors. So basically I _will_ find the ways to silence down the errors, but getting things improved (or at least documented) on valgrind side would be a good result after my many-hours research of those false-positives. :) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398518] New: Dolphin crashes whenever
https://bugs.kde.org/show_bug.cgi?id=398518 Bug ID: 398518 Summary: Dolphin crashes whenever Product: dolphin Version: 16.08.3 Platform: Debian stable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: ninja53...@hotmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Application: dolphin (16.08.3) Qt Version: 5.7.1 Frameworks Version: 5.28.0 Operating System: Linux 4.9.0-8-amd64 x86_64 Distribution: Debian GNU/Linux 9.5 (stretch) -- Information about the crash: - What I was doing when the application crashed: I was on the web with Konqueror, at http://www.nyan.cat/cats/original.gif, and I decided that what I wanted was a copy of that flying pop-tart gif. So, I opened up Dolphin, and dragged Nyan Cat into my pictures folder. I then get a notification that Dolphin crashed, and then the Dolphin window disappears. - Custom settings of the application: I have bash running in a terminal at the bottom of Dolphin. The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f048e574e00 (LWP 4087))] Thread 4 (Thread 0x7f046fb28700 (LWP 4091)): #0 0x7f048df8867d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f0482e159f6 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0482e15b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0488cbb06b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f0488c649ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0488a920f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0488a96da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0485197494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x7f048df91acf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7f04770ae700 (LWP 4090)): #0 0x7f0488a8df09 in QMutex::lock() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f0488cba7df in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f0482e14edd in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0482e1591b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0482e15b0c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0488cbb06b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f0488c649ca in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f0488a920f3 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f048e6626d5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f0488a96da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f0485197494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f048df91acf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7f04785b0700 (LWP 4089)): #0 0x7f048df8867d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f0482551150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f0482552ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f047a2d4b69 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f0488a96da8 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f0485197494 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7f048df91acf in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 1 (Thread 0x7f048e574e00 (LWP 4087)): [KCrash Handler] #6 0x7f0489f69e26 in KUrlMimeData::urlsFromMimeData(QMimeData const*, KUrlMimeData::DecodeOptions, QMap*) () from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5 #7 0x7f048c81f013 in KIO::drop(QDropEvent const*, QUrl const&, QFlags) () from /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5 #8 0x7f048dc48255 in DragAndDropHelper::dropUrls(QUrl const&, QDropEvent*, QWidget*) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #9 0x7f048dc3894e in DolphinView::dropUrls(QUrl const&, QDropEvent*) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #10 0x7f048dc406cd in DolphinView::slotItemDropEvent(int, QGraphicsSceneDragDropEvent*) () from /usr/lib/x86_64-linux-gnu/libdolphinprivate.so.5 #11 0x7f0488c9295e in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f048dc63dea in KItemListController::itemDropEvent(int, QGraphicsSceneDragDropEvent*) ()
[KBibTeX] [Bug 398136] kbibtex crashes when editing element
https://bugs.kde.org/show_bug.cgi?id=398136 --- Comment #3 from Cor Blom --- After applying the patch kbibtex works fine and does not crash. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file
https://bugs.kde.org/show_bug.cgi?id=398342 --- Comment #6 from A. Wilcox (awilfox) --- It is not possible to "mix" endians, unfortunately, so there is no way for us to compile LabPlot in LE mode. I applied the attached patch to our tree and rebuilt. The exact same stack trace was present; only the memory addresses were different, due to ASLR. Attempting to pass -DENABLE_LIBORIGIN=OFF to CMake resulted in a build error: In file included from /usr/src/packages/user/labplot/src/labplot-2.5.0/src/backend/datasources/projects/OriginProjectParser.h:34:0, from /usr/src/packages/user/labplot/src/labplot-2.5.0/src/kdefrontend/MainWin.cpp:40: /usr/src/packages/user/labplot/src/labplot-2.5.0/liborigin/OriginFile.h:34:30: fatal error: liborigin/config.h: No such file or directory #include "liborigin/config.h" ^ compilation terminated. make[2]: *** [src/CMakeFiles/labplot2lib.dir/build.make:333: src/CMakeFiles/labplot2lib.dir/kdefrontend/MainWin.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs In file included from /usr/src/packages/user/labplot/src/labplot-2.5.0/src/backend/datasources/projects/OriginProjectParser.h:34:0, from /usr/src/packages/user/labplot/src/labplot-2.5.0/src/kdefrontend/datasources/ImportProjectDialog.cpp:33: /usr/src/packages/user/labplot/src/labplot-2.5.0/liborigin/OriginFile.h:34:30: fatal error: liborigin/config.h: No such file or directory #include "liborigin/config.h" ^ compilation terminated. make[2]: *** [src/CMakeFiles/labplot2lib.dir/build.make:541: src/CMakeFiles/labplot2lib.dir/kdefrontend/datasources/ImportProjectDialog.cpp.o] Error 1 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 398445] uninitialized memory false reports on shared memory
https://bugs.kde.org/show_bug.cgi?id=398445 --- Comment #3 from Philippe Waroquiers --- (In reply to Stas Sergeev from comment #2) > Created attachment 114889 [details] > 2-process test-case > > Hi, thanks for your reply. > Here is the test-case that does the same > thing but with 2 processes scheme. > Same valgrind error. > While the first test-case represents my real > program more, I really see no difference. For valgrind, there is no way a first valgrind process can track what another valgrind process does to the shared memory. In one single process, I think all would work ok if the memory/file would be mapped only once. It is not very clear to me what is the reason to map twice the same file. At my work, we are using shared memory between several processes. We just declare the shared memory as initialised just after mmap. This avoids false positive (and of course, introduces the risk of a false negative). > > As for the difficulty of fixing this - yes, > I perfectly understand it. While I can think > of some ugly work-arounds (like, for example, > checking if the values have changed, and consider > them initialized in that case), nothing good can > probably be done. How about downgrading the error > to warning if it comes from the shared mem? There is no concept of 'undefined error' and 'undefined warning', and introducing this distinction seems not too desirable (e.g. impact on suppression files, etc). So, if you really have to keep the multiple mmap in a single process, the best way to avoid false positive is to declare the memory as initialised after mmap using VALGRIND_MAKE_MEM_DEFINED or disable error reporting for the mmap-ed address range using VALGRIND_DISABLE_ADDR_ERROR_REPORTING_IN_RANGE -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 397611] [ERR-5]: Format de date non pris en charge importation boobank
https://bugs.kde.org/show_bug.cgi?id=397611 Stephane MANKOWSKI changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED Latest Commit||https://commits.kde.org/skr ||ooge/c67397c75822a8d09f66db ||a1c80491a1b51f4de1 --- Comment #11 from Stephane MANKOWSKI --- Git commit c67397c75822a8d09f66dba1c80491a1b51f4de1 by Stephane MANKOWSKI. Committed on 11/09/2018 at 21:57. Pushed by smankowski into branch 'master'. [ERR-5]: Format de date non pris en charge importation boobank M +1-0CHANGELOG M +0-1plugins/import/skrooge_import_backend/CMakeLists.txt M +2-2 plugins/import/skrooge_import_backend/org.kde.skrooge-import-backend-weboob.desktop D +0-107 plugins/import/skrooge_import_backend/org.kde.skrooge-import-backend-weboob0g.desktop M +2-2 plugins/import/skrooge_import_backend/org.kde.skrooge-import-backend-weboob_coming.desktop M +36 -6plugins/import/skrooge_import_csv/skgimportplugincsv.cpp M +4-4tests/input/skgtestimportbackend/320716_1/boobank M +6-6tests/input/skgtestimportbackend/320716_2/boobank D +0-15 tests/input/skgtestimportbackend/329876/boobank M +2-2tests/input/skgtestimportbackend/397055/boobank C +2-2tests/input/skgtestimportbackend/397611/boobank [from: tests/input/skgtestimportbackend/397055/boobank - 060% similarity] M +4-4tests/input/skgtestimportbackend/betterselection/boobank M +3-3tests/input/skgtestimportbackend/double/boobank M +7-7tests/input/skgtestimportbackend/fake1/boobank M +4-4tests/input/skgtestimportbackend/joint_accounts/boobank M +2-2tests/input/skgtestimportbackend/kevin/boobank M +2-2tests/input/skgtestimportbackend/merge/boobank M +13 -13 tests/input/skgtestimportbackend/stamm/boobank D +0-13 tests/input/skgtestimportbackend/weboob0h/boobank M +24 -47 tests/skgbankmodelertest/skgtestimportweboob.cpp https://commits.kde.org/skrooge/c67397c75822a8d09f66dba1c80491a1b51f4de1 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 398405] Session planner copies RA/DEC to Scheduler without fractional part
https://bugs.kde.org/show_bug.cgi?id=398405
--- Comment #6 from Jasem Mutlaq ---
I changed toDMSString in dms.cpp to this:
QString dummy;
char pm(' ');
QChar zero('0');
int dd = abs(degree());
int dm = abs(arcmin());
int ds = abs(arcsec());
if (Degrees() < 0.0)
pm = '-';
else if (forceSign && Degrees() > 0.0)
pm = '+';
if (machineReadable)
return QString("%1%2:%3:%4").arg(pm)
.arg(dd, 2, 10, QChar('0'))
.arg(dm, 2, 10, QChar('0'))
.arg(ds, 2, 10, QChar('0'));
if (highPrecision)
{
double sec = arcsec() + marcsec() / 1000.;
return QString("%1%2° %3\' %4\"").arg(pm)
.arg(dd, 2, 10, zero)
.arg(dm, 2, 10, zero)
.arg(sec, 2, 'f', 2, zero);
}
return QString("%1%2° %3\' %4\"").arg(pm)
.arg(dd, 2, 10, zero)
.arg(dm, 2, 10, zero)
.arg(ds, 2, 10, zero);
However, I am still getting decimal point even though I changed the language
and then also changed the system locale and logged out then in again. I also
briefly tried with QLocale().toString with same results. Can you find out
what's wrong?
--
You are receiving this mail because:
You are watching all bug changes.
[KBibTeX] [Bug 398136] kbibtex crashes when editing element
https://bugs.kde.org/show_bug.cgi?id=398136 Thomas Fischer changed: What|Removed |Added Latest Commit||bddb06c5cec1d5b6e22b423f248 ||5825261ad8f49 Status|CONFIRMED |ASSIGNED --- Comment #2 from Thomas Fischer --- I think I have fixed the problem, at least Valgrind no longer reports a memory issue in this context. Please test and confirm yourself. The code is in my personal clone of the KBibTeX repository, not (yet) in the official one: https://commits.kde.org/clones/kbibtex/thomasfischer/kbibtex/bddb06c5cec1d5b6e22b -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 397834] Native Firefox/Wayland port works poorly on Wayland Plasma
https://bugs.kde.org/show_bug.cgi?id=397834 --- Comment #11 from David Edmundson --- >d but mouse input is ignored, mouse pointer reacts to content under Firefox >window. I've been investigating this first as I have a raster dialog on my startup. Firefox uses subsurfaces. [1911371.914] -> zxdg_shell_v6@17.get_xdg_surface(new id zxdg_surface_v6@31, wl_surface@30) [1911388.950] -> wl_subcompositor@29.get_subsurface(new id wl_subsurface@41, wl_surface@40, wl_surface@30) Here we have surface 30 as the parent which is the toplevel, surface 40 is the subsurface our pointer only enters surface 40 wl_pointer@3.enter(4096, wl_surface@40, 323.00, 122.00) as it fills the whole area we never enter surface 30 gdkdevice-wayland.c:1507 pointer_handle_enter has the line if (!GDK_IS_WINDOW (wl_surface_get_user_data (surface))) return; our subsurface is not a window so we fail early. It then ignores all mouse events as it thinks no window has focus. Our code is definitely going out of it's way to make sure we send things to the subsurface; docs are a bit unclear on whether it's right or not. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398479] DigiKam crashing at startup Thread 2 Crashed:: Digikam::ScanController
https://bugs.kde.org/show_bug.cgi?id=398479 --- Comment #8 from benjcmin --- So yes it seems it's coming down to the RAW files. Right now installation from package digiKam-6.0.0-beta1-20180910T183526-MacOS-x86-64.pkg is starting without problems but only with a few images and WITHOUT RAW files. But as soon as I add an RAW image file to the folder it crashs on the same thread but when I delete the RAW file it starts up fine again. Thread 2 Crashed:: Digikam::ScanController 0 libsystem_platform.dylib0x7fff50d74c69 _platform_bzero$VARIANT$Haswell + 41 1 libdigikamcore.6.0.0.dylib 0x000106528cbb LibRaw::LibRaw(unsigned int) + 219 2 libdigikamcore.6.0.0.dylib 0x0001064a0601 Digikam::DRawDecoder::rawFileIdentify(Digikam::RawInfo&, QString const&) + 641 3 libdigikamcore.6.0.0.dylib 0x0001061123cf Digikam::RAWLoader::load(QString const&, Digikam::DImgLoaderObserver*) + 143 4 libdigikamcore.6.0.0.dylib 0x0001063104b7 Digikam::DImg::load(QString const&, int, Digikam::DImgLoaderObserver*, Digikam::DRawDecoding const&) + 4743 5 libdigikamcore.6.0.0.dylib 0x00010630f1ba Digikam::DImg::loadImageInfo(QString const&, bool, bool, bool, bool) + 298 6 libdigikamdatabase.6.0.0.dylib 0x00010ed90e02 Digikam::ImageScanner::loadFromDisk() + 242 7 libdigikamdatabase.6.0.0.dylib 0x00010ed912dc Digikam::ImageScanner::newFile(int) + 28 8 libdigikamdatabase.6.0.0.dylib 0x00010ec9c657 Digikam::CollectionScanner::scanNewFile(QFileInfo const&, int) + 727 9 libdigikamdatabase.6.0.0.dylib 0x00010ec97fc4 Digikam::CollectionScanner::scanAlbum(Digikam::CollectionLocation const&, QString const&) + 2548 10 libdigikamdatabase.6.0.0.dylib 0x00010ec96634 Digikam::CollectionScanner::scanAlbumRoot(Digikam::CollectionLocation const&) + 180 11 libdigikamdatabase.6.0.0.dylib 0x00010ec99fdb Digikam::CollectionScanner::partialScan(QString const&, QString const&) + 1627 12 libdigikamdatabase.6.0.0.dylib 0x00010ec99922 Digikam::CollectionScanner::partialScan(QString const&) + 98 13 libdigikamgui.6.0.0.dylib 0x000104ec25e3 Digikam::ScanController::run() + 1795 14 org.qt-project.QtCore 0x00010e7bb8f7 0x10e79 + 178423 15 libsystem_pthread.dylib 0x7fff50d7a661 _pthread_body + 340 16 libsystem_pthread.dylib 0x7fff50d7a50d _pthread_start + 377 17 libsystem_pthread.dylib 0x7fff50d79bf9 thread_start + 13 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 --- Comment #6 from Vincent PINON --- Movit's *integration in MLT* is not stable. I believe the lib itself is quite seriously tested (at least on some configurations of graphics cards & drivers), but MLT wrapping has been mainly a one-shot sprint. The crash backtrace confirms the error is in libmltopengl. Can you forward the issue to MLT on github? -- You are receiving this mail because: You are watching all bug changes.
[libkcddb] [Bug 398515] FindMusicBrainz5.cmake: MUSICBRAINZ5_INCLUDE_DIRS not used or searched for anymore (regression)
https://bugs.kde.org/show_bug.cgi?id=398515 --- Comment #1 from Rex Dieter --- Or can just live with this and require libmusticbrainz >= 5.1 where the strict dependency on libxml2 was dropped. (And I can just workaround it downstream by manually adding include dirs as needed) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398464] Discover crashes when I try to launch it
https://bugs.kde.org/show_bug.cgi?id=398464 --- Comment #1 from doctor --- Created attachment 114905 --> https://bugs.kde.org/attachment.cgi?id=114905&action=edit New crash information added by DrKonqi plasma-discover (5.13.80) using Qt 5.11.1 All latest version of packages, usual x-org session, also graphic options was set to OpenGL 3.1 -- Backtrace (Reduced): #6 0x7f42f601b428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f42f601d02a in __GI_abort () at abort.c:89 [...] #9 0x7f42f606637a in malloc_printerr (ar_ptr=, ptr=, str=0x7f42f6176fe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7f42f606a53c in __GI___libc_free (mem=) at malloc.c:2968 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398464] Discover crashes when I try to launch it
https://bugs.kde.org/show_bug.cgi?id=398464 doctor changed: What|Removed |Added CC||strelok5...@yandex.ru -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Sefa Eyeoglu changed: What|Removed |Added CC||sefa6...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 398517] New: UI - Korganizer day and bar that contains the day number seems to be hard coded.
https://bugs.kde.org/show_bug.cgi?id=398517 Bug ID: 398517 Summary: UI - Korganizer day and bar that contains the day number seems to be hard coded. Product: korganizer Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: monthview Assignee: kdepim-b...@kde.org Reporter: walter.joseph...@gmail.com Target Milestone: --- On a 4k monitor, the bar that contains the day number appears to be too small to display the day, so only a small part of the day number is displayed. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 398516] New: UI - Akregator comments section font seems to be hard coded. Font is tiny on a 4k monitor
https://bugs.kde.org/show_bug.cgi?id=398516 Bug ID: 398516 Summary: UI - Akregator comments section font seems to be hard coded. Font is tiny on a 4k monitor Product: akregator Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: walter.joseph...@gmail.com Target Milestone: --- The comments section appear to be hard coded, as it ignores smallest font setting. On a 4k monitor, it appears to be less than 5 points and it can't be changed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395262] Transparency/blur is corrupted on context menu of desktop files
https://bugs.kde.org/show_bug.cgi?id=395262 --- Comment #23 from Alex Nemeth --- (In reply to Alex Nemeth from comment #22) > I also still have the problem. > Here is an attempt to fix it for the desktop icon context menu: D15435 Full link: https://phabricator.kde.org/D15435 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395262] Transparency/blur is corrupted on context menu of desktop files
https://bugs.kde.org/show_bug.cgi?id=395262 --- Comment #22 from Alex Nemeth --- I also still have the problem. Here is an attempt to fix it for the desktop icon context menu: D15435 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398443] okular sometimes goes into a state where "space" is recognized for navigation, but not "delete" or "pageup/pagedown"
https://bugs.kde.org/show_bug.cgi?id=398443 Frederick Eaton changed: What|Removed |Added CC||frede...@ofb.net --- Comment #1 from Frederick Eaton --- I realized on further observation that this seems related to Okular's on-demand loading of PDF data. Sometimes when Okular is open in a tab, I can cause it to enter a bad-focus state just by scrolling down in a recently-opened document. In other words, it'll be in a state where "space" and "delete" both work; then I press "space" several times and Okular pauses a second while loading the next page, and then I find that it no longer recognizes "delete" to scroll up... and I have to use the mouse button to restore focus. So you can probably ignore the information about my window manager, and certainly my web browser, in the initial report; the bug can be triggered entirely within Okular. By the way how do I get a list of bugs I've submitted? The "My Requests" link in the header doesn't show anything... -- You are receiving this mail because: You are watching all bug changes.
[libkcddb] [Bug 398515] FindMusicBrainz5.cmake: MUSICBRAINZ5_INCLUDE_DIRS not used or searched for anymore (regression)
https://bugs.kde.org/show_bug.cgi?id=398515 Rex Dieter changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Keywords||regression Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398449] error al abrir la aplicacion dolphin
https://bugs.kde.org/show_bug.cgi?id=398449 Julian Schraner changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |NEEDSINFO CC||juliquad...@gmail.com --- Comment #1 from Julian Schraner --- Hello, and thank you for reporting your crash. If I understood your problem correctly, Dolphin opens up and then crashes after throwing an error that it couldn't save something somewhere. Is that correct? Also, we'd need a complete backtrace to further debug this crash. Please install the dolphin-dbgsym package and add a new backtrace here. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[libkcddb] [Bug 398515] New: FindMusicBrainz5.cmake: MUSICBRAINZ5_INCLUDE_DIRS not used or searched for anymore (regression)
https://bugs.kde.org/show_bug.cgi?id=398515 Bug ID: 398515 Summary: FindMusicBrainz5.cmake: MUSICBRAINZ5_INCLUDE_DIRS not used or searched for anymore (regression) Product: libkcddb Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: lark...@gmail.com Reporter: rdie...@gmail.com CC: myr...@kde.org, sit...@kde.org, tdfisc...@kde.org Target Milestone: --- Since merge of kf5 branch, lost the effective modifcation from past commit https://cgit.kde.org/libkcddb.git/commit/cmake/FindMusicBrainz5.cmake?id=a6ef64de33a84d4842659241d8bda3b12190f8ca to support (multiple) include dirs, so builds will effectively use $ pkg-config --cflags libmusicbrainz5 (output on my box includes: -I/usr/include/neon -I/usr/include/libxml2 ) I noticed this primarily because libkcddb fails to build on RHEL7 without that. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 360624] Implement "Invert Filter" option
https://bugs.kde.org/show_bug.cgi?id=360624 Julian Schraner changed: What|Removed |Added CC||juliquad...@gmail.com --- Comment #3 from Julian Schraner --- Hello tuxflo and thanks for your comment. As KDE is a community project, we cannot (and do not want to) decide what the developers should work on. A good way to raise the visibility of an issue is to vote on it (there should be a link next to the "Importance" field). You are of course also more than welcome to implement the feature yourself. Have a nice day! -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 398514] New: Add youtube-dl integration
https://bugs.kde.org/show_bug.cgi?id=398514 Bug ID: 398514 Summary: Add youtube-dl integration Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: kolya...@gmail.com Target Milestone: --- Consider adding youtube-dl support if it's installed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 398486] Okular cannot print to remote cups server
https://bugs.kde.org/show_bug.cgi?id=398486 Michael Weghorn changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||m.wegh...@posteo.de --- Comment #2 from Michael Weghorn --- Thanks for your report. A few more questions: A) Does printing work when you enable "Force rasterization" in the PDF options in the print dialog (this should make Okular use the "default" Qt way of printing). B) Do other Qt/KDE applications work? And if so, how much works there? (e.g. I'd usually expect that printing itself should mostly to the same extent as with "Force rasterization" in Okular, and the greyed out options are probably always the same?) c) What Qt version are you using? (There were quite some improvements to the Qt print dialog in Qt 5.11). -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 335730] No easy way to reposition krunner window
https://bugs.kde.org/show_bug.cgi?id=335730 Rog131 changed: What|Removed |Added CC||fabi...@keemail.me --- Comment #15 from Rog131 --- *** Bug 398378 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 398378] Allow to set krunner window position
https://bugs.kde.org/show_bug.cgi?id=398378 Rog131 changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||samrog...@hotmail.com --- Comment #1 from Rog131 --- *** This bug has been marked as a duplicate of bug 335730 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 398492] Adding second inline image changes first one
https://bugs.kde.org/show_bug.cgi?id=398492 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org Resolution|--- |WAITINGFORINFO Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Laurent Montel --- Hi, Sorry I can't reproduce it in last version. I need more info about it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 380019] Kdenlive crashes when using "Fade from black" on an image
https://bugs.kde.org/show_bug.cgi?id=380019 --- Comment #5 from farid --- (In reply to Jakob Sinclair from comment #3) > Can reproduce this issue when GPU is enabled. Every time I add Fade from > Black to a video or image it instantly crashes. I don't have debug packages > on Solus so I can't provide a backtrace. Unfortunately MOVIT (GPU effects) is not stable and not ready for production use. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373839] Continuously face thumbnails flicker/update
https://bugs.kde.org/show_bug.cgi?id=373839
--- Comment #28 from Kristian Karl ---
Complete printout of information regarding the VM machine
$ VBoxManage showvminfo "Kubuntu 18.04"
Name:Kubuntu 18.04
Groups: /
Guest OS:Ubuntu (64-bit)
UUID:73aa30f4-e0f1-4359-96ba-b1e860f8038f
Config file: /home/krikar/VirtualBox VMs/Kubuntu 18.04/Kubuntu 18.04.vbox
Snapshot folder: /home/krikar/VirtualBox VMs/Kubuntu 18.04/Snapshots
Log folder: /home/krikar/VirtualBox VMs/Kubuntu 18.04/Logs
Hardware UUID: 73aa30f4-e0f1-4359-96ba-b1e860f8038f
Memory size: 4610MB
Page Fusion: off
VRAM size: 33MB
CPU exec cap:100%
HPET:off
Chipset: piix3
Firmware:BIOS
Number of CPUs: 1
PAE: off
Long Mode: on
Triple Fault Reset: off
APIC:on
X2APIC: on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:on
IOAPIC: on
BIOS APIC mode: APIC
Time offset: 0ms
RTC: UTC
Hardw. virt.ext: on
Nested Paging: on
Large Pages: off
VT-x VPID: on
VT-x unr. exec.: on
Paravirt. Provider: Default
Effective Paravirt. Provider: KVM
State: powered off (since 2018-09-11T16:41:47.67600)
Monitor count: 1
3D Acceleration: on
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration:
Autostart Enabled: off
Autostart Delay: 0
Default Frontend:
Storage Controller Name (0):IDE
Storage Controller Type (0):PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0):on
Storage Controller Name (1):SATA
Storage Controller Type (1):IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1): 30
Storage Controller Port Count (1): 1
Storage Controller Bootable (1):on
IDE (1, 0): Empty
SATA (0, 0): /home/krikar/VirtualBox VMs/Kubuntu
18.04/Snapshots/{d346dd72-695a-4b30-a07f-9e743849bb7a}.vdi (UUID:
d346dd72-695a-4b30-a07f-9e743849bb7a)
NIC 1: MAC: 0800272205A2, Attachment: NAT, Cable connected: on,
Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority:
0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64,
receive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
UART 3: disabled
UART 4: disabled
LPT 1: disabled
LPT 2: disabled
Audio: enabled (Driver: PulseAudio, Controller: AC97, Codec: AD1980)
Audio playback: disabled
Audio capture: enabled
Clipboard Mode: disabled
Drag and drop Mode: disabled
VRDE:disabled
USB: enabled
EHCI:enabled
XHCI:disabled
USB Device Filters:
Bandwidth groups:
Shared folders:
Capturing: not active
Capture audio: not active
Capture screens:0
Capture file: /home/krikar/VirtualBox VMs/Kubuntu 18.04/Kubuntu
18.04.webm
Capture dimensions: 1024x768
Capture rate: 512 kbps
Capture FPS:25
Capture options:ac_enabled=false
Guest:
Configured memory balloon size: 0 MB
Snapshots:
Name: Prestine (UUID: 43f8bf90-35c4-440e-b854-23041d709ac4) *
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 398510] The Background Contrast effect ignores data.brightness() and data.saturation()
https://bugs.kde.org/show_bug.cgi?id=398510 Vlad Zagorodniy changed: What|Removed |Added Priority|NOR |LO --- Comment #1 from Vlad Zagorodniy --- The problem is that content of the panel is translucent. W.r.t. the blur effect, it makes sense to not modulate blurred stuff with "brightness and saturation". On the other hand, with the background contrast effect, things are a little bit different... I'm not sure whether that's a bug at all. Anyway, I can think of 2 potential solutions: * copy and increase contrast in a single pass, then use a shader from libkwineffects to map and also modulate the result; * copy what's underneath, then increase contrast and "modulate" in a single pass(e.g. by tweaking color matrix). I'm lowering priority of this bug report because it's really hard to notice this bug(?). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373839] Continuously face thumbnails flicker/update
https://bugs.kde.org/show_bug.cgi?id=373839 --- Comment #27 from Kristian Karl --- System === Processors: 1 CPU Base memory: 4610 MB Acceleration: VT-x/AMD-V, Nested Paging, KVM Paravirtualization Display === Video memory: 33 MB Acceleration: 3D -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398479] DigiKam crashing at startup Thread 2 Crashed:: Digikam::ScanController
https://bugs.kde.org/show_bug.cgi?id=398479 --- Comment #7 from caulier.gil...@gmail.com --- The difference between 5.9.0 and 6.0.0 is the libraw used internally to decode RAW files. This can explain the crash. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 394914] Table default values not displayed
https://bugs.kde.org/show_bug.cgi?id=394914 Jarosław Staniek changed: What|Removed |Added Blocks||379306 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=379306 [Bug 379306] Zero values not showing up -- You are receiving this mail because: You are watching all bug changes.
[KEXI] [Bug 379306] Zero values not showing up
https://bugs.kde.org/show_bug.cgi?id=379306 Jarosław Staniek changed: What|Removed |Added Depends on||394914 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=394914 [Bug 394914] Table default values not displayed -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398513] New: Plasmashell crash with memory access error
https://bugs.kde.org/show_bug.cgi?id=398513 Bug ID: 398513 Summary: Plasmashell crash with memory access error Product: plasmashell Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: xxvign...@gmail.com Target Milestone: 1.0 plasmashell crashes frequently (5+ times per day) when doing seemingly random tasks. Haven't been able to pinpoint it. relevant part from journalctl: Sep 11 16:13:37 vigneshk systemd-coredump[2139]: Process 1260 (plasmashell) of user 1000 dumped core. Stack trace of thread 1260: #0 0x7f7bf7b97d7f n/a (n/a) relevant part from coredump -> gdb -> bt [New LWP 2240] [New LWP 2209] Cannot access memory at address 0x7f949c9640e8 Cannot access memory at address 0x7f949c9640e0 Failed to read a valid object file image from memory. Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7f9499694d7f in ?? () -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398447] Some icons are badly visible on a dark background
https://bugs.kde.org/show_bug.cgi?id=398447 Michail Vourlakos changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #1 from Michail Vourlakos --- sorry there is no way for Latte to support this because plasma frameworks does not support this yet. Only solution is to find a plasma theme or icon theme that provides whitish such icons -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398502] Preview for grouped task not working
https://bugs.kde.org/show_bug.cgi?id=398502 Michail Vourlakos changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Michail Vourlakos --- *** This bug has been marked as a duplicate of bug 397193 *** -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 397193] Latte fails to show window thumbnails with multiple application windows
https://bugs.kde.org/show_bug.cgi?id=397193 Michail Vourlakos changed: What|Removed |Added CC||braindead...@gmail.com --- Comment #7 from Michail Vourlakos --- *** Bug 398502 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398479] DigiKam crashing at startup Thread 2 Crashed:: Digikam::ScanController
https://bugs.kde.org/show_bug.cgi?id=398479 --- Comment #6 from benjcmin --- It's set to 12bit. FYI with the latest version 5.9.0 is working with those images. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373839] Continuously face thumbnails flicker/update
https://bugs.kde.org/show_bug.cgi?id=373839 --- Comment #26 from caulier.gil...@gmail.com --- ok, What's about the cores assigned to the VM ? Same for the system memory and the video memory. This is important because it can influence to the rendering performances. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[kiofuse] [Bug 75324] Integrate KIO Slaves into file system using FUSE gateway
https://bugs.kde.org/show_bug.cgi?id=75324 Pau Ruiz Safont changed: What|Removed |Added CC||unduthe...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 398512] New: Pointer threshold has wrong default?
https://bugs.kde.org/show_bug.cgi?id=398512 Bug ID: 398512 Summary: Pointer threshold has wrong default? Product: systemsettings Version: 5.12.6 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: kais...@gmail.com CC: unassigned-b...@kde.org Target Milestone: --- It seems that the "Pointer threshold" value is set to 4 (when doing a clean install with Ubuntu 18.04.1 as base) but its default is 2 (when clicking the default button). So is it correct to be 4 or not? I did a clean install of Ubuntu 18.04.1, installed updates, restarted Then installed kubunto-desktop, restarted, logged in Opened system settings->input devices->mouse->advanced Had some problems with tabs in konsole as seen in: https://bugs.kde.org/show_bug.cgi?id=398497 and noticed that 2 is the default but it is installed with 4 -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 398485] Adding widget zoom setting
https://bugs.kde.org/show_bug.cgi?id=398485 --- Comment #6 from Michail Vourlakos --- (In reply to Olivier Boucard from comment #5) > Sorry, how could I miss that. Latte dock has so many features it is amazing. no worries -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 373839] Continuously face thumbnails flicker/update
https://bugs.kde.org/show_bug.cgi?id=373839 --- Comment #25 from Kristian Karl --- With 3D Acceleration enabled, I still get flickering on my VirtualBox installation, I'm afraid. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-karchive] [Bug 398511] New: It allows to go upper than the root of the compressed file
https://bugs.kde.org/show_bug.cgi?id=398511 Bug ID: 398511 Summary: It allows to go upper than the root of the compressed file Product: frameworks-karchive Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: jtam...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Open a .zip file in /home/user/compressed.zip with dolphin, the url now is: krarc:///home/user/ccompressed.zip/ If I press up, dolphin goes to "krarc:///home/user/", that doesn't exist. Probably related to https://phabricator.kde.org/D13674 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394505] Many "unnamed" identities are created without intervention
https://bugs.kde.org/show_bug.cgi?id=394505 --- Comment #2 from Alejandro Lorenzo --- I am also seeing this behaviour, will try to remove from emailidentities -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398510] New: The Background Contrast effect ignores data.brightness() and data.saturation()
https://bugs.kde.org/show_bug.cgi?id=398510 Bug ID: 398510 Summary: The Background Contrast effect ignores data.brightness() and data.saturation() Product: kwin Version: git master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: vladz...@gmail.com Target Milestone: --- Steps to reproduce: * [enable the kscreen effect]; * Set "Animation speed" to "Very slow"; * Lock screen. Expected results: * The panel fades to black; Actual results: * The panel stays bright. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398509] Request for Outline Tool
https://bugs.kde.org/show_bug.cgi?id=398509 Boudewijn Rempt changed: What|Removed |Added CC||b...@valdyas.org --- Comment #1 from Boudewijn Rempt --- Doesn't https://docs.krita.org/en/reference_manual/tools/colorize_mask.html fill your requirements? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398509] New: Request for Outline Tool
https://bugs.kde.org/show_bug.cgi?id=398509 Bug ID: 398509 Summary: Request for Outline Tool Product: krita Version: 4.1.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: k...@kenevans.net Target Milestone: --- Created attachment 114904 --> https://bugs.kde.org/attachment.cgi?id=114904&action=edit Example of using a Lasso or Outline Tool with Fill. It would be nice to have an Outline Tool, working like the Polygon Tool but selecting like the Outline Selection Tool. It shouldn't be that hard to implement since the parts are already there in the Polygon Tool and Outline Selection Tool. I have just discovered the Lasso Fill Tool in Clip Studio Paint. (Lasso is their name for what Krita calls Outline.) It is INCREDIBLY useful for inking large areas. You just draw around the area, and it fills. Very fast and easy. You can do this in Krita with the Polygon Tool, but it is slow and the edges are not smooth curves. I am attaching an example. I did it fast, and it may not be the best inking, but it shows what can be done easily with such a tool. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394505] Many "unnamed" identities are created without intervention
https://bugs.kde.org/show_bug.cgi?id=394505 --- Comment #1 from Adam Bark --- I found that the identities are located at ~/.config/emailidentities and removing them from there seemed to stick but I also reset akonadi at the same time so I don't know if that's the only requirement. Removing these unnamed identities through the interface just seemed to make them double when restarting kmail. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 394505] Many "unnamed" identities are created without intervention
https://bugs.kde.org/show_bug.cgi?id=394505 Alejandro Lorenzo changed: What|Removed |Added CC||alejandro_a...@yahoo.es -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398508] [WAYLAND] Wacom stylus not detected
https://bugs.kde.org/show_bug.cgi?id=398508 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |LATER Status|UNCONFIRMED |RESOLVED --- Comment #2 from David Edmundson --- Yes, we have no code for it. It will be added in the future. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 398378] Allow to set krunner window position
https://bugs.kde.org/show_bug.cgi?id=398378 fabi...@keemail.me changed: What|Removed |Added CC||fabi...@keemail.me -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 393200] Off-center icon & text label in root password request dialog
https://bugs.kde.org/show_bug.cgi?id=393200 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Resolution|UPSTREAM|FIXED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398508] [WAYLAND] Wacom stylus not detected
https://bugs.kde.org/show_bug.cgi?id=398508 --- Comment #1 from Roman Šmakal --- Created attachment 114903 --> https://bugs.kde.org/attachment.cgi?id=114903&action=edit hwinfo -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 393200] Off-center icon & text label in root password request dialog
https://bugs.kde.org/show_bug.cgi?id=393200 Scott Harvey changed: What|Removed |Added Resolution|--- |UPSTREAM Status|UNCONFIRMED |RESOLVED --- Comment #2 from Scott Harvey --- This is fixed in patch https://phabricator.kde.org/R121:d4ee26a76a217a5beed73c44080b3a49b7b681a0 I believe it will show up in the next Plasma release. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file
https://bugs.kde.org/show_bug.cgi?id=398342 --- Comment #5 from Alexander Semke --- Can you please apply the attached patch and run the tests again? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 398508] New: [WAYLAND] Wacom stylus not detected
https://bugs.kde.org/show_bug.cgi?id=398508 Bug ID: 398508 Summary: [WAYLAND] Wacom stylus not detected Product: kwin Version: 5.13.5 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: libinput Assignee: kwin-bugs-n...@kde.org Reporter: schmakeri...@gmail.com Target Milestone: --- Created attachment 114902 --> https://bugs.kde.org/attachment.cgi?id=114902&action=edit libinput list Touchscreen works flawless, but there is no pen input even though libinput actually recognizes input from my pen. Only happens on wayland. -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 398342] ProjectImportTest segfaults while loading Excel file
https://bugs.kde.org/show_bug.cgi?id=398342 --- Comment #4 from Alexander Semke --- Created attachment 114901 --> https://bugs.kde.org/attachment.cgi?id=114901&action=edit fix big endian import in liborigin -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 398507] New: Updater notifies of updates available but will not download them, app freezes
https://bugs.kde.org/show_bug.cgi?id=398507 Bug ID: 398507 Summary: Updater notifies of updates available but will not download them, app freezes Product: Discover Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Updater Assignee: aleix...@kde.org Reporter: d.thomp...@runbox.com Target Milestone: --- Discover app notifies of system updates available and i can see list but nothing happens, I have tried to start the update but the discover app has 'frozen'. I updated via terminal - sudo apt update, then sudo apt upgrade which seems to have updated the system updates. When i now try to close the discover app I get error message 'cannot close as tasks are still being performed. -- You are receiving this mail because: You are watching all bug changes.
