[plasmashell] [Bug 481058] Recording windows or screens with OBS or spectacle is broken in Plasma 6 RC2 on Wayland: Failed to start pipewire screencast
https://bugs.kde.org/show_bug.cgi?id=481058 Patrick Holthaus changed: What|Removed |Added CC||patrick.holthaus@googlemail ||.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 336369] Lock screen: shut down and restart are missing
https://bugs.kde.org/show_bug.cgi?id=336369 Patrick Holthaus changed: What|Removed |Added CC||patrick.holthaus@googlemail ||.com --- Comment #57 from Patrick Holthaus --- Can I please ask (again) for all these options (including hibernate and sleep) to be user configurable? I do understand that ultimately one cannot prevent people from shutting down a computer if they have physical access to the machine there are some valid use cases where exposing these options are suboptimal, especially when touch screens are involved. Having the option to hide the functionality decreases the risk for your children to shutdown or put your computer to sleep while important processes are running (they like to touch screens!). Also if you run something in a kiosk mode and need to lock the screen exposing such options is less desirable. If there's an option to expose media playing, I don't see a problem to not display options for showing shutdown/sleep in the kcm - quite the opposite, I was surprised I didn't find them there. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432233] Not much space to read events with descriptions
https://bugs.kde.org/show_bug.cgi?id=432233 Patrick Holthaus changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Patrick Holthaus --- The solution in 5.22 is great. Thank you so much! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 437191] New: baloo_file_extractor crashes on plasma startup
https://bugs.kde.org/show_bug.cgi?id=437191 Bug ID: 437191 Summary: baloo_file_extractor crashes on plasma startup Product: frameworks-baloo Version: 5.82.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: stefan.bru...@rwth-aachen.de Reporter: patrick.holth...@googlemail.com CC: baloo-bugs-n...@kde.org, n...@kde.org Target Milestone: --- Created attachment 138477 --> https://bugs.kde.org/attachment.cgi?id=138477=edit System settings search module info SUMMARY Everytime I log into plasma, baloo_file_extractor crashes at mdb_midl_xmerge STEPS TO REPRODUCE 1. Boot system 2. Log into plasmashell (5.21.90) 3. See note that baloo_file_extractor has crashed OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux-5.12.2-gentoo (available in About System) KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Backtrace: Application: baloo_file_extractor (baloo_file_extractor), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (LWP 9251)] [KCrash Handler] #6 0x7fdc97e500e4 in mdb_midl_xmerge (idl=idl@entry=0x7f9be8c65018, merge=merge@entry=0x7f9d053ce010) at midl.c:207 #7 0x7fdc97e4752e in mdb_page_alloc (num=num@entry=1235, mp=mp@entry=0x7ffc865dcfa0, mc=, mc=) at mdb.c:2280 #8 0x7fdc97e498a7 in mdb_page_new (mp=, num=1235, flags=4, mc=0x7ffc865dd120) at mdb.c:7193 #9 mdb_node_add (mc=mc@entry=0x7ffc865dd120, indx=, key=key@entry=0x7ffc865dd500, data=0x7ffc865dd510, pgno=pgno@entry=0, flags=0) at mdb.c:7335 #10 0x7fdc97e4cef9 in mdb_cursor_put (mc=mc@entry=0x7ffc865dd120, key=key@entry=0x7ffc865dd500, data=data@entry=0x7ffc865dd510, flags=flags@entry=0) at mdb.c:6960 #11 0x7fdc97e4f5cb in mdb_put (txn=0x563d9c8ccc70, dbi=3, key=key@entry=0x7ffc865dd500, data=data@entry=0x7ffc865dd510, flags=flags@entry=0) at mdb.c:9045 #12 0x7fdc99095c8c in Baloo::PositionDB::put (this=this@entry=0x7ffc865dd600, term=..., list=...) at /var/tmp/portage/kde-frameworks/baloo-5.82.0/work/baloo-5.82.0/src/engine/positiondb.cpp:69 #13 0x7fdc990a83ce in Baloo::WriteTransaction::commit (this=) at /var/tmp/portage/kde-frameworks/baloo-5.82.0/work/baloo-5.82.0/src/engine/writetransaction.cpp:316 #14 0x7fdc9909f961 in Baloo::Transaction::commit (this=0x563d9c8c5200) at /var/tmp/portage/kde-frameworks/baloo-5.82.0/work/baloo-5.82.0/src/engine/transaction.cpp:272 #15 0x563d9c8266fc in Baloo::App::processNextFile (this=0x7ffc865ddb10) at /var/tmp/portage/kde-frameworks/baloo-5.82.0/work/baloo-5.82.0/src/file/extractor/app.cpp:109 #16 0x7fdc988047d3 in QObject::event (this=0x7ffc865ddb10, e=0x563d9ca1e580) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qobject.cpp:1314 #17 0x7fdc987d9a18 in QCoreApplication::notifyInternal2 (receiver=0x7ffc865ddb10, event=0x563d9ca1e580) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1063 #18 0x7fdc987dcf07 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x563d9c859440) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qcoreapplication.cpp:1817 #19 0x7fdc9882afc3 in postEventSourceDispatch (s=0x563d9c85ef80) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:277 #20 0x7fdc974365eb in g_main_dispatch (context=0x7fdc90005000) at ../glib-2.68.2/glib/gmain.c:3337 #21 g_main_context_dispatch (context=0x7fdc90005000) at ../glib-2.68.2/glib/gmain.c:4055 #22 0x7fdc97436898 in g_main_context_iterate (context=context@entry=0x7fdc90005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib-2.68.2/glib/gmain.c:4131 #23 0x7fdc9743694f in g_main_context_iteration (context=0x7fdc90005000, may_block=may_block@entry=1) at ../glib-2.68.2/glib/gmain.c:4196 #24 0x7fdc9882aa80 in QEventDispatcherGlib::processEvents (this=0x563d9c89d880, flags=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/src/corelib/kernel/qeventdispatcher_glib.cpp:423 #25 0x7fdc987d84eb in QEventLoop::exec (this=this@entry=0x7ffc865dda80, flags=..., flags@entry=...) at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/global/qflags.h:69 #26 0x7fdc987e07d0 in QCoreApplication::exec () at /var/tmp/portage/dev-qt/qtcore-5.15.2-r2/work/qtbase-everywhere-src-5.15.2/include/QtCore/../../src/corelib/global/qflags.h:121 #27 0x563d9c823356 in main (argc=, argv=0x7ffc865ddb10) at /var/tmp/portage/kde-frameworks/baloo-5.82.0/work/baloo-5.82.0/src/file/extractor/main.cpp:37 [Inferior 1 (process 9251)
[plasmashell] [Bug 432233] Not much space to read events with descriptions
https://bugs.kde.org/show_bug.cgi?id=432233 --- Comment #1 from Patrick Holthaus --- Created attachment 138448 --> https://bugs.kde.org/attachment.cgi?id=138448=edit Updated screenshot with plasma 5.21.90 Dear all, Thanks for working on this issue and I like the idea of using tool tips for the extended description. The applet looks a lot better now! The problem with this solution right now is that all the tool tips show up immediately upon opening the calendar (by clicking the clock) and also if I select a specific day. Sometimes (as in the attached screenshot) the tool tips cover the whole applet making it impossible to hide them without closing the entire applet. I would have expected the tips to show up on clicking or hovering the event in the list on the left. Again, many thanks for your hard work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432241] New: Plasma panel too wide
https://bugs.kde.org/show_bug.cgi?id=432241 Bug ID: 432241 Summary: Plasma panel too wide Product: plasmashell Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: patrick.holth...@googlemail.com Target Milestone: 1.0 SUMMARY Plasma panel is too wide if it has a minimum size. STEPS TO REPRODUCE 1. Create a panel with minimum width (smaller than how much the components need). 2. If you edit the panel, a "Configure..." button appears. 3. After exiting edit mode, the space for the configure button (icon) is still occupied. OBSERVED RESULT An empty space where the configure button was remains. EXPECTED RESULT The panel should resize to the desired minimum width. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (available in About System) KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Screenshots: https://imgur.com/a/MCveH99 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 432233] New: Plasma calendar applet vertical space in the event list
https://bugs.kde.org/show_bug.cgi?id=432233 Bug ID: 432233 Summary: Plasma calendar applet vertical space in the event list Product: plasmashell Version: 5.20.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: patrick.holth...@googlemail.com Target Milestone: 1.0 Created attachment 135256 --> https://bugs.kde.org/attachment.cgi?id=135256=edit Applet screenshot SUMMARY Individual events take up too much space in the widget if they contain a description. There are some events (eg MS teams invitations) that take up more than the whole vertical space and there's no room for other events on that day. A lot of space is further occupied by the time zone part of the applet. I have attached a screenshot for that matter. STEPS TO REPRODUCE 1. Enable PIM Events plugin for your calendar in the applet 2. Create (a few) events in the calendar that have a long description of multiple lines. 3. Open the widget OBSERVED RESULT Excessive amounts of scrolling are necessary to see all events, especially when multiple events have a description. If there was a method to shorten the event description to maybe one or two lines max that'd be awesome. EXPECTED RESULT Event title plus a truncated description that does not exceed a single line or maybe two. Reserve more space in favour of the event list over the space reserved for timezones. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo/Linux (available in About System) KDE Plasma Version: 5.9.20 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 372562] Allow easy switching between selected audio profile
https://bugs.kde.org/show_bug.cgi?id=372562 --- Comment #4 from Patrick Holthaus --- I would also very much appreciate a usability improvement over the current situation. Especially with all the video conferences happening nowadays, it would become very handy to quickly switch the BT profile. I don't know exactly but I have a feeling that with the recently introduced changes in plasma 5.12 beta (which are otherwise looking good!) it needs even more effort/clicks than before. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 372562] Allow easy switching between selected audio profile
https://bugs.kde.org/show_bug.cgi?id=372562 Patrick Holthaus changed: What|Removed |Added CC||patrick.holthaus@googlemail ||.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 398867] Dolphin search doesn't work in $HOME when you select "From here"
https://bugs.kde.org/show_bug.cgi?id=398867 --- Comment #13 from Patrick Holthaus --- Thank you Nate. Great to hear there is a patch already! Just because it may become useful: I tried to reproduce the bug on another system but was not successful. I don't know what could be the reason for that because both systems are more or less up-to-date although their update cycle is vastly different meaning that the other system did not get a lot of updates in between. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398867] Dolphin search doesn't work in $HOME when you select "From here"
https://bugs.kde.org/show_bug.cgi?id=398867 --- Comment #5 from Patrick Holthaus --- Sorry, that has gone missing due to editing the original post. Yes, it works perfectly when you select "Everywhere". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398867] Dolphin search doesn't work in $HOME when you select "From here"
https://bugs.kde.org/show_bug.cgi?id=398867 --- Comment #3 from Patrick Holthaus --- I thought that selecting "From here (pholthaus)" is actually the explicit variant that searches in the current folder. The only other option is "Everywhere". -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398867] Dolphin search doesn't work in $HOME when you select "From here"
https://bugs.kde.org/show_bug.cgi?id=398867 --- Comment #2 from Patrick Holthaus --- Created attachment 115140 --> https://bugs.kde.org/attachment.cgi?id=115140=edit Screenshot of search bar -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 398867] New: Dolphin search doesn't work in $HOME when you select "From here"
https://bugs.kde.org/show_bug.cgi?id=398867
Bug ID: 398867
Summary: Dolphin search doesn't work in $HOME when you select
"From here"
Product: dolphin
Version: 18.08.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: search
Assignee: dolphin-bugs-n...@kde.org
Reporter: patrick.holth...@googlemail.com
Target Milestone: ---
If you select "From here" while in the user's home directory, search doesn't
work: Even files that are obviously there and are visible in the directory
before opening the search don't appear. This happens whether you search for
filenames or content (I didn't check further options).
Some more observations:
* After a while, dolphin notifies the user that baloosearch died: "The process
for the baloosearch protocol died unexpectedly."
* balooctl status reports: "Baloo File Indexer is running.", Index looks
healthy as well.
* dolphin's terminal output contains: "Empty filename passed to function" on
searching.
* dolphin's terminal output sometimes contains: "org.kde.dolphin:
slotUrlSelectionRequested: QUrl("file:///{{homedir}}/{{selected folder}}")"
after selecting different folders (at somerandom point later?)
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 398184] Inconsistency between application launcher and leave options
https://bugs.kde.org/show_bug.cgi?id=398184 --- Comment #2 from Patrick Holthaus --- Nice, that patch looks almost identical to mine! But what I'd really like to have is configurable logout options. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 398184] New: Inconsistency between application launcher and leave options
https://bugs.kde.org/show_bug.cgi?id=398184 Bug ID: 398184 Summary: Inconsistency between application launcher and leave options Product: plasmashell Version: master Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Look & Feel package Assignee: plasma-b...@kde.org Reporter: patrick.holth...@uni-bielefeld.de CC: plasma-b...@kde.org Target Milestone: 1.0 (I'm not sure if this is the correct component, please move/reassign accordingly.) The logout dialogue offers the following options if the system is capable of these: suspend, reboot, shutdown, log out. The application launcher instead has the following options available (separated by type): Session: lock, log out, switch user System: hibernate, suspend, reboot, shutdown Wouldn't it be worth to somehow unify these interfaces in terms of functionality? I, for example, frequently get confused when pressing ctrl+alt+del because not all options appear there. I have even created a patch for myself to add the hibernate option to the logout dialogue because of frustration, see https://github.com/pholthau/gentoo-patches/blob/master/kde-plasma/plasma-workspace/enable-hibernate-in-logout.patch I can understand that we want to have simple and intuitive default options and I totally agree with that. But many users may need to frequently switch users or hibernate their system by default. Not having the options in the main leave dialogue may hinder some (including me) in their workflow. There is even an infrastructure to support a better user experience: The "Desktop Session Login and Logout" kcm already has a tick box to offer shutdown options. Why not let the user decide about every option individually? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 363585] Wrong message "Some parts of this message will not be signed"
https://bugs.kde.org/show_bug.cgi?id=363585 Patrick Holthaus <patrick.holth...@uni-bielefeld.de> changed: What|Removed |Added CC||patrick.holthaus@uni-bielef ||eld.de --- Comment #1 from Patrick Holthaus <patrick.holth...@uni-bielefeld.de> --- Same thing here. Just two remarks: * It does not happen, if I select signing plus encryption. * I'm not quite sure yet but I think it produces bad signatures if I select "Send as it is". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 362941] Java Process Is Unresponsive In System Tray - Jitsi
https://bugs.kde.org/show_bug.cgi?id=362941 Patrick Holthaus <patrick.holth...@uni-bielefeld.de> changed: What|Removed |Added CC||patrick.holthaus@uni-bielef ||eld.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 363947] kde connect: Could not mount device.
https://bugs.kde.org/show_bug.cgi?id=363947 Patrick Holthaus <patrick.holth...@uni-bielefeld.de> changed: What|Removed |Added CC||patrick.holthaus@uni-bielef ||eld.de -- You are receiving this mail because: You are watching all bug changes.
