Bug#993047: A libvirt-qemu user is added and shown on the login screen because the UID is too high

2021-08-26 Thread mYnDstrEAm
Package: libvirt Version: 5.0.0 I didn't create this user - I think it was added by installing the "Virtual Machine manager" (virt-manager) on Debian10/KDE, or more specifically by libvirt-daemon-system. `grep -E 'libvirt|qemu' /etc/passwd` returns `libvirt-qemu:x:64055:1xx:Libvirt

Bug#994791: During the Debian10->11 upgrade there is an rkhunter bug and the upgrade can fail due to lack of disk-space; after the upgrade the cursortheme isn't working, KDE Plasma doesn't start due t

2021-09-20 Thread mYnDstrEAm
Package: Debian Version: 11 Maybe these should be separate bug reports. However, I'm not sure about that and this is made more inconvenient and outdated by using emails for bug-reports. Filing it all under Debian rather than e.g. rkhunter or KDE Plasma packages is implying or calling for such

Bug#1023024: Session crashes when switching back to first display from a second one connected with HDMI when Wayland is used with KDE

2022-10-29 Thread mYnDstrEAm
Package: plasma-workspace Version: 5.20.5-6 First of all I don't know which package is causing this but it has to do with Wayland and KDE. Full description of the issue with some logs:

Bug#1018003: comment

2022-10-09 Thread mYnDstrEAm
May also be related to "Plasmashell problems after changing the HDMI output and KDE does not recognize the new display": https://bugs.kde.org/show_bug.cgi?id=457755 Currently, it doesn't crash anymore but I often need to go to an alt+f3 (any number) terminal and run `loginctl unlock-session

Bug#1018003: comment

2022-10-09 Thread mYnDstrEAm
In the totally outdated issue tracker I can't edit the text: it doesn't crash anymore because as a workaround I have the monitor HDMI cable disconnected except when I use it. When connecting the HDMI cable, the session ends only when the monitor that the HDMI cable is plugged into is turned

Bug#1068823: Stepwise Debian upgrade to enable systems with little free storage space to upgrade without breaks due to "No space left on device"

2024-04-11 Thread mYnDstrEAm
Package: general A distro upgrade of Debian needs a lot of disk space on the root partition. That partition often doesn't have a large size. That could for example be because it's on a mobile device, on a SSD drive, has lots of installed software, or because the user simply followed the advice

Bug#1068829: Disabling the autostart of KDE Connect and screenreader KAccessible

2024-04-11 Thread mYnDstrEAm
Package: kde-plasma-desktop Version: 5:142 These aren't needed for most users and are a privacy and security risk. In principle, it makes sense to only autostart things one actually needs to reduce the likelihood of crashes, the number of irrelevant log entries, the hardware resource

Bug#1068774: (No Subject)

2024-04-11 Thread mYnDstrEAm
> You found with #956330 already a feature request that asks for that No, that other issue is not about kept-back packages in specific. I don't see how the functionality of that issue would be very useful but for kept-back packages asking the user or by default not marking them as manually

Bug#1068832: Apper does not show the installation history anymore

2024-04-11 Thread mYnDstrEAm
Package: apper Version: 1.0.0 I think the installation history of the GUI Apper is very useful: it shows a history of package installs and removals with timestamps. I think it should also show other installations made via the command-line (dpkg.log files and .deb file installs). I don't know

Bug#1068769: When removing a package with an entry in /etc/xdg/autostart/ ask the user whether the autostart file should be removed or remove it by default

2024-04-10 Thread mYnDstrEAm
Package: apt Version: 2.6.1 See https://unix.stackexchange.com/questions/774058/shouldnt-files-in-etc-xdg-autostart-be-removed-when-removing-a-package/774068 Please make apt-get remove autostart entries from the /etc/xdg/autostart/ folder also if the --purge option is not used. Alternatively,

Bug#956330: (No Subject)

2024-04-10 Thread mYnDstrEAm
I think this would good. Created a similar issue here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068774 However, I don't think it's common that one manually installs a package that one already had installed as a dependency and doesn't want to mark it as manually installed, or is it? I

Bug#1068785: Sometimes the keyboard is turned off when waking from standby after upgrading to Debian12

2024-04-10 Thread mYnDstrEAm
Package: sddm Version: 0.19.0-5 This could also be an issue of the Sleep function. I'm using a laptop that suspends to swap partition. After upgrading to Debian12 with KDE, sometimes the keyboard of a laptop is turned off while the touchpad still works. It doesn't work again after putting it

Bug#1068777: plasma-systemmonitor with the process manager is not installed anymore after upgrading to Debian12

2024-04-10 Thread mYnDstrEAm
Package: kde-plasma-desktop Version: 5:142 After upgrading from Debian11/KDE to Debian12, plasma-systemmonitor was not installed. This should definitely be an installed package and I think it is configured to be. On Debian11, KSysGuard was used. Now there only is KSysguard in "Background

Bug#993047: (No Subject)

2024-04-10 Thread mYnDstrEAm
This problem still exists in Debian12! Shouldn't the user be hidden there because the UID is larger than the Maximum user UID set for the login screen in SDDM?

Bug#1068776: Apper and Discover ask to install "orphan-sysvinit-scripts" but not apt-get

2024-04-10 Thread mYnDstrEAm
Package: apper Version: 1.0.0 Why is that and is this a bug? If this is not the correct place to file it, please move this or tell me where to report it. sudo apt upgrade and sudo apt-get upgrade don't ask for this to be installed so I don't know why Apper and Discover ask for it to be

