[konsole] [Bug 468099] New: Implement an option for auto-switching between dark and light "Color scheme & font"
https://bugs.kde.org/show_bug.cgi?id=468099 Bug ID: 468099 Summary: Implement an option for auto-switching between dark and light "Color scheme & font" Classification: Applications Product: konsole Version: master Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: bugs@varum.dk Target Milestone: --- SUMMARY I am using the "Yin & Yang" to auto-switch between light and dark theme in KDE Plasma, and most of the Applications now a day detect this switches along with the desktop. https://github.com/oskarsh/Yin-Yang However, Konsole is one of the applications which does not follow the desktop in this regard, at least not for the "Color scheme & font" in the application. It would be really appreciated if there was a feature in Konsole to detect and change the "Color scheme & font" so that it follows KDE Plasma desktop theme. This feature does not have to be enabled by default, but if it were an option that would be amazing :D STEPS TO REPRODUCE Note: I am not certain how much this makes sense for a feature request 1. Open Konsole 2. Open system settings 3. Change from the theme Breeze Dark to Breeze OBSERVED RESULT The "Color scheme & font" in Konsole does not change EXPECTED RESULT The "Color scheme & font" in Konsole changes from "Breeze" to "Black on White" SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (available in About System) KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466580] [NVIDIA] Panel freezes when rearranging or unpinning on icons only task manager widget
https://bugs.kde.org/show_bug.cgi?id=466580 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #5 from Dennis --- I have the same issue on an Alienware R14 with nvidia Geforce RTX 3070 with Nvidia-driver-525. Using kubuntu 23.04 plasma version 5.27.4 KDE Frameworks version 5.104.0 Qt version 5.15.8 Kernel 6.2.0.20-generic Wayland I think I had this bug for a while, in 22.04 and 22.10. Up until now I restarted the system or restarted kde, which was a pain, so thanks for the workaround. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452075] Wallpaper reset to default and all widgets disappear after new start
https://bugs.kde.org/show_bug.cgi?id=452075 Dennis changed: What|Removed |Added CC||dennis...@protonmail.com --- Comment #26 from Dennis --- Hey, I have to chime in since I'm experiencing similar behavior since around 2-4 weeks on both, my work and my private machines. I'm on X however with Plasma 5.27.5. I'm noticing that my wallpaper and my panel configuration reset on every reboot. It's indeed very annoying. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460753] New: Feature request: network manager VPN connection parameter free field
https://bugs.kde.org/show_bug.cgi?id=460753 Bug ID: 460753 Summary: Feature request: network manager VPN connection parameter free field Classification: Applications Product: systemsettings Version: 5.25.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_networkmanagement Assignee: jgrul...@redhat.com Reporter: dennis@thegood.cloud CC: plasma-b...@kde.org Target Milestone: --- Created attachment 153053 --> https://bugs.kde.org/attachment.cgi?id=153053&action=edit proposal to add command options free field SUMMARY *** The network manager has only fixed fields, so perhaps it might be an idea to offer a parameter field in the connection. *** Like this: !nm-cli-option.png! SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.10 (available in About System) KDE Plasma Version: 5.25 KDE Frameworks Version: 5.98 Qt Version: 5.15.6 ADDITIONAL INFORMATION I ran into this issue while encountering that the openvpn has -cipher deprecated: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1988301?comments=all Let me know if you need more info or if I need to submit somewhere else, this is my first KDE bug submit. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460753] Feature request: network manager VPN connection parameter free field
https://bugs.kde.org/show_bug.cgi?id=460753 --- Comment #2 from Dennis --- That is automatied comment I think?As this is not a bug, but a feature request. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 489120] New: upgraded to latest version of kstars now stuck at starting Indi services
https://bugs.kde.org/show_bug.cgi?id=489120 Bug ID: 489120 Summary: upgraded to latest version of kstars now stuck at starting Indi services Classification: Applications Product: kstars Version: 3.7.1 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: dennisjcoll...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. open kstars 2. select my astro gear profile 3. start ekos OBSERVED RESULT hangs at starting INDI services. If I try to stop and restart it states another instance is running and will crash when I stop it. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489559] Plasmashell crashed after removing flatpak QT app
https://bugs.kde.org/show_bug.cgi?id=489559 --- Comment #1 from Dennis --- Created attachment 171245 --> https://bugs.kde.org/attachment.cgi?id=171245&action=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489559] New: Plasmashell crashed after removing flatpak QT app
https://bugs.kde.org/show_bug.cgi?id=489559
Bug ID: 489559
Summary: Plasmashell crashed after removing flatpak QT app
Classification: Plasma
Product: plasmashell
Version: 6.1.1
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: crap-den...@gmx.net
Target Milestone: 1.0
Application: plasmashell (6.1.1)
Qt Version: 6.7.1
Frameworks Version: 6.3.0
Operating System: Linux 6.9.6-200.fc40.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 40 (KDE Plasma)"
DrKonqi: 6.1.1 [CoredumpBackend]
-- Information about the crash:
I am using Fedora 40 with KDE Plasma 6.1.1 and I tried out the flathub version
of KColorChooser to compare it with the version from the distribution. I then
closed the app and removed the flatpak app again, and shortly afterwards
plasmashell suddenly crashed and restarted itself. I just tried the same
actions again, this time there was no crash, and I had not experienced this
before either. I hope the backtrace is helpful.
The reporter is unsure if this crash is reproducible.
-- Backtrace (Reduced):
#5 0x7f0934bbeb8f in
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}::operator()() const (__closure=0x56418c53c900) at
/usr/src/debug/plasma-workspace-6.1.1-1.fc40.x86_64/applets/kicker/plugin/kastatsfavoritesmodel.cpp:196
#6 QtPrivate::FunctorCall, QtPrivate::List<>, void,
KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}>::call(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*,
QString const&)::{lambda()#1}&, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:137
#7
QtPrivate::FunctorCallable::call,
void>(KAStatsFavoritesModel::Private::Private(KAStatsFavoritesModel*, QString
const&)::{lambda()#1}&, void*, void**) (f=..., arg=) at
/usr/include/qt6/QtCore/qobjectdefs_impl.h:345
#8
QtPrivate::QCallableObject, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=,
this_=0x56418c53c8f0, r=, a=, ret=) at /usr/include/qt6/QtCore/qobjectdefs_impl.h:555
#9 0x7f09681ebdeb in QObject::event (this=0x56418c1efb90,
e=0x564191717f70) at
/usr/src/debug/qt6-qtbase-6.7.1-2.fc40.x86_64/src/corelib/kernel/qobject.cpp:1452
Reported using DrKonqi
--
You are receiving this mail because:
You are watching all bug changes.
[neon] [Bug 478147] New: fwupd shows segmentation fault
https://bugs.kde.org/show_bug.cgi?id=478147 Bug ID: 478147 Summary: fwupd shows segmentation fault Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY fwupd-service does not run (core-dump) and fwupdmgr/fwupdtool shows segmentation fault. STEPS TO REPRODUCE 1. pkcon update to latest 2. `sudo systemctl status fwupd.service` 3. `sudo fwupdtool refresh` && `sudo fwupdmgr get-updates` OBSERVED RESULT 1. `sudo systemctl status fwupd.service 2. `fwupd.service - Firmware update daemon` ``` Loaded: loaded (/lib/systemd/system/fwupd.service; static) Active: failed (Result: core-dump) since Wed 2023-12-06 07:32:01 CET; 10min ago Docs: https://fwupd.org/ Process: 32744 ExecStart=/usr/libexec/fwupd/fwupd (code=dumped, signal=SEGV) Main PID: 32744 (code=dumped, signal=SEGV) CPU: 1.345s dec 06 07:31:57 xps13-edge systemd[1]: Starting Firmware update daemon... dec 06 07:31:58 xps13-edge fwupd[32744]: 06:31:58.395 FuEngine failed to add device usb:06:00:01:02: No de> dec 06 07:31:59 xps13-edge fwupd[32744]: 06:31:59.466 FuPluginIntelMe failed to get public key using /fpf/OemCred> dec 06 07:32:01 xps13-edge fwupd[32744]: 06:32:01.051 FuCommon fu_path_get_files: assertion 'path != NULL'> dec 06 07:32:01 xps13-edge systemd[1]: fwupd.service: Main process exited, code=dumped, status=11/SEGV dec 06 07:32:01 xps13-edge systemd[1]: fwupd.service: Failed with result 'core-dump'. dec 06 07:32:01 xps13-edge systemd[1]: Failed to start Firmware update daemon. dec 06 07:32:01 xps13-edge systemd[1]: fwupd.service: Consumed 1.345s CPU time. ``` 2. `sudo fwupdtool refresh` ``` Loading… [***]06:42:49.363 FuEngine failed to add device usb:06:00:01:02: No device GType set Loading… [***]06:42:50.458 FuPluginIntelMe failed to get public key using /fpf/OemCred: generic failure [0xb] Loading… [** ]06:42:51.949 FuCommon fu_path_get_files: assertion 'path != NULL' failed Segmentation fault ``` 3. `sudo fwupdmgr get-updates` ``` Failed to connect to daemon: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) ``` EXPECTED RESULT 1. the system service fwupd.service should be running, yes? SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: `sudo fwupdtool --version`: ``` Loading… [** ]06:42:40.741 FuEngine failed to update history database: device ID a45df35ac0e948ee180fe216a5f703f32dda163f was not found compile org.freedesktop.fwupd 1.9.7 compile com.hughsie.libxmlb 0.3.14 compile com.hughsie.libjcat 0.1.9 runtime org.freedesktop.fwupd-efi 1.4 compile org.freedesktop.gusb 0.3.10 runtime org.freedesktop.gusb 0.3.10 runtime org.freedesktop.fwupd 1.9.7 runtime org.kernel6.2.0-37-generic ``` ADDITIONAL INFORMATION - apt packages: ``` fwupd-signed/jammy-updates,now 1.51.1~22.04.1+1.4-0ubuntu0.1 amd64 [installed,automatic] fwupd/jammy,now 1.9.7-1+22.04+jammy+unstable+build1 amd64 [installed,automatic] libfwupd2/jammy,now 1.9.7-1+22.04+jammy+unstable+build1 amd64 [installed,automatic] ``` -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478148] New: kwallet-pam missing?
https://bugs.kde.org/show_bug.cgi?id=478148 Bug ID: 478148 Summary: kwallet-pam missing? Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY After login, I get the password login for kwallet. Installing kwallet-pam should fix this, correct? But I can't find that package available, although there is a version for Neon Unstable here: https://archlinux.org/packages/kde-unstable/x86_64/kwallet-pam/ STEPS TO REPRODUCE 1. Install kde neon unstable 2. login --> presented with prompt 3. `apt install kwallet-pam` shows `Unable to locate package kwallet-pam` OBSERVED RESULT kwallet-pam not available EXPECTED RESULT kwallet-pam should be available and installable? SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 463065] paste issue to applications
https://bugs.kde.org/show_bug.cgi?id=463065 Dennis changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460753] Feature request: network manager VPN connection parameter free field
https://bugs.kde.org/show_bug.cgi?id=460753 Dennis changed: What|Removed |Added Version|master |5.90.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477665] Cannot relocate icon on icon-only taskbar if multiple instances of an app are running
https://bugs.kde.org/show_bug.cgi?id=477665 Dennis changed: What|Removed |Added Summary|Cannot relocate icon on |Cannot relocate icon on |icon-only taskbar if|icon-only taskbar if |multiple instances of an|multiple instances of an |app arer unning |app are running -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478148] kwallet-pam missing?
https://bugs.kde.org/show_bug.cgi?id=478148 --- Comment #2 from Dennis --- Hi, thank you for your work. I have the lib installed now: kf6-kwallet-dev/jammy,now 5.245.0+p22.04+vunstable+git20231130.0327-0 amd64 [installed,automatic] kf6-kwallet/jammy,now 5.245.0+p22.04+vunstable+git20231130.0327-0 amd64 [installed,automatic] kwalletcli/jammy,now 3.03-1 amd64 [installed] kwalletmanager/jammy,now 4:23.08.4+p22.04+vunstable+git20231206.2352-0 amd64 [installed] libkwalletbackend5-5/jammy,now 5.113.0+p22.04+vunstable+git20231205.0358-0 amd64 [installed,automatic] libpam-kwallet-common/jammy,jammy,jammy,now 4:5.27.10+p22.04+vunstable+git20231206.1224-0 all [installed,automatic] libpam-kwallet6/jammy,now 4:5.27.10+p22.04+vunstable+git20231206.1224-0 amd64 [installed] signon-kwallet-extension/jammy,now 4:23.08.4+p22.04+vunstable+git20231207.0023-0 amd64 [installed,auto-removable] So that fixes kwallet-pam installed correct? Now I still have the issue that it pops up a password login for kwallet.. But that might be an other issue? Should I report that issue anew? Or change the subject of this issue? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478147] fwupd shows segmentation fault
https://bugs.kde.org/show_bug.cgi?id=478147 Dennis changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468128] AppImages cannot be started, when Dolphin is launched via keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=468128 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #10 from Dennis --- I can't reproduce it either on plasma6 beta1, the specs of my system: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478469] New: screen locking 'unable to unlock, use loginctl instead' when system is locked
https://bugs.kde.org/show_bug.cgi?id=478469 Bug ID: 478469 Summary: screen locking 'unable to unlock, use loginctl instead' when system is locked Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY After updating today I am experiencing the bug reported in: https://bugs.kde.org/show_bug.cgi?id=405219 STEPS TO REPRODUCE 1. update neon 2. Lock screen with meta+L (I reconfigured this to be CTL-ALT-DEL btw) 3. the screen turns black with only the mouse cursor. OBSERVED RESULT Sometimes the screen message "screen locking is broken, use loginctl.." appears, but not always. The solution to unlock from cli in another shell works for me. EXPECTED RESULT Screen (un)locking to work SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION I did not experience this behaviour on the 11th of december, I seem to experience this only after updating the packages today (13th of december). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478469] screen locking 'unable to unlock, use loginctl instead' when system is locked
https://bugs.kde.org/show_bug.cgi?id=478469 --- Comment #2 from Dennis --- Yes, multiple times as . I also tried if the actions from comment5 (https://bugs.kde.org/show_bug.cgi?id=405219#c5) crashed the kscreenlocker_greet, but it didn't actually crash. Let me know if I can test anything more or submit logging if needed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477486] Ark not built with Qt6
https://bugs.kde.org/show_bug.cgi?id=477486 --- Comment #16 from Dennis --- Works! Ark integration is back in Dolphin. For reference: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478469] screen locking 'unable to unlock, use loginctl instead' when system is locked
https://bugs.kde.org/show_bug.cgi?id=478469 Dennis changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Dennis --- I don't experience this anymore after the last update, I gave my systems specs below this comment. However, I expect the issue to be related to the use of an external screen or the Dell dock I am using (TB16). I will investigate further. If I can't reproduce, I'll close the bug. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478469] screen locking 'unable to unlock, use loginctl instead' when system is locked
https://bugs.kde.org/show_bug.cgi?id=478469 Dennis changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Dennis --- Can't reproduce, even with external monitor and TB16. current version is (updated just now): Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478880] New: plasmashell crash after updating
https://bugs.kde.org/show_bug.cgi?id=478880 Bug ID: 478880 Summary: plasmashell crash after updating Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 164363 --> https://bugs.kde.org/attachment.cgi?id=164363&action=edit crash handler report. SUMMARY I updated my system today with pkcon and after rebooting, plasmashell crashed while logging back in, which left me with a black background and no panel. STEPS TO REPRODUCE 1. update Neon-unstable to today (22 dec 2023, 12:39) 2. reboot system 3. log back in. I can reproduce by: 1. starting a terminal 2. run `kstart plasmashell` eventually panel and desktop reappear 3. run `kquitapp6 plasmashell` 4. run `kstart plasmashell` OBSERVED RESULT no background, no panel after logging in after fresh reboot. EXPECTED RESULT I should be having a normal desktop, yes? ;-) SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION I'm not a dev, so let me know if more testing/logging/info is needed. I saw a lot of similar bugs, but nothting that fitted, but I might have overlooked, sorry on forehand for that. Application: plasmashell (plasmashell), signal: Segmentation fault This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.neon.kde.org/: Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [New LWP 9486] [New LWP 9513] [New LWP 9491] [New LWP 9494] [New LWP 9493] [New LWP 9492] [New LWP 9495] [New LWP 9514] [New LWP 9550] [New LWP 9498] [New LWP 9497] [New LWP 9528] [New LWP 9535] [New LWP 9499] [New LWP 9504] [New LWP 9539] [New LWP 9505] [New LWP 9551] [New LWP 9507] [New LWP 9549] [New LWP 9515] [New LWP 9530] [New LWP 9496] [New LWP 9529] [New LWP 9506] [New LWP 9531] [New LWP 9490] [New LWP 9532] [New LWP 9548] [New LWP 9534] [New LWP 9536] [New LWP 9512] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=140266681092800) at ./nptl/pthread_kill.c:44 [Current thread is 1 (Thread 0x7f9261b34ac0 (LWP 9486))] Cannot QML trace cores :( [Current thread is 1 (Thread 0x7f9261b34ac0 (LWP 9486))] Thread 32 (Thread 0x7f9222ffd640 (LWP 9512)): #0 0x7f9265b189df in __GI___poll (fds=0x5584e8e68f20, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9264f841f6 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9264f2c3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9266505790 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #4 0x7f921fbb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #5 0x7f926659ce38 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #6 0x7f926655f6ed in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #7 0x7f9265a94ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #8 0x7f9265b26660 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 31 (Thread 0x7f91e3559640 (LWP 9536)): #0 0x7f9265b189df in __GI___poll (fds=0x7f91cc01d4a0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f9264f841f6 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f9264f2c3e3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f9266505790 in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #4 0x7f921fbb in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #5 0x7f926659ce38 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #6 0x7f9267dabd4c in () at /lib/x86_64-linux-gnu/libQt6Quick.so.6 #7 0x7f926655f6ed in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #8 0x7f9265a94ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #9 0x7f9265b26660 in clone3 () at ../sysdeps/unix/sysv/linux/
[neon] [Bug 478880] plasmashell crash after updating
https://bugs.kde.org/show_bug.cgi?id=478880 Dennis changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478880] plasmashell crash after updating
https://bugs.kde.org/show_bug.cgi?id=478880 --- Comment #1 from Dennis --- I see I'm missing debug symbols.. Reproducing and new backtrace will follow. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 478883] New: drkonqi does not install debug packages on Neon unstable edition (plasma6_beta2)
https://bugs.kde.org/show_bug.cgi?id=478883 Bug ID: 478883 Summary: drkonqi does not install debug packages on Neon unstable edition (plasma6_beta2) Classification: Applications Product: drkonqi Version: 5.27.8 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: dennis@thegood.cloud Target Milestone: --- SUMMARY *** Im experiencing a plasmashell crash after logging in. I'm trying so sumbit a bug report, but drkonqi is reporting the debug symbols are not installed. Clicking "install debug symbols" looks like it's doing something, but after quite a long time it fails. Installing with apt succeeded. I suspect (im no dev) drkonqi needs to be v5.91 instead of v5.27.8 on plasma_beta2. I have existing bugs, but they for some time ago and quite a few fixed, I think this is still a usefull bug report for plasma6_beta2. For reference I checked: https://bugs.kde.org/show_bug.cgi?id=472948 https://bugs.kde.org/show_bug.cgi?id=473017 https://bugs.kde.org/show_bug.cgi?id=412395 Sorry if I missed a duplicate bug report, there are quite a lot out there. *** STEPS TO REPRODUCE 1. try to install debug symbols with drkonqi 2. timeout happens and no packages are installed (apt not even locked). OBSERVED RESULT It looks like drkonqi is busy, but I think it times out and no packages are installed. EXPECTED RESULT packages should be installed after cliking install debug symbols. Also terminal log would be nice to see progress. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION shouldn't this be version 5.91? Currently installed is: drkonqi-pk-debug-installer/jammy,now 0.1+p22.04+vunstable+git20231222.0408-0 amd64 [installed,automatic] drkonqi/jammy,now 5.27.8+p22.04+vunstable+git20231222.0051-0 amd64 [installed,automatic] -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478880] plasmashell crash after updating
https://bugs.kde.org/show_bug.cgi?id=478880 --- Comment #2 from Dennis --- Trying to sumbit through drkonqi and found https://bugs.kde.org/show_bug.cgi?id=478883 (wrong version of drkonqi?) I have no idea on how to submit more info, tried a lot of the kde wiki debugging pages, but I gave up (i'm not a dev) let me know how to proceed. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478885] New: drkonqi is unable to generate report on Neon unstable, plasma_beta2 (v5.91)
https://bugs.kde.org/show_bug.cgi?id=478885 Bug ID: 478885 Summary: drkonqi is unable to generate report on Neon unstable, plasma_beta2 (v5.91) Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY I'm trying to report a plasmashell report (https://bugs.kde.org/show_bug.cgi?id=478880), but it won't generate ending with `The crash information could not be generated.` STEPS TO REPRODUCE 1. plasmashell crashes (bug #478880) 2. trying to report through drkonqi 3. clicking dev information 4. Wait and it eventually reports "crash info could not be generated". OBSERVED RESULT crash report could not be generated EXPECTED RESULT crash report to be generated SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION drkonqi version: 5.27.8+p22.04+vunstable+git20231222.0051-0 500 shouldn't this be version 5.91? I catched this from drkoni prior to the msg "crash info could not be generated": [New LWP 13153] [New LWP 13158] [New LWP 13159] [New LWP 13160] [New LWP 13156] [New LWP 13165] [New LWP 13161] [New LWP 13163] [New LWP 13293] [New LWP 13162] [New LWP 13166] [New LWP 13164] [New LWP 13171] [New LWP 13254] [New LWP 13296] [New LWP 13172] [New LWP 13173] [New LWP 13174] [New LWP 13294] [New LWP 13236] [New LWP 13297] [New LWP 13251] [New LWP 13230] [New LWP 13252] [New LWP 13231] [New LWP 13255] [New LWP 13250] [New LWP 13298] [New LWP 13299] [New LWP 13229] [New LWP 13288] [New LWP 13295] This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.neon.kde.org/: Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/plasmashell'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=140320683649728) at ./nptl/pthread_kill.c:44 [Current thread is 1 (Thread 0x7f9ef480eac0 (LWP 13153))] Cannot QML trace cores :( /build/gdb-ZgDh0V/gdb-12.1/gdb/findvar.c:209: internal-error: store_typed_address: type is not a pointer or reference A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) [answered Y; input not from terminal] -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476930] Unable to change or preview non-Breeze splash screens
https://bugs.kde.org/show_bug.cgi?id=476930 --- Comment #10 from Dennis --- So I see we can't choose any splash screens currently, because plasma6 splash screens got a new category? Just to confirm, I understand if it is so. If so, we have the same issue on the login screen I think. And the boot splash screen. Some work btw, but most don't. Should we create new bug reports for those? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478147] fwupd shows segmentation fault
https://bugs.kde.org/show_bug.cgi?id=478147 --- Comment #2 from Dennis --- Seems to be fixed in: Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #15 from Dennis --- ah yes, sorry. doing too much at the same time. The issue is still there in notifications. im currently on: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900 12-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: NV174 Manufacturer: Alienware Product Name: Alienware Aurora Ryzen Edition R14 System Version: 2.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 446119] plasma-browser-integration-host crashes after closing Firefox
https://bugs.kde.org/show_bug.cgi?id=446119
Dennis changed:
What|Removed |Added
CC||dennis@thegood.cloud
--- Comment #2 from Dennis ---
I see the same issue.
I updated the system today and I'm on:
Operating System: KDE neon Unstable Edition
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.5.0-28-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15,3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: Dell Inc.
Product Name: XPS 13 9380
As there is no bug reporting address:
https://bugs.kde.org/show_bug.cgi?id=443053
I'm reporting this issue manually. I can't confirm it is actually firefox, but
it looks like it. I have firefox on autostart and I use the save session
feature from kde. Whic results in 2 firefox windows to be started after logging
in, one of them with empty tabs. If I close that one, 10 crash handlers start.
the crash report:
Application: Crash Handler (drkonqi), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 QScopedPointer >::get()
const (this=0x8, this=) at
./src/corelib/tools/qscopedpointer.h:110
#7 qGetPtrHelper > >(QScopedPointer >&) (ptr=..., ptr=) at
./src/corelib/global/qtclasshelpermacros.h:79
#8 QObject::d_func() (this=0x0) at ./src/corelib/kernel/qobject.h:107
#9 QObject::deleteLater() (this=0x0) at ./src/corelib/kernel/qobject.cpp:2456
#10 0x5c73322da648 in BacktraceGenerator::slotProcessExited(int,
QProcess::ExitStatus) (this=0x5c73339c74a0, exitCode=6,
exitStatus=QProcess::CrashExit) at ./src/backtracegenerator.cpp:136
#11 0x79433aa6355e in QtPrivate::QSlotObjectBase::call(QObject*, void**)
(a=0x7fff5118a250, r=0x5c73339c74a0, this=, this=, r=, a=) at
./src/corelib/kernel/qobjectdefs_impl.h:469
#12 doActivate(QObject*, int, void**) (sender=0x5c73339ef940,
signal_index=10, argv=0x7fff5118a250) at ./src/corelib/kernel/qobject.cpp:4078
#13 0x79433a8ed54c in QProcess::finished(int, QProcess::ExitStatus)
(this=, _t1=, _t2=) at
./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qprocess.cpp:346
#14 0x79433aa6383b in doActivate(QObject*, int, void**)
(sender=0x5c7333f1abe0, signal_index=3, argv=0x7fff5118a360) at
./src/corelib/kernel/qobject.cpp:4090
#15 0x79433aa0e653 in QSocketNotifier::activated(QSocketDescriptor,
QSocketNotifier::Type, QSocketNotifier::QPrivateSignal)
(this=this@entry=0x5c7333f1abe0, _t1=..., _t2=, _t3=...) at
./obj-x86_64-linux-gnu/src/corelib/Core_autogen/include/moc_qsocketnotifier.cpp:195
#16 0x79433aa13096 in QSocketNotifier::event(QEvent*) (this=0x5c7333f1abe0,
e=) at ./src/corelib/kernel/qsocketnotifier.cpp:327
#17 0x79433be0992b in QApplicationPrivate::notify_helper(QObject*, QEvent*)
(this=, receiver=0x5c7333f1abe0, e=0x7fff5118a4a0) at
./src/widgets/kernel/qapplication.cpp:3287
#18 0x79433aaa1c38 in QCoreApplication::notifyInternal2(QObject*, QEvent*)
(receiver=0x5c7333f1abe0, event=0x7fff5118a4a0) at
./src/corelib/kernel/qcoreapplication.cpp:1134
#19 0x79433a875454 in socketNotifierSourceDispatch(GSource*, GSourceFunc,
gpointer) (source=0x5c73338b9db0) at
./src/corelib/kernel/qeventdispatcher_glib.cpp:75
#20 0x794339c34d3b in g_main_context_dispatch () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x794339c8a258 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x794339c323e3 in g_main_context_iteration () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x79433a876591 in
QEventDispatcherGlib::processEvents(QFlags)
(this=0x5c7333839a30, flags=...) at
./src/corelib/kernel/qeventdispatcher_glib.cpp:396
#24 0x79433aaa3e3b in
QEventLoop::exec(QFlags)
(this=this@entry=0x7fff5118a6d0, flags=..., flags@entry=...) at
./src/corelib/global/qflags.h:34
#25 0x79433aaa5a6c in QCoreApplication::exec() () at
./src/corelib/global/qflags.h:74
#26 0x79433b0e4330 in QGuiApplication::exec() () at
./src/gui/kernel/qguiapplication.cpp:1926
#27 0x79433be078d9 in QApplication::exec() () at
./src/widgets/kernel/qapplication.cpp:2555
#28 0x5c73322cbb92 in main(int, char**) (argc=,
argv=) at ./src/main.cpp:290
[Inferior 1 (process 6609) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #7 from Dennis --- Seems to be fixed in: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900 12-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: NV174 Manufacturer: Alienware Product Name: Alienware Aurora Ryzen Edition R14 System Version: 2.15.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 Dennis changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477665] Cannot move icon in icons-only task manager if multiple instances of a program are running
https://bugs.kde.org/show_bug.cgi?id=477665 Dennis changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Dennis --- It is not happening to me either in Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900 12-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: NV174 Manufacturer: Alienware Product Name: Alienware Aurora Ryzen Edition R14 System Version: 2.15.0 cl;osing the issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" display-visualization is missing
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #8 from Dennis --- Seems to be fixed in: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900 12-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: NV174 Manufacturer: Alienware Product Name: Alienware Aurora Ryzen Edition R14 System Version: 2.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #117 from Dennis --- Does not seem to be happening anymore on: Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-26-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900 12-Core Processor Memory: 31,2 GiB of RAM Graphics Processor: NV174 Manufacturer: Alienware Product Name: Alienware Aurora Ryzen Edition R14 System Version: 2.15.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #10 from Dennis --- Created attachment 168340 --> https://bugs.kde.org/attachment.cgi?id=168340&action=edit breeze1 breeze theme selected -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #11 from Dennis --- Created attachment 168341 --> https://bugs.kde.org/attachment.cgi?id=168341&action=edit breeze2 second breeze theme selected -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477674] Notifications KCM "Choose Custom Position" UI is broken
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #12 from Dennis --- I can't reproduce in unstable, fixed upstream? I tested breeze and Breeze dark. I am on: Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.3 Kernel Version: 6.5.0-27-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 I attached 2 screenshots from breeze and breeze dark. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483896] New: Addition to Software update: update software at restart or shutdown
https://bugs.kde.org/show_bug.cgi?id=483896 Bug ID: 483896 Summary: Addition to Software update: update software at restart or shutdown Classification: Plasma Product: plasmashell Version: 6.0.2 Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: dennis@thegood.cloud CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY *** I would like a feature request to add an update option to the shutdown/restart button. So add an option to "update and shutdown" besides shutdown. *** ADDITIONAL INFORMATION We have discussed the feature on discuss here: https://discuss.kde.org/t/addition-to-software-update-update-software-at-restart-or-shutdown/11524/15 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] SDDM and kscreenlocker does not accept enter key in X11
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #42 from Dennis --- @Carlos De Maine, Thank you for helping me with virtualbox and kde unstable. To confirm: - I could reproduce this in Virtualbox with kde unstable, source: neon-unstable-20231224-1120.iso - After updating to today's packages (6th of feb) the bug still exists. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 446119] plasma-browser-integration-host crashes after closing Firefox
https://bugs.kde.org/show_bug.cgi?id=446119 --- Comment #3 from Dennis --- Does not happen anymoren on: Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 External monitor connected through Dell TB16. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487322] New: Guide Module shows FOV as 35.2 x 12015.8 using simulator guide scope. Can't see stars to guide by.
https://bugs.kde.org/show_bug.cgi?id=487322 Bug ID: 487322 Summary: Guide Module shows FOV as 35.2 x 12015.8 using simulator guide scope. Can't see stars to guide by. Classification: Applications Product: kstars Version: 3.7.0 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: dennisjcoll...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Using simulators I apparently get a glitch with FOV in guide module. If I select sample guide scope it reports fov of 35.2 x 12015.8. Interestingly, for the primary train using Sample Primary 700@F/5.8 it shows FOV is 24.1 x 17.9. However as an attempt to troubleshoot I also set the Sample Primary scope for secondary train and it shows the same scope now with a field of view of 15.1 x 5149.6. STEPS TO REPRODUCE 1. using simulator choose use sample guide 300@F/6.0 2. In guide module select secondary train 3. Scope / Lens Info shows FOV 35.2 x 12015.8 OBSERVED RESULT Can't see any stars to track EXPECTED RESULT Track multi stars SOFTWARE/OS VERSIONS macOS: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487333] New: Discover doesnt update
https://bugs.kde.org/show_bug.cgi?id=487333 Bug ID: 487333 Summary: Discover doesnt update Classification: Applications Product: Discover Version: 5.27.11 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: dsou...@gmx.com CC: aleix...@kde.org Target Milestone: --- Created attachment 169685 --> https://bugs.kde.org/attachment.cgi?id=169685&action=edit Themessage received *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am receiving an error: Aborted due to failure (While trying to apply extra data: apply_extra script failed, exit status 256) and discover is not updating applications (Kubuntu 24.04). -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487342] New: Capture Module under file settings cannot change directory
https://bugs.kde.org/show_bug.cgi?id=487342 Bug ID: 487342 Summary: Capture Module under file settings cannot change directory Classification: Applications Product: kstars Version: 3.7.0 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: dennisjcoll...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When selecting the folder button next to the Directory field under File Settings in the Capture Module nothing happens. A spinning color wheel appears indicating it is attempting the operation but it eventually just times out and nothing happens. STEPS TO REPRODUCE 1. goto capture module 2. select folder icon to change directory under file settings 3. nothing happens OBSERVED RESULT Spinning colored wheel and eventually times out EXPECTED RESULT window appear to change directory where images will be saved to SOFTWARE/OS VERSIONS Windows: macOS: version 14.4.1 Sonoma Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487333] Discover doesnt update
https://bugs.kde.org/show_bug.cgi?id=487333 --- Comment #2 from Dennis --- Thank you very very much! Στις 22/5/24 10:16, ο/η Harald Sitter έγραψε: > https://bugs.kde.org/show_bug.cgi?id=487333 > > Harald Sitter changed: > > What|Removed |Added > > CC||sit...@kde.org > Resolution|--- |WAITINGFORINFO > Status|REPORTED|NEEDSINFO > > --- Comment #1 from Harald Sitter --- > what's the output of > > flatpak repair > flatpak update > -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443735] Thumbnails for .cbz files does not support .webp, .avif etc
https://bugs.kde.org/show_bug.cgi?id=443735 Dennis changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |crap-den...@gmx.net Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||crap-den...@gmx.net Ever confirmed|0 |1 --- Comment #2 from Dennis --- Created attachment 150945 --> https://bugs.kde.org/attachment.cgi?id=150945&action=edit webp works, avif does not I came across the same problem with avif files inside cbz containers and stumbled upon this bug report. Although it says it was resolved, I still have no thumbnails for containers only having avif files. Testing it with webp, I noticed that it works with here, so it looks like this issue was only partially solved. Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-41-generic (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 5 1500X Quad-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443735] Thumbnails for .cbz files does not support .webp, .avif etc
https://bugs.kde.org/show_bug.cgi?id=443735 Dennis changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Dennis --- This has just been fixed in 9f540815 That was a fast fix! I don't know if you saw this post which made you push to fix this, as it seems you faced the same issue on your own, but thank you anyway, Pedro! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478880] plasmashell crash after updating
https://bugs.kde.org/show_bug.cgi?id=478880 Dennis changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Dennis --- Ok, updated today and can't reproduce. Closing. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477621] theming like login screen and splash screen do not seem compatible with plasma6
https://bugs.kde.org/show_bug.cgi?id=477621 --- Comment #2 from Dennis --- I understand. wouldn't it be better to seperate the qt5 from the qt6? Like they did with the splash screens here: https://bugs.kde.org/show_bug.cgi?id=476930 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479071] New: I can't use enter at login screen
https://bugs.kde.org/show_bug.cgi?id=479071 Bug ID: 479071 Summary: I can't use enter at login screen Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install KDE Neon unstable 2. start it 3. try to login with password + enter. OBSERVED RESULT this doesn't work. I need to click > to login. Or use tab to highlight > and enter. EXPECTED RESULT I should be able to login by filling in password + enter. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION This is not so critical, except.. As most current theme's are not compatible in qt6 (as I understand it, i'm not a dev) there is no > in the fallback theme and you can't login. Manually copying the breeze theme to the non-working theme fixed this, but this should be fixed to prevent ppl locking themselves out in the final version. - the theming details: https://bugs.kde.org/show_bug.cgi?id=477621 - related: https://bugs.kde.org/show_bug.cgi?id=476930 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479071] I can't use enter to confirm password at login screen
https://bugs.kde.org/show_bug.cgi?id=479071 Dennis changed: What|Removed |Added Summary|I can't use enter at login |I can't use enter to |screen |confirm password at login ||screen -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479071] I can't use enter at login screen to confirm password
https://bugs.kde.org/show_bug.cgi?id=479071 Dennis changed: What|Removed |Added Summary|I can't use enter to|I can't use enter at login |confirm password at login |screen to confirm password |screen | -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477674] popup position for notification misses screen
https://bugs.kde.org/show_bug.cgi?id=477674 --- Comment #5 from Dennis --- (In reply to Dennis from comment #1) > Still happens on > > Operating System: KDE neon Unstable Edition > KDE Plasma Version: 5.90.0 > KDE Frameworks Version: 5.246.0 > Qt Version: 6.6.0 > Kernel Version: 6.2.0-37-generic (64-bit) > Graphics Platform: Wayland > Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz > Memory: 15,3 GiB of RAM > Graphics Processor: Mesa Intel® UHD Graphics 620 > Manufacturer: Dell Inc. > Product Name: XPS 13 9380 And: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460753] Feature request: network manager VPN connection parameter free field
https://bugs.kde.org/show_bug.cgi?id=460753 Dennis changed: What|Removed |Added Version|5.90.0 |5.91.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478990] Plasmashell crashes upon unplugging and repluging a monitor in portrait mode
https://bugs.kde.org/show_bug.cgi?id=478990 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #3 from Dennis --- Ok, weird stuff is happening after trying to reproduce. I can confirm things aren't working as they should, but I have to note: - I tried it while my system was connected to a TB16 docking, which has the external monitor coupled. - I can't report the crash due to https://bugs.kde.org/show_bug.cgi?id=478883 https://bugs.kde.org/show_bug.cgi?id=478885 I do have the bug reports saved locally, although drkonqi reports it is not usable. let me know if they are still of interest. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #7 from Dennis --- confirmed on: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #8 from Dennis --- does not happen to me with kscreenlocker -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478898] Visual corruption on panel when using adaptive or translucent opacity in portrait mode
https://bugs.kde.org/show_bug.cgi?id=478898 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #2 from Dennis --- I can't reproduce this with: - one laptop with built-in screen of 3840x2160 - Dell TB16 docking connected to external screen 3840x2160 - panels on both screens. - panel on external monitor with adaptive (and tried) translucent Can you attach the screenshot? My specs: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 478994] A disabled screen disconnecting and reconnecting itself causes display layout updates
https://bugs.kde.org/show_bug.cgi?id=478994 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #1 from Dennis --- I can't reproduce. What I did was: 1. have an external monitor (Dell U2718Q) connected through docking Dell TB16 on a XPS13 laptop. External is configured as main. 2. have both displays connected 3. Go to settings, display config, unselect "Enabled" on the external monitor. 4. The screen focusses on the built-in screen as expected. No flickering on unexpected behaviour. The monitor tries to find a signal and finding none, it goes into sleep mode. 5. Wait until the display config times out as it does not get a confirmation (takes 15secs). 6. the system defaults to original settings, which has the external display as main and the monitor comes out of sleep mode. Let me know if I tested correctly or what I should do. I don't fully comprehend what the G27Q is doing. Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478898] Visual corruption on panel when using adaptive or translucent opacity in portrait mode
https://bugs.kde.org/show_bug.cgi?id=478898 --- Comment #4 from Dennis --- Created attachment 164478 --> https://bugs.kde.org/attachment.cgi?id=164478&action=edit corruption1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478898] Visual corruption on panel when using adaptive or translucent opacity in portrait mode
https://bugs.kde.org/show_bug.cgi?id=478898 --- Comment #5 from Dennis --- Created attachment 164479 --> https://bugs.kde.org/attachment.cgi?id=164479&action=edit corruption2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478898] Visual corruption on panel when using adaptive or translucent opacity in portrait mode
https://bugs.kde.org/show_bug.cgi?id=478898 --- Comment #6 from Dennis --- Ignore my previous comment, I missed it's in portrait mode. I can reproduce the issue somewhat, I see: - very small task bar icons (see attachment). The launcher icon and system tray icons are the correct size. - some corruption in the preview (see attachment) My system: - one laptop with built-in screen of 3840x2160 - Dell TB16 docking connected to external screen 3840x2160 - panel on external monitor with adaptive panel Can you attach the screenshot? My specs: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478898] Visual corruption on panel when using adaptive or translucent opacity in portrait mode
https://bugs.kde.org/show_bug.cgi?id=478898 --- Comment #7 from Dennis --- Does not happen on neon-testing-20231219-0252.iso -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #10 from Dennis --- I use wayland (In reply to fanzhuyifan from comment #9) > (In reply to Dennis from comment #7) > > confirmed on: > > > > Operating System: KDE neon Unstable Edition > > KDE Plasma Version: 5.91.90 > > KDE Frameworks Version: 5.248.0 > > Qt Version: 6.6.1 > > Kernel Version: 6.2.0-39-generic (64-bit) > > Graphics Platform: Wayland > > Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz > > Memory: 15,3 GiB of RAM > > Graphics Processor: Mesa Intel® UHD Graphics 620 > > Manufacturer: Dell Inc. > > Product Name: XPS 13 9380 > > Is your sddm using wayland or x11? Wayland as far as I can see. I login with Wayland selected at least. I'm not sure if the system boots up with x11/wayland before logging in. I looked at the sddm config files, but no x11 is set. Let me know how I can check this further if you need to know more. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479384] New: energy settings not honered?
https://bugs.kde.org/show_bug.cgi?id=479384 Bug ID: 479384 Summary: energy settings not honered? Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY *** I have a TB16 dock with an external monitor. I have my energy settings set to do nothing when closing the lid while on AC power. I could close the lid and keep on working. It looks like this behaviour does not work correctly anymore *** STEPS TO REPRODUCE 1. have neon unstable updated, clean start OS with dock attached and lid open. 2. connect TB16 dock to my XPS13 with external monitor 3. login to session 4. both displays are enabled (or just external monitor), close lid. 5. system goes to sleep mode (this used to be the previous setting. OBSERVED RESULT closing lid lets system sleep while energy settings are set to do nothing. EXPECTED RESULT Closing the lid should not do anything as I have configured the energy settings to do nothing. Software versions: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION Interesting, this used to work. I don't know with what previous version, I presume about a month ago or so. It also results in a crash of plasmashell. I can't attach drkonqi reports due to bugs: https://bugs.kde.org/show_bug.cgi?id=478885 https://bugs.kde.org/show_bug.cgi?id=478883 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479384] energy settings not honered?
https://bugs.kde.org/show_bug.cgi?id=479384 Dennis changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478147] fwupd shows segmentation fault
https://bugs.kde.org/show_bug.cgi?id=478147 --- Comment #1 from Dennis --- sudo fwupdmgr get-updates results currently in: Failed to connect to daemon: Error calling StartServiceByName for org.freedesktop.fwupd: Failed to activate service 'org.freedesktop.fwupd': timed out (service_start_timeout=25000ms) Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #13 from Dennis --- I tried to install a VM with Neon unstable to reproduce on a clean system, but currently the Neon unstable iso's won't install a Virtualbox VM. it does not happen with kscreenlocker after I'm logged in, which would suggest my system boots with an X11 and switches to wayland after logging in. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #16 from Dennis --- (In reply to Russ Hay from comment #15) > (In reply to Russ Hay from comment #14) > > I also had this issue - but reconfigured sddm to use Wayland > > (https://wiki.archlinux.org/title/SDDM#Running_under_Wayland) and the enter > > key works with SDDM on Wayland. > > I'm running Plasma 6 Beta 2 on KDE Neon (unstable) I tried it, but does not seem to work for me. I entered: [General] DisplayServer=wayland updated the system, rebooted but still no joy. /etc/sddm.conf is empty (0 bytes) /etc/sddm.conf.d/kde_settings.conf has just basic settings: [Autologin] Relogin=false Session= User= [General] HaltCommand= RebootCommand= [Theme] Current=breeze CursorSize= CursorTheme=breeze_cursors Font=Noto Sans,10,-1,0,400,0,0,0,0,0,0,0,0,0,0,1 [Users] MaximumUid=6 MinimumUid=1000 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478875] Cannot login by pressing enter/return
https://bugs.kde.org/show_bug.cgi?id=478875 --- Comment #18 from Dennis --- Ah yes, did read it but was not registered in my brain. My bad. I don't know too much on all the details, I was just reading up what a compositor was, weston vs kwin, etc. A bit new on this stuff all. I'm mainly here to report bugs and test, for all the rest im a newb. But it was fixed! For reference, my /etc/sddm.conf.d/10-wayland.conf contains now: [General] DisplayServer=wayland GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell [Wayland] CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1 Is this just a side effect from running unstable or does there need to be action for plasma6? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 479485] New: dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=479485 Bug ID: 479485 Summary: dolphin crashed Classification: Applications Product: dolphin Version: 24.01.85 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dennis@thegood.cloud CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (24.01.85) Qt Version: 6.6.1 Frameworks Version: 5.248.0 Operating System: Linux 6.2.0-39-generic x86_64 Windowing System: Wayland Distribution: KDE neon Unstable Edition DrKonqi: 5.91.90 [CoredumpBackend] -- Information about the crash: I tried to go directory /home/dennis/Documents/talk2.tgc/07. Medewerkers Drive/Dennis/Ubuntu Scripts/ and Dolphin crashed. It kept crashing if i repeated the action. 8 hours later I started Nextcloud desktop client (which syncs this dir) I could open this directory again. The crash does not seem to be reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault This GDB supports auto-downloading debuginfo from the following URLs: https://debuginfod.neon.kde.org/: Enable debuginfod for this session? (y or [n]) [answered N; input not from terminal] Debuginfod has been disabled. To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit. [New LWP 11353] [New LWP 11290] [New LWP 11293] [New LWP 11292] [New LWP 11288] [New LWP 11289] [New LWP 11308] [New LWP 11307] [New LWP 11295] [New LWP 11296] [New LWP 11328] [New LWP 11309] [New LWP 11325] [New LWP 11298] [New LWP 11327] [New LWP 11310] [New LWP 11329] [New LWP 11291] [New LWP 11330] [New LWP 11294] [New LWP 11323] [New LWP 11297] [New LWP 11354] [New LWP 11324] [New LWP 11361] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/dolphin'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=140379891385920) at ./nptl/pthread_kill.c:44 [Current thread is 1 (Thread 0x7facbd8f4640 (LWP 11353))] Cannot QML trace cores :( [Current thread is 1 (Thread 0x7facbd8f4640 (LWP 11353))] Thread 25 (Thread 0x7facbc8f2640 (LWP 11361)): #0 0x7fad24718ade in __ppoll (fds=0x7facbc8f1778, nfds=1, timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42 #1 0x7fad2514e544 in ppoll (__ss=0x0, __timeout=0x0, __nfds=1, __fds=0x7facbc8f1778) at /usr/include/x86_64-linux-gnu/bits/poll2.h:64 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7facbc8f1778) at ./src/corelib/kernel/qcore_unix.cpp:126 #3 qt_safe_poll (timeout_ts=, nfds=, fds=) at ./src/corelib/kernel/qcore_unix.cpp:149 #4 qt_safe_poll (fds=fds@entry=0x7facbc8f1778, nfds=nfds@entry=1, timeout_ts=) at ./src/corelib/kernel/qcore_unix.cpp:144 #5 0x7fad249732f7 in qt_poll_msecs (nfds=1, timeout=, fds=0x7facbc8f1778) at ./obj-x86_64-linux-gnu/include/QtCore/6.6.1/QtCore/private/../../../../../../src/corelib/kernel/qcore_unix_p.h:404 #6 QNativeSocketEnginePrivate::nativeSelect (this=, timeout=, checkRead=, checkWrite=, selectForRead=0x7facbc8f185f, selectForWrite=0x7facbc8f185e) at ./src/network/socket/qnativesocketengine_unix.cpp:1379 #7 0x7fad249c7aa9 in QNativeSocketEngine::waitForReadOrWrite (this=0x7faca0005fd0, readyToRead=0x7facbc8f185f, readyToWrite=, checkRead=, checkWrite=, msecs=, timedOut=0x0) at ./src/network/socket/qnativesocketengine.cpp:1084 #8 0x7fad249bfb93 in QAbstractSocket::waitForReadyRead (this=0x7faca0002988, msecs=-1) at ./src/network/socket/qabstractsocket.cpp:2162 #9 0x7fad271d8be8 in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6 #10 0x7fad272c66df in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6 #11 0x7fad272a4d0b in ?? () from /lib/x86_64-linux-gnu/libKF6KIOCore.so.6 #12 0x7fad2515f6ed in operator() (__closure=) at ./src/corelib/thread/qthread_unix.cpp:324 #13 (anonymous namespace)::terminate_on_exception > (t=...) at ./src/corelib/thread/qthread_unix.cpp:260 #14 QThreadPrivate::start (arg=0x55b8d17378f0) at ./src/corelib/thread/qthread_unix.cpp:283 #15 0x7fad24694ac3 in start_thread (arg=) at ./nptl/pthread_create.c:442 #16 0x7fad24726660 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 Thread 24 (Thread 0x7facd4cf6640 (LWP 11324)): #0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x7facd4cf5970, op=137, expected=0, futex_word=0x55b8d15a2f14) at ./nptl/futex-internal.c:57 #1 __futex_abstimed_wait_common (cancel=true, private=0, abstime=0x7facd4cf5970, clockid=560, expected=0, futex_word=0x55b8d15a2f14) at ./nptl/futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x55b8d15a2f14, expected=expected@entry=0, clockid=clockid@en
[dolphin] [Bug 479485] dolphin crashed
https://bugs.kde.org/show_bug.cgi?id=479485 Dennis changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478885] drkonqi is unable to generate report on Neon unstable, plasma_beta2 (v5.91)
https://bugs.kde.org/show_bug.cgi?id=478885 --- Comment #1 from Dennis --- Not sure if it is fixed, but I just reported a crashed Dolphin through Drkonqi and that worked: https://bugs.kde.org/show_bug.cgi?id=479485 If plasmashell crashes (any way to force/simulate that?) i'll test again with drkonqi. My currect specs are: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478885] drkonqi is unable to generate report on Neon unstable, plasma_beta2 (v5.91)
https://bugs.kde.org/show_bug.cgi?id=478885 Dennis changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Dennis --- This is fixed in my edition, I had a plasmashell crash again and I could report through Drkonqi again. I'm currently at: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 Updated to latest on 10 jan 2024. I'm closing this issue. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 478883] drkonqi does not install debug packages on Neon unstable edition (plasma6_beta2)
https://bugs.kde.org/show_bug.cgi?id=478883 Dennis changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Dennis --- This issue was raised because I had an issue with reporting through drkonqi (bug report: https://bugs.kde.org/show_bug.cgi?id=478885). As that bug has been resolved, I think this issue can be closed too, so I'm closing. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479607] New: plasmashell crash after login with closed lid
https://bugs.kde.org/show_bug.cgi?id=479607 Bug ID: 479607 Summary: plasmashell crash after login with closed lid Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 164786 --> https://bugs.kde.org/attachment.cgi?id=164786&action=edit drkonqi plasmashell crash.md SUMMARY If I login with the lid closed of my laptop, plasmashell crashed. I have connected a dock with an external monitor. STEPS TO REPRODUCE 1. Laptop turned off, lid closed. 2. Connect to Dell TB16 Dock. 3. Laptop turns itself on, I get a grub menu on the external monitor 4. system boots to Loginscreen 5. I login with my creds, screen turns black. 6. After I open the lid, the screen comes back with Drkonqi with a plasmashell crash. OBSERVED RESULT black screen after login EXPECTED RESULT having a desktop session, without plasmashell crash. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.91.90 KDE Frameworks Version: 5.248.0 Qt Version: 6.6.1 Kernel Version: 6.2.0-39-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION - Drkonqi crash report attached - updated neon unstable to today. - -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479607] plasmashell crash after login with closed lid
https://bugs.kde.org/show_bug.cgi?id=479607 Dennis changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479607] plasmashell crash after login with closed lid
https://bugs.kde.org/show_bug.cgi?id=479607 --- Comment #1 from Dennis --- Created attachment 164787 --> https://bugs.kde.org/attachment.cgi?id=164787&action=edit Ubuntu 23.10 specs -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479607] plasmashell crash after login with closed lid
https://bugs.kde.org/show_bug.cgi?id=479607 --- Comment #2 from Dennis --- It does not happen on Ubuntu 23.10, I have attached the specs of the kubuntu env I tested with. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 479607] plasmashell crash after login with closed lid
https://bugs.kde.org/show_bug.cgi?id=479607 --- Comment #3 from Dennis --- Created attachment 164789 --> https://bugs.kde.org/attachment.cgi?id=164789&action=edit crash happens when opening / closing the lid It also happens if I close the lid and open it, reproducable every time. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479886] New: Save session (Session Restore) does not seem to work
https://bugs.kde.org/show_bug.cgi?id=479886 Bug ID: 479886 Summary: Save session (Session Restore) does not seem to work Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: dennis@thegood.cloud CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY *** If I choose "save session" from the launcher and reboot I get an empty/normal shell. Saving the session does not seem to work. *** STEPS TO REPRODUCE 1. Install KDE Neon (stable) 2. Set Desktop Session -> Session Restore --> When session was manually saved 3. Reboot 4. run a bunch of programs, like Firefox, Terminator, Brave, spotify, signal, etc. 5. Login, start launcher, choose "save session" 6. Reboot 7. Login OBSERVED RESULT normal/empty shell. Only apps in startup list are started. EXPECTED RESULT I would expect to have my previous session back SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27 (available in About System) KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 472635] New: Feature request: Add shortcut for "Enlarge Font" and "Shrink Font"
https://bugs.kde.org/show_bug.cgi?id=472635 Bug ID: 472635 Summary: Feature request: Add shortcut for "Enlarge Font" and "Shrink Font" Classification: Applications Product: yakuake Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: task Priority: NOR Component: general Assignee: h...@kde.org Reporter: bugs@varum.dk Target Milestone: --- Created attachment 160523 --> https://bugs.kde.org/attachment.cgi?id=160523&action=edit screenshot of Konsole shortcuts Hey Yakuake project, will it be possible to add a shortcut to increase and decrease the terminal font size? I know that it is possible by keeping the CTRL button down and using the scroll-wheel, but I would like to have a keyboard shortcut for this. In Konsole these shortcuts are called "Enlarge Font" and "Shrink Font", so I suggest naming them the same here -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 472635] Feature request: Add shortcut for "Enlarge Font" and "Shrink Font"
https://bugs.kde.org/show_bug.cgi?id=472635 Dennis changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 476647] xdg-portal-desktop-kde start after xdg-portal-desktop, if it even starts
https://bugs.kde.org/show_bug.cgi?id=476647 Dennis changed: What|Removed |Added Summary|xdg-portal-desktop-kde |xdg-portal-desktop-kde |startd before |start after |xdg-portal-desktop, if it |xdg-portal-desktop, if it |even starts |even starts -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 476993] New: KBibTex crash when trying to save a element with a crossref
https://bugs.kde.org/show_bug.cgi?id=476993 Bug ID: 476993 Summary: KBibTex crash when trying to save a element with a crossref Classification: Applications Product: KBibTeX Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fisc...@unix-ag.uni-kl.de Reporter: bugs@varum.dk Target Milestone: --- Application: kbibtex (0.10.0) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.1.60-1-lts x86_64 Windowing System: Wayland Distribution: "Arch Linux" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: KBibTex crash when trying to save a element with a crossref, it happens quite offent but not always. The crash can be reproduced sometimes. -- Backtrace: Application: KBibTeX (kbibtex), signal: Segmentation fault [KCrash Handler] #4 0x7fd660eaeb42 in __cxxabiv1::__dynamic_cast(void const*, __cxxabiv1::__class_type_info const*, __cxxabiv1::__class_type_info const*, ptrdiff_t) (src_ptr=0x556173986b10, src_type=0x5561718eb300 , dst_type=0x7fd663088248 , src2dst=0) at /usr/src/debug/gcc/gcc/libstdc++-v3/libsupc++/dyncast.cc:58 #5 0x7fd66337d0e0 in FieldInput::selectCrossRef() () at /usr/lib/libkbibtexgui.so.0 #6 0x7fd6614d1097 in () at /usr/lib/libQt5Core.so.5 #7 0x7fd66225c677 in QAbstractButton::clicked(bool) () at /usr/lib/libQt5Widgets.so.5 #8 0x7fd66225ef2a in () at /usr/lib/libQt5Widgets.so.5 #9 0x7fd66226042c in () at /usr/lib/libQt5Widgets.so.5 #10 0x7fd6622605d0 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #11 0x7fd6621af1a1 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #12 0x7fd6621788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #13 0x7fd66217ddaf in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #14 0x7fd66149c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #15 0x7fd66217c0ea in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #16 0x7fd6621cce85 in () at /usr/lib/libQt5Widgets.so.5 #17 0x7fd6621cebd7 in () at /usr/lib/libQt5Widgets.so.5 #18 0x7fd6621788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #19 0x7fd66149c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #20 0x7fd66194194c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #21 0x7fd66192a6e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #22 0x7fd651ae5ce5 in () at /usr/lib/libQt5WaylandClient.so.5 #23 0x7fd656e3af69 in () at /usr/lib/libglib-2.0.so.0 #24 0x7fd656e99327 in () at /usr/lib/libglib-2.0.so.0 #25 0x7fd656e39162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #26 0x7fd6614eaf7c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #27 0x7fd66149ae74 in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #28 0x7fd66237473b in QDialog::exec() () at /usr/lib/libQt5Widgets.so.5 #29 0x7fd6633891ce in FileView::editElement(QSharedPointer) () at /usr/lib/libkbibtexgui.so.0 #30 0x7fd5d3f3aeeb in () at /usr/lib/qt/plugins/kbibtexpart.so #31 0x7fd6614d1097 in () at /usr/lib/libQt5Core.so.5 #32 0x7fd66335519a in FileView::elementExecuted(QSharedPointer) () at /usr/lib/libkbibtexgui.so.0 #33 0x7fd66338501b in FileView::itemActivated(QModelIndex const&) () at /usr/lib/libkbibtexgui.so.0 #34 0x7fd6614d1097 in () at /usr/lib/libQt5Core.so.5 #35 0x7fd6623e372a in QAbstractItemView::doubleClicked(QModelIndex const&) () at /usr/lib/libQt5Widgets.so.5 #36 0x7fd66244c805 in QTreeView::mouseDoubleClickEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #37 0x7fd6621aef2b in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #38 0x7fd66225d9d3 in QFrame::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #39 0x7fd661499142 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #40 0x7fd6621788ef in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #41 0x7fd66217ddaf in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #42 0x7fd66149c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #43 0x7fd66217c0ea in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /us
[systemsettings] [Bug 476930] Unable to change or preview non-Breeze splash screens
https://bugs.kde.org/show_bug.cgi?id=476930 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #5 from Dennis --- Something is wrong with the temporary location, for example if I try to install the "beatifulltree" splash screen it shows: ``` kf.newstuff.core: Install: "BeautifulTreeAnimation" from "/tmp/CgosWX-BeautifulTreeAnimation.tar.gz" kf.package: Couldn't open metadata file "/tmp/CgosWX-BeautifulTreeAnimation.tar.gz" "/tmp/systemsettings-tfPoiI/BeautifulTreeAnimation/" ``` But there is no dir available with that directory: ``` ll /tmp/systemsettings- systemsettings-AJBtpW/ systemsettings-efOAMj/ systemsettings-nuLniY/ systemsettings-xOhdWD/ systemsettings-AYZJrt/ systemsettings-mtpmty/ systemsettings-pyITvm/ systemsettings-ZYXjXB/ ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475700] Vertical non-center-aligned panel overlaps windows
https://bugs.kde.org/show_bug.cgi?id=475700 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #1 from Dennis --- Created attachment 163440 --> https://bugs.kde.org/attachment.cgi?id=163440&action=edit correct behaviour -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475700] Vertical non-center-aligned panel overlaps windows
https://bugs.kde.org/show_bug.cgi?id=475700 --- Comment #2 from Dennis --- I can confirm this, I'm on: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475700] Vertical non-center-aligned panel overlaps windows
https://bugs.kde.org/show_bug.cgi?id=475700 --- Comment #3 from Dennis --- Created attachment 163441 --> https://bugs.kde.org/attachment.cgi?id=163441&action=edit correct -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475700] Vertical non-center-aligned panel overlaps windows
https://bugs.kde.org/show_bug.cgi?id=475700 Dennis changed: What|Removed |Added Attachment #163440|0 |1 is obsolete|| --- Comment #4 from Dennis --- Created attachment 163442 --> https://bugs.kde.org/attachment.cgi?id=163442&action=edit incorrect (actual) behaviour incorrect (actual) behaviour -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474430] Tiny cursor on Firefox when using scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=474430 Dennis changed: What|Removed |Added CC||dennis@thegood.cloud --- Comment #8 from Dennis --- I have the issue as well, I'm on: Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477485] New: Remmina does not display correct icon on plasma 5.81
https://bugs.kde.org/show_bug.cgi?id=477485 Bug ID: 477485 Summary: Remmina does not display correct icon on plasma 5.81 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- Created attachment 163447 --> https://bugs.kde.org/attachment.cgi?id=163447&action=edit remmina-no-systemtray-icon ## SUMMARY When installing remmina through snap on Neon, the system tray is not correctly loaded STEPS TO REPRODUCE 1. Install remmina through snap 2. start remmina OBSERVED RESULT 3. shows bad system tray icon, see attachment. EXPECTED RESULT should be an remmina icon SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477486] New: On Neon unstable, dolphin does not have any compress/extract context menu's anymore
https://bugs.kde.org/show_bug.cgi?id=477486 Bug ID: 477486 Summary: On Neon unstable, dolphin does not have any compress/extract context menu's anymore Classification: Applications Product: dolphin Version: 24.01.75 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: dennis@thegood.cloud CC: kfm-de...@kde.org Target Milestone: --- SUMMARY I'm missing the compress/extract options in Dolphin. STEPS TO REPRODUCE 1. Install Neon unstable 2. open dolphin OBSERVED RESULT No compress/extract options anymore. EXPECTED RESULT I would expect to have the compress/extract options as a context menu option. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477486] On Neon unstable, dolphin does not have any compress/extract context menu's anymore
https://bugs.kde.org/show_bug.cgi?id=477486 --- Comment #3 from Dennis --- Hi, Ark is installed. So I have 2 setups, on my workstation the integration is there, but it was a upgrade of ubuntu 23.10 to 24.04 (but it's 5.27.9). The Neon is a new installation (upgraded to latest) and it's missing integration. Please let me know how I can help. I'm not an dev but an sysop and can do a lot of testing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 --- Comment #19 from Dennis --- The bug is not solved by enabling the nvidia suspend thing. I experience this problem when the monitors turn off by the energy saving setting while the computer is still on, not by suspending the entire computer. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477621] New: theming like login screen and splash screen do not seem compatible with plasma6
https://bugs.kde.org/show_bug.cgi?id=477621 Bug ID: 477621 Summary: theming like login screen and splash screen do not seem compatible with plasma6 Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: dennis@thegood.cloud CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- STEPS TO REPRODUCE 1. try to install a login theme and apply. Only the breeze theme works 2. log back in. OBSERVED RESULT theme not applied, reverted to fallback. EXPECTED RESULT theme applied SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.81.80 KDE Frameworks Version: 5.245.0 Qt Version: 6.6.0 Kernel Version: 6.2.0-37-generic (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz Memory: 15,3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: Dell Inc. Product Name: XPS 13 9380 ADDITIONAL INFORMATION - Is this to be expected? Do we need to differentiate between plasma5/6 theming? how are we going to handle compatibility? - Im not a dev, but let me know how I can help with testing. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 --- Comment #21 from Dennis --- (In reply to fanzhuyifan from comment #20) > (In reply to Dennis from comment #19) > > The bug is not solved by enabling the nvidia suspend thing. I experience > > this problem when the monitors turn off by the energy saving setting while > > the computer is still on, not by suspending the entire computer. > > Humm do you also see this if you set the "when locked, turn off screen" to > 10 sec and then lock your computer and wait 10 seconds for the screen to > turn off? I wanted to double check because by default, the energy saving > setting also puts the computer to sleep after 15 min of inactivity, which > may be triggering in your case. > > It would also be great if you could provide the output of `journalctl -b` > when you see this again. > > Thanks! Yes. My test case: logging to KDE with Wayland, go to System Settings > Power Management > Energy Saving and set "Screen Energy Saving" to "1 min". I wait for the screens to turn off into stand-by. Then after a few seconds I move the mouse again to wake them up. This is when the entire desktop is black, windows are glitchy, taskbar is semi-broken. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 --- Comment #22 from Dennis --- Created attachment 163546 --> https://bugs.kde.org/attachment.cgi?id=163546&action=edit Journalctl log when the screen energy saver activates -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 477486] On Neon unstable, dolphin does not have any compress/extract context menu's anymore
https://bugs.kde.org/show_bug.cgi?id=477486 --- Comment #6 from Dennis --- No, Ark is using: Qt Version 5.15.11 (built against 5.15.11) Dolphin is using: Qt Version 6.6.0 (built against 6.6.0) -- You are receiving this mail because: You are watching all bug changes.
