[systemsettings] [Bug 487773] New: Nightlight not working after suspend/sleep
https://bugs.kde.org/show_bug.cgi?id=487773 Bug ID: 487773 Summary: Nightlight not working after suspend/sleep Classification: Applications Product: systemsettings Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com CC: kwin-bugs-n...@kde.org Target Milestone: --- *** After system goes into suspend, the nightlight remains "off" setting it and unsettling it does not make it behave as it should, it always stays off. STEPS TO REPRODUCE 1. go into suspend/sleep mode 2. engage it / or wait for it if configured on a certain time/location OBSERVED RESULT Nightlight remains off; cant activate it, only reboot fixes it. __ Operating System: openSUSE Tumbleweed 20240524 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-1-default (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Framework Product Name: Laptop (12th Gen Intel Core) System Version: A4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 412471] Make Do not disturb times configurable with a repeating schedule
https://bugs.kde.org/show_bug.cgi?id=412471 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #6 from Danny Medina --- *** Bug 486271 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486271] [Request] Please add a time based "do not disturb" option
https://bugs.kde.org/show_bug.cgi?id=486271 Danny Medina changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Danny Medina --- *** This bug has been marked as a duplicate of bug 412471 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486271] New: [Request] Please add a time based "do not disturb" option
https://bugs.kde.org/show_bug.cgi?id=486271 Bug ID: 486271 Summary: [Request] Please add a time based "do not disturb" option Classification: Applications Product: systemsettings Version: 6.0.4 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_notify Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com CC: k...@privat.broulik.de Target Milestone: --- Created attachment 168982 --> https://bugs.kde.org/attachment.cgi?id=168982=edit Add a from: and a to: for a time based duration. SUMMARY Allow to set a schedule for do not disturb mode ei: just like android has. OBSERVED RESULT currently Do no disturb mode activates only via screen sharing ,when screens are mirrored, and manually via shortcut. EXPECTED RESULT The ability to set a time based schedule. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 473586] New: [Wishlist] Allow workspaces only on certain screens.
https://bugs.kde.org/show_bug.cgi?id=473586 Bug ID: 473586 Summary: [Wishlist] Allow workspaces only on certain screens. Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- SUMMARY *** For users that have screens/ monitors for tasks that don't change ei: TV watching /streaming , Gaming, static tasks, but use workspaces on the other screens. *** * It would be nice to have the ability to turn off workspaces say, for screen number X or more. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 --- Comment #1 from Danny Medina --- Created attachment 148954 --> https://bugs.kde.org/attachment.cgi?id=148954=edit media player applet -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 --- Comment #3 from Danny Medina --- Created attachment 148956 --> https://bugs.kde.org/attachment.cgi?id=148956=edit Elisa options There are two options into one tick to use the tray icon to keep playing in the background after a close -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 --- Comment #2 from Danny Medina --- Created attachment 148955 --> https://bugs.kde.org/attachment.cgi?id=148955=edit media player applet menu? there are many seperate options that should be all condenced. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453986] New: Elisa tray icon + media player applet
https://bugs.kde.org/show_bug.cgi?id=453986 Bug ID: 453986 Summary: Elisa tray icon + media player applet Product: Elisa Version: 22.04.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 148953 --> https://bugs.kde.org/attachment.cgi?id=148953=edit elisa tray It would be nice if the tray icon of elisa could be integrated or merged to the media player applet, that way there would only be one icon to manage instead of the elisa's icon alongside it since its a little redundant. Also if the tray icon merge request is denied then I think the option to keep elisa running in the background should be seperate. System info| Operating System: openSUSE Tumbleweed 20220516 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Kernel Version: 5.17.5-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453678] Starup extremelly laggy and slow
https://bugs.kde.org/show_bug.cgi?id=453678 --- Comment #1 from Danny Medina --- Created attachment 148749 --> https://bugs.kde.org/attachment.cgi?id=148749=edit This is how it looks when you try to use it upon launching. This is how it looks when you try to use it upon launching.. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 453678] New: Starup extremelly laggy and slow
https://bugs.kde.org/show_bug.cgi?id=453678 Bug ID: 453678 Summary: Starup extremelly laggy and slow Product: Elisa Version: 22.04.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 148748 --> https://bugs.kde.org/attachment.cgi?id=148748=edit This is how it looks when you try to use it upon launching.. SUMMARY *** Elisa conducts a startup scan [which in my opinion should be in the options to toggle on/off] I have alot of music and i find myself having to wait almost a minute to actually operate the UI otherwise there will be alot of UI latency and sluggishness. I tried setting elisa to use direct scanning to see if the issue remained but it still does it. *** STEPS TO REPRODUCE 1. close and quit Elisa 2. launch elisa 3. behold OBSERVED RESULT Sluggishnes, click delays, top-right notification in elisa says "Scanning music..." for somewhat of a long time until it finishes. EXPECTED RESULT The UI is responsive after it finished scanning for music.. this happens every single time elisa is launched. Naturally there would be some UI sluggishness because its scanning, but it doesnt need to scan every single time i launch it, it hurts the experience. Operating System: openSUSE Tumbleweed 20220509 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.2 Kernel Version: 5.17.5-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION Nothing else pertaining to this but, as an addition, the music player clementine has the option to allow you to continue playing from the track you left off and is quick and responsive and allows you to conduct on demand scanning to not slow things down. Elisa should be able to do the same indeed, but this scanning issue is preventing that from happening [I think if you have alot of music in your home folder this happens since it scans all music upon startup] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #72 from Danny Medina --- I am able to reproduce this BUT, it happens sometimes.. its difficult to pin point exactly when. This is my system info: Operating System: openSUSE Tumbleweed 20220402 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.16.15-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450925] Jittery cursor after suspend/hibernate
https://bugs.kde.org/show_bug.cgi?id=450925 --- Comment #1 from Danny Medina --- (In reply to Danny Medina from comment #0) > I have encountered this bug, apparently it has been here for a while. Not > kde speciffic, not sure what it is but I can confirm that when the system > goes to suspend and after i turn it back on the cursor movement is > extremelly jittery and laggy. I ran a dmesg and a usb bus would say that it > disconnected. Then i would look in the touchpad settings and the touchpad > device would not be there. > > Maybe is the way it suspends? > I found out that once that happens you have to invoke a " sudo systemctl > suspend " then turn it back on and the problem would be solved immediately. > > Maybe whatever mechanism its being used to suspend can append a workarround > for this? > > The laptop that has this issue is my Thinkpad T480, with my T470 I dont > recall having this issue. > > > STEPS TO REPRODUCE > 1. wait for the system to suspend > 2. turn it back on > 3. touchpad /mouse cursor will have the issue (happens very often but i cant > say it will be 100% all the time) > > OBSERVED RESULT > If i invoke a " sudo systemctl suspend " and bring the computer back on, the > issue is gone. > If i dont the issue remains. > > Operating System: openSUSE Tumbleweed 20220225 > KDE Plasma Version: 5.24.2 > KDE Frameworks Version: 5.91.0 > Qt Version: 5.15.2 > Kernel Version: 5.16.10-1-default (64-bit) > Graphics Platform: Wayland > Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz > Memory: 31.2 GiB of RAM > Graphics Processor: Mesa Intel® UHD Graphics 620 It apperas the issue is the trackpoint?? I had to disable it in the BIOS so my mouse would work.. Havent noticed in on other DEs though.. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 451454] New: Battery levels (thresholds) reset after a 0% Drain.
https://bugs.kde.org/show_bug.cgi?id=451454 Bug ID: 451454 Summary: Battery levels (thresholds) reset after a 0% Drain. Product: Powerdevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Please allow for the charging thresholds to remain after the battery drains completely to 0. I noticed that after the battery reachers 0% (for example unattended, in a task, or w.e.) after i put it to charge the battery charging thresholds/limits reset to " always charge" an dthe limit to 100% * I have a T480 and set my thresholds 70%-80% and after the 0% battery; they're gone! STEPS TO REPRODUCE 1. Drain battery to 0% 2. plug in charger + let the PC boot ofcourse 3. go to systemsettings5 > advaced power settings > thresholds are indeed reset. (Battery levels) OBSERVED RESULT Same as stated. EXPECTED RESULT Same as stated. Operating System: openSUSE Tumbleweed 20220310 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.11-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 451452] Auto suspend activities on idle time
https://bugs.kde.org/show_bug.cgi?id=451452 --- Comment #1 from Danny Medina --- it may also help wth powersavings.. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 451452] New: Auto suspend activities on idle time
https://bugs.kde.org/show_bug.cgi?id=451452 Bug ID: 451452 Summary: Auto suspend activities on idle time Product: kactivitymanagerd Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: lyrix...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 147471 --> https://bugs.kde.org/attachment.cgi?id=147471=edit activities I use? This is a wishlist report to please allow us to set something like an auto suspend for activities that havent been used for xx ammount of time. If you guys think this is a good idea than yay, if not.. yay! but to me it is since i have been noticing on my use case that i would leave some programs open on one activity and instead of closing down everything i would manually suspend the activity until im in at that said workflow again. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450925] New: Jittery cursor after suspend/hibernate
https://bugs.kde.org/show_bug.cgi?id=450925 Bug ID: 450925 Summary: Jittery cursor after suspend/hibernate Product: Powerdevil Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- I have encountered this bug, apparently it has been here for a while. Not kde speciffic, not sure what it is but I can confirm that when the system goes to suspend and after i turn it back on the cursor movement is extremelly jittery and laggy. I ran a dmesg and a usb bus would say that it disconnected. Then i would look in the touchpad settings and the touchpad device would not be there. Maybe is the way it suspends? I found out that once that happens you have to invoke a " sudo systemctl suspend " then turn it back on and the problem would be solved immediately. Maybe whatever mechanism its being used to suspend can append a workarround for this? The laptop that has this issue is my Thinkpad T480, with my T470 I dont recall having this issue. STEPS TO REPRODUCE 1. wait for the system to suspend 2. turn it back on 3. touchpad /mouse cursor will have the issue (happens very often but i cant say it will be 100% all the time) OBSERVED RESULT If i invoke a " sudo systemctl suspend " and bring the computer back on, the issue is gone. If i dont the issue remains. Operating System: openSUSE Tumbleweed 20220225 KDE Plasma Version: 5.24.2 KDE Frameworks Version: 5.91.0 Qt Version: 5.15.2 Kernel Version: 5.16.10-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445506] New: Desktop wallpaper overlap with more than one screen connected.
https://bugs.kde.org/show_bug.cgi?id=445506 Bug ID: 445506 Summary: Desktop wallpaper overlap with more than one screen connected. Product: KScreen Version: 5.23.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 143558 --> https://bugs.kde.org/attachment.cgi?id=143558=edit Overlapped wallpaper that is supposed to go on the screen at the bottom SUMMARY *** Everytime i connect another monitor to my laptop (Lenovo Thinkpad T480) The wallpaper of the extra monitor(s) overlap with the primary desktop, also obstructing the icons. The menus on the non-primary displays also cannot be accessed, I click and nothing happens unless, I right click on the overlapped wallpaper(s). I cant provide any backtraces because i do not know where to look for this specific issue. *** STEPS TO REPRODUCE 1. Connect another display; witness. 2. Try to right click on the non-primary screens; witness no menu appearing. 3. Right click on the overlapped wallpapers; witness the menu(s) for the appropiate screen(s) appear. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211107 KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.14-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION I have a MOKIN USB-C Dock with many inputs/outputs, I also used to have a Pinebook pro Dock in which i also connected my peripherals includig my screens. And both of them had that issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444218] Upon 1-time click the PIM events will not show on the calendar.
https://bugs.kde.org/show_bug.cgi?id=444218 --- Comment #1 from Danny Medina --- Created attachment 142751 --> https://bugs.kde.org/attachment.cgi?id=142751=edit AFter clicking some random date; events now appear Purpose of this screenshot is for the sake of comparison. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444218] New: Upon 1-time click the PIM events will not show on the calendar.
https://bugs.kde.org/show_bug.cgi?id=444218 Bug ID: 444218 Summary: Upon 1-time click the PIM events will not show on the calendar. Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Digital Clock Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: 1.0 Created attachment 142750 --> https://bugs.kde.org/attachment.cgi?id=142750=edit After plasma starts "No events" SUMMARY When the digital clock is clicked and the calendar pops up, i can see the blue dots (which should be the same theme accent color ;D) but my events are not shown. It says "No events to display when it should have events to display therefore, I have to select another date for my events to show up; the events should show up everytime. STEPS TO REPRODUCE 1. kill plasmashell 2. start plasmashell & upon starting click on the digital clock & viola! "No events to display" OBSERVED RESULT I can confirm the bug reproduces that way, upon plasmashell startup. EXPECTED RESULT Same SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20211016 KDE Plasma Version: 5.23.0 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m
https://bugs.kde.org/show_bug.cgi?id=421700 --- Comment #38 from Danny Medina --- Created attachment 141512 --> https://bugs.kde.org/attachment.cgi?id=141512=edit New crash information added by DrKonqi plasmashell (5.22.5) using Qt 5.15.2 Just logged in normally on the wayland session. -- Backtrace (Reduced): #6 0x7f63a9b1e810 in QScreen::name (this=0x558977dad340) at kernel/qscreen.cpp:195 #7 0x5589772bd38a in ShellCorona::addOutput (this=this@entry=0x558977deb030, screen=, screen@entry=0x558977dad340) at /usr/src/debug/plasma5-workspace-5.22.5-1.1.x86_64/shell/shellcorona.cpp:1251 #8 0x5589772be00b in ShellCorona::load (this=) at /usr/src/debug/plasma5-workspace-5.22.5-1.1.x86_64/shell/shellcorona.cpp:701 #9 0x7f63a96d4033 in QtPrivate::QSlotObjectBase::call (a=0x7ffd3535ca60, r=0x558977deb030, this=0x558977fa9fa0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #10 doActivate (sender=0x558977f44450, signal_index=4, argv=0x7ffd3535ca60) at kernel/qobject.cpp:3886 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421700] Plasma crashed in QScreen::name()/ShellCorona::addOutput()/ShellCorona::load()/KActivities::Consumer::serviceStatusChanged after I've switched from main laptop to external m
https://bugs.kde.org/show_bug.cgi?id=421700 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440947] Option to delay shutdown prompt/poweroff activation
https://bugs.kde.org/show_bug.cgi?id=440947 --- Comment #4 from Danny Medina --- (In reply to Nate Graham from comment #3) > I understand how annoying this must be! > > The thing is, implementing the kind of delay you want needs to be > implemented at a lower level: in hardware, in upower, or in the kernel > drivers. My laptop for example already does implement this at one of those > levels. If we implemented a different delay on top of it, I would have to > press for even longer, and would risk accidentally force-shutting-down the > machine. > > Please report this issue upstream to one of the aforementioned locations. Oh ok, now i get it. Yeah ill have to do that! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 438716] Lid close leads to suspend even when external monitor is attached
https://bugs.kde.org/show_bug.cgi?id=438716 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #3 from Danny Medina --- I can confirm that this happens to me. i close the laptop lid while an external monitor i plugged in and i immediately get put on Lockscreen, then the laptop suspends. It only happens on the Wayland session, here are my specs: Operating System: openSUSE Tumbleweed 20210810 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.8-1-default (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8350U CPU @ 1.70GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics 620 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440947] Option to delay shutdown prompt/poweroff activation
https://bugs.kde.org/show_bug.cgi?id=440947 --- Comment #2 from Danny Medina --- (In reply to Méven Car from comment #1) > The option you are asking is a too niche to be implemented IMO. > > I guess what you need is not a delay (there is a delay when the shutdown > fullscreen dialog shows up) but a sound so that you can stop typing when > this happens. > > Or we could interpret keys, not arrows or enter to make a sound or dismiss > the dialog then. > > Or you could change the key association of your unconventionally placed > shutdown button in the shorctuts settings. The idea is to prevent accidental shutdowns, so a delay instead of a tap to bring up the shutdown prompt I believe would be able to squash this.. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 440947] New: Option to delay shutdown prompt/poweroff activation
https://bugs.kde.org/show_bug.cgi?id=440947 Bug ID: 440947 Summary: Option to delay shutdown prompt/poweroff activation Product: Powerdevil Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 140701 --> https://bugs.kde.org/attachment.cgi?id=140701=edit Example Keyboard Layout (not restricted to pinebookpro) Please add the option to delay the activation of the shutdown prompt. For example I have a laptop that has the power button right on top of the delete/backspace key and very frequently when I'm typing i accidentally tap the power button; only to be presented with the shutdown screen and sometimes as i continue to type the laptop shuts down due to this. Operating System: Manjaro-ARM KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.7-1-MANJARO-ARM (64-bit) Graphics Platform: Wayland Processors: 6 Memory: 3.8 GiB of RAM Graphics Processor: Mali T860 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 440067] New: Akondai Crash at start of session
https://bugs.kde.org/show_bug.cgi?id=440067 Bug ID: 440067 Summary: Akondai Crash at start of session Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: lyrix...@gmx.com Target Milestone: --- Application: akonadiserver (5.17.3 (21.04.3)) Qt Version: 5.15.2 Frameworks Version: 5.84.0 Operating System: Linux 5.13.1-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.3 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Resumed my laptop to the KDE wayland session - Unusual behavior I noticed: Attached Screens would not pick up the signal until the laptop lid was opened. After that i logged in and the crash appeared. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f78648da840 (LWP 3649))] [KCrash Handler] #6 0x55f312a5e0c3 in ?? () #7 0x7f786744af5e in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #8 0x7f786741e93f in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #9 0x7f78674219b7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #10 0x7f78674767d3 in ?? () from /lib64/libQt5Core.so.5 #11 0x7f786565980f in g_main_dispatch (context=0x55f313b07a30) at ../glib/gmain.c:3337 #12 g_main_context_dispatch (context=0x55f313b07a30) at ../glib/gmain.c:4055 #13 0x7f7865659b98 in g_main_context_iterate (context=context@entry=0x55f313b07a30, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #14 0x7f7865659c4f in g_main_context_iteration (context=0x55f313b07a30, may_block=1) at ../glib/gmain.c:4196 #15 0x7f7867475e54 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #16 0x7f786741d36b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #17 0x7f7867425650 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #18 0x55f312a543d9 in ?? () #19 0x7f7866d68b35 in __libc_start_main (main=0x55f312a53720, argc=1, argv=0x7fff56d8d468, init=, fini=, rtld_fini=, stack_end=0x7fff56d8d458) at ../csu/libc-start.c:332 #20 0x55f312a56fbe in ?? () [Inferior 1 (process 3649) detached] The reporter indicates this bug may be a duplicate of or related to bug 439597. Possible duplicates by query: bug 439991, bug 439928, bug 439916, bug 439901, bug 439800. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 439445] New: Request to toggle Bluetooth on/off via custom shortcut
https://bugs.kde.org/show_bug.cgi?id=439445 Bug ID: 439445 Summary: Request to toggle Bluetooth on/off via custom shortcut Product: Bluedevil Version: 5.22.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: system tray Assignee: now...@gmail.com Reporter: lyrix...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- I'm requesting for the Bluetooth applet or system tray icon to have a map-able shortcut to toggle Bluetooth on and off. i know most laptops have some sort of function key for this but I'm on a Desktop with a Bluetooth adapter. I thought id be convenient to map a shortcut to toggle it on and off. Scenario: You want to do some gaming and you have your Bluetooth gamepad. You then right click on the Bluetooth applet and switch it on when you can just press something like ctl+alt+b or whatever custom shortcut to toggle it on/off on the fly. -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 324840] sync notes with owncloud notes app
https://bugs.kde.org/show_bug.cgi?id=324840 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com --- Comment #6 from Danny Medina --- I would love to see this as well, as a matter of fact it would be a swell idea to sync all the nextcloud services/apps to the corresponding kde apps. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 438876] New: KDE Connect Crashes upon startup/system startup
https://bugs.kde.org/show_bug.cgi?id=438876 Bug ID: 438876 Summary: KDE Connect Crashes upon startup/system startup Product: kdeconnect Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: lyrix...@gmx.com Target Milestone: --- Application: kdeconnectd (21.04.2) Qt Version: 5.15.2 Frameworks Version: 5.83.0 Operating System: Linux 5.12.10-1-default x86_64 Windowing System: Wayland Drkonqi Version: 5.22.0 Distribution: "openSUSE Tumbleweed" -- Information about the crash: I just rebooted my system and i see that it segfaults. Everytime i log into the system it does it. It happened out of nowhere weather X11 or wayland it doesnt matter, It still happens. The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7fd8c4288d00 (LWP 2508))] [KCrash Handler] #6 QCA::Certificate::Certificate (this=, opts=..., key=..., provider=..., this=, opts=..., key=..., provider=...) at /usr/src/debug/qca-qt5-2.3.3-2.1.x86_64/src/qca_cert.cpp:1466 #7 0x7fd8c812d681 in KdeConnectConfig::generateCertificate (this=this@entry=0x7fd8c814bdf0 , certPath=...) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:347 #8 0x7fd8c812dbfc in KdeConnectConfig::loadCertificate (this=this@entry=0x7fd8c814bdf0 ) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:287 #9 0x7fd8c812e01c in KdeConnectConfig::KdeConnectConfig (this=, this=) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:92 #10 0x7fd8c812e1d5 in KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65 #11 KdeConnectConfig::instance () at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/kdeconnectconfig.cpp:65 #12 0x7fd8c81312b2 in Daemon::init (this=0x7ffe30419520) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/core/daemon.cpp:89 #13 0x7fd8c6bb009e in QObject::event (this=0x7ffe30419520, e=0x55b6500e3ba0) at kernel/qobject.cpp:1314 #14 0x7fd8c77d3a5f in QApplicationPrivate::notify_helper (this=, receiver=0x7ffe30419520, e=0x55b6500e3ba0) at kernel/qapplication.cpp:3632 #15 0x7fd8c6b83aaa in QCoreApplication::notifyInternal2 (receiver=0x7ffe30419520, event=0x55b6500e3ba0) at kernel/qcoreapplication.cpp:1063 #16 0x7fd8c6b86af7 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55b6500808a0) at kernel/qcoreapplication.cpp:1817 #17 0x7fd8c6bdba73 in postEventSourceDispatch (s=s@entry=0x55b6500b5a30) at kernel/qeventdispatcher_glib.cpp:277 #18 0x7fd8c505e80f in g_main_dispatch (context=0x55b6500d4f40) at ../glib/gmain.c:3337 #19 g_main_context_dispatch (context=0x55b6500d4f40) at ../glib/gmain.c:4055 #20 0x7fd8c505eb98 in g_main_context_iterate (context=context@entry=0x55b6500d4f40, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #21 0x7fd8c505ec4f in g_main_context_iteration (context=0x55b6500d4f40, may_block=1) at ../glib/gmain.c:4196 #22 0x7fd8c6bdb0f4 in QEventDispatcherGlib::processEvents (this=0x55b6500b99d0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #23 0x7fd8c6b824bb in QEventLoop::exec (this=this@entry=0x7ffe30419410, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #24 0x7fd8c6b8a790 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #25 0x7fd8c6fe11fc in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #26 0x7fd8c77d39d5 in QApplication::exec () at kernel/qapplication.cpp:2824 #27 0x55b64ec9fa47 in main (argc=, argv=0x7ffe304194c0) at /usr/src/debug/kdeconnect-kde-21.04.2-1.1.x86_64/daemon/kdeconnectd.cpp:174 [Inferior 1 (process 2508) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 438873] Please add an opaque setting in the Dashboard plugin configuration
https://bugs.kde.org/show_bug.cgi?id=438873 --- Comment #1 from Danny Medina --- Created attachment 139496 --> https://bugs.kde.org/attachment.cgi?id=139496=edit This is how its supposed to be. It appears like that if you screenshoot it. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 438873] New: Please add an opaque setting in the Dashboard plugin configuration
https://bugs.kde.org/show_bug.cgi?id=438873 Bug ID: 438873 Summary: Please add an opaque setting in the Dashboard plugin configuration Product: kdeplasma-addons Version: 5.22.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Dashboard Assignee: h...@kde.org Reporter: lyrix...@gmx.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 139495 --> https://bugs.kde.org/attachment.cgi?id=139495=edit with transparency & blur turned off Please add an option to make the Dashboard plugin opaque. For users with low end devices turning off blur and or transparency makes the desktop experience faster, but in doing so it will also leave the dash to dock applet in a transparent/dimmed state instead of it being opaque/black. * Also, upon taking a screenshot of it the dashboard turns opaque as I believe it should remain. STEPS TO REPRODUCE 1. turn off transparency & blur in effects section 2. activate the dashboard menu plugin 3. observe SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE Tumbleweed 20210615 (available in About System) KDE Plasma Version: 5.22.0 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Lenovo Thinkpad T470 Intel Core i5-7300u Intel HD 620 (i915|KBL GT2) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] Please add a sidebar embedded category for files/Directories
https://bugs.kde.org/show_bug.cgi?id=438625 Danny Medina changed: What|Removed |Added Summary|Please add a sidebar|Please add a sidebar |embedded category for files |embedded category for ||files/Directories -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] Please add a sidebar embedded category for files
https://bugs.kde.org/show_bug.cgi?id=438625 Danny Medina changed: What|Removed |Added Platform|OpenBSD Packages|unspecified -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] Please add a sidebar embedded category for files
https://bugs.kde.org/show_bug.cgi?id=438625 Danny Medina changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 438625] New: Please add a sidebar embedded category for files
https://bugs.kde.org/show_bug.cgi?id=438625 Bug ID: 438625 Summary: Please add a sidebar embedded category for files Product: Elisa Version: unspecified Platform: OpenBSD Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: lyrix...@gmx.com Target Milestone: --- Created attachment 139311 --> https://bugs.kde.org/attachment.cgi?id=139311=edit Visual representation Im submitting this fetaure request because it would be an easier option to search for the folders in which you have your music in through the sidebar instead f the middle section of elisa; sort of how clementine has it. I've come to this conclusion over and over because not all my music has its metadata like it should and alot of songs from the same folder are under different albums and genres thereby making it harder to navegate from a specific project -- You are receiving this mail because: You are watching all bug changes.
[kdelibs] [Bug 329787] KsysGuard crash
https://bugs.kde.org/show_bug.cgi?id=329787 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 426047] Crash in KQuickAddons::ConfigModule::~ConfigModule() for multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 --- Comment #17 from Danny Medina --- Created attachment 133692 --> https://bugs.kde.org/attachment.cgi?id=133692=edit New crash information added by DrKonqi systemsettings5 (5.20.2) using Qt 5.15.2 - What I was doing when the application crashed: Changing the wallpaper category of the "Wallpaper of the day" plugin, afterwards i locked the screen to see the changes, then closed the lock screen appareance settings and while the application exited, it also crashed upon exit. - Custom settings of the application: Had the "Wallpaper of the day" plugin enabled. -- Backtrace (Reduced): #4 0x7fa5321f48aa in QQmlData::wasDeleted (object=0x558dbe34af00) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/qml/qqmldata_p.h:338 #5 QV4::QObjectWrapper::getQmlProperty (engine=engine@entry=0x558dbe319f80, qmlContext=qmlContext@entry=0x558dbe322fb0, object=0x558dbe34af00, name=0x7fa4bd3185e8, revisionMode=revisionMode@entry=QV4::QObjectWrapper::CheckRevision, hasProperty=hasProperty@entry=0x7fffd81593c8, property=0x7fffd81593d0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4qobjectwrapper.cpp:360 #6 0x7fa5321d42ca in QV4::QQmlContextWrapper::getPropertyAndBase (resource=, id=..., receiver=, hasProperty=0x7fffd8159447, base=0x0, lookup=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #7 0x7fa5321d4b93 in QV4::QQmlContextWrapper::resolveQmlContextPropertyLookupGetter (l=0x558dbe3947c0, engine=0x558dbe319f80, base=0x0) at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/include/QtQml/5.15.2/QtQml/private/../../../../../src/qml/common/qv4staticvalue_p.h:325 #8 0x7fa532211410 in QV4::Moth::VME::interpret (frame=0x7fffd8159630, engine=0x558dbe319f80, code=0x7fa4bccf8a0b "\030\n(N\030\r\247a\001") at /usr/src/debug/libqt5-qtdeclarative-5.15.2-1.1.x86_64/src/qml/jsruntime/qv4vme_moth.cpp:585 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 426047] Crash in KQuickAddons::ConfigModule::~ConfigModule() for multiple System Settings KCMs
https://bugs.kde.org/show_bug.cgi?id=426047 Danny Medina changed: What|Removed |Added CC||lyrix...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