Bug#1068778: geoclue and gpsd are running by default (they aren't needed and could be used for location tracking)

2024-04-10 Thread mYnDstrEAm
Package: general I wondered why Debian comes with geoclue-2.0 and gpsd running by default (which could be used for location tracking). Please do not install them by default or if you really must, please do not make them autostart. At most it could be useful for a few users if it was installed

Bug#1068779: Shortcuts for systemmonitor and plasma-systemmonitor are missing after upgrade or when installing it

2024-04-10 Thread mYnDstrEAm
Package: plasma-systemmonitor Version: 5.27.5-2 On one of the machines I upgraded to Debian12 from Deb11/KDE the Default shortcut Ctrl+Esc for "Show System Activity" in "KDE Daemon" under Shortcuts is disabled but not on the other. This meant that the process manager didn't show anymore when

Bug#1068783: After upgrading to Debian12 the session SDDM automatically logs in to is changed

2024-04-10 Thread mYnDstrEAm
Package: sddm Version: 0.19.0-5 On one of the machines upgraded from Debian11 to Debian12 I had configured that it automatically logs in. But it seems like in the dropdown next to "with session" after the upgrade this was changed to "Kodi" instead of "Plasma (X11)" (there was no noticeable

Bug#1068774: When installing a package that is kept back with apt-get install do not mark it as manually installed or ask the user whether the mark should be added

2024-04-10 Thread mYnDstrEAm
Package: apt Version: 2.6.1 Could you please make apt not mark packages as manually installed when installing packages that have been kept back in specific? Alternatively, the user could be asked whether they want to have it marked if the mark would be added but I think most users would not

Bug#1042467: (No Subject)

2024-04-10 Thread mYnDstrEAm
Same here on multiple Debian/KDE machines after upgrading to Debian12. I think the title should be clearer or should this package actually be installed? I doubt it. For me it wants to remove way more than 30 packages, many of them being essential packages. See

Bug#1068780: Two login screens with the same name and with no preview/image

2024-04-10 Thread mYnDstrEAm
Package: sddm Version: 0.19.0-5 In Debian12 with KDE5 (SDDM v0.19.0-5) after an Upgrade from Debian11 under System Settings -> Startup and Shutdown -> Login Screen (SDDM) there are two Login screens with the same name and no preview. Screenshot in the link below (this issue tracking system is

Bug#1068784: When configuring Wayland to be the default at the login screen this doesn't change the session the user is automatically logged into

2024-04-10 Thread mYnDstrEAm
Package: sddm Version: 0.19.0-5 When configuring Wayland to be the default at the login screen (dropdown in the upper left) as recommended at places where people asked about how to switch from X11 to Wayland, this doesn't change the session the user is automatically logged into. I think it

Bug#1068774: (No Subject)

2024-04-13 Thread mYnDstrEAm
> So, which is it: You install random things you don't care about because their > name appeared in the kept-back list or you explicitly install that package > from the kept-back list because you care very deeply about it? I and many others (this issue is not about me) install them like that

Bug#1068774: (No Subject)

2024-04-13 Thread mYnDstrEAm
> And I tried to explain to you that many others believe in the exact opposite Sure, I'm aware of that. Once again, this is about kept-back packages. When kept-back packages in specific are installed through apt-get install, then that is usually not because the user wanted to mark them as

Bug#1068823: (No Subject)

2024-04-13 Thread mYnDstrEAm
Thanks guys, these are very useful methods and I'll mention these as alternatives to disk cleanups recommended at https://unix.stackexchange.com/q/774199/233262 (this would probably very useful to have at places about upgrades failing due to disk space issues even though people only look these

Bug#1068823: (No Subject)

2024-04-13 Thread mYnDstrEAm
> Personally, I don't think a machine that has that limited storage ought to be > upgraded using apt from one Debian stable release to another. It's not the machine but the partition. One can set up Debian to use a separate partition for the home directory. When the root partition on a SSD has

Bug#1068801: (No Subject)

2024-04-19 Thread mYnDstrEAm
When I run apper from the console there is this: > apper.lib: errorCode: PackageKit::Transaction::ErrorNotAuthorized "Failed to > obtain authentication." > apper.lib: PackageKit::Transaction::ExitFailed > PackageKit::Transaction::RoleInstallPackages > kf.kwidgetsaddons: Invalid pixmap

Bug#1069325: A smaller lockscreen is shown above a larger one due to a second enabled powered-off display device

2024-04-19 Thread mYnDstrEAm
Package: kde-plasma-desktop Version: 5:142 This is occurring after upgrading to Debian12 whenever waking from sleep or locking the screen. First submitted this here: https://bugs.kde.org/show_bug.cgi?id=485199 I could click on both password boxes to enter the password and login (it doesn't

Bug#1019438: (No Subject)

2024-04-14 Thread mYnDstrEAm
Control: reassign -1 kde-plasma-desktop [5:142] This problem still exists in Debian12 with Wayland. It only works with the VLC player where I can use the preview to change tracks but it doesn't work for apps like Dolphin, konsole, firefox, Discover and so on. I checked and there is this output

Bug#1068801: Apper shows Authorization failed error "You have failed to provide correct authentication." when trying to install packages

2024-04-11 Thread mYnDstrEAm
Package: apper Version: 1.0.0 I think I had this same problem already long ago sometimes and whenever it happened just used apt-get install instead of Apper (which works without any issues). I'm using Debian12 with KDE. The full error message in the box that plops up after confirming the