[kwin] [Bug 391728] Improve ultrawide screen support: Maximize on the left or right area
https://bugs.kde.org/show_bug.cgi?id=391728 --- Comment #4 from Martin Flöser--- I'm not saying we should add a deco button for it. But it could be added to the user action's menu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391551] Scrolling with the touchpad to switch desktops is too fast
https://bugs.kde.org/show_bug.cgi?id=391551 --- Comment #4 from RaitaroH--- Also this is the fix for gwenview: https://bugs.kde.org/show_bug.cgi?id=388353#c19 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391485] Wallpaper chooser UI not very discoverable; consider making it into a KCM so we can expose it via System Settings
https://bugs.kde.org/show_bug.cgi?id=391485 --- Comment #8 from Nate Graham--- Here is an example of what I'm talking about: https://www.reddit.com/r/gnome/comments/8360xr/gnome_is_design/dvh9reu/ > They also throw so many functionalities at your face, but basic things like > right-click and set as wallpaper is not there. Kde was built by developers > for developers. What!? It's right there, under "Configure Desktop"! ...Only the word "Wallpaper isn't used, so people don't find it, because making the connection between the Desktop and the Wallpaper is apparently something that regular users are having difficulty with. Tentative trivial short-term fix: change the string to "Configure Wallpaper and Desktop": https://phabricator.kde.org/D11253 I think that would really help. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391551] Scrolling with the touchpad to switch desktops is too fast
https://bugs.kde.org/show_bug.cgi?id=391551 --- Comment #3 from RaitaroH--- Here is what the developer of the event calendar said: https://github.com/Zren/plasma-applet-eventcalendar/issues/4#issuecomment-372145550 Maybe it can help. It seems it is a QT bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 391741] New: System Settings crashed when changing Keyboard Layouts
https://bugs.kde.org/show_bug.cgi?id=391741 Bug ID: 391741 Summary: System Settings crashed when changing Keyboard Layouts Product: systemsettings Version: 5.12.3 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dwilc...@gmail.com Target Milestone: --- Application: systemsettings5 (5.12.3) Qt Version: 5.9.1 Frameworks Version: 5.43.0 Operating System: Linux 4.13.0-36-generic x86_64 Distribution: Ubuntu 17.10 -- Information about the crash: - What I was doing when the application crashed: I was changing the keyboard layouts, I then started typing to test one of the layouts and it crashed. - Unusual behavior I noticed: Earlier when moving a window from one desktop to the other (clicked in the windows's bar and dragged to the other desktop) the system froze for 15 seconds, I don't know if that can be related. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f579fc02140 (LWP 2121))] Thread 18 (Thread 0x7f571580f700 (LWP 5403)): #0 0x7f579b659951 in __GI___poll (fds=0x5639f10da570, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f579558c169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f579558c502 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f571db15b26 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7f57955b3645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f57978757fc in start_thread (arg=0x7f571580f700) at pthread_create.c:465 #6 0x7f579b665b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f5716010700 (LWP 5402)): #0 0x7f57955d15b9 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f579558b891 in g_main_context_query () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f579558c0e7 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f579558c27c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f579558c2c1 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f57955b3645 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f57978757fc in start_thread (arg=0x7f5716010700) at pthread_create.c:465 #7 0x7f579b665b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f5707fff700 (LWP 2322)): #0 0x7f579b659951 in __GI___poll (fds=0x7f5710178c30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f579558c169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f579558c27c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f579bf9949b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f579bf3ee3a in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f579bd5e3ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f57998d3f45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f579bd6329d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f57978757fc in start_thread (arg=0x7f5707fff700) at pthread_create.c:465 #9 0x7f579b665b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 15 (Thread 0x7f5740aad700 (LWP 2137)): #0 0x7f579787c072 in futex_wait_cancelable (private=, expected=0, futex_word=0x5639f0020aa8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5639f0020a58, cond=0x5639f0020a80) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5639f0020a80, mutex=0x5639f0020a58) at pthread_cond_wait.c:655 #3 0x7f5778c7324b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f5778c73167 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f57978757fc in start_thread (arg=0x7f5740aad700) at pthread_create.c:465 #6 0x7f579b665b5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 14 (Thread 0x7f5741f1b700 (LWP 2136)): #0 0x7f579787c072 in futex_wait_cancelable (private=, expected=0, futex_word=0x5639efc2df1c) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x5639efc2dec8, cond=0x5639efc2def0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x5639efc2def0, mutex=0x5639efc2dec8) at pthread_cond_wait.c:655 #3 0x7f5778c7324b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f5778c73167 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f57978757fc in
[kate] [Bug 383665] Keywords are not bold in most themes
https://bugs.kde.org/show_bug.cgi?id=383665 Christoph Feckchanged: What|Removed |Added CC||maxime.haselbauer@googlemai ||l.com --- Comment #7 from Christoph Feck --- *** Bug 391040 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 391040] Highlighting scheme not displaying keyword as bold since last update
https://bugs.kde.org/show_bug.cgi?id=391040 Christoph Feckchanged: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 383665 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 306425] Screen brightness reset to max after login
https://bugs.kde.org/show_bug.cgi?id=306425 Martin Klapetekchanged: What|Removed |Added CC|mklape...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381154] Certain notifications freeze plasma
https://bugs.kde.org/show_bug.cgi?id=381154 Martin Klapetekchanged: What|Removed |Added CC|mklape...@kde.org | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 384031] Monitor Scaling / HiDPI support breaks font Anti-Aliasing
https://bugs.kde.org/show_bug.cgi?id=384031 Nate Grahamchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #18 from Nate Graham --- This is caused by the use of QTQuickControls widgets that use a font rendering style that doesn't support non-integer scale factors. System Settings KCMs are being rewritten (see https://phabricator.kde.org/tag/plasma_kcm_redesign/), which will fix this one KCM at a time. Plasma itself will be fixed with https://phabricator.kde.org/D11244 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391701] Searching for a program needs the whole package name
https://bugs.kde.org/show_bug.cgi?id=391701 Nate Grahamchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Discover isn't a package manager, it's an app store. It doesn't show packages, only pieces of software that have AppStream information. What does `appstreamcli search wayland` show? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 388353] In View mode, with the scroll behavior set to "Browse", scrolling with the touchpad is too fast
https://bugs.kde.org/show_bug.cgi?id=388353 Huonchanged: What|Removed |Added Version Fixed In||18.04.0 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 388353] In View mode, with the scroll behavior set to "Browse", scrolling with the touchpad is too fast
https://bugs.kde.org/show_bug.cgi?id=388353 Huonchanged: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://commits.kde.org/gwe ||nview/8b11365cace8b06023683 ||7c4938668842bbe7b6a --- Comment #19 from Huon --- Git commit 8b11365cace8b060236837c4938668842bbe7b6a by Huon Imberger. Committed on 12/03/2018 at 03:14. Pushed by huoni into branch 'master'. Fix scrolling with touchpad when in Image view and mouse wheel behaviour set to Browse Summary: Similar to zooming using Ctrl+touchpad two-finger scroll, using touchpad scrolling in image view when mouse wheel behaviour is set to Browse, browsing images is way too fast. This implements the same fix in {D7744} for this case. Test Plan: # Settings > Image View > Mouse wheel behaviour = Browse # Open folder with a bunch of images, switch to Image view # Enable thumbnail bar # With mouse over image, scroll with the touchpad Reviewers: #gwenview, ngraham, rkflx Reviewed By: #gwenview, ngraham, rkflx Subscribers: mart Differential Revision: https://phabricator.kde.org/D11200 M +5-2lib/documentview/documentview.cpp https://commits.kde.org/gwenview/8b11365cace8b060236837c4938668842bbe7b6a -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 390264] Clicking autocomplete entry crashes application
https://bugs.kde.org/show_bug.cgi?id=390264 Michael Carpinochanged: What|Removed |Added CC||w...@dougie.io --- Comment #9 from Michael Carpino --- *** Bug 391739 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391739] In Gnome (Or possibly all GTK-based desktops) selecting a payee with your mouse crashes the program
https://bugs.kde.org/show_bug.cgi?id=391739 Michael Carpinochanged: What|Removed |Added CC||mfcarp...@gmail.com Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Michael Carpino --- This bug has already been documented and fixed in the upcoming update within 5.0.1 that should be released in the coming weeks. https://bugs.kde.org/show_bug.cgi?id=390264 The workaround is to use your keyboard and navigate the selection of the payee by using the up/down keys and then use the tab key to move forward. Using the mouse will cause the crash. Here's the fix. https://cgit.kde.org/kmymoney.git/commit/?id=7f63b5c02775ae7499f86cff46fef6b54bdb3a78 *** This bug has been marked as a duplicate of bug 390264 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 385314] Exit Full Screen button needs text, like Kate's button has
https://bugs.kde.org/show_bug.cgi?id=385314 --- Comment #2 from Nate Graham--- At the moment, it's sort of pointless since the button isn't even visible by default. But I feel very strongly that any app with a full screen mode needs a *visible* means to leave the mode. I've seen normal users absolutely *panic* when they enter full screen mode and realize they don't know how to leave it. It's a serious issue. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 391611] Spectacle keeps running in the background if clicked on image of the screenshot in the notification and not on "open" button
https://bugs.kde.org/show_bug.cgi?id=391611 Nate Grahamchanged: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|UNCONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 389479] Plasma not mount disk
https://bugs.kde.org/show_bug.cgi?id=389479 --- Comment #45 from Nate Graham--- Let's track the remaining issues in Bug 391706. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems mounting internal partitions, eSATA-hdds, and LUKS-containers
https://bugs.kde.org/show_bug.cgi?id=391706 Nate Grahamchanged: What|Removed |Added Summary|1384f275ab2f1ad1841753ee163 |1384f275ab2f1ad1841753ee163 |af6d1b0bb952b causes|af6d1b0bb952b causes |problems with mounting |problems mounting internal |eSATA-hdds and |partitions, eSATA-hdds, and |LUKS-containers with|LUKS-containers |Dolphin | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390858] When compositing is disabled, switching to another virtual desktop with Kicker open prevents it from showing again
https://bugs.kde.org/show_bug.cgi?id=390858 Nate Grahamchanged: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #19 from Nate Graham --- Yep, can confirm. Steps to reproduce: 1. Have at least two virtual desktops 2. Disable compositor on startup (System Settings > Display & Monitor > Compositor Uncheck "Enable compositor on startup") 3. Reboot 4. Open your menu (kicker kickoff, SimpleMenu, whatever) 5. Use a keyboard shortcut to switch desktops 6. Boom, menu no longer launches until plasmashell is restarted or you re-enable the compositor. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390674] plasmashell freeze as long as you have gnome-disks running after doing a sudo from it
https://bugs.kde.org/show_bug.cgi?id=390674 Nate Grahamchanged: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 391740] New: krunner crash
https://bugs.kde.org/show_bug.cgi?id=391740 Bug ID: 391740 Summary: krunner crash Product: krunner Version: 5.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: k...@privat.broulik.de Reporter: sbo...@blueyonder.co.uk Target Milestone: --- Application: krunner (5.12.3) Qt Version: 5.10.0 Frameworks Version: 5.43.0 Operating System: Linux 4.16.0-rc5-smp+ x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: AL-F2 and tried to launch xcalc, launcher crashed and reported it had. The crash can be reproduced every time. -- Backtrace: Application: krunner (krunner), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f730c6f38c0 (LWP 13749))] Thread 23 (Thread 0x7f72caff0700 (LWP 15368)): #0 0x7f7305f8556c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7308782f4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f72ec584ad5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f72ec588b28 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f72ec583cfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f72ec586a6b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7308781bf0 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f7305f7f59b in start_thread () at /lib64/libpthread.so.0 #8 0x7f7308079a1f in clone () at /lib64/libc.so.6 Thread 22 (Thread 0x7f72cb7f1700 (LWP 15367)): [KCrash Handler] #6 0x7f72e2c69463 in () at /usr/lib64/libsqlite3.so.0 #7 0x7f72e2cb1979 in () at /usr/lib64/libsqlite3.so.0 #8 0x7f72e2c8c472 in () at /usr/lib64/libsqlite3.so.0 #9 0x7f72e2cb8791 in () at /usr/lib64/libsqlite3.so.0 #10 0x7f72e2cd627b in () at /usr/lib64/libsqlite3.so.0 #11 0x7f72e2cdf871 in sqlite3_step () at /usr/lib64/libsqlite3.so.0 #12 0x7f72e2f6275d in () at /usr/lib64/qt5/plugins/sqldrivers/libqsqlite.so #13 0x7f7303636341 in QSqlCachedResult::cacheNext() () at /usr/lib64/libQt5Sql.so.5 #14 0x7f73036222de in QSqlQuery::next() () at /usr/lib64/libQt5Sql.so.5 #15 0x7f72e317e66d in FetchSqlite::query(QString const&, QMap) (this=, sql=..., bindObjects=...) at /usr/src/debug/plasma5-workspace-5.12.3-1.1.x86_64/runners/bookmarks/fetchsqlite.cpp:87 #16 0x7f72e3185340 in Firefox::match(QString const&, bool) (this=0x55971cfc03f0, term=..., addEverything=false) at /usr/src/debug/plasma5-workspace-5.12.3-1.1.x86_64/runners/bookmarks/browsers/firefox.cpp:101 #17 0x7f72e3182fee in BookmarksRunner::match(Plasma::RunnerContext&) (this=0x55971cf32d00, context=...) at /usr/src/debug/plasma5-workspace-5.12.3-1.1.x86_64/runners/bookmarks/bookmarksrunner.cpp:81 #18 0x7f72ec7ae740 in Plasma::AbstractRunner::performMatch(Plasma::RunnerContext&) () at /usr/lib64/libKF5Runner.so.5 #19 0x7f72ec5882e8 in ThreadWeaver::Executor::run(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #20 0x7f72ec587060 in ThreadWeaver::Job::execute(QSharedPointer const&, ThreadWeaver::Thread*) () at /usr/lib64/libKF5ThreadWeaver.so.5 #21 0x7f72ec586b2d in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #22 0x7f7308781bf0 in () at /usr/lib64/libQt5Core.so.5 #23 0x7f7305f7f59b in start_thread () at /lib64/libpthread.so.0 #24 0x7f7308079a1f in clone () at /lib64/libc.so.6 Thread 21 (Thread 0x7f72cbff2700 (LWP 15366)): #0 0x7f7305f8556c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7308782f4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f72ec584ad5 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7f72ec588b28 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7f72ec583cfd in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7f72ec586a6b in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7f7308781bf0 in () at /usr/lib64/libQt5Core.so.5 #7 0x7f7305f7f59b in start_thread () at /lib64/libpthread.so.0 #8 0x7f7308079a1f in clone () at /lib64/libc.so.6 Thread 20 (Thread 0x7f72cc7f3700 (LWP 15365)): #0 0x7f7305f8556c in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f7308782f4b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7f72ec584ad5 in
[frameworks-kio] [Bug 373352] file open / save / save as dialog is slow if automounted filesystems are not available (nfs, smb, etc )
https://bugs.kde.org/show_bug.cgi?id=373352 --- Comment #3 from Nate Graham--- *** Bug 388004 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 388004] Save / Open File Dialog hangs on autofs mounts
https://bugs.kde.org/show_bug.cgi?id=388004 Nate Grahamchanged: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 373352 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 388004] Save / Open File Dialog hangs on autofs mounts
https://bugs.kde.org/show_bug.cgi?id=388004 Nate Grahamchanged: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |fa...@kde.org CC||kdelibs-b...@kde.org, ||n...@kde.org Component|general |general Version|17.04.2 |5.44.0 Summary|Save / Open File Dialog |Save / Open File Dialog |hangs |hangs on autofs mounts Product|dolphin |frameworks-kio -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 388004] Save / Open File Dialog hangs on autofs mounts
https://bugs.kde.org/show_bug.cgi?id=388004 Nate Grahamchanged: What|Removed |Added Version|5.44.0 |5.32.0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 373352] file open / save / save as dialog is slow if automounted filesystems are not available (nfs, smb, etc )
https://bugs.kde.org/show_bug.cgi?id=373352 Nate Grahamchanged: What|Removed |Added Assignee|kdelibs-b...@kde.org|fa...@kde.org CC||kdelibs-b...@kde.org, ||n...@kde.org Component|general |general Version|unspecified |5.44.0 Product|kfile |frameworks-kio -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391739] New: In Gnome (Or possibly all GTK-based desktops) selecting a payee with your mouse crashes the program
https://bugs.kde.org/show_bug.cgi?id=391739 Bug ID: 391739 Summary: In Gnome (Or possibly all GTK-based desktops) selecting a payee with your mouse crashes the program Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: w...@dougie.io Target Milestone: --- Below is a video to help you understand what is happening: https://gfycat.com/GlamorousPopularAlligatorgar In the video, I demonstrate how if you attempt to select a payee with your mouse, the program crashes. I show that you can still select a payee with tab (or the up/down arrow key) but can't with the mouse. It is worth noting that when that final dialog pops up, whether I pick save or discard, it will still crash. It is also worth noting that if I click that little carrot to make a payee selection, that works fine without crashing. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391739] In Gnome (Or possibly all GTK-based desktops) selecting a payee with your mouse crashes the program
https://bugs.kde.org/show_bug.cgi?id=391739 Doug Bchanged: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390632] Breeze task switcher has a transparent rectangle at the bottom
https://bugs.kde.org/show_bug.cgi?id=390632 --- Comment #8 from Vlad Zagorodniy--- I hope it'll help somehow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390632] Breeze task switcher has a transparent rectangle at the bottom
https://bugs.kde.org/show_bug.cgi?id=390632 --- Comment #7 from Vlad Zagorodniy--- Dialog's blur region is set to a mask(I don't really know what it is and how it is computed :( https://github.com/KDE/plasma-framework/blob/master/src/plasmaquick/dialog.cpp#L245 And, in my case, the mask for task switcher is QRegion(size=2, bounds=(0,0 216x768) - [(0,0 216x758), (206,758 10x10)]) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390632] Breeze task switcher has a transparent rectangle at the bottom
https://bugs.kde.org/show_bug.cgi?id=390632 --- Comment #6 from Vlad Zagorodniy--- KWin has nothing to do with this. For example, the blur effect gets the following blur region QRegion(size=2, bounds=(0,0 216x768) - [(0,0 216x758), (206,758 10x10)]) You can clearly see that bottom part is omitted. (my screen resolution is 1366x768) Anyway, after digging a little bit, I think these issues are (maybe) caused by PlasmaCore.Dialog or dialogs/background.svgz. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391738] New: Dolphin needlesly scans /sys for no good reason
https://bugs.kde.org/show_bug.cgi?id=391738 Bug ID: 391738 Summary: Dolphin needlesly scans /sys for no good reason Product: dolphin Version: 17.12.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: zakhar.nasi...@gmail.com CC: elvis.angelac...@kde.org Target Milestone: --- Created attachment 111334 --> https://bugs.kde.org/attachment.cgi?id=111334=edit strace -f -T -tt -o log.txt dolphin It takes it a while to start up, ran: strace -f -T -tt -o log.txt dolphin output is log.txt which is attached. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 391738] Dolphin needlesly scans /sys for no good reason
https://bugs.kde.org/show_bug.cgi?id=391738 Zakharchanged: What|Removed |Added Platform|Other |Gentoo Packages -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 391737] New: Konsole crash at shell exit
https://bugs.kde.org/show_bug.cgi?id=391737 Bug ID: 391737 Summary: Konsole crash at shell exit Product: konsole Version: 16.04.3 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: b...@visi.com Target Milestone: --- Application: konsole (16.04.3) Qt Version: 5.6.1 Frameworks Version: 5.36.0 Operating System: Linux 4.4.0-116-generic x86_64 Distribution: Linux Mint 18.3 Sylvia -- Information about the crash: - What I was doing when the application crashed: Just opened a bunch of konsole's, then exited the shell in each until one crashed. -- Backtrace: Application: Konsole (konsole), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f85a38cb940 (LWP 4766))] Thread 2 (Thread 0x7f85900f0700 (LWP 4767)): #0 0x7f85a338427d in read () at ../sysdeps/unix/syscall-template.S:84 #1 0x7f85969f1f55 in ?? () from /usr/lib/nvidia-340/tls/libnvidia-tls.so.340.104 #2 0x7f859ade26f0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f859ad9ee74 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f859ad9f330 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f859ad9f49c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f859fecc37b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f859fe74ffa in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f859fc9d9e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f85a399e515 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #10 0x7f859fca2808 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f859b4d66ba in start_thread (arg=0x7f85900f0700) at pthread_create.c:333 #12 0x7f85a339441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f85a38cb940 (LWP 4766)): [KCrash Handler] #6 0x7f85a32c2428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 #7 0x7f85a32c402a in __GI_abort () at abort.c:89 #8 0x7f85a33047ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f85a341ded8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 #9 0x7f85a330d37a in malloc_printerr (ar_ptr=, ptr=, str=0x7f85a341dfe8 "double free or corruption (out)", action=3) at malloc.c:5006 #10 _int_free (av=, p=, have_lock=0) at malloc.c:3867 #11 0x7f85a331153c in __GI___libc_free (mem=) at malloc.c:2968 #12 0x7f859fea0c1c in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f859fea0c79 in QMetaCallEvent::~QMetaCallEvent() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f859fe7989f in QCoreApplication::removePostedEvents(QObject*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f859fea302a in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f859fea31d9 in QObjectPrivate::~QObjectPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f859feab0dc in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f858f52a299 in QXcbConnection::~QXcbConnection() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #19 0x7f858f52bab6 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #20 0x7f858f52bbb9 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #21 0x7f85a01bc613 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7f85a07a89f9 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x7f859feab0dc in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x7f859fe78d12 in QCoreApplication::~QCoreApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #25 0x7f85a07aa524 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f85a367e15c in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so #27 0x7f85a32ad830 in __libc_start_main (main=0x4006c0, argc=1, argv=0x7ffd9e980988, init=, fini=, rtld_fini=, stack_end=0x7ffd9e980978) at ../csu/libc-start.c:291 #28 0x004006f9 in _start () The reporter indicates this bug may be a duplicate of or related to bug 342201. Possible duplicates by query: bug 390429, bug 389308, bug 389272, bug 388951, bug 388364. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 391736] Request: Icons for Weather Widget
https://bugs.kde.org/show_bug.cgi?id=391736 --- Comment #2 from uRohan--- Created attachment 111333 --> https://bugs.kde.org/attachment.cgi?id=111333=edit Weather Widget icon is missed in System Tray Settings Entries -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 354492] The panel is visually frozen
https://bugs.kde.org/show_bug.cgi?id=354492 --- Comment #14 from Nick--- (In reply to Nick from comment #13) > I've disabled docky to see if that's triggering the problem. Yep, no further problems since uninstalling Docky. I guess it was a conflict between Docky and KDE/Plasma. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 391736] New: Request: Icons for Weather Widget
https://bugs.kde.org/show_bug.cgi?id=391736 Bug ID: 391736 Summary: Request: Icons for Weather Widget Product: Breeze Version: 5.12.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: navigator.ro...@gmail.com CC: kain...@gmail.com Target Milestone: --- Created attachment 111331 --> https://bugs.kde.org/attachment.cgi?id=111331=edit Weather Widget icon is missed in Plasma Widgets Gallery OS: openSUSE Tumbleweed 20180309 KDE Plasma Version: 5.12.3 KDE Frameworks Version: 5.43.0 Qt Version: 5.10.0 Please add the Weather Widget icon. Weather Widget is a popular plasmoid for showing weather information from yr.no and Open Weather Map servers (https://store.kde.org/p/998917/; https://github.com/kotelnik/plasma-applet-weather-widget). The icon is included in plasmoid as .svg and you can find it here: https://github.com/kotelnik/plasma-applet-weather-widget/tree/master/package/contents/images Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 391736] Request: Icons for Weather Widget
https://bugs.kde.org/show_bug.cgi?id=391736 --- Comment #1 from uRohan--- Created attachment 111332 --> https://bugs.kde.org/attachment.cgi?id=111332=edit Weather Widget icon is missed in System Tray Settings General -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391382] Trojita with watchFolders=all or watchFolders=subscribed crash
https://bugs.kde.org/show_bug.cgi?id=391382 --- Comment #4 from Pali Rohár--- It is strange that I can reproduce it just against one server, local process via ssh. All other configurations IMAP via TCP, or local process via ssh to other servers do not hit. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 358485] CardDAV support
https://bugs.kde.org/show_bug.cgi?id=358485 char...@mcevoy.com changed: What|Removed |Added CC||char...@mcevoy.com -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391382] Trojita with watchFolders=all or watchFolders=subscribed crash
https://bugs.kde.org/show_bug.cgi?id=391382 --- Comment #3 from Jan Kundrát--- It looks like there's a race between the time the mailboxes get re-created in response to LIST, and the time CALL_LATER takes effect. I however don't understand how it's possible that I cannot reproduce this. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kactivities-stats] [Bug 391712] Application Launcher crashes plasma
https://bugs.kde.org/show_bug.cgi?id=391712 Ivan Čukićchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Ivan Čukić --- Fixed in master. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 381154] Certain notifications freeze plasma
https://bugs.kde.org/show_bug.cgi?id=381154 Aleksey Kontsevichchanged: What|Removed |Added CC||akontsev...@gmail.com --- Comment #7 from Aleksey Kontsevich --- (In reply to kyrimis from comment #6) > The problem is still there in plasma 5.12.2. And in Plasma 5.12.3 too. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391727] Trojita crashed when idling in INBOX
https://bugs.kde.org/show_bug.cgi?id=391727 --- Comment #2 from Jan Kundrát--- Can you please measure this with some heap profiler so that we know where the leak is? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391710] Trojita crash when searching
https://bugs.kde.org/show_bug.cgi?id=391710 --- Comment #1 from Jan Kundrát--- This might have something to do with that latest change wihch enabled SORT and THREAD to co-exist, which is kind of a hack. Can you please attach a complete IMAP log of this one? -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391718] Trojita hangs in infinite loop
https://bugs.kde.org/show_bug.cgi?id=391718 --- Comment #1 from Jan Kundrát--- If this is indeed an infinite loop, there's at least one cycle in the `threading` map. It would be nice to have access to the raw IMAP log. Without that log, I cannot really do anything. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 370742] Setting the scrollback size doesn't do anything
https://bugs.kde.org/show_bug.cgi?id=370742 Kurt Hindenburgchanged: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #9 from Kurt Hindenburg --- I recall fixing this - it doesn't happen w/ latest version. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 391735] New: Recurrence end after X occurrences does not count excluded dates
https://bugs.kde.org/show_bug.cgi?id=391735 Bug ID: 391735 Summary: Recurrence end after X occurrences does not count excluded dates Product: korganizer Version: 5.6.3 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: recurrence Assignee: kdepim-b...@kde.org Reporter: ostrof...@users.sourceforge.net Target Milestone: --- (I only noticed this with weekly occurrence, so I am only assuming it happens with other periods.) If I create an event with weekly recurrence, ending after 6 occurrences, it gets created correctly. If I then add an exception on the second occurrence, the last date does not get extended by one week. I claim that a date marked as an exception, is no longer an occurrence, so the end date should be extended by one more period. If you claim this works as desired, then please convert this bug to a wish list for 1) change text to "after X period" (rather than occurrences) and add an option so that adding an exception does extend the last occurrence. Perhaps this could be a pop-up when adding an exception to a recurring event by count: "Do you want to extend the final occurrence by one period?". -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 389311] disk quota icon in breeze-icons
https://bugs.kde.org/show_bug.cgi?id=389311 uRohanchanged: What|Removed |Added CC||navigator.ro...@gmail.com --- Comment #7 from uRohan --- OS: openSUSE Tumbleweed 20180309 KDE Plasma Version: 5.12.3 KDE Frameworks Version: 5.43.0 Qt Version: 5.10.0 Disk Quota icon still missed in System Tray Settings. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 391734] New: Can't export to google photos: SSL Handshake failed
https://bugs.kde.org/show_bug.cgi?id=391734 Bug ID: 391734 Summary: Can't export to google photos: SSL Handshake failed Product: digikam Version: 5.8.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Export-Google Assignee: digikam-bugs-n...@kde.org Reporter: erme...@gmail.com Target Milestone: --- Created attachment 111330 --> https://bugs.kde.org/attachment.cgi?id=111330=edit Screenshot of the error displayed after copy paste the code provided by google Hi, I have this issue since I upgraded from 5.6 to 5.7. I'm now in 5.8, using the appimage. Before, I was able to export to google photos. Then I had to reconnect to my google account: - a webbrowser open a tab which tel me that kipi-plugins need some rights - from the webbrowser, I accept: google provide me a code - I past this code in the window in digikam but It failed with the following error: An error happen during authentication "SSL handshake failed (6)" See screenshot below. I'm not sure this is related to digikam or ubuntu because I upgrade also many times my ubuntu (16.04, 17.10), etc. But it reproduce each time now. When I launch digikam from a terminal and I reproduce this bug, no additional relevant information are displayed in the console. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 390556] plasma-workspace lookandfeel needs to be ported to QtQuickControls2 to support HiDPI screens
https://bugs.kde.org/show_bug.cgi?id=390556 Nate Grahamchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Nate Graham --- Yes, Text.NativeRendering is affected by a bug for non-integer scale factors that causes this issue: https://bugreports.qt.io/browse/QTBUG-67007 The QQC2-desktop-style package works around this bug by forcing the use of Text.QtRendering, which works fine. However that only works for QQC2 controls, not QQC1 controls or PlasmaComponents controls, which is what are used in the logout overlay. I have submitted a patch to resolve that: https://phabricator.kde.org/D11244 Though this bug was originally filed against the logout overlay, it looks like it's now tracking the Look & Feel KCM. The logout overlay issue is tracked by Bug 391691, and should be fixed by my patch. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391733] Startup WM Class is wrong
https://bugs.kde.org/show_bug.cgi?id=391733 --- Comment #1 from Doug B--- Doesn't look like I can edit comments here. Just want to correct my last sentence: 'Next, I edited the desktop file for KMyMoney and found the StartupWMClass was "Kmymoney" with a capital "K". I changed "K" to lowercase "k" and the problem was solved.' -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 391733] New: Startup WM Class is wrong
https://bugs.kde.org/show_bug.cgi?id=391733 Bug ID: 391733 Summary: Startup WM Class is wrong Product: kmymoney Version: 5.0.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: w...@dougie.io Target Milestone: --- I am not 100% sure if this is an Arch AUR problem or if this something you control, so I apologize if the former is true. I noticed that when I launched KMyMoney, it didn't open in the proper icon in my favorites menu. This is the behaviour that usually happens when the WM Class is not set properly. So, I used the command, "xprop WM_CLASS" to examine the window manager class of KMyMoney. -- It was "kmymoney". Next, I edited the desktop file for KMyMoney and say it's StartupWMClass was "Kmymoney" with a capital "K". I changed "K" to lowercase "k" and the problem was solved. Cheers. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 391224] Kontact/KMail crashes when clicking security settings tab
https://bugs.kde.org/show_bug.cgi?id=391224 Matt McCannchanged: What|Removed |Added CC||matt.mccan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 362831] Do not increase brightness when entering low battery mode
https://bugs.kde.org/show_bug.cgi?id=362831 Nate Grahamchanged: What|Removed |Added CC||shaloksha...@protonmail.ch --- Comment #7 from Nate Graham --- *** Bug 381387 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 381387] display brightness is increased when come back from closed lid
https://bugs.kde.org/show_bug.cgi?id=381387 Nate Grahamchanged: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Nate Graham --- *** This bug has been marked as a duplicate of bug 362831 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 391683] Brightness 100% after screen locking
https://bugs.kde.org/show_bug.cgi?id=391683 Nate Grahamchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #2 from Nate Graham --- Can't reproduce with any lock method (timeout, keyboard shortcut, button in Kickoff, etc,), a single screen in 5.12.3 and Kubuntu 17.10. with all brightness checkboxes in Powerdevil checked. Does this issue reproduce when you don't have your external screen connected? -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 391732] New: Use Noto Sans font on Planet KDE
https://bugs.kde.org/show_bug.cgi?id=391732 Bug ID: 391732 Summary: Use Noto Sans font on Planet KDE Product: Planet KDE Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: ranveeraggar...@gmail.com Reporter: matheus4...@hotmail.com Target Milestone: --- Be consistent with the default Plasma font. Currently, it is using the Oxygen font. -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 391732] Use Noto Sans font on Planet KDE
https://bugs.kde.org/show_bug.cgi?id=391732 matheus4...@hotmail.com changed: What|Removed |Added OS|Linux |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391728] Improve ultrawide screen support: Maximize on the left or right area
https://bugs.kde.org/show_bug.cgi?id=391728 --- Comment #3 from Lionel Chauvin--- Ok, I understand. So, what is missing is the ability to add as many icon as needed in the window decoration in order to properly command the quick tiling. And the quick tiling must manage several states in order to restore a window to its previous position. This will not break more stuff ? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 386271] [Wayland] "Active window" mode does not work
https://bugs.kde.org/show_bug.cgi?id=386271 jm.ouwerk...@gmail.com changed: What|Removed |Added CC||jm.ouwerk...@gmail.com --- Comment #5 from jm.ouwerk...@gmail.com --- Note that by contrast "window under cursor" mode does work. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383631] What exactly does "Even when an external monitor is connected" do?
https://bugs.kde.org/show_bug.cgi?id=383631 Nate Grahamchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Nate Graham --- I think it's pretty clear. Just read the whole thing as a sentence: "When Laptop lid closed, , [ ] Even when an external monitor is connected." So when that setting is checked, then the action you configure for what happens when you close your laptop lid is also carried out when an external display is plugged in. If that setting is unchecked, then the action is not carried out. This is useful to, for example, dock your laptop to an external screen or docking station and close its screen, but not put it to sleep. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 391727] Trojita crashed when idling in INBOX
https://bugs.kde.org/show_bug.cgi?id=391727 --- Comment #1 from Pali Rohár--- Same situation, memory usage about 2.7 GB and crash again with following, but different backtrace: terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Thread 1 "trojita" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: Adresár alebo súbor neexistuje. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x7273342a in __GI_abort () at abort.c:89 #2 0x7304a0ad in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x73048066 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x730480b1 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x730482c9 in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #6 0x733cb9b2 in qBadAlloc() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x73449c9a in QListData::realloc_grow(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x73449d0f in QListData::append(int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x5573bb10 in QList::operator+= (this=this@entry=0x7fffa6c8, l=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:942 #10 0x5573c127 in QList::append (t=..., this=0x7fffa6c8) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:960 #11 Imap::Mailbox::ThreadingMsgListModel::threadForeach(unsigned int const&, std::function) const (this=this@entry=0x55dbb590, root=@0x7fffa73c: 6899, root@entry=@0x7fffa73c: , callback=...) at trojita/src/Imap/Model/ThreadingMsgListModel.cpp:1251 #12 0x55730fcb in Imap::Mailbox::ThreadingMsgListModel::threadAggregatedFlags (this=this@entry=0x55dbb590, root=) at trojita/src/Imap/Model/ThreadingMsgListModel.cpp:1271 #13 0x5573a78c in Imap::Mailbox::ThreadingMsgListModel::data (this=0x55dbb590, proxyIndex=..., role=963) at trojita/src/Imap/Model/ThreadingMsgListModel.cpp:307 #14 0x7357dba9 in QSortFilterProxyModel::data(QModelIndex const&, int) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x55723d39 in Imap::Mailbox::PrettyMsgListModel::data (this=, index=..., role=963) at trojita/src/Imap/Model/PrettyMsgListModel.cpp:175 #16 0x5562786f in QModelIndex::data (arole=963, this=0x7fffac80) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:426 #17 Gui::MsgItemDelegate::itemColor (this=this@entry=0x55c476a0, index=...) at trojita/src/Gui/MsgItemDelegate.cpp:47 #18 0x55627b5d in Gui::MsgItemDelegate::paint (this=0x55c476a0, painter=0x7fffaff0, option=..., index=...) at trojita/src/Gui/MsgItemDelegate.cpp:89 #19 0x74127b10 in QTreeView::drawRow(QPainter*, QStyleOptionViewItem const&, QModelIndex const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7412d597 in QTreeView::drawTree(QPainter*, QRegion const&) const () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x741320b6 in QTreeView::paintEvent(QPaintEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x73ee4278 in QWidget::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #23 0x73fcca0e in QFrame::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x740f3503 in QAbstractItemView::viewportEvent(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x74132f6c in QTreeView::viewportEvent(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x735b9741 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x73e9cb65 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x73ea4341 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x735b99e0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x73edcfda in QWidgetPrivate::sendPaintEvent(QRegion const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x73edd646 in QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x73ede34c in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*, QWidgetBackingStore*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x73ede239 in QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList const&, int, QRegion const&, QPoint const&, int, QPainter*,
[Akonadi] [Bug 391731] New: Incorrect collectiontable[remoteId] leads to "Duplicate Entry" errors
https://bugs.kde.org/show_bug.cgi?id=391731 Bug ID: 391731 Summary: Incorrect collectiontable[remoteId] leads to "Duplicate Entry" errors Product: Akonadi Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: benjamin.gira...@nebux.org CC: kdepim-b...@kde.org Target Milestone: --- akonadi version: 5.7.3 (not listed in 'version' field above) What I did: Create a toplevel folder in an IMAP account. This resulted in having two folders with a remoteId field in collectiontable beginning with the character '/' instead of '.' (the one I added, plus another one -- which may or may not be the result of restarting akonadi in an attempt to fix the previous duplicate error on the added folder). Manually fixing the entries in collectiontable to replace the wrong character '/' by the correct '.' fixed the error. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 357045] Remember brigthness level between logins
https://bugs.kde.org/show_bug.cgi?id=357045 Nate Grahamchanged: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Nate Graham --- Right, just uncheck the "Screen Brightness" setting, and then powerdevil won't mess with your brightness level at all. *** This bug has been marked as a duplicate of bug 306425 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 306425] Screen brightness reset to max after login
https://bugs.kde.org/show_bug.cgi?id=306425 Nate Grahamchanged: What|Removed |Added CC||mklape...@kde.org --- Comment #8 from Nate Graham --- *** Bug 357045 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 350258] Screen brightness is not remembered
https://bugs.kde.org/show_bug.cgi?id=350258 Nate Grahamchanged: What|Removed |Added Status|CONFIRMED |RESOLVED CC||n...@kde.org Resolution|--- |DUPLICATE --- Comment #8 from Nate Graham --- Just uncheck the "Brightness" checkboxes and then Powerdevil won't override your brightness settings on login. This works flawlessly for me in 5.12.3. *** This bug has been marked as a duplicate of bug 306425 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 306425] Screen brightness reset to max after login
https://bugs.kde.org/show_bug.cgi?id=306425 Nate Grahamchanged: What|Removed |Added CC||bugs.kde@falkensweb.com --- Comment #7 from Nate Graham --- *** Bug 350258 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 362831] Do not increase brightness when entering low battery mode
https://bugs.kde.org/show_bug.cgi?id=362831 --- Comment #6 from Nate Graham--- LOL! I mean 5.12.3, of course. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 338252] building valgrind with -flto (link time optimisation) fails
https://bugs.kde.org/show_bug.cgi?id=338252 Philippe Waroquierschanged: What|Removed |Added Attachment #88247|0 |1 is obsolete|| Attachment #88254|0 |1 is obsolete|| --- Comment #13 from Philippe Waroquiers --- Created attachment 111329 --> https://bugs.kde.org/attachment.cgi?id=111329=edit patch adding --enable-lto=yes configure option Fix 338252 - building valgrind with -flto (link time optimisation) fails * Addition of a new configure option --enable-lto=yes or --enable-lto=no Default value is --enable-lto=no, as the build is significantly slower, so is not appropriate for valgrind development : this should be used only on buildbots and/or by packagers. * Some files containins asm functions have to be compiled without lto: coregrind/m_libcsetjmp.c coregrind/m_main.c If these are compiled with lto, that gives undefined symbols at link time. The files to compile without lto are coregrind/m_libcsetjmp.c coregrind/m_main.c To compile these files with other options, a noinst target lib is defined. The objects of this library are then added to the libcoregrind. * memcheck/mc_main.c : move the handwritten asm helpers to mc_main_asm.c. This avoids undefined symbols on some toolchains. Due to this, the preprocessor symbols that activate the fast or asm memcheck helpers are moved to mc_include.h Platforms with handwritten helpers will also have the memcheck primary map defined non static. * In VEX, auxprogs/genoffsets.c also has to be compiled without lto, as the asm produced by the compiler is post-processed to produce pub/libvex_guest_offsets.h. lto not producing asm means the generation fails if we used -flto to compile this file. * all the various Makefile*am are modified to use LTO_CFLAGS for (most) targets. LTO_CFLAGS is empty when --enable-lto=no, otherwise is set to the flags needed for gcc. If --enable-lto=no, LTO_AR and LTO_RANLIB are the standard AR and RANLIB, otherwise they are the lto capable versions (gcc-ar and gcc-ranlib). * This has been tested on: debian 9.4/gcc 6.3.0/amd64+x86 rhel 7.4/gcc 6.4.0/amd64 ubuntu 17.10/gcc 7.2.0/amd64+x86 fedora26/gcc 7.3.1/s390x No regressions on the above. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 362831] Do not increase brightness when entering low battery mode
https://bugs.kde.org/show_bug.cgi?id=362831 --- Comment #5 from Piotr Kloc--- (In reply to Nate Graham from comment #3) > Can confirm with Plasma 5.13.3 that when the brightness is lower than the > level set for low battery mode, the brightness is not increased when > entering low battery mode. May I have some time with your time machine, please? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 306425] Screen brightness reset to max after login
https://bugs.kde.org/show_bug.cgi?id=306425 Nate Grahamchanged: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Nate Graham --- Can't reproduce in Plasma 5.13.3: If I set the brightness to some arbitrary level, uncheck the Brightness checkboxes in Powerdevil, and then reboot, the system come up at whatever brightness level it had when I rebooted it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391728] Improve ultrawide screen support: Maximize on the left or right area
https://bugs.kde.org/show_bug.cgi?id=391728 --- Comment #2 from Nate Graham--- Right, this is definitely a better case not for changing the Maximize button behavior, but rather for making Quick Tiling more discoverable. Most other platforms have the functionality bound to Meta+Left/Right, but we don't, I notice. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 371514] Ambiguous "Wireless power saving" in Energy Saving
https://bugs.kde.org/show_bug.cgi?id=371514 Nate Grahamchanged: What|Removed |Added Resolution|--- |FIXED CC||n...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Nate Graham --- It's powerdevil. The UI has been improved here to just say "Wireless" as a category header, and there are individual entries with more descriptive names. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 377357] configurable timer setting to turn off the keyboard's backlight
https://bugs.kde.org/show_bug.cgi?id=377357 Nate Grahamchanged: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 362831] Do not increase brightness when entering low battery mode
https://bugs.kde.org/show_bug.cgi?id=362831 Nate Grahamchanged: What|Removed |Added CC||frmdst...@gmail.com --- Comment #4 from Nate Graham --- *** Bug 377673 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 377046] Switch brightness levels smoothly, not instantaneously
https://bugs.kde.org/show_bug.cgi?id=377046 Nate Grahamchanged: What|Removed |Added Severity|normal |wishlist CC||n...@kde.org Summary|smooth brightness switch|Switch brightness levels ||smoothly, not ||instantaneously Keywords||junior-jobs -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 377673] Brightness gets brighter when low battery
https://bugs.kde.org/show_bug.cgi?id=377673 Nate Grahamchanged: What|Removed |Added Resolution|--- |DUPLICATE CC||n...@kde.org Status|UNCONFIRMED |RESOLVED --- Comment #2 from Nate Graham --- *** This bug has been marked as a duplicate of bug 362831 *** -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 362831] Do not increase brightness when entering low battery mode
https://bugs.kde.org/show_bug.cgi?id=362831 Nate Grahamchanged: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||n...@kde.org --- Comment #3 from Nate Graham --- Can confirm with Plasma 5.13.3 that when the brightness is lower than the level set for low battery mode, the brightness is not increased when entering low battery mode. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 383631] What exactly does "Even when an external monitor is connected" do?
https://bugs.kde.org/show_bug.cgi?id=383631 Nate Grahamchanged: What|Removed |Added CC||n...@kde.org Keywords||junior-jobs, usability -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 384106] Can't control brightness under X11
https://bugs.kde.org/show_bug.cgi?id=384106 Nate Grahamchanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||n...@kde.org Resolution|--- |WORKSFORME --- Comment #1 from Nate Graham --- Works for me on X11. There's almost no information in this bug, so if you can reproduce it, please read https://community.kde.org/Get_Involved/Bug_Reporting and then add enough information for us to triage it. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 391702] Amarok loses collection
https://bugs.kde.org/show_bug.cgi?id=391702 Myriam Schweingruberchanged: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Myriam Schweingruber --- Unfortunately you do not have debugging symbols installed. We would need a better backtrace, see also https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports To repair a corrupt database, you could also check this page: https://community.kde.org/Amarok/Community/MySQL#Repair_a_Corrupted_Database -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391682] Inconsistent HiDPI Rendering
https://bugs.kde.org/show_bug.cgi?id=391682 --- Comment #16 from battagli...@gmail.com --- Created attachment 111328 --> https://bugs.kde.org/attachment.cgi?id=111328=edit Correct GTK3 scaling behavior - GDK_SCALE=2 and GDK_DPI_SCALE=0.5 Correct behavior with GDK_SCALE=2 and GDK_DPI_SCALE=0.5. Note that without GDK_DPI_SCALE=0.5, fonts get double-scaled. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391682] Inconsistent HiDPI Rendering
https://bugs.kde.org/show_bug.cgi?id=391682 --- Comment #15 from battagli...@gmail.com --- Created attachment 111327 --> https://bugs.kde.org/attachment.cgi?id=111327=edit Incorrect default scaling behavior for GTK3 apps - ex: manjaro-hello and Lollypop This has KDE scaling = 2.0 and no other changes. This problem is independent of the Qt scaling problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391682] Inconsistent HiDPI Rendering
https://bugs.kde.org/show_bug.cgi?id=391682 --- Comment #14 from battagli...@gmail.com --- So below are attached two pictures of the GTK3 problem, and how I was able to fix it. Note that this is a completely separate dimension from the Qt scaling issue, and that the problem is for all GTK3 apps, not only the Manjaro-Hello one. I have pictures of manjaro-hello and Lollypop for comparison. The first picture is what the two apps look like with KDE's Display settings set to scale=2.0. Setting PLASMA_USE_QT_SCALING=true here makes no difference. The second picture is what I get if I set GDK_SCALE=2.0 and GDK_DPI_SCALE=0.5. Everything looks great. Setting GDK_DPI_SCALE=0.5 is necessary because if you don't, GTK widgets are scaled correctly, but fonts are double-scaled. GDK_DPI_SCALE de-scales the fonts while keeping widgets correct. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391228] [Feature Request] Put keyboard focus on page content after presse enter on location bar
https://bugs.kde.org/show_bug.cgi?id=391228 David Roscachanged: What|Removed |Added CC||kepl...@cmc.pl --- Comment #3 from David Rosca --- *** Bug 391729 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 391729] invalid scheme in the URL bar after a redirect
https://bugs.kde.org/show_bug.cgi?id=391729 David Roscachanged: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Rosca --- *** This bug has been marked as a duplicate of bug 391228 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 175051] mount .iso option in context menu
https://bugs.kde.org/show_bug.cgi?id=175051 --- Comment #16 from Nate Graham--- Right, I tested them all recently and couldn't find one that actually worked. IMHO we need this functionality built-in, not provided by unstable 3rd-party code. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391709] kwin crashs on linux mint
https://bugs.kde.org/show_bug.cgi?id=391709 Martin Flöserchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #1 from Martin Flöser --- Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391719] Window controls don't work
https://bugs.kde.org/show_bug.cgi?id=391719 Martin Flöserchanged: What|Removed |Added Resolution|--- |BACKTRACE Status|UNCONFIRMED |NEEDSINFO --- Comment #2 from Martin Flöser --- If KWin crashes, please provide the backtrace. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 391728] Improve ultrawide screen support: Maximize on the left or right area
https://bugs.kde.org/show_bug.cgi?id=391728 Martin Flöserchanged: What|Removed |Added Severity|normal |wishlist Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #1 from Martin Flöser --- We cannot change the maximize button without breaking lots of internal and external state. Furthermore what you suggest is anything but not maximize. This would be highly confusing to the userbase. A UI needs to function in an expected way. If a maximize button does random things ( I'm exaggerating on purpose) our users cannot trust the UI any more and in worst case move somewhere else. What you seem to wish for is better exposing of quick tiling. As given your description what you want is quick tile left/right. This again is a reason to not change the maximize button as the functionality already exists in other areas. -- You are receiving this mail because: You are watching all bug changes.
[KTechLab] [Bug 391730] New: ktechlab buid fails on osx
https://bugs.kde.org/show_bug.cgi?id=391730 Bug ID: 391730 Summary: ktechlab buid fails on osx Product: KTechLab Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: zoltan.pad...@gmail.com Reporter: zoltan.pad...@gmail.com CC: jul...@svg4all.de Target Milestone: --- >From issue report on mailing list: I downloaded the latest ktechlab (040) on osx sierra. I’m running macports. I use XQuartz. compile fails not able to find x11Screen, x11SetScreen. I have googled several combinations, no help there. Any suggestions? --- . . . [ 94%] Building CXX object src/CMakeFiles/ktechlab.dir/variablelabel.cpp.o [ 94%] Building CXX object src/CMakeFiles/ktechlab.dir/canvas.cpp.o /Users/***/Desktop/ktechlab-0.40.0/src/canvas.cpp:513:10: error: no member named 'x11SetScreen' in 'QPixmap' offscr.x11SetScreen(p->device()->x11Screen()); ~~ ^ /Users/***/Desktop/ktechlab-0.40.0/src/canvas.cpp:513:36: error: no member named 'x11Screen' in 'QPaintDevice' offscr.x11SetScreen(p->device()->x11Screen()); ~~~ ^ /Users/***/Desktop/ktechlab-0.40.0/src/canvas.cpp:821:17: error: no member named 'x11SetScreen' in 'QPixmap' if (p) offscr.x11SetScreen(p->device()->x11Screen()); ~~ ^ /Users/***/Desktop/ktechlab-0.40.0/src/canvas.cpp:821:43: error: no member named 'x11Screen' in 'QPaintDevice' if (p) offscr.x11SetScreen(p->device()->x11Screen()); ~~~ ^ 4 errors generated. make[2]: *** [src/CMakeFiles/ktechlab.dir/canvas.cpp.o] Error 1 make[1]: *** [src/CMakeFiles/ktechlab.dir/all] Error 2 make: *** [all] Error 2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 390632] Breeze task switcher has a transparent rectangle at the bottom
https://bugs.kde.org/show_bug.cgi?id=390632 Nate Grahamchanged: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #5 from Nate Graham --- Notably, the gray bar is visible on the bottom even if the pop-up loads from the side of the screen (e.g. if your panel is on the side). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 385040] Discover crashes in QQuickItem::isVisible() when attempting to go to home page
https://bugs.kde.org/show_bug.cgi?id=385040 Nate Grahamchanged: What|Removed |Added CC||john.wayne.corn...@gmail.co ||m --- Comment #8 from Nate Graham --- *** Bug 391725 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 391725] Discover scroll crash
https://bugs.kde.org/show_bug.cgi?id=391725 Nate Grahamchanged: What|Removed |Added CC||n...@kde.org Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 385040 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 389168] Discover reproducibly crashes in QQuickItem::isVisible() when you attempt to search while on an Application page
https://bugs.kde.org/show_bug.cgi?id=389168 Nate Grahamchanged: What|Removed |Added Resolution|UPSTREAM|DUPLICATE --- Comment #7 from Nate Graham --- *** This bug has been marked as a duplicate of bug 378339 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 378339] Crash in QQuickItem::isVisible() when removing characters in search text box
https://bugs.kde.org/show_bug.cgi?id=378339 --- Comment #29 from Nate Graham--- *** Bug 389168 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] 1384f275ab2f1ad1841753ee163af6d1b0bb952b causes problems with mounting eSATA-hdds and LUKS-containers with Dolphin
https://bugs.kde.org/show_bug.cgi?id=391706 Nate Grahamchanged: What|Removed |Added Summary|[solid] 5.43.0-2 has|1384f275ab2f1ad1841753ee163 |problems with mounting |af6d1b0bb952b causes |eSATA-hdds and |problems with mounting |LUKS-containers with|eSATA-hdds and |dolphin |LUKS-containers with ||Dolphin -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 391706] [solid] 5.43.0-2 has problems with mounting eSATA-hdds and LUKS-containers with dolphin
https://bugs.kde.org/show_bug.cgi?id=391706 Nate Grahamchanged: What|Removed |Added Ever confirmed|0 |1 CC||k...@privat.broulik.de, ||n...@kde.org Status|UNCONFIRMED |CONFIRMED Severity|normal |grave --- Comment #2 from Nate Graham --- Kai, this was apparently caused by the patch to fix the issue caused by https://cgit.kde.org/solid.git/commit/?id=1384f275ab2f1ad1841753ee163af6d1b0bb952b. Since you're somewhat familiar with this code, would you mind taking a look? Also it would be really nice to get some more tests on this code, since apparently it's pretty fragile. -- You are receiving this mail because: You are watching all bug changes.