[plasmashell] [Bug 402912] Plasma Panel Autohide does not work when KWin HideUtilityWindowsForInactive is false
https://bugs.kde.org/show_bug.cgi?id=402912 Martin Flöser changed: What|Removed |Added Product|kwin|plasmashell Component|core|Panel Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Target Milestone|--- |1.0 --- Comment #1 from Martin Flöser --- Hiding is triggered from Plasma side -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402913] Application Shortcuts Blocked by KDE
https://bugs.kde.org/show_bug.cgi?id=402913 --- Comment #2 from Markus Ewald --- I have tried to check which versions of plasma shell, frameworks and Qt I was running before. I could find the following version numbers in my distro's package manager log: Uninstalled: - kde-plasma/plasma-pa-5.13.5 - kde-frameworks/krunner-5.50.0 - dev-qt/qtquickcontrols2-5.11.1 Installed - kde-plasma/breeze-5.14.3 - kde-frameworks/krunner-5.52.0 - dev-qt/qttranslations-5.11.1 So my last update took me to different versions of the plasma shell and frameworks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402911] KWin Crash
https://bugs.kde.org/show_bug.cgi?id=402911 Martin Flöser changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 396723 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 396723] kwin crash when I close a window
https://bugs.kde.org/show_bug.cgi?id=396723 Martin Flöser changed: What|Removed |Added CC||christoph.smi...@gmail.com --- Comment #2 from Martin Flöser --- *** Bug 402911 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402906] Kwin crashed when switching mpv to fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=402906 Martin Flöser changed: What|Removed |Added Resolution|--- |BACKTRACE Status|REPORTED|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.
[frameworks-knewstuff] [Bug 402888] ghns_exclude tagged items are not actually excluded
https://bugs.kde.org/show_bug.cgi?id=402888 Nate Graham changed: What|Removed |Added CC||lei...@leinir.dk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402913] Application Shortcuts Blocked by KDE
https://bugs.kde.org/show_bug.cgi?id=402913 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- So this worked in 5.14.2? Can you verify that it didn't break with Frameworks 5.52? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402913] New: Application Shortcuts Blocked by KDE
https://bugs.kde.org/show_bug.cgi?id=402913 Bug ID: 402913 Summary: Application Shortcuts Blocked by KDE Product: plasmashell Version: 5.14.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: cy...@nuclex.org CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I am using Blender on KDE Plasma. Until recently, I was able to use shortcuts such as Alt+G, Alt+H and Alt+S inside the application. After updating to KDE Plasma 5.14.3, the shortcuts stopped working. They are still assigned in Blender and they are have no conflicting assignments in System Settings / Global Keyboard Shortcuts. If I DO assign these keys as a shortcut in KDE's System Settings, then unassign them again, they resume working in Blender. But only until the next reboot. I also tried this with a new user accoun and the problem exists there as well. STEPS TO REPRODUCE 1. Run Blender (any version, I used 2.79) on KDE Plasma 5.14.3 2. Move (G) or Scale (S) the box in the default scene 3. Press Alt+G or Alt+S to reset the box translation or scale OBSERVED RESULT Nothing happens EXPECTED RESULT Keyboard shortcuts to work (i.e. Alt+G to move the box back to the center, Alt+S to reset its scale, Alt+H to reveal hidden objects). SOFTWARE/OS VERSIONS Gentoo Linux, Kernel 4.14.90 KDE Plasma Version: 5.14.3 KDE Frameworks Version: 5.52.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION Shortcut worked for 18 months, problem appeared with recent update to KDE Plasma 5.14.3 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397391] Unusual Output from Levels Filter in Krita
https://bugs.kde.org/show_bug.cgi?id=397391 Jeremy Hollobon changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Jeremy Hollobon --- Somewhere along the line (probably Krita 4.1.1) this got fixed. As far as I can tell, it now works as expected. Big thanks to the devs for their great work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 356076] Window decorations KCM looks bad with breeze-dark
https://bugs.kde.org/show_bug.cgi?id=356076 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REOPENED|CONFIRMED --- Comment #5 from Nate Graham --- Will be fixed with https://phabricator.kde.org/D17982 -- You are receiving this mail because: You are watching all bug changes.
[ksim] [Bug 84904] size to large (half screen) after plugin change, not rezisable anymore
https://bugs.kde.org/show_bug.cgi?id=84904 joycha...@gmail.com changed: What|Removed |Added CC||joycha...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 346222] kcmshell5 kwindecoration: cannot drag button to left-most position
https://bugs.kde.org/show_bug.cgi?id=346222 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397887] Can't delete default Activity ?
https://bugs.kde.org/show_bug.cgi?id=397887 Nate Graham changed: What|Removed |Added Version Fixed In||5.12.8 CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 397887] Can't delete default Activity ?
https://bugs.kde.org/show_bug.cgi?id=397887 Nate Graham changed: What|Removed |Added Latest Commit||https://commits.kde.org/pla ||sma-desktop/eafb35076fa3e88 ||951712a7f5bed2a33ccb7b4e0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Nate Graham --- Git commit eafb35076fa3e88951712a7f5bed2a33ccb7b4e0 by Nate Graham. Committed on 06/01/2019 at 06:55. Pushed by ngraham into branch 'Plasma/5.12'. [Activities KCM] Disable delete button when there's only one activity FIXED-IN; 5.12.8 M +3-0kcms/activities/qml/activitiesTab/ActivitiesView.qml https://commits.kde.org/plasma-desktop/eafb35076fa3e88951712a7f5bed2a33ccb7b4e0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396725] Configure desktop effects dialog:reading the effect names is impossible with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=396725 Nate Graham changed: What|Removed |Added Component|kcm_lookandfeel |general -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 386216] Desktop Behavior/Desktop Effects KCM: use of QtQuickControls1 and/or PlasmaComponents labels causes blurry pixellated text with non-integer scale factors
https://bugs.kde.org/show_bug.cgi?id=386216 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from Nate Graham --- Remaining issues will be tracked at 396725. *** This bug has been marked as a duplicate of bug 396725 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 396725] Configure desktop effects dialog:reading the effect names is impossible with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=396725 Nate Graham changed: What|Removed |Added CC||pawelci...@gmail.com --- Comment #6 from Nate Graham --- *** Bug 386216 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 402837] kpat / kpatience gives an error on "Help about Freecell" (or other Solitaire variants)
https://bugs.kde.org/show_bug.cgi?id=402837 Yuri Chornoivan changed: What|Removed |Added Latest Commit||https://commits.kde.org/kpa ||t/0fd079dcfd49d4c66bc6483c3 ||6fb49f7529373ee Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Yuri Chornoivan --- Git commit 0fd079dcfd49d4c66bc6483c36fb49f7529373ee by Yuri Chornoivan. Committed on 06/01/2019 at 06:26. Pushed by yurchor into branch 'Applications/18.12'. Correct help link for the new versions of KF5 (>52) Summary: Due to me "broken" KHelpClient in KF 5.52, links in the help menu show error messages now. Test Plan: 1. Start KPat. 2. Select Freecell. 3. On the menubar, select "Help -> Help with Freecell". 4. Help for Freecell should be shown. Reviewers: #kde_games, aacid, ltoscano Reviewed By: ltoscano Subscribers: ltoscano, kde-games-devel Differential Revision: https://phabricator.kde.org/D17953 M +1-1mainwindow.cpp https://commits.kde.org/kpat/0fd079dcfd49d4c66bc6483c36fb49f7529373ee -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 398478] User Interface crashes when clip job stabilizing and adding .mlt automatically
https://bugs.kde.org/show_bug.cgi?id=398478 --- Comment #11 from Evert Vorster --- Hi there, emohr. To re-iterate from comment #3. 1. an invalid .mlt file is being generated. 2. UI crashes with invalid input. If changing the backend vid.stab in project manager clip jobs will fix #1, then maybe it's something that needs to be done. That still leaves #2... The error handling on input files of the UI needs work. Personally, I use Blender 3D to stabilize and render these days. Kind regards, -Evert- -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402848] Discover 5.14.4 crashed when clicking on Checking for updates and about 50 notifications appeared
https://bugs.kde.org/show_bug.cgi?id=402848
Matt Fagnani changed:
What|Removed |Added
CC||jgrul...@redhat.com
Component|discover|Flatpak Backend
--- Comment #5 from Matt Fagnani ---
I ran gdb plasma-discover. The segmentation fault was shown as
Thread 79 "QNetworkAccessM" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x9c9ffb40 (LWP 2647)]
0xb5c9c23b in QHttpNetworkConnectionChannel::sendRequest (this=0x9ce0b114)
at access/qhttpnetworkconnectionchannel.cpp:251
251 return protocolHandler->sendRequest();
protocolHandler and its component object had null pointers as follows.
(gdb) p protocolHandler
$1 = {d = 0x0}
(gdb) p protocolHandler.d
$2 = (QAbstractProtocolHandler *) 0x0
protocolHandler->sendRequest() seemed to be a null pointer dereference
resulting in the segmentation fault at qhttpnetworkconnectionchannel.cpp:251
I saw two other segmentation faults in gdb which occurred after the one above
involving gpgme, flatpak, and ostree on two different runs.
Thread 13 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa2969b40 (LWP 3076)]
0xa336255f in _gpgme_debug_buffer () from /lib/libgpgme.so.11
(gdb) bt
#0 0xa336255f in _gpgme_debug_buffer () at /lib/libgpgme.so.11
#1 0xa335f7dc in _gpgme_io_read () at /lib/libgpgme.so.11
#2 0xa336586e in _gpgme_get_program_version () at /lib/libgpgme.so.11
#3 0xa3350184 in gpg_get_version () at /lib/libgpgme.so.11
#4 0xa334df9d in _gpgme_set_engine_info () at /lib/libgpgme.so.11
#5 0xa3364b4e in gpgme_ctx_set_engine_info () at /lib/libgpgme.so.11
#6 0xa3215493 in () at /lib/libostree-1.so.1
#7 0xa3201f53 in () at /lib/libostree-1.so.1
#8 0xa31a5c46 in () at /lib/libostree-1.so.1
#9 0xa31ae378 in () at /lib/libostree-1.so.1
#10 0xa31aec3a in ostree_repo_verify_summary () at /lib/libostree-1.so.1
#11 0xa31d09c1 in ostree_repo_remote_fetch_summary_with_options ()
at /lib/libostree-1.so.1
#12 0xa31a88f2 in ostree_repo_remote_fetch_summary () at /lib/libostree-1.so.1
#13 0xa33f5ae1 in () at /lib/libflatpak.so.0
#14 0xa33f62e4 in () at /lib/libflatpak.so.0
#15 0xa343b4ea in flatpak_installation_list_remote_refs_sync ()
at /lib/libflatpak.so.0
#16 0xa343b7ae in flatpak_installation_list_installed_refs_for_update ()
at /lib/libflatpak.so.0
#17 0xa34ac059 in () at /usr/lib/qt5/plugins/discover/flatpak-backend.so
#18 0xb5704af0 in QThreadPoolThread::run() (this=)
at thread/qthreadpool.cpp:101
#19 0xb570d7e9 in QThreadPrivate::start(void*) (arg=)
at thread/qthread_unix.cpp:367
#20 0xb4f035de in start_thread (arg=) at pthread_create.c:486
#21 0xb531997a in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
(gdb) bt
#0 0xa336255f in _gpgme_debug_buffer () at /lib/libgpgme.so.11
#1 0xa335f7dc in _gpgme_io_read () at /lib/libgpgme.so.11
#2 0xa336586e in _gpgme_get_program_version () at /lib/libgpgme.so.11
#3 0xa3350184 in gpg_get_version () at /lib/libgpgme.so.11
#4 0xa334df9d in _gpgme_set_engine_info () at /lib/libgpgme.so.11
#5 0xa3364b4e in gpgme_ctx_set_engine_info () at /lib/libgpgme.so.11
#6 0xa3215493 in () at /lib/libostree-1.so.1
#7 0xa3201f53 in () at /lib/libostree-1.so.1
#8 0xa31a5c46 in () at /lib/libostree-1.so.1
#9 0xa31ae378 in () at /lib/libostree-1.so.1
#10 0xa31aec3a in ostree_repo_verify_summary () at /lib/libostree-1.so.1
#11 0xa31d09c1 in ostree_repo_remote_fetch_summary_with_options ()
at /lib/libostree-1.so.1
#12 0xa31a88f2 in ostree_repo_remote_fetch_summary () at /lib/libostree-1.so.1
#13 0xa33f5ae1 in () at /lib/libflatpak.so.0
#14 0xa33f62e4 in () at /lib/libflatpak.so.0
#15 0xa343b4ea in flatpak_installation_list_remote_refs_sync ()
at /lib/libflatpak.so.0
#16 0xa343b7ae in flatpak_installation_list_installed_refs_for_update ()
at /lib/libflatpak.so.0
#17 0xa34ac059 in () at /usr/lib/qt5/plugins/discover/flatpak-backend.so
#18 0xb5704af0 in QThreadPoolThread::run() (this=)
at thread/qthreadpool.cpp:101
#19 0xb570d7e9 in QThreadPrivate::start(void*) (arg=)
at thread/qthread_unix.cpp:367
#20 0xb4f035de in start_thread (arg=) at pthread_create.c:486
--Type for more, q to quit, c to continue without paging--
#21 0xb531997a in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:108
Thread 13 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xa296ab40 (LWP 5956)]
0xa335e55f in _gpgme_debug_buffer (lvl=7, fmt=0xa3365b11 "%s: check: %s",
func=0xa3367b97 "_gpgme_io_read", buffer=0xa2969afc "", len=4294967295)
at debug.c:393
393 val = buffer[idx++];
I noticed discover output various errors for firefox, kde, gnome flatpak
remotes I had added months ago using the flatpak cli. I removed the firefox,
kde, gnome flatpak remotes in groups one at a time using flatpak remo
[systemsettings] [Bug 401310] System Settings crash when I download new Themes
https://bugs.kde.org/show_bug.cgi?id=401310 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[artwork] [Bug 115575] mark this feed/s read icons are the same
https://bugs.kde.org/show_bug.cgi?id=115575 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402442] kwin_x11 segfaults after 18.04->18.10 upgrade
https://bugs.kde.org/show_bug.cgi?id=402442 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 87928] No icon for Konqueror Extension Manager
https://bugs.kde.org/show_bug.cgi?id=87928 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 401553] Can't "View Document" with question mark in filename
https://bugs.kde.org/show_bug.cgi?id=401553 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[artwork] [Bug 69814] Kolf: new game button icon not clear enough (usability)
https://bugs.kde.org/show_bug.cgi?id=69814 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402448] Krita resolution issue
https://bugs.kde.org/show_bug.cgi?id=402448 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 400672] Add feature to export/save selected entries only to a new bibtex file
https://bugs.kde.org/show_bug.cgi?id=400672 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402912] Plasma Panel Autohide does not work when KWin HideUtilityWindowsForInactive is false
https://bugs.kde.org/show_bug.cgi?id=402912 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402912] New: Plasma Panel Autohide does not work when KWin HideUtilityWindowsForInactive is false
https://bugs.kde.org/show_bug.cgi?id=402912 Bug ID: 402912 Summary: Plasma Panel Autohide does not work when KWin HideUtilityWindowsForInactive is false Product: kwin Version: 5.14.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: oyvi...@everdot.org Target Milestone: --- 1. Set panel to auto-hide 2. Set HideUtilityWindowsForInactive to unchecked/false with Systemsettings -> Window management -> Window actions and behavior -> [ ] Hide utility windows for inactive applications. This setting changes $HOME/.config/kwinrc [Windows] section setting HideUtilityWindowsForInactive This setting makes panel auto-hiding stop working. It reappears switching between windows by clicking on them or by changing with alt-tab and then it's stuck, forever, until mouse pointer is hoovered over the panel. Changing HideUtilityWindowsForInactive back to true fixes this. However, having this true hides the utility windows - as intended. These windows are sometimes useful, smplayer's playlist is one such window. Open smplayer and the playlist and dolphin and try to drag files from dolphin to the playlist with this setting and You can't because the playlist is gone the moment you click dolphin. There's other reasons why I don't want this setting. The current situation is that I can use a kwin setting I don't want and have auto-hiding panel(s) or have working auto-hide and utility windows go away when I need them. XFCE4 does not have this problem. While kwin setting is what triggers this it's probably an effect of plasmashell/the way the panel works. Please let me know if I can provide more information and how to gather it if that is the case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402911] New: KWin Crash
https://bugs.kde.org/show_bug.cgi?id=402911 Bug ID: 402911 Summary: KWin Crash Product: kwin Version: 5.14.4 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: christoph.smi...@gmail.com Target Milestone: --- Application: kwin_x11 (5.14.4) (Compiled from sources) Qt Version: 5.12.0 Frameworks Version: 5.45.0 Operating System: Linux 4.12.14-lp150.12.28-default x86_64 Distribution: "openSUSE Leap 15.0" -- Information about the crash: - What I was doing when the application crashed: I installed stellarium using Yast this afternoon, and also added Chrome using the google repositories, and also latte-dock (which might be the main problem).. I also tried configuring spamassassin (with no luck) so I am afraid that I caused some conflicts with Kwin... I am unskilled with Linux although I have tinkered with it off and on for years. I would like to help resolve this issue... After installing these apps i started having KWIN crashes when clicking on the plasma panel... to close open windows... email me if you need anything more from me... thanks The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa0cbde3940 (LWP 3580))] Thread 6 (Thread 0x7fa092986700 (LWP 3593)): #0 0x7fa0c46e989d in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa0c79a87a4 in ?? () from /usr/lib64/libQt5Script.so.5 #2 0x7fa0c79a87e9 in ?? () from /usr/lib64/libQt5Script.so.5 #3 0x7fa0c46e3559 in start_thread () from /lib64/libpthread.so.0 #4 0x7fa0cb75681f in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fa093bc7700 (LWP 3592)): #0 0x7fa0cb74c176 in ppoll () from /lib64/libc.so.6 #1 0x7fa0c8cd3991 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fa08c000d18) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7fa08c000d18, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7fa0c8cd509e in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fa0c8c7922a in QEventLoop::exec (this=this@entry=0x7fa093bc6c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fa0c8aa0fda in QThread::exec (this=this@entry=0x7fa0ac00b370) at thread/qthread.cpp:531 #7 0x7fa0c31086b5 in QQmlThreadPrivate::run (this=0x7fa0ac00b370) at /usr/src/debug/libqt5-qtdeclarative-5.12.0-lp150.1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #8 0x7fa0c8aa2782 in QThreadPrivate::start (arg=0x7fa0ac00b370) at thread/qthread_unix.cpp:361 #9 0x7fa0c46e3559 in start_thread () from /lib64/libpthread.so.0 #10 0x7fa0cb75681f in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fa0a8f35700 (LWP 3590)): #0 0x7fa0cb74c176 in ppoll () from /lib64/libc.so.6 #1 0x7fa0c8cd3991 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fa0ad18) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7fa0ad18, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7fa0c8cd509e in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fa0c8c7922a in QEventLoop::exec (this=this@entry=0x7fa0a8f34c50, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fa0c8aa0fda in QThread::exec (this=this@entry=0x5561a2e7cfc0) at thread/qthread.cpp:531 #7 0x7fa0c31086b5 in QQmlThreadPrivate::run (this=0x5561a2e7cfc0) at /usr/src/debug/libqt5-qtdeclarative-5.12.0-lp150.1.1.x86_64/src/qml/qml/ftw/qqmlthread.cpp:148 #8 0x7fa0c8aa2782 in QThreadPrivate::start (arg=0x5561a2e7cfc0) at thread/qthread_unix.cpp:361 #9 0x7fa0c46e3559 in start_thread () from /lib64/libpthread.so.0 #10 0x7fa0cb75681f in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fa0ab414700 (LWP 3585)): #0 0x7fa0cb74c176 in ppoll () from /lib64/libc.so.6 #1 0x7fa0c8cd3991 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7fa0a400a488) at kernel/qcore_unix.cpp:132 #3 qt_safe_poll (fds=0x7fa0a400a488, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:153 #4 0x7fa0c8cd509e in QEventDispatcherUNIX::processEvents (this=, flags=...) at kernel/qeventdispatcher_unix.cpp:500 #5 0x7fa0c8c7922a in QEventLoop::exec (this=this@entry=0x7fa0ab413c40, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7fa0c8aa0fda in QThread::exec (this=) at thread/qthread.cpp:531 #7 0x7fa0c1f78d55 in ?? () from /u
[Breeze] [Bug 402910] New: Need preferences-desktop-navigation icon
https://bugs.kde.org/show_bug.cgi?id=402910 Bug ID: 402910 Summary: Need preferences-desktop-navigation icon Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: n...@kde.org CC: kain...@gmail.com Target Milestone: --- Created attachment 117302 --> https://bugs.kde.org/attachment.cgi?id=117302&action=edit Navigation icon This icon needs to connote navigation somehow. The existing `preferences-system-windows-effect-flipswitch` icon looks pretty good for this IMO; see attachment. However it's a 64px applet icon. We need a 32px preferences icon. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402909] My drawing will not finish rendering. It will not let me draw or save. please help.
https://bugs.kde.org/show_bug.cgi?id=402909 Raghavendra kamath changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||ra...@raghukamath.com Status|REPORTED|NEEDSINFO --- Comment #1 from Raghavendra kamath --- Does it say waiting for operation with a progress bar? you need to provide us with more information, to solve this -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 402909] New: My drawing will not finish rendering. It will not let me draw or save. please help.
https://bugs.kde.org/show_bug.cgi?id=402909 Bug ID: 402909 Summary: My drawing will not finish rendering. It will not let me draw or save. please help. Product: krita Version: 4.1.7 Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: justna...@yahoo.com Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402907] After retrurning from virtual terminal (textmode) to graphics mode the gui hangs for about 20sec
https://bugs.kde.org/show_bug.cgi?id=402907 --- Comment #2 from slartibar...@gmail.com --- Created attachment 117301 --> https://bugs.kde.org/attachment.cgi?id=117301&action=edit kwin crash report -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402907] After retrurning from virtual terminal (textmode) to graphics mode the gui hangs for about 20sec
https://bugs.kde.org/show_bug.cgi?id=402907 --- Comment #1 from slartibar...@gmail.com --- i managed to get a crash report with my testuseraccount (the one displaying the popup of kwin being restarted) See attachments -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 402539] look for offline Maxima documentation
https://bugs.kde.org/show_bug.cgi?id=402539 --- Comment #2 from John Scott --- (In reply to Nikita Sirgienko from comment #1) That'd be great. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 402908] New: system logout / suspend battery settings not working when second, additional monitor is hooked up via HDMI
https://bugs.kde.org/show_bug.cgi?id=402908 Bug ID: 402908 Summary: system logout / suspend battery settings not working when second, additional monitor is hooked up via HDMI Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Dev Edition [stable] Assignee: neon-b...@kde.org Reporter: riks...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY when an additional external monitor is hooked up to the system (eg with a laptop and an extra screen), the timeout battery settings do not seem to work. Eg my battery settings are to suspend after 30 minutes, which works when i am using just my laptop, but when i add an additional external screen via HDMI, the system logs out after 5min, and there seems to be nothing i can do to change that (the settings remain to show 'suspend after 30min'). STEPS TO REPRODUCE 1. install KDE neon package on laptop 2. set battery settings to suspend or log out after a longer time, eg 30min 3. hook up a tv via HDMI as a 2nd monitor OBSERVED RESULT system logs out after 5min or so EXPECTED RESULT system suspends after 30min SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: latest KDE Neon stable release KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402907] New: After retrurning from virtual terminal (textmode) to graphics mode the gui hangs for about 20sec
https://bugs.kde.org/show_bug.cgi?id=402907
Bug ID: 402907
Summary: After retrurning from virtual terminal (textmode) to
graphics mode the gui hangs for about 20sec
Product: plasmashell
Version: 5.14.4
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: slartibar...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
I am using an (older) nvidia grahics card with the 390.87 driver (single
graphics card) on a desktop machine with the latest-testing fedora 29 updates
and plasma5 desktop.
I noticed, that when i switch over to a virtual console (textmode) and going
back to graphics mode (Ctrl-Alt-F1) the screen is properly redrawn, but any
input like mouse clicks for context-menu or dragging a window do not work any
more.
This problem/freeze stays for about 15 to 20 seconds, then all is back to
normal.
I created a second useraccount just for testing purposes (for fresh configs)
and tried the same: After returning from textmode, the gui has a problem and
indicates this in a popup in the taskbar:
"desktop effects were restarted due to a graphics reset"
and all is fine again - this takes way less than the above 15-20secs!
Another test with the former, problematic account never shows this popup at
all. I tried again, this time disabling the compositor (Alt-Shift F12, no more
shadow-decorations on windows for example) first.
Returning from textmode gives an immediate usable gui again, although without
compositing effects. If you now switch them on using the Alt-Shift-F12
shortcut, then the 15-20second penalty hits you again...
I discovered, that in those 15-20seconds the process:
"/usr/libexec/Xorg -nolisten tcp -auth
/var/run/sddm/{b67ef872-33b8-42a5-8a0b-0b8f681c717d} -background none -noreset
-displayfd 17 -seat seat0 vt1"
took on between 60 to 75% of cpu time (on a 8 core machine) for the exact
15-20seconds waiting penalty - something that did not happen with the
previously mentioned test useraccount (and switching from text to gui)
Questions:
- what kind of logfiles can i provide to narrow down the problem?
- is there any config files we could tweak, so that the gui recovers more
quickly? (see testuser-account above and the popup-hint)
Good thing this is easily reproducible, and besides switching between text/gui
i haven't seen any other defects - so i don't think of a configuration problem.
Moreover, this switching has worked before without any time-penalties of the
compositor
Any help is appreciated
--
You are receiving this mail because:
You are watching all bug changes.
[Systemd KCM] [Bug 361558] No clear way to run Systemd KCM from terminal if systemsettings5 not installed
https://bugs.kde.org/show_bug.cgi?id=361558 --- Comment #7 from Rex Dieter --- sorry, typo, make that: kcmshell5 systemd -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 361558] No clear way to run Systemd KCM from terminal if systemsettings5 not installed
https://bugs.kde.org/show_bug.cgi?id=361558 Rex Dieter changed: What|Removed |Added CC||rdie...@gmail.com --- Comment #6 from Rex Dieter --- To answer the original query: kcmshell systemd should do the trick. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 339513] kget should remember columns' widths on reopen
https://bugs.kde.org/show_bug.cgi?id=339513 --- Comment #9 from Wolfgang Bauer --- And speaking generally, patches should better be proposed on phabricator.kde.org (or reviewboard.kde.org in the past) to have them reviewed properly. Adding them to some bug report just tends to them getting lost, forgotten, or overlooked, especially if new people take over... -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 339513] kget should remember columns' widths on reopen
https://bugs.kde.org/show_bug.cgi?id=339513 Wolfgang Bauer changed: What|Removed |Added CC||wba...@tmo.at --- Comment #8 from Wolfgang Bauer --- (In reply to Linux User #330250 from comment #7) > Why is this fix not yet merged upstream in the kget sources? Who reads–or > rather doesn't read–this bug tracker? I do read it, but I didn't get notified of new comments in this bug report. But it actually is something that bothered me as well since years anyway. But, the proposed fix is not completely working. It causes a new problem, because if you hide a column via the list header's right-click context menu, this is remembered as well now. Good thing in principle of course, but the initial state of the menu is wrong then, i.e. it shows up as activated on next start although it is hidden (the state is just inverted in that case). I do have a fix ready for that as well, but that shows that I probably should think more about whether this is actually the right way to fix it or there's a better one. And I haven't found the time to do that yet, sorry. It is on my TODO list, but I also preferred to fix regressions in the KF5 port for now. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 400345] [PATCH] perl syntax highlighting: add labels
https://bugs.kde.org/show_bug.cgi?id=400345 Dominik Haumann changed: What|Removed |Added Summary|perl syntax highlighting: |[PATCH] perl syntax |add labels |highlighting: add labels -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402906] New: Kwin crashed when switching mpv to fullscreen mode
https://bugs.kde.org/show_bug.cgi?id=402906
Bug ID: 402906
Summary: Kwin crashed when switching mpv to fullscreen mode
Product: kwin
Version: 5.14.4
Platform: openSUSE RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kwin-bugs-n...@kde.org
Reporter: hiwatari.se...@gmail.com
Target Milestone: ---
Application: kwin_x11 (5.14.4)
Qt Version: 5.12.0
Frameworks Version: 5.53.0
Operating System: Linux 4.19.11-1-default x86_64
Distribution: "openSUSE Tumbleweed"
-- Information about the crash:
- Custom settings of the application:
ScaleMethod: Accurate
RenderingBackend: OpenGL 3.1
TearingPrevention: Automatic
Allow applications to block compositing: yes
Two screens (2560 x 1440)
4 virtual desktops (1 row, 4 columns)
Desktop effect: Wobbly Windows
- What I was doing when the application crashed:
I was using mpv 0.29.1.
I moved its window and double-clicked it to switch mpv to fullscreen mode. (It
was quite fast, so the wobble effect might have still been "playing")
I was on the 4th virtual desktop when it happened.
Since the last setting ("Allow applications to block compositing") is set to
yes, kwin stops compositing, when mpv is switched to fullscreen mode.
This normally flickers for a couple of frames and then continues to work.
Extremely seldomly, kwin crashes during this transition. (This is such a case)
I don't know if it's related or if it's a kwin bug, but sometimes when I
double-click mpv to switch into full-screen mode, mpv's window frame
disappears, but the window stays the same size and doesn't actually go
fullscreen.
The crash does not seem to be reproducible.
-- Backtrace:
Application: KWin (kwin_x11), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f08ec8d7600 (LWP 1331))]
Thread 18 (Thread 0x7f08a57fa700 (LWP 2797)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08e09c2ac3 in () at /usr/lib64/dri/radeonsi_dri.so
#2 0x7f08e09c2817 in () at /usr/lib64/dri/radeonsi_dri.so
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4 0x7f08f4b32ccf in clone () at /lib64/libc.so.6
Thread 17 (Thread 0x7f08a4ff9700 (LWP 1491)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08f314609a in () at /usr/lib64/libQt5Script.so.5
#2 0x7f08f31460bb in () at /usr/lib64/libQt5Script.so.5
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4 0x7f08f4b32ccf in clone () at /lib64/libc.so.6
Thread 16 (Thread 0x7f08a5ffb700 (LWP 1476)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08e09c2ac3 in () at /usr/lib64/dri/radeonsi_dri.so
#2 0x7f08e09c2817 in () at /usr/lib64/dri/radeonsi_dri.so
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4 0x7f08f4b32ccf in clone () at /lib64/libc.so.6
Thread 15 (Thread 0x7f08a67fc700 (LWP 1475)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08e09c2ac3 in () at /usr/lib64/dri/radeonsi_dri.so
#2 0x7f08e09c2817 in () at /usr/lib64/dri/radeonsi_dri.so
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4 0x7f08f4b32ccf in clone () at /lib64/libc.so.6
Thread 14 (Thread 0x7f08a6ffd700 (LWP 1474)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08e09c2ac3 in () at /usr/lib64/dri/radeonsi_dri.so
#2 0x7f08e09c2817 in () at /usr/lib64/dri/radeonsi_dri.so
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4 0x7f08f4b32ccf in clone () at /lib64/libc.so.6
Thread 13 (Thread 0x7f08a77fe700 (LWP 1473)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08e09c2ac3 in () at /usr/lib64/dri/radeonsi_dri.so
#2 0x7f08e09c2817 in () at /usr/lib64/dri/radeonsi_dri.so
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4 0x7f08f4b32ccf in clone () at /lib64/libc.so.6
Thread 12 (Thread 0x7f08a7fff700 (LWP 1472)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08e09c2ac3 in () at /usr/lib64/dri/radeonsi_dri.so
#2 0x7f08e09c2817 in () at /usr/lib64/dri/radeonsi_dri.so
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4 0x7f08f4b32ccf in clone () at /lib64/libc.so.6
Thread 11 (Thread 0x7f08c4ff9700 (LWP 1471)):
#0 0x7f08f265a4dc in pthread_cond_wait@@GLIBC_2.3.2 () at
/lib64/libpthread.so.0
#1 0x7f08e09c2ac3 in () at /usr/lib64/dri/radeonsi_dri.so
#2 0x7f08e09c2817 in () at /usr/lib64/dri/radeonsi_dri.so
#3 0x7f08f2654554 in start_thread () at /lib64/libpthread.so.0
#4
[k3b] [Bug 266461] cdrecord returned an unknown error - code 255
https://bugs.kde.org/show_bug.cgi?id=266461 --- Comment #6 from publicpant...@gmail.com --- It is still a problem. Retested using current Ubuntu 18.04 kernel. Brasero had no problem blanking and burning the ISO using the same drive. Devices --- TSSTcorp CDDVDW SH-S202N SB01 (/dev/sr0, CD-R, CD-RW, CD-ROM, DVD-ROM, DVD-R, DVD-RW, DVD-R DL, DVD+R, DVD+RW, DVD+R DL) [DVD-ROM, DVD-R Sequential, DVD-R Dual Layer Sequential, DVD-R Dual Layer Jump, DVD-RAM, DVD-RW Restricted Overwrite, DVD-RW Sequential, DVD+RW, DVD+R, DVD+R Dual Layer, CD-ROM, CD-R, CD-RW] [SAO, TAO, RAW, SAO/R96P, SAO/R96R, RAW/R16, RAW/R96P, RAW/R96R, Restricted Overwrite, Layer Jump] [%7] System --- K3b Version: 17.12.3 KDE Version: 5.44.0 Qt Version: 5.9.5 Kernel: 4.15.0-43-generic Used versions --- cdrecord: 1.1.11 cdrecord --- /usr/bin/wodim: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits. /usr/bin/wodim: Resource temporarily unavailable. Cannot get mmap for 12587008 Bytes on /dev/zero. TOC Type: 1 = CD-ROM cdrecord command: --- /usr/bin/wodim -v gracetime=2 dev=/dev/sr0 speed=4 -tao driveropts=burnfree blank=all -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 374882] Double clicks needed instead of single ones
https://bugs.kde.org/show_bug.cgi?id=374882 Johannes Zarl-Zierl changed: What|Removed |Added Latest Commit||https://commits.kde.org/kph ||otoalbum/dca2a7cab56d1632df ||33ae2dfeb5e078a2d1e853 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Johannes Zarl-Zierl --- Git commit dca2a7cab56d1632df33ae2dfeb5e078a2d1e853 by Johannes Zarl-Zierl. Committed on 05/01/2019 at 21:59. Pushed by johanneszarl into branch 'master'. Fix item activation when workspace is set up for double-clicks. When the workspace behavior is set to use double-clicks (as configured using "kcmshell5 kcm_workspace"), then kphotoalbum would require double-clicks for the following items: 1. Selecting an item in the BrowserPage (i.e. when browsing categories) 2. Selecting a person in the birthday settings page 3. Selecting a tag/category in the tag groups settings page This has now been fixed to use single clicks for the items mentioned above. M +2-2Browser/BrowserWidget.cpp M +1-1Settings/BirthdayPage.cpp M +1-1Settings/TagGroupsPage.cpp https://commits.kde.org/kphotoalbum/dca2a7cab56d1632df33ae2dfeb5e078a2d1e853 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 386291] lazy synchronization
https://bugs.kde.org/show_bug.cgi?id=386291 --- Comment #10 from stefan.mueller...@gmail.com --- Hallo Maik, if the described behaviour cannot be prevented I would like to have a stop/start screen refresh or un-/freeze database operations button. It may need to be activated first in the options menu. As soon as the button is pressed DK won't alter the refresh the thumbnail windows or the database and thus the displayed images won't be updated. Any change on the metadata shall lead either to a strikethrough of the deleted tag or mark new ones yellow (or whatever color you prefer). That would spare not little frustrations and thus save me a lot of energy. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 402905] New: KMail: Not properly updating message list
https://bugs.kde.org/show_bug.cgi?id=402905 Bug ID: 402905 Summary: KMail: Not properly updating message list Product: kmail2 Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: message list Assignee: kdepim-b...@kde.org Reporter: fred_we...@charter.net Target Milestone: --- SUMMARY Intermittently, kmail does not immediately update message list when deleting or moving messages to another folder. It often takes upwards of a minute or more, with no visual progress indicator, causing user to believe the operation has failed. STEPS TO REPRODUCE 1. Open Kmail 2. Select message(s) 3. Drag to destination folder OBSERVED RESULT Message list not updated for indefinite period. EXPECTED RESULT Message list should be updated immediately or within 1-2 seconds. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.1 KMail Version: 5.9.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 402796] Part of the GUI on the left buttom is not readable
https://bugs.kde.org/show_bug.cgi?id=402796 wpoet changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from wpoet --- I am posting a work-around/fix for the current version of korganizer shipped with Ubuntu 18.10. Ubuntu uses the Adwaita icon scheme as its default. This theme does not have the icons needed by korganizer. I switched to the oxygen theme, and installed the related packages via apt: sudo apt install oxygen-icon-theme install oxygen-icon-theme-complete kde-style-oxygen. Now korganizer finds most of the icons. (a restart might be required), and the buttom left part of the gui appears alright -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402904] New: The status bar imposes a limit on the minimum width of the window
https://bugs.kde.org/show_bug.cgi?id=402904 Bug ID: 402904 Summary: The status bar imposes a limit on the minimum width of the window Product: kate Version: 18.08.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: franciscodezuvi...@gmail.com Target Milestone: --- SUMMARY Let's say that I want a really small (20 chars width) instance of kwrite for note taking (to achieve a small 'always on top' sticky note) - it cannot be done unless the status bar is hidden. STEPS TO REPRODUCE 1. Open Kwrite 2. Make sure status bar is showing 3. Shrink horizontally as much as possible OBSERVED RESULT The status bar imposes a limit on the minimum width of the window. EXPECTED RESULT Any of the following (from easy to hard): A: Status bar should get cut B: Status bar should get shrinked C: Status bar should be scrollable I think 'B' is the current behaviour in Kate, but not sure since I'm on an old version. ADDITIONAL INFORMATION This was discussed in https://phabricator.kde.org/D17730 where the status bar was reworked for Kate (note: this is a Kwrite bug). It was concluded that the length issue was out of scope and better handled separately. This same bug was treated and fixed for gwenview and kst in 2003 and 2005 (https://bugs.kde.org/show_bug.cgi?id=69885 and https://bugs.kde.org/show_bug.cgi?id=104347). I don't use those and maybe this is completely irrelevant, but maybe there is some useful code to reuse? Who knows? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 402797] all icons missing in korganizer gui
https://bugs.kde.org/show_bug.cgi?id=402797 --- Comment #3 from wpoet --- I am posting a work-around/fix for the current version of korganizer shipped with Ubuntu 18.10. Ubuntu uses the Adwaita icon scheme as its default. This theme does not have the icons needed by korganizer. I switched to the oxygen theme, and installed the related packages via apt: sudo apt install oxygen-icon-theme install oxygen-icon-theme-complete kde-style-oxygen. Now korganizer finds most of the icons. (a restart might be required). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401757] Complex weird behavior with layers and undo history
https://bugs.kde.org/show_bug.cgi?id=401757 --- Comment #7 from Rebecca Breu --- I wonder if this is due to the same commit: Since about the same time I've had frequent segfaults when confirming moves or transformations. I haven't found a reliable set of steps to reproduce, though, but once this issue is fixed I can try again and see if I still get them. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402865] Drag Maximized window doesn't reduce it
https://bugs.kde.org/show_bug.cgi?id=402865 Vlad Zagorodniy changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402865] Drag Maximized window doesn't reduce it
https://bugs.kde.org/show_bug.cgi?id=402865 --- Comment #4 from compte.ada...@gmail.com --- (In reply to Martin Flöser from comment #3) > Please enable electricBorderMaximize It fixed it. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Systemd KCM] [Bug 361558] No clear way to run Systemd KCM from terminal if systemsettings5 not installed
https://bugs.kde.org/show_bug.cgi?id=361558 --- Comment #5 from Alexander Potashev --- ping? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 359932] Okular is very slow at opening some EPUB's
https://bugs.kde.org/show_bug.cgi?id=359932 fabi...@keemail.me changed: What|Removed |Added CC||fabi...@keemail.me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 396247] Double Trash Bin on the Desktop - Folder View
https://bugs.kde.org/show_bug.cgi?id=396247 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Nate Graham --- Though I can't find it right now, I recall the KIO changes you're talking about and Kai fixed some fallout that they caused. And now I can't reproduce this anymore on a system with the fix. Let's call it fixed! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402869] Add write permission to files copied from an MTP device
https://bugs.kde.org/show_bug.cgi?id=402869 --- Comment #2 from martonmiklos --- Hi Julian! Many thanks for pointing to it! Unfortunately it will took a while before I can test it on Ubuntu but it is good to know that it is fixed . (In reply to Julian Schraner from comment #1) > Thanks for reporting this bug. I have tried to reproduce this behavior on my > local machine connecting my phone via MTP and copied several files, and all > permissions are copied correctly for me. Your bug was most likely fixed with > our new MTP implementation (first available with Dolphin 18.12.0 and KDE > Frameworks 5.51 if I am not mistaken). > > We can sadly not backport this implementation to older versions of Dolphin, > so you'd need to update your system to the latest version of Dolphin. If the > bug does still occur with Dolphin 18.12.0, please reopen this bug report. > Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385920] [Wayland] With "resolution dependent" size, cursor is huge when hovering over Plasma desktop
https://bugs.kde.org/show_bug.cgi?id=385920 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402903] New: [Wayland] Launch feedback on taskbar does not work
https://bugs.kde.org/show_bug.cgi?id=402903 Bug ID: 402903 Summary: [Wayland] Launch feedback on taskbar does not work Product: plasmashell Version: 5.14.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager Assignee: h...@kde.org Reporter: aspotas...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY [Wayland] Launch feedback on taskbar does not work. STEPS TO REPRODUCE 1. Run wayland plasma session. 2. Click on the Google Chrome icon in taskbar's quick launch area. 3. Look at the taskbar. OBSERVED RESULT Nothing happens until the Chrome window is finally visible. EXPECTED RESULT Taskbar should display a fake button for Chrome immediately to indicate that my click on the Chrome icon is acknowledged by Plasma. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.14.4 KDE Frameworks Version: 5.53.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 307280] Option for disabling downloading chunks for preview
https://bugs.kde.org/show_bug.cgi?id=307280 ZyX changed: What|Removed |Added Version|4.3.1 |5.1 --- Comment #3 from ZyX --- Definitely still the case in 5.1.1. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402869] Add write permission to files copied from an MTP device
https://bugs.kde.org/show_bug.cgi?id=402869 Julian Schraner changed: What|Removed |Added CC||m...@xyquadrat.ch Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Julian Schraner --- Thanks for reporting this bug. I have tried to reproduce this behavior on my local machine connecting my phone via MTP and copied several files, and all permissions are copied correctly for me. Your bug was most likely fixed with our new MTP implementation (first available with Dolphin 18.12.0 and KDE Frameworks 5.51 if I am not mistaken). We can sadly not backport this implementation to older versions of Dolphin, so you'd need to update your system to the latest version of Dolphin. If the bug does still occur with Dolphin 18.12.0, please reopen this bug report. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389739] Yakuake won't open at the write spot (Wayland)
https://bugs.kde.org/show_bug.cgi?id=389739 --- Comment #2 from Alexander Potashev --- possible duplicate of bug #385882 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 395768] keyboard indicator is not working under wayland
https://bugs.kde.org/show_bug.cgi?id=395768 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 389739] Yakuake won't open at the write spot (Wayland)
https://bugs.kde.org/show_bug.cgi?id=389739 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 385882] Yakuake Wayland: when launching Yakuake the second time it appears in the middle of the screen
https://bugs.kde.org/show_bug.cgi?id=385882 Alexander Potashev changed: What|Removed |Added CC||aspotas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 402266] Baloo_file_extractor Crashes in KFileMetaData::TagLibExtractor::extract()
https://bugs.kde.org/show_bug.cgi?id=402266 Bradley Ridnour changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Bradley Ridnour --- (In reply to Alexander Stippich from comment #2) > Can you determine the file which causes the crash using balooctl monitor? > It should be a wma file. Unfortunately no. The problem recently fixed itself during a system upgrade. -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 332191] Kget crash after server authenticate cancel
https://bugs.kde.org/show_bug.cgi?id=332191 Wolfgang Bauer changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED --- Comment #18 from Wolfgang Bauer --- Sorry, it wasn't my intention to have this auto-closed... :-/ I still cannot reproduce it though. Regarding comment#13: the crash happens when kget creates the entries to hide columns in the list header's right-click context menu. So transfers.kgt shouldn't be relevant here. It might be somehow related to ~/.config/kgetrc (or ~/.kde(4)/share/config/kgetrc) though, so it might be worth a try to delete/rename that one. Judging from the backtrace, this crash must have been introduced by https://cgit.kde.org/kget.git/commit/?h=KDE/4.12&id=c6531c0334a7cab9d37cc921fb5792b4727b0611 (and it seems to fit that this originally has been reported against 4.12.2, which is the first version that includes that change). Calling populateHeaderActions() more than once (which happens since that change) is not really great, as it allocates the actions on the heap and never frees them... (but that shouldn't cause a crash) But just reverting that is probably not a good idea either, as it was a fix for another crash (bug#329957). I'll have to think more about it, not being able to reproduce makes it hard to investigate what really goes wrong though... -- You are receiving this mail because: You are watching all bug changes.
[ktouch] [Bug 402902] New: libxkbfile specified as optional, but CMake still fails if it is not present
https://bugs.kde.org/show_bug.cgi?id=402902 Bug ID: 402902 Summary: libxkbfile specified as optional, but CMake still fails if it is not present Product: ktouch Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: sebastian.gottfr...@posteo.de Reporter: spiolli...@googlemail.com Target Milestone: --- While packaging ktouch for NixOS, I found out that libxkbfile doesn't seem to be as optional as described: Although the README [1] specifies libxkbfile as optional, when libxkbfile is not provided to the build environment cmake fails: ``` builder for '/nix/store/ljm4ikyz4c785jf9qxk4q2lpbdqvarmh-ktouch-18.12.0.drv' failed with exit code 1; last 10 log lines: used as include directory in directory /build/ktouch-18.12.0/src used as include directory in directory /build/ktouch-18.12.0/src used as include directory in directory /build/ktouch-18.12.0/src used as include directory in directory /build/ktouch-18.12.0/src used as include directory in directory /build/ktouch-18.12.0/src X11_Xkbfile_LIB (ADVANCED) linked by target "ktouch" in directory /build/ktouch-18.12.0/src -- Configuring incomplete, errors occurred! ``` I could narrow it down to the call `find_package(X11)` [2], which invokes the CMake module `FindX11` and thus also searches for libxkbfile, failing if it is not found. Thus it'd be interesting whether the `find_package(X11)` could be marked optional. Otherwise the README needs some adjustments. [1] https://cgit.kde.org/ktouch.git/tree/README.md [2] https://cgit.kde.org/ktouch.git/tree/src/CMakeLists.txt#n7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401757] Complex weird behavior with layers and undo history
https://bugs.kde.org/show_bug.cgi?id=401757 --- Comment #6 from Rebecca Breu --- I can reproduce this with various recent nightly builds. There's probably other combinations of selecting/layer actions leading to this, but the steps above work every time for me. Krita Version: 4.2.0-pre-alpha (git 52afd0c) Qt Version (compiled): 5.10.0 Version (loaded): 5.10.0 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 4.9.0-8-amd64 Pretty Productname: Debian GNU/Linux 9 (stretch) Product Type: debian Product Version: 9 OpenGL Info Vendor: Intel Open Source Technology Center Renderer: "Mesa DRI Intel(R) Kabylake GT2 " Version: "3.0 Mesa 13.0.6" Shading language: 1.30 Requested format: QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(CompatibilityProfile)) Current format:QSurfaceFormat(version 3.0, options QFlags(DeprecatedFunctions), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 0, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 0, colorSpace QSurfaceFormat::ColorSpace(DefaultColorSpace), profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Version: 3.0 Supports deprecated functions true is OpenGL ES: false -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 396509] Krita randomly becomes unresponsive, or exits entirely
https://bugs.kde.org/show_bug.cgi?id=396509 Storm Engineer changed: What|Removed |Added CC||storm.ant...@gmail.com --- Comment #16 from Storm Engineer --- I have reported an issue that may be the same or related: https://bugs.kde.org/show_bug.cgi?id=401757 I did git bisect on that one. First bad commit: commit 5f91230f074be53379ba1461c6a1560d1f8aa1eb Author: Boudewijn Rempt Date: Wed Nov 28 12:44:43 2018 +0100 add a createActions method to KoToolFactoryBase -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 387536] Kdenlive Opens with Different Icon in Gnome Launcher
https://bugs.kde.org/show_bug.cgi?id=387536 Patrick Silva changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Patrick Silva --- I'm not the submitter, but the bug persists. Arch Linux kdenlive-18.12.0c-x86_64.appimage Gnome 3.30.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401757] Complex weird behavior with layers and undo history
https://bugs.kde.org/show_bug.cgi?id=401757 --- Comment #5 from Storm Engineer --- First bad commit (via git bisect): commit 5f91230f074be53379ba1461c6a1560d1f8aa1eb Author: Boudewijn Rempt Date: Wed Nov 28 12:44:43 2018 +0100 add a createActions method to KoToolFactoryBase -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 402817] Project Bin clip description not editable after adding Zone subclip
https://bugs.kde.org/show_bug.cgi?id=402817 --- Comment #2 from emohr --- With right click on the clips and click on Rename you can rename as you wish. Or click on the clip and hit F2. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401768] [feature] - show app number overlay earlier
https://bugs.kde.org/show_bug.cgi?id=401768 --- Comment #12 from tr...@yandex.com --- (In reply to Martin Flöser from comment #11) > I have no idea what unity did, I have no idea what Latte does. Please > explain things so that someone not knowing the feature can understand. Sorry, I meant, we want to detect when the user holds the Meta key in about x seconds (and when he releases the key afterwards). Is it possible? Could you please suggest some idea? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #15 from Martin Flöser --- It's still the same. Backtraces are top to bottom -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402865] Drag Maximized window doesn't reduce it
https://bugs.kde.org/show_bug.cgi?id=402865 --- Comment #3 from Martin Flöser --- Please enable electricBorderMaximize -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 401768] [feature] - show app number overlay earlier
https://bugs.kde.org/show_bug.cgi?id=401768 --- Comment #11 from Martin Flöser --- I have no idea what unity did, I have no idea what Latte does. Please explain things so that someone not knowing the feature can understand. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 255658] DevExpress website - login window is not shown
https://bugs.kde.org/show_bug.cgi?id=255658 DIESEL changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from DIESEL --- Login page looks good -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 255657] DevExpress header menu renders incorrectly
https://bugs.kde.org/show_bug.cgi?id=255657 --- Comment #6 from DIESEL --- The bug still exists with khtml 5.52.0. Menu items render stricken out but should be underlined -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 402901] New: kdesrc-build --initial-setup reports "* No installer for linux!" when executing the command on Debian 9 stable
https://bugs.kde.org/show_bug.cgi?id=402901 Bug ID: 402901 Summary: kdesrc-build --initial-setup reports "* No installer for linux!" when executing the command on Debian 9 stable Product: kdesrc-build Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mp...@kde.org Reporter: tauheed.elahee.hobb...@gmail.com Target Milestone: --- Created attachment 117300 --> https://bugs.kde.org/attachment.cgi?id=117300&action=edit Shows the error message when running the command. SUMMARY --initial-setup does not install the necessary packages for kdesrc-build to work. STEPS TO REPRODUCE 1. git clone kde:kdesrc-build 2. kdesrc-build --initial-setup Steps where found on the get involved page at https://community.kde.org/Get_Involved/development. OBSERVED RESULT The dependencies for kdesrc-build to function properly are not installed and as a result kdesrc-build does not work. EXPECTED RESULT The dependencies for kdesrc-build to be installed so that kdesrc-build can work properly. SOFTWARE/OS VERSIONS Windows: MacOS: Linux/KDE Plasma: Debian 9.6 (available in About System) KDE Plasma Version: 5.8.6 KDE Frameworks Version: 5.28.0 Qt Version: 5.7.1 ADDITIONAL INFORMATION I read through and followed the instructions on the get involved page on the KDE website to setup the get involved page. I would like to have it so that by following the instructions on the page one can setup a development environment. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 400911] [nightly build/flatpak] Icons in the toolbox change on mouseover while a third-party icon theme is used on the system
https://bugs.kde.org/show_bug.cgi?id=400911 --- Comment #7 from Patrick Silva --- (In reply to Martin Koller from comment #6) > Is there any change if you remove or rename > /usr/lib/plugins/platformthemes/libqflatpak.so > before you start kolourpaint ? No. Such file does not exist on my system. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402784] Dolphin crashes during shutdown, when stopping activity
https://bugs.kde.org/show_bug.cgi?id=402784 Elvis Angelaccio changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Elvis Angelaccio --- The problem is that when we stop the activity, the KItemListViewAccessible destructor is called *after* QApplication::exec() from the main() returns (no idea why). At that point, m_cells contains only dangling pointers and everything falls apart. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 402827] kwin_wayland segfault on monitor wakeup
https://bugs.kde.org/show_bug.cgi?id=402827 --- Comment #14 from JordanL --- "svn patch" would't play ball, so I manually applied the patch to 5.14.4 and rebuilt. The issue still occurs. The backtrace is different though, so I think this is progress. The backtrace differs from #8 onwards as far as I can see. Thread 1 (Thread 0x7fe8a331e440 (LWP 1160)): #0 0x7fe8ab0dfc70 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:28 #1 0x7fe8ab0ca672 in __GI_abort () at abort.c:79 #2 0x7fe8ab4ab7fc in () at /usr/lib/libQt5Core.so.5 #3 0x7fe8ab4aac83 in () at /usr/lib/libQt5Core.so.5 #4 0x7fe8a13b170e in QVector::at(int) const () at /usr/lib/qt/plugins/org.kde.kwin.waylandbackends/KWinWaylandDrmBackend.so #5 0x7fe8a13b170e in KWin::EglGbmBackend::prepareRenderingForScreen(int) (this=, screenId=) at /usr/src/debug/kwin-5.14.4/plugins/platforms/drm/egl_gbm_backend.cpp:342 #6 0x7fe8a034970e in KWin::SceneOpenGL::paint(QRegion, QList) (this=this@entry=0x55db40fa39a0, damage=..., toplevels=...) at /usr/src/debug/kwin-5.14.4/plugins/scenes/opengl/scene_opengl.cpp:663 #7 0x7fe8ac4897de in KWin::Compositor::performCompositing() (this=0x55db40989f30) at /usr/src/debug/kwin-5.14.4/composite.cpp:745 #8 0x7fe8ab6ccb1b in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #9 0x7fe8abaade34 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #10 0x7fe8abab5671 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7fe8ab6a18f9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #12 0x7fe8ab6f6955 in QTimerInfoList::activateTimers() () at /usr/lib/libQt5Core.so.5 #13 0x7fe8ab6f4a9e in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #14 0x7fe8a30198be in QUnixEventDispatcherQPA::processEvents(QFlags) () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so #15 0x7fe8ab6a058c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #16 0x7fe8ab6a8896 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #17 0x55db3f62d852 in main(int, char**) (argc=, argv=) at /usr/src/debug/kwin-5.14.4/main_wayland.cpp:807 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 382582] Video stutters when played
https://bugs.kde.org/show_bug.cgi?id=382582 Ernest Beinrohr changed: What|Removed |Added CC||ern...@beinrohr.sk -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398998] Allow kioclient exec to open kwrite/kate documents at specified cursor
https://bugs.kde.org/show_bug.cgi?id=398998 --- Comment #7 from Gleb Popov <6year...@gmail.com> --- (In reply to Elvis Angelaccio from comment #6) > Actually, if Kate adds support for row/column as URL parameters, we probably > wouldn't need to patch KRun at all. Sounds OK, I'll try implementing it. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 122776] todo color for items due today is same for both completed and uncompleted items
https://bugs.kde.org/show_bug.cgi?id=122776 Boian Berberov changed: What|Removed |Added CC||bberberov+...@gmail.com --- Comment #4 from Boian Berberov --- The `todoview` appears to work correctly in 5.10.0. However, this exact issue occurs in `agendaview` now. `agendaview` does not use "To-do due today color" either. That's with "To-dos use category colors" off." Could be related to #388302. Should I file a new bug or update this one? I'm on openSUSE Tumbleweed, Korganizer 5.10.0. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 398288] digikam no write access to folder
https://bugs.kde.org/show_bug.cgi?id=398288 --- Comment #13 from Steve Franks --- Sorry I stopped the process after about 9 hours. It was about 45% complete. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402842] Can not print with kate and kwrite
https://bugs.kde.org/show_bug.cgi?id=402842 --- Comment #2 from Potomac --- Created attachment 117299 --> https://bugs.kde.org/attachment.cgi?id=117299&action=edit log of cups when a print has failed here is a debug log of cups, we have much more details -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 402900] New: Kontact crashed after fetching new mail from second IMAP mailbox
https://bugs.kde.org/show_bug.cgi?id=402900 Bug ID: 402900 Summary: Kontact crashed after fetching new mail from second IMAP mailbox Product: kontact Version: 5.7.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: markus.mahlst...@posteo.de Target Milestone: --- Application: kontact (5.7.3) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-43-generic x86_64 Distribution: Ubuntu 18.04.1 LTS -- Information about the crash: - What I was doing when the application crashed: I was fetching mail from a new IMAP mailbox which I added to the already existing one - Custom settings of the application: 2 different identities for first mailbox, 1 identity for new mailbox, new IMAP account and new SMTP account configured for new mailbox The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f17fba01b80 (LWP 9032))] Thread 41 (Thread 0x7f179e7fc700 (LWP 4)): #0 0x7f17f8f0a62d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f17f20b4a98 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f17f20b546b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f17f20b564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f17f8f0a90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f17f8eaf9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f17f8cce22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f17f8cd316d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f17f41356db in start_thread (arg=0x7f179e7fc700) at pthread_create.c:463 #9 0x7f17f83b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 40 (Thread 0x7f1663099700 (LWP 9196)): #0 0x7f17f413b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fe0697fd78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f17f413b9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55fe0697fd28, cond=0x55fe0697fd50) at pthread_cond_wait.c:502 #2 0x7f17f413b9f3 in __pthread_cond_wait (cond=0x55fe0697fd50, mutex=0x55fe0697fd28) at pthread_cond_wait.c:655 #3 0x7f17e912ec95 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #4 0x7f17e912f177 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #5 0x7f17e912ff11 in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #6 0x7f17e912c5eb in () at /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5 #7 0x7f17f41356db in start_thread (arg=0x7f1663099700) at pthread_create.c:463 #8 0x7f17f83b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 39 (Thread 0x7f166e96a700 (LWP 9104)): #0 0x7ffee0be9979 in () #1 0x7ffee0be9c30 in clock_gettime () #2 0x7f17f83c5ea6 in __GI___clock_gettime (clock_id=1, tp=0x7f166e969790) at ../sysdeps/unix/clock_gettime.c:115 #3 0x7f17f8f0a221 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f17f8f08a59 in QTimerInfoList::updateCurrentTime() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f17f8f09035 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f17f8f0a67e in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f17f20b4a98 in g_main_context_prepare () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7f17f20b546b in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7f17f20b564c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x7f17f8f0a90b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f17f8eaf9ea in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f17f8cce22a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7f17f8cd316d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f17f41356db in start_thread (arg=0x7f166e96a700) at pthread_create.c:463 #15 0x7f17f83b688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 38 (Thread 0x7f166f16b700 (LWP 9094)): #0 0x7f17f413b9f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55fe0697fd78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 0x7f17f413b9f3 in __pthread_cond_wait_common (abstime=0x0, mutex=0x55fe0697fd28, cond=0x55fe0697fd50) at pthread_cond_wait.c:502 #2 0x7f17f413b9f3 in __pthread_cond_wait (cond=
[kate] [Bug 402899] New: kate does not remember the cursor position of last view or edit
https://bugs.kde.org/show_bug.cgi?id=402899 Bug ID: 402899 Summary: kate does not remember the cursor position of last view or edit Product: kate Version: 18.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: wba...@tmo.at Target Milestone: --- SUMMARY kate 17.12.3 remembered the current cursor position and restored it when reloading the text file, but since 18.04 the cursor is always at the top. Seems to only happen in an unnamed session though, when explictly saving the session and restoring it later the cursor position is restored too. If I load a file last edited with 17.12.3 in a newer version, it seems to restore the cursor position as well. STEPS TO REPRODUCE 1. run kate 2. enter some text, move/keep the cursor on some arbitrary position (other then at the beginning of the first line) and save it 3. restart kate and load the text file OBSERVED RESULT The text cursor is on the beginning of the first line. EXPECTED RESULT The cursor should be where it was left when saving/closing kate. KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.53.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION Downgrading kate to 17.12.3 makes it work again, with the very same KDE Frameworks/ktexteditor and Qt versions. Originally reported at https://bugzilla.opensuse.org/show_bug.cgi?id=1120845, but I don't think it is distribution specific. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 402896] .editorconfig makes Kate gui settings unapplicable
https://bugs.kde.org/show_bug.cgi?id=402896 Lothar changed: What|Removed |Added CC||loh@googlemail.com --- Comment #1 from Lothar --- As said*, that happens not only for .editorconfig but also for .kateconfig The requested behavior seems to me incompatible with the goals of these config files, to force special settings different from users preferences for some project. But there must be a hint to the user that some settings are forced and by which config file. * https://bugs.kde.org/show_bug.cgi?id=397956#c7 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398998] Allow kioclient exec to open kwrite/kate documents at specified cursor
https://bugs.kde.org/show_bug.cgi?id=398998 --- Comment #6 from Elvis Angelaccio --- Actually, if Kate adds support for row/column as URL parameters, we probably wouldn't need to patch KRun at all. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 398998] Allow kioclient exec to open kwrite/kate documents at specified cursor
https://bugs.kde.org/show_bug.cgi?id=398998 Elvis Angelaccio changed: What|Removed |Added CC||elvis.angelac...@kde.org --- Comment #5 from Elvis Angelaccio --- (In reply to Gleb Popov from comment #2) > (In reply to Aleix Pol from comment #1) > > I'd say best way to deal with it would be to use url semantics (e.g. > > file.cpp?l=23). Either way, this needs to be decided by kate maintainers. > > This is less comfortable to type and as I said, the main idea is to be able > to copy-paste error line produced by the compiler, like: > > /absolute/path/to/foo.cpp:123:1: > Couldn't find #include What if kioclient converts from "foo.cpp:123:1" to url parameters? This way you can just copy-paste the thing and the patch in KIO would be less invasive (no need to add/change the KRun API). -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 394517] the search-function has no results except if I search for big towns (Cannot parse osm nominatim result)
https://bugs.kde.org/show_bug.cgi?id=394517 Kevin Kofler changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #11 from Kevin Kofler --- I can confirm that this is fixed at least in 18.12.0 (I think, in some 18.08.x too, but I went directly from 18.04.3 to 18.12.0). I tested with marble-18.12.0-1.fc28 on Fedora 28. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401757] Complex weird behavior with layers and undo history
https://bugs.kde.org/show_bug.cgi?id=401757 --- Comment #4 from Storm Engineer --- I have finally found a consistent way to reproduce: Open existing file or make a new, just have two layers and at least one with content. 1; Move layer with Move tool 2; Switch back to Brush tool 3; Select the other layer and try to draw. What happens: The canvas won't update. Toggling layer visibility won't update. Undo won't work. You can't save, add new layer, or perform seve4ral other operations (Popup: Waiting for current operation). 4; Select another layer What happens: Canvas and layers suddenly update, and a bogus "Move" entry is added to history. This keeps happening every time another layer is selected. It can temporarily be fixed by doing this: 1; Toggle the visibility of a layer that is currently invisible and NOT selected (it wont't work) 2; Select the layer you toggled What happens: Canvas and layer updates, you can draw, save, undo, add layer etc. again but only until you select another layer, which will then trigger the bug again. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 402562] Discover crashes at startup
https://bugs.kde.org/show_bug.cgi?id=402562 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org --- Comment #5 from Antonio Rojas --- As per https://bugs.archlinux.org/task/61198 this is caused by flatpak 1.1.2. I can't reproduce it myself, though -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 399613] user-trash should not look like a folder at large sizes
https://bugs.kde.org/show_bug.cgi?id=399613 Sven Mauch changed: What|Removed |Added CC||s...@mauch.me -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 402793] Sometimes Dolphin crashes on Wayland when I drag a file to the breadcrumb
https://bugs.kde.org/show_bug.cgi?id=402793 Elvis Angelaccio changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
