[neon] [Bug 467409] New: Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 Bug ID: 467409 Summary: Dependencies broken Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: nicod...@posteo.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 157312 --> https://bugs.kde.org/attachment.cgi?id=157312&action=edit Upgrade messages SUMMARY It seems as if the recent updates have broken dependencies. In consequence, apt virtually proposes to uninstall the entire desktop. The problems started about three days ago with the proposal to remove skrooge and digikam. STEPS TO REPRODUCE sudo apt-get update && sudo apt-get dist-upgrade OBSERVED RESULT See attached file. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 --- Comment #1 from Nico Dorn --- There are further users that reported similiar problems: https://forum.kde.org/viewtopic.php?f=309&t=177454 https://forum.kde.org/viewtopic.php?f=309&t=177357&start=15 The proposed fix doesn't work for me, unfortunately. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 Nico Dorn changed: What|Removed |Added Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 Nico Dorn changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 --- Comment #4 from Nico Dorn --- See https://forum.kde.org/viewtopic.php?f=309&t=176375&p=461467#p461467 The 32-bit version of libharfbuzz0b was not updated. That might be the core of the current problems. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 --- Comment #5 from Nico Dorn --- This is still an issue. Could you please provide an i386 version for libjpeg-turbo8? That is important for users that need win32:i386. There are other users that are affected by this, too (see https://forum.kde.org/viewtopic.php?f=309&t=176375&start=15#p461785). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 Nico Dorn changed: What|Removed |Added Attachment #157312|0 |1 is obsolete|| --- Comment #6 from Nico Dorn --- Created attachment 157816 --> https://bugs.kde.org/attachment.cgi?id=157816&action=edit Broken dependencies apt-get output Added attachment with details about broken dependencies (ouptut apt-get). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 --- Comment #8 from Nico Dorn --- Thanks, Jonathan. I'lll check it out. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 467409] Dependencies broken
https://bugs.kde.org/show_bug.cgi?id=467409 Nico Dorn changed: What|Removed |Added Resolution|--- |WORKSFORME Status|CONFIRMED |RESOLVED --- Comment #9 from Nico Dorn --- TL;DR: works for me … now. Okay, I finally tackled this unfortunated situation and allowed the system to remove a bunch of i386 packages that are essential for me (especially wine32:i386). As I'm in need of wine32:i386, I tried to reinstall it with "sudo apt-get install wine32:i386". This didn't work due to severe dependency issues. What I did to solve the situation: sudo apt-get --allow-remove-essential purge ".*:i386" (--allow-remove-essential was necessary as there were some packages deemd essential by apt) sudo dpkg --remove-architecture i386 (restart, don't know if that was necessary) sudo dpkg --add-architecture i386 sudo apt-get update sudo apt-get install wine32 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477797] Updates try to remove skrooge due to dependency issues
https://bugs.kde.org/show_bug.cgi?id=477797 Nico Dorn changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 480386] New: Skrooge 2.31.0 won't start due to incompatible Qt version
https://bugs.kde.org/show_bug.cgi?id=480386 Bug ID: 480386 Summary: Skrooge 2.31.0 won't start due to incompatible Qt version Classification: Applications Product: skrooge Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: steph...@mankowski.fr Reporter: nicod...@posteo.de Target Milestone: --- Starting from the terminal gives the following message: ##FATAL: Cannot mix incompatible Qt library (5.15.11) with this library (5.15.12) -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 480386] Skrooge 2.31.0 won't start due to incompatible Qt version
https://bugs.kde.org/show_bug.cgi?id=480386 Nico Dorn changed: What|Removed |Added Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 480386] Skrooge 2.31.0 won't start due to incompatible Qt version
https://bugs.kde.org/show_bug.cgi?id=480386 --- Comment #1 from Nico Dorn --- Forgot my system information Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.5.0-10022-tuxedo (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480386] Skrooge 2.31.0 won't start due to incompatible Qt version
https://bugs.kde.org/show_bug.cgi?id=480386 Nico Dorn changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 480386] Skrooge 2.31.0 won't start due to incompatible Qt version
https://bugs.kde.org/show_bug.cgi?id=480386 Nico Dorn changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #4 from Nico Dorn --- Resolved with the latest updates. Cheers! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408908] File Transfer notification are gone since update to Plasma 5.16.0
https://bugs.kde.org/show_bug.cgi?id=408908 --- Comment #9 from Nico Dorn --- Works for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 444176] New: Key strokes are propagated to window contents while resizing/moving window by keyboard only
https://bugs.kde.org/show_bug.cgi?id=444176 Bug ID: 444176 Summary: Key strokes are propagated to window contents while resizing/moving window by keyboard only Product: frameworks-kwindowsystem Version: 5.87.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: nicod...@posteo.de Target Milestone: --- SUMMARY If one tries to resize/move a window only by using the keyboard, the key strokes are propagated to the active application which runs inside the window. This is a longstanding bug (several years old). STEPS TO REPRODUCE 1. Open Konsole. 2. Move the window only using the keyboard: Alt + F3 > More Actions > Move > Cursor keys up/down/right/left > Enter when satisfied. OBSERVED RESULT If you hit the up or down cursor during the moving process Konsole's history function is invoked. The Enter key to complete the action produces an new blank prompt or executes the command on the prompt. EXPECTED RESULT Key strokes should not be propgated to the application during moving action. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.1 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-38-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 430036] konsole no-toolbar setting missing or forgotten
https://bugs.kde.org/show_bug.cgi?id=430036 Nico Dorn changed: What|Removed |Added CC||nicod...@posteo.de --- Comment #43 from Nico Dorn --- I just installed KDE Gear 21.08 and hit the bug for the first time ever: scaly toolbars that force Konsole windows to have a width of about 1400px. "Settings > Tab Bar/Splitters > Appearance > Show > Never" is ignored. Also specific toolbar settings (e.g. no text) are not remembered. If the cited commit from comment #28 is already included in the current version (21.08.0) and should have fixed this: it didn't. Workaround: enable "Settings > General > Remember window size". (Naturally, this stifles the possibility to open new Konsole windows with a default size specified in the default profile.) -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 475037] New: Dashboard: the font in "Income & Expenditure" is too small and has a bad contrast
https://bugs.kde.org/show_bug.cgi?id=475037 Bug ID: 475037 Summary: Dashboard: the font in "Income & Expenditure" is too small and has a bad contrast Classification: Applications Product: skrooge Version: 2.30.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: steph...@mankowski.fr Reporter: nicod...@posteo.de Target Milestone: --- SUMMARY On the dashboard, the font size in "Accounts" and "Advices" is just fine. The one used in the "Income & Expenditure" blocks is much too small. It should just have the same size. Also, the font color is always black. On the green and especially on the red background it's hardly readable. If I remeber right, in prior versions this part was a pill with a grey and partially red or green background. The font was always white which was no strain to the eyes. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.2.0-33-generic (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477041] New: registerShortcut() is not registering many shortcuts
https://bugs.kde.org/show_bug.cgi?id=477041
Bug ID: 477041
Summary: registerShortcut() is not registering many shortcuts
Classification: Plasma
Product: kwin
Version: 5.27.9
Platform: Neon
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: scripting
Assignee: kwin-bugs-n...@kde.org
Reporter: nicod...@posteo.de
Target Milestone: ---
Nearly no shortcut is working with registerShortcut(). There are some, though,
but it seems that every letter shortcut is rejected. Among the ones I tested
are "Meta+I", "Meta+Ctrl+I", "Meta+N", "Meta+B", "Ctrl+Alt+B" … I made sure to
test shortcuts that were not registered yet.
But some shortcuts do work, for example "Meta+F4" or "Meta+Num+8" (if NumPad is
enabled). A working example:
print("started");
registerShortcut("Test", "Test", "Meta+F4", () => print("works"));
"started" is always printed to the journal, "works" only after a shortcut that
was really registered (like "Meta+F4") is triggered. There is never any error
message in the journal.
SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Kernel Version: 6.2.0-36-generic (64-bit)
Graphics Platform: X11
Processors: 16 × Intel® Core™ i7-10875H CPU @ 2.30GHz
Memory: 62.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: TUXEDO
Product Name: TUXEDO Book XC1711
System Version: Not Applicable
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 477041] registerShortcut() is not registering many shortcuts
https://bugs.kde.org/show_bug.cgi?id=477041 --- Comment #1 from Nico Dorn --- I got it up and running, but honestly, I don't know how. Mayby the shortcuts list was all messed up due to all my testing and this did the trick: qdbus org.kde.kglobalaccel /component/kwin org.kde.kglobalaccel.Component.cleanUp That might be it, as uninstalling or updating a script via UI (System Settings > Window Management > KWin Scripts) does not expunge the shortcuts list in ~/.config/kglobalshortcutsrc. But that doesn't explain why it didn't work in the first place. Hm, weird… -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477797] New: Updates try to remove skrooge due to dependency issues
https://bugs.kde.org/show_bug.cgi?id=477797 Bug ID: 477797 Summary: Updates try to remove skrooge due to dependency issues Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: nicod...@posteo.de CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY The updates from 11/30/2023 are producing two dependency issues. One can only be solved by uninstalling skrooge: Starting pkgProblemResolver with broken count: 2 Starting 2 pkgProblemResolver with broken count: 2 Investigating (0) kross:amd64 < 5.112.0-0xneon+22.04+jammy+release+build40 @ii mK Ib > Broken kross:amd64 Depends on libkf5krossui5:amd64 < 5.112.0-0xneon+22.04+jammy+release+build40 -> 5.112.0-0xneon+22.04+jammy+release+build41 @ii umU > (= 5.112.0-0xneon+22.04+jammy+release+build40) Considering libkf5krossui5:amd64 2 as a solution to kross:amd64 8 Added libkf5krossui5:amd64 to the remove list Fixing kross:amd64 via keep of libkf5krossui5:amd64 Try to Re-Instate (0) libkf5krossui5:amd64 Investigating (0) skrooge:amd64 < 2.31.0-0xneon+22.04+jammy+release+build28 @ii mK Ib > Broken skrooge:amd64 Depends on skrooge-common:amd64 < 2.31.0-0xneon+22.04+jammy+release+build28 -> 2.31.0-0xneon+22.04+jammy+release+build29 @ii umU > (= 2.31.0-0xneon+22.04+jammy+release+build28) Considering skrooge-common:amd64 0 as a solution to skrooge:amd64 0 Removing skrooge:amd64 rather than change skrooge-common:amd64 Any ideas? SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.112.0 Qt Version: 5.15.11 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463224] New: Unable to close file from split view
https://bugs.kde.org/show_bug.cgi?id=463224 Bug ID: 463224 Summary: Unable to close file from split view Classification: Applications Product: kate Version: 22.12.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: nicod...@posteo.de Target Milestone: --- SUMMARY In some cases one is unable to close a currently open file if split view is enabled. STEPS TO REPRODUCE 1. Enable documents sidebar (View > Tools View > Show Documents). 2. Open file A. 3. View > Split View > Split Vertical 4. Open file B *directly into the right* split view area. 5. Switch to the left split view area (with file A). 6. Go to file B in the left split view area. 7. File > Close OBSERVED RESULT Kate gos to file A in the left split view area, but file B remains open (as one can see in the documents sidebar). EXPECTED RESULT File B should be closed directly. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics System Version: Not Applicable ADDITIONAL INFORMATION This applies also to the shortcut Ctrtl + W, and the toolbar icon. The only way to close file B is via a right click in the documents view or every other way after closing every split view. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 463224] Unable to close file from split view
https://bugs.kde.org/show_bug.cgi?id=463224 --- Comment #2 from Nico Dorn --- Thanks for looking into it, and thanks for the clarification! It is dysfunctional nevertheless, as in this case File > Close does not do what it says. So from my point of view, it's still a usability bug. BTW, the behavior used to be different some time ago. "Close" actually closed a file in any circumstances. At least, the close button in Documents is a bit of a relief. Thanks for the tip! But it still bothers me to use the mouse for every day stuff like this. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 464145] New: Skrooge (2.28.0) crashes after qt update
https://bugs.kde.org/show_bug.cgi?id=464145 Bug ID: 464145 Summary: Skrooge (2.28.0) crashes after qt update Classification: Applications Product: skrooge Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: nicod...@posteo.de CC: steph...@mankowski.fr Target Milestone: --- STEPS TO REPRODUCE 1. Open Skrooge 2. Open "Accounts" 3. Mark an item (left click with mouse is enough) 4. App crashes OBSERVATIONS If I start Skrooge via Konsole, I get this message (unfortunately, DrKonqui doesn't give any backtrace): ##FATAL: Cannot mix incompatible Qt library (5.15.7) with this library (5.15.8) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = skrooge path = /usr/bin pid = 16158 KCrash: Arguments: /usr/bin/skrooge Looks like it's got somthing to do with todays qt update. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.8 Kernel Version: 5.15.0-57-generic (64-bit) Graphics Platform: X11 Processors: 16 × Intel® Core™ i7-10875H CPU @ 2.30GHz Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 464145] Skrooge (2.28.0) crashes after qt update
https://bugs.kde.org/show_bug.cgi?id=464145 --- Comment #3 from Nico Dorn --- Wow, that was quick! Thanks Jonathan, works for me! Et pour toi, Stephane? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 423294] New: Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 Bug ID: 423294 Summary: Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead Product: dolphin Version: 20.04.2 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: nicod...@posteo.de CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Instead of using a notification dialog, Dolphin pops up a special dialog to show the progress, when I'm copying/moving files. It should use the notification dialog instead as it is the default behavior, I assume. Is there some kind of conifguration that needs to be changed? (I can't figure out where.) Could it be a package that triggers this behavior? Earlier this week, when my system installation was fresh, everything was fine. Now I'm getting this nasty window. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.19 KDE Plasma Version: 5.19.1 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-59-generic OS Type: 64-bit Processors: 16 × Intel® Core™ i7-10875H CPU @ 2.30GHz Memory: 62,6 GiB of RAM Graphics Processor: Mesa DRI Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 --- Comment #2 from Nico Dorn --- Thank for your reply, Nate. But I'm lost. What is the kjobserver? What can I do to find the cause? It's not as if the notification dialog is used from time to time until something dies. It's always that way. I've this problem for, let's say, since about a year, and I'm quite convinced that it must be some configurational issue or some package that interferes the process as everything was fine for the first hours after setting up a new system installation. Dunno... -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 --- Comment #4 from Nico Dorn --- All of them are checked. I don't think I ever disabeled those. A wild guess: As I want to use kstart from time to time, I installed kde-runtime. A lot of dependencies as I remember. Could that have caused the issue? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 --- Comment #6 from Nico Dorn --- When I want to restart Plasma without restarting the whole system I do kquitapp5 plasmashell kstart plasmashell kstart isn't installed by default. What I tried now: uninstall kde-runtime then sudo apt-get --purge autoremove Then I copied a large folder, no change. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 --- Comment #7 from Nico Dorn --- Next test: I created a new user on the same machine, started a huge copy task and got the progress notification right where it belongs. So I guess it's not a package or something. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 --- Comment #9 from Nico Dorn --- > The correct command is `kstart5`. > > However if plasmashell is already running you can just do `plasmashell > --replace`. Ah thanks, didn't know that! If you need more infos regarding the issue, please let me know! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423294] Dolphin opens up a special dialog when copying/moving files, but should use notification dialog instead
https://bugs.kde.org/show_bug.cgi?id=423294 Nico Dorn changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #11 from Nico Dorn --- So, I've been playing around. I disabled some options in System Settings > Notifications, renabled them, startetd copying a huge folder––and it worked. Yeah! As I wasn't sure what exactly made the difference, I've been fiddeling around a while and also reinstalled the (as I know now, unneeded) kde-runtime package. And bam, the dialog was broken again. I purged kde-runtime and all of it's dependencies. Then I *restarted* my machine (I guess that's what I've been missing out yesterday) and everything was fine again. TL;DR: A classical PBCAK, I'd say… :-) But thanks again, Nate! Finally nice progress dialogs also for me. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 462035] New: Toggling Night Color Control via keyboard shortcut opens an empty plasma window
https://bugs.kde.org/show_bug.cgi?id=462035 Bug ID: 462035 Summary: Toggling Night Color Control via keyboard shortcut opens an empty plasma window 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: nicod...@posteo.de Target Milestone: --- STEPS TO REPRODUCE 1. Assign a shortcut to Night Color Control (System Settings > Shortcuts > Plasma > Activate Night color Control Widget), I used Meta + Shift + R. 2. Enable the widget's tray icon, choose "always shown" (this is important). 3. Use the shortcut. OBSERVED RESULT The toggle works, but it also opens an empty plasma module (?) window. EXPECTED RESULT The module window should not pop up. SOFTWARE/OS VERSION Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-53-generic (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] New: Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 Bug ID: 462170 Summary: Discover does not notify about pending updates Classification: Applications Product: Discover Version: 5.26.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifier Assignee: plasma-b...@kde.org Reporter: nicod...@posteo.de CC: aleix...@kde.org Target Milestone: --- SUMMARY Disocver does not notify about updates. STEPS TO REPRODUCE This might be due to the configuration. In my case, System Settings > Software Updates is configured as such: Update software: Manually Notification frequency: daily Use offline updates: off Nevertheless the file ~/.config/PlasmaDiscoverUpdates has this content right now (today is 11/23/2022): [Global] LastNotificationTime=2022,11,19,10,59,16.507 Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 5.15.0-53-generic (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 --- Comment #2 from Nico Dorn --- No, unfortunately not. "pkcon refresh" doesn't do the trick. I should maybe mention that in System Tray Settings the icon Updates is set to "Shown when relevant" (which is the default, I guess). -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 --- Comment #3 from Nico Dorn --- I forgot: If I open Discover manually, right now it shows 13 Updates available. It's only about the missing notification. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 --- Comment #5 from Nico Dorn --- That works. Unfortunately, I have to do it every time I reboot the system. Otherwise the system tray icon states "offline". -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 --- Comment #8 from Nico Dorn --- Yes, the process was running. But the icon in the tray said "offline". Another thing I disovered right now that might have something to do with it: I wrote a script that pops up at startup and executes `/usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier --replace` after I press enter. (Weirdly, I have a login script, but it won't work from there, even if I give the command a huge delay of 30 secs.) After that, the update notifier works as expected. But, if I cut the internet connection, the notifier turns back into the "offline" state and won't get active again, even if I reestablish the connection. But at startup it never works out of the box, whether there's an internet connection present or not. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 --- Comment #11 from Nico Dorn --- In addition to Stefans comment: I made a fresh install of KDE neon some weeks ago after the rebase on jammy. Since then I face this bug. I might have found a way to reproduce the notifier's behaviours: Establishing a network connection switches the notfier off. Steps to reproduce: 1. Make sure DiscoverNotifer is running. 2. Disconnet your network connection (turn off Wifi or LAN) => DiscoverNotifier's state is unchanged. 3. Reconnect Wifi or LAN => DiscoverNotifier switches into "offline" mode. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 --- Comment #15 from Nico Dorn --- (In reply to Nate Graham from comment #14) > Nico, does this fix the issue for you as well? I'd like to test that, but don't know how, Nate. I think, the version of my packagekit libraries is acutally lower than the one, Luca gave, e.g.: libpackagekit-glib2-18:amd64 1.2.5-2ubuntu2? Unfortunately, there ist no other version I could force. Maybe due to the fresh install I made a month ago? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 462170] Discover does not notify about pending updates
https://bugs.kde.org/show_bug.cgi?id=462170 --- Comment #17 from Nico Dorn --- Nothing for packagekit, some for DiscoverNotifier, but not the same as yours and quite irregular (not every day). There are three different types, but none of them appear on a daily basis: Nov 13 10:23:54 nico systemd[1167]: Started /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier. Nov 19 11:59:24 nico DiscoverNotifier[2090]: Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. Nov 30 14:58:34 nico DiscoverNotifier[3065]: "Object does not exist at path “/org/freedesktop/NetworkManager/ActiveConnection/1”" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 274931] Windows with no border (decoration) are visible on all activities
https://bugs.kde.org/show_bug.cgi?id=274931 Nico Dorn changed: What|Removed |Added CC|nicod...@posteo.de | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408908] File Transfer notification are gone since update to Plasma 5.16.0
https://bugs.kde.org/show_bug.cgi?id=408908 Nico Dorn changed: What|Removed |Added CC||nicod...@posteo.de --- Comment #7 from Nico Dorn --- Doesn't work for me neither. Yesterday I've been positivly surprised that finally the dysfunctional file transfer window disappeared in favor of a nice unobstrstusive notification. But today the transfer window reappeared again, no notification. :-( Operating System: Ubuntu 18.04.3 LTS (Bionic Beaver) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.60.0 Qt Version: 5.12.3 Kernel Version: 5.0.0-23-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382535] Impossible to predefine filters with --getopenfilename
https://bugs.kde.org/show_bug.cgi?id=382535 Nico Dorn changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 395647] No action proposed by notifier for encrypted removable devices (dmcrypt LUKS)
https://bugs.kde.org/show_bug.cgi?id=395647 Nico Dorn changed: What|Removed |Added Ever confirmed|0 |1 CC||nicod...@posteo.de Status|REPORTED|CONFIRMED --- Comment #2 from Nico Dorn --- Confirmed! OS: Ubuntu (bionic) with KDE neon 5.14.2 Frameworks: 5.51.0 Qt: 5.11.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 394053] Device notifier should not show "Removing..." and "The device can now be safely removed" at the same time
https://bugs.kde.org/show_bug.cgi?id=394053 Nico Dorn changed: What|Removed |Added CC||nicod...@posteo.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Nico Dorn --- Confirmed! In my case "Removing..." never disappears despite the device has been removed successfully. Operating System: KDE neon 5.14 KDE Plasma Version: 5.14.2 Qt Version: 5.11.2 KDE Frameworks Version: 5.51.0 Kernel Version: 4.15.0-38-generic -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413915] All electron apps have grey menus when using breeze gtk3 theme
https://bugs.kde.org/show_bug.cgi?id=413915 Nico Dorn changed: What|Removed |Added CC||nicod...@posteo.de --- Comment #16 from Nico Dorn --- (In reply to Ivan Safonov from comment #14) > It seems like "Active Titlebar Text" has a wrong colour in the Breeze theme Changing that option makes things even worse. The menu of the Electron app would be fine, but the titlebar text would be unrecognizable in all and every window. I'm dispatching the following on autostart which fixes the issue for me: sed -i 's/theme_titlebar_foreground.*/theme_titlebar_foreground rgb(35,38,39);/' "$HOME/.config/gtk-3.0/colors.css" -- You are receiving this mail because: You are watching all bug changes.
[kronometer] [Bug 421515] New: Wrong time restored from session
https://bugs.kde.org/show_bug.cgi?id=421515 Bug ID: 421515 Summary: Wrong time restored from session Product: kronometer Version: 2.2.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: nicod...@posteo.de Target Milestone: --- SUMMARY Times stored in a session (File > Save as) cannot be restored correctly when the stopwatch has been paused several times before. STEPS TO REPRODUCE 1. Open Kronometer and start the stopwatch (hit space). 2. Pause (hit space) after 5 seconds, save as session (Ctrl + Shift + S). 3. Resume (hit space), stop after 5 seconds. Now the clock shows 10 seconds, save it (Ctrl + S). 4. Resume, stop after 5 seconds again. Now the clock show 15 seconds, save it (Ctrl + S). 5. Quit Kronometer. 6. Reopen Kronometer, open the saved session (Strg + O), the time shown is 10 seconds but it should be 15. Using the stopwatch in real life can result in huge differences (several hours). Seems as if times after pauses are being ignored, at least sometimes. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-51-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2670QM CPU @ 2.20GHz Memory: 7,7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 396700] Korganizer crashes on startup after installing over 400 updates to KDE Neon.
https://bugs.kde.org/show_bug.cgi?id=396700 Nico Dorn changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 CC||nicod...@posteo.de --- Comment #1 from Nico Dorn --- Same problem here, also running KDE neon with lateste Packages. -- Backtrace: Application: KOrganizer (korganizer), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4a62f91940 (LWP 30561))] Thread 2 (Thread 0x7f4a3b95a700 (LWP 30564)): #0 0x7f4a547768f8 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f4a547772bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f4a5477749c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f4a5f30b0bb in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f4a5f2b25ba in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f4a5f0e75e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f4a5dca1f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f4a5f0f2727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f4a564846ba in start_thread (arg=0x7f4a3b95a700) at pthread_create.c:333 #9 0x7f4a5e7e941d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 Thread 1 (Thread 0x7f4a62f91940 (LWP 30561)): [KCrash Handler] #6 0xfff0 in ?? () #7 0x7f4a62c66d3d in KontactInterface::PimUniqueApplication::start(QStringList const&, bool) () from /usr/lib/x86_64-linux-gnu/libKF5KontactInterface.so.5 #8 0x004084ce in ?? () #9 0x7f4a5e702830 in __libc_start_main (main=0x408180, argc=1, argv=0x7ffe37c0aee8, init=, fini=, rtld_fini=, stack_end=0x7ffe37c0aed8) at ../csu/libc-start.c:291 #10 0x004087b9 in _start () -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 Nico Dorn changed: What|Removed |Added CC||nicod...@posteo.de --- Comment #25 from Nico Dorn --- After the recent updates the problem is partially fixed for me. KOrganizer won't start directly (see duplicate #396700). But the workaround via Kontact, proposed by Paweł Krzak, works. Distro: KDE Neon User Edition -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 396694] Kontact crashes right after start
https://bugs.kde.org/show_bug.cgi?id=396694 --- Comment #27 from Nico Dorn --- Now it's fixed! Thanks! -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 376999] Muon searchbox not working
https://bugs.kde.org/show_bug.cgi?id=376999 Nico Dorn changed: What|Removed |Added CC||nicod...@posteo.de --- Comment #1 from Nico Dorn --- Confirmed, makes muon unusable, a real pitty. -- You are receiving this mail because: You are watching all bug changes.
[muon] [Bug 376999] Muon searchbox not working
https://bugs.kde.org/show_bug.cgi?id=376999 --- Comment #2 from Nico Dorn --- May be related to https://bugs.kde.org/show_bug.cgi?id=372343. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 348366] Disable sound feedback option does not work
https://bugs.kde.org/show_bug.cgi?id=348366 --- Comment #4 from Nico Dorn --- Works for me now. Plasma 5.10.2 KF 5.35. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 348366] Disable sound feedback option does not work
https://bugs.kde.org/show_bug.cgi?id=348366 Nico Dorn changed: What|Removed |Added CC||nicod...@posteo.de --- Comment #2 from Nico Dorn --- Confirmed! Neither works for me. Plasma 5.8.5 Frameworks 5.28.0 -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 348366] Disable sound feedback option does not work
https://bugs.kde.org/show_bug.cgi?id=348366 --- Comment #3 from Nico Dorn --- I investigated a bit further. Everytime "volume feedback" is unchecked Kmix creates a new set of options in plasma-org.kde.plasma.desktop-appletsrc, like so: [Containments][6][Applets][9] immutability=1 plugin=org.kde.plasma.volume [Containments][6][Applets][9][Configuration][ConfigDialog] DialogHeight=540 DialogWidth=720 [Containments][6][Applets][9][Configuration][General] volumeFeedback=false Kmix obeys the option--but only for the current session. After restart of plasmashell "volume feedback" is always reenabled. If I disable it a new set of options (like those above) is created. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382535] New: Impossible to predefine filters with --getopenfilename
https://bugs.kde.org/show_bug.cgi?id=382535 Bug ID: 382535 Summary: Impossible to predefine filters with --getopenfilename Product: kdialog Version: 1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: nicod...@posteo.de Target Milestone: --- The code below opens the expected dialog window but doesn't set the passed filters. Since it doesn't set any filters, no file can be selected - until one types the filters manually. I think the bug was introduced with the latest revision of KDE Frameworks, i.e. version 5.36.0. kdialog --getopenfilename /tmp/ ".tar.gz" -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382535] Impossible to predefine filters with --getopenfilename
https://bugs.kde.org/show_bug.cgi?id=382535 Nico Dorn changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382536] New: Alt + O doesn't work anymore with --textinputbox
https://bugs.kde.org/show_bug.cgi?id=382536 Bug ID: 382536 Summary: Alt + O doesn't work anymore with --textinputbox Product: kdialog Version: 1.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: br...@frogmouth.net Reporter: nicod...@posteo.de Target Milestone: --- Steps to reproduce: 1) kdialog --textinputbox "Insert data:" 2) Alt + o Result: An o is added to the input box. Expected result: The input box closes. This bug has been introduced with KDE Applications 17.04.3. -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382536] Alt + O doesn't work anymore with --textinputbox
https://bugs.kde.org/show_bug.cgi?id=382536 Nico Dorn changed: What|Removed |Added Platform|Other |Neon Packages -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382535] Impossible to predefine filters with --getopenfilename
https://bugs.kde.org/show_bug.cgi?id=382535 --- Comment #1 from Nico Dorn --- Pardon me! It must have been introduced with KDE Applications 17.04.3, naturally. :) -- You are receiving this mail because: You are watching all bug changes.
[kdialog] [Bug 382535] Impossible to predefine filters with --getopenfilename
https://bugs.kde.org/show_bug.cgi?id=382535 --- Comment #3 from Nico Dorn --- Thanks for your answer! That works indeed. It used to work without wildcard. But it's correct to presume it's use. So I'd say, this is not a bug, but I would like to propse to add another helpline to kdialog --help, since filters can be used for several functions. Something like that: Arguments: [arg] Arguments - depending on main option [filter] File type filter - usage: "*.xml" or "XML file (*.xml)" -- You are receiving this mail because: You are watching all bug changes.
