Bug#1104205: maliit-keyboard: When typing in the chromium url bar it acts like the shift key is pressed

Package: maliit-keyboard Version: 2.3.1-6+b2 Severity: normal If I enter "123" in the URL bar of Firefox it appears as expected, but when I do it in Chromium it gives "!@#". It also takes '.' as '>' making it impossible to type a URL. I don't know how much blame should be attributed to chromium

Bug#1104190: nvidia-kernel-dkms: package postinst failing due to module overwrite

On Sunday, 27 April 2025 17:04:25 AEST Andreas Beckmann wrote: > > The error about the module version not being newer would be because the > > postinst has been run many times (every time I install packages) and > > compiles the same files. Maybe there should be a --force to address that > > case.

Bug#1104199: kmod: incorrect and confusing error message on EACCES

Package: kmod Version: 34.2-2 Severity: normal When modinfo is unable to access a module due to path permissions it gets EACCES and that should be reported to the user as "permission denied" (or similar). It currently says "not found" which leads the user to believe that it was not there which is

Bug#1104190: nvidia-kernel-dkms: package postinst failing due to module overwrite

Package: nvidia-kernel-dkms Version: 535.216.03-3 Severity: normal -rw-r--r--. 1 root root 44804808 Apr 27 15:09 /var/lib/dkms/nvidia-current/535.216.03/6.12.22-amd64/x86_64/module//nvidia-current.ko.xz -rw-r--r--. 1 root root 599228 Apr 27 15:09 /var/lib/dkms/nvidia-current/535.216.03/6.12.22-a

Bug#1103676: screenshot attached

Here's the screenshot of display settings. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1103676: kwin-wayland: Running testing my workstation is getting two "virtual output" displays when I turn my monitor off

Package: kwin-wayland Version: 4:6.3.4-2 Severity: normal I am turning my workstation monitor off overnight. Now when I turn it on again it's not giving me an unlock screen so I ssh in from my laptop and use loginctl to unlock it. Then when I get it unlocked it has the 5K monitor with nothing bu

Bug#908676: is this still a bug?

I had this happen on Bookworm, but on upgrading the laptop in question to Testing it worked OK. Should we consider this as fixed upstream if there are no reports of it happening again? -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1102716: libruby3.3: failed to build with test errors

Package: libruby3.3 Version: 3.3.8-1 Severity: normal Tags: ftbfs X-Debbugs-Cc: debian-am...@lists.debian.org User: debian-am...@lists.debian.org Usertags: amd64 I got the following test errors when trying to rebuild this package on a system running Unstable: [26614/26682] TestZlibGzipFile#test_

Bug#1102698: python3.13: wish the build was more parallel

Package: python3.13 Version: 3.13.3-2 Severity: wishlist Below is the tail of building python on a system with 44 CPU cores and -j44, it uses on average 1.08 cores out of 44. If we could even average 4 cores that would take the build time from over 2 hours to half an hour. dpkg-genbuildinfo -O.

Bug#1095376: more info

Here are the results of running valgrind with a debugging build of every relevant package installed: ==241689== Invalid read of size 8 ==241689==at 0x53A92E: UnknownInlinedFun (objimpl.h:6) ==241689==by 0x53A92E: _PyObject_New (object.c:534) ==241689==by 0x70D3532: SWIG_Python_newvarl

Bug#1102615: hardening-runtime: kaslr is now enabled by default and gives a warning for the command line

Package: hardening-runtime Version: 2 Severity: normal [0.045001] Unknown kernel command line parameters "kaslr", will be passed to user space. I get the above on boot because kaslr is now the default. For Trixie please remove this setting from the hardening-runtime package as all Trixie ke

Bug#1102614: libqt6core6t64: uses wireless extensions which will stop working for Wi-Fi 7 hardware

Package: libqt6core6t64 Version: 6.8.2+dfsg-5+b1 Severity: normal [ 37.598292] warning: `kdeconnectd' uses wireless extensions which will stop working for Wi-Fi 7 hardware; use nl80211 I get the above message after logging in, this message only happens for the first process that triggers the c

Bug#1102484: isc-dhcp-keama: keama should remove duplicate reservations as kea will abort while the ISC server just worked

Package: isc-dhcp-keama Version: 4.4.3-P1-5+b1 Severity: normal failed to create or run parser for configuration element reservations: failed to add new host using the HW address '1c:6f:65:9f:ec:1e' to the IPv4 subnet id '0' as this host has already been added I had kea abort when I first ran i

Bug#1102483: isc-dhcp-keama: generates bad config file with 'got unexpected keyword "reservation-mode" in Dhcp4 map'

Package: isc-dhcp-keama Version: 4.4.3-P1-5+b1 Severity: normal Below is part of the diff between a working config file and that which is written by keama: --- /etc/kea/kea-dhcp4.conf 2025-04-09 23:41:24.792270901 +1000 +++ /root/kea-dhcp4.conf2025-04-09 23:39:14.501232144 +1000 @@ -

Bug#926208: could we split this package?

On Friday, 4 April 2025 09:15:32 AEDT Chris Hofstaedtler wrote: > ISC DHCP is EOL upstream. I would find packaging changes like that a > bit surprising at this time. Fair enough. I've filed a bug report requesting that the description of the package be changed to note that it is EOL upstream. I

Bug#1034140: more info on this

Currently I think it's expected that /sbin will be a symlink to /usr/sbin so this will work in all systems with a regular configuration. But having one reference to it with full path and another to it without a path is a bug in any case so the proposed fix is reasonable. A bigger problem is tha

Bug#1102021: isc-dhcp-server: please change description to mention the upstream deprecation and transition to kea

Package: isc-dhcp-server Version: 4.4.3-P1-5+b1 Severity: normal https://www.isc.org/kea/ The above URL states that the isc-dhcp-server was EOL in 2022. Trixie will be stable until at least 2027 which means that this package will be EOL for 5 years before Trixie is replaced. I think that the pa

Bug#926208: could we split this package?

There have been ongoing issues of IPv4 vs IPv6 for years, this bug is from 2019 and #792894 is from 2015. Could we just split the package? Then if someone doesn't want IPv6 functionality they just don't install that package. IPv4 has limited addresses and needs different management methods to

Bug#1101898: dracut-install: cp command run with preserve xattr causing problems on chroots under SE Linux

Package: dracut-install Version: 106-5 Severity: normal I used a system running SE Linux to upgrade a removable device in a chroot environment that is configured without SE Linux. This is one of many uses of containers etc on SE Linux that are not uncommon. When it built the initrd as part of co

Bug#1101163: rasdaemon: package should include /var/lib/rasdaemon

Package: rasdaemon Version: 0.8.1-3 Severity: normal Currently the package does not include the /var/lib/rasdaemon directory which means that the daemon has to create it and creating var_lib_t directories is not permitted by SE Linux. One solution to this is to have the postinst create the direct

Bug#1098793: already fixed

close 1098793 thanks This was already fixed and the fix is not in testing. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#984879: [DSE-Dev] Bug#984879: does this still happen?

close 984879 thanks > Thank you for the information. I've re-enabled labeling for my podman > containers and it seems to work now. Thanks a lot! Great! -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1099992: ktorrent: SEGV after running for a while

Package: ktorrent Version: 24.12.0-2 Severity: normal After years of running well a recent update (maybe a KDE library update) made ktorrent start crashing. Below is the backtrace from one of them. I noticed that bugs #602324 and #599914 are similar but I don't think a crash from 15 years ago is

Bug#984879: does this still happen?

The container module is now built along with crio and podman. Does it work now? -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1099175: fwupd: strange errors about connecting to 127.0.0.1 port 2321

Package: fwupd Version: 2.0.6-3 Severity: normal I have just upgraded a HP z640 system from Bookworm to Trixie and fwupd gives the following errors on startup: Mar 01 20:23:08 servername fwupd[4523]: WARNING:tcti:src/util-io/io.c:262:socket_connect() Failed to connect to host 127.0.0.1, port 2

Bug#1098793: fixed in refpolicy

severity 1098793 normal thanks This is fixed in refpolicy 2.20250213-1 by depending on the right versions of everything. I'll leave it open for the moment while things are still getting through to testing but I've lowered the priority. -- My Main Blog http://etbe.coker.com.au/ My Docu

Bug#1091109: fixed upstream

close 1091109 thanks The 3.8 upstream release incorporated a fix for this. Sorry for dropping the NMU changelog entry. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1096169: more info

Here's a full trace from Valgrind when waitpid() is called with a bad parameter. ==251974== Syscall param waitid(infop) points to unaddressable byte(s) ==251974==at 0x760C6F9: syscall (syscall.S:38) ==251974==by 0x70700F2: UnknownInlinedFun (forkfd_linux.c:67) ==251974==by 0x70700F2:

Bug#1096169: gwenview: crash on ALT-F4

On Monday, 17 February 2025 20:46:02 AEDT Sune Stolborg Vuorela wrote: > On Monday, February 17, 2025 5:25:19 AM CET Russell Coker wrote: > > Package: gwenview > > Version: 4:24.12.0-1 > > Severity: normal > > > > A frequent occurance for me on recent v

Bug#1096169: gwenview: crash on ALT-F4

Package: gwenview Version: 4:24.12.0-1 Severity: normal A frequent occurance for me on recent versions of Debian/Unstable is for gwenview to crash on exit. For most uses it was intermittant but I have found a case where it's 100% repeatable. I run "gwenview ." in a directory with 3 pics of my ca

Bug#1096091: Acknowledgement (geary: The trash button doesn't work on phone, but works on deskop running the same version)

Strangely it started working for no apparent reason. Seems to be an intermittent problem.

Bug#1096091: geary: The trash button doesn't work on phone, but works on deskop running the same version

Package: geary Version: 46.0-6 Severity: normal Running Geary on Mobian on my OnePlus6 the trash button when viewing a message is a slightly darker shade of gray (appears disabled) and when pressed does nothing. When run on my desktop PC it works correctly. -- System Information: Debian Release:

Bug#1095944: qcom-phone-utils: should conflict with the mobian package q6voiced

Package: qcom-phone-utils Version: 0.3.1 Severity: normal Unpacking qcom-phone-utils (0.4.0) over (0.3.1) ... dpkg: error processing archive /var/cache/apt/archives/qcom-phone-utils_0.4.0_arm64.deb (--unpack): trying to overwrite '/usr/bin/q6voiced', which is also in package q6voiced (0.0.0+git

Bug#1095864: geary: clicking on the desktopn icon for geary doesn't bring up minimised window

Package: geary Version: 46.0-6 Severity: normal On Plasma Mobile the Gwaey icon doesn't bring up a minimised/background instance. It brings up a new window which then goes away. I exoect it to act likw Nheko, Firefox, and most other desktop apps ans bring up the running copy. Thia is really ann

Bug#1095376: the cause of this

The command "python3 -bb -t -t -E -W error support/validate-appconfig.py -c / usr/bin/chkcon -l -s -v -x tmp/appconfig tmp/policy.bin" is crashing. Here's a backtrace: #0 0x005378ee in _PyObject_New () #1 0x7763919f in SWIG_Python_newvarlink () at ./src/ selinuxswig_python_wrap

Bug#1095540: lmdb-utils: please create file(1) entries for the LMDB files

Package: lmdb-utils Version: 0.9.31-1+b2 Severity: normal 16 lelong 0xbeefc0de lmdb little endian data file >20 lelong x version %d 0 lelong 0xbeefc0de lmdb little endian lock file >6 leshort x version %d >4 leshort >0 , pidlo

Bug#1093397: this is a lmdb issue

I installed the lmdb-utils package and ran: mv ~/.local/share/nheko/nheko/db-$NAME ~/.local/share/nheko/nheko/db-$NAME.old mkdir ~/.local/share/nheko/nheko/db-$NAME lmdb_copy -c $BACKUP/.local/share/nheko/nheko/db-$NAME \ ~/.local/share/nheko/nheko/db-$NAME Then I ran nheko and it worked. htt

Bug#1095467: ruby3.3: ruby has too many valgrind errors which makes debugging ruby libraries difficult

Package: ruby3.3 Version: 3.3.7-1 Severity: normal echo "" | valgrind ruby I ran the above command to get valgrind output on ruby doing nothing. It gave the following as prt of it's output. I expect to see significantly fewer than 100,000 errors on a run of a program with no actual work to do.

Bug#1095018: this would be the swig change

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%231091131 Below is the backtrace from the Ruby test case you provided. It shows that it fails in SWIG related code. The attached patch was recently applied in version 3.7-3.1 to build with SWIG 4.3 and close the above bug. The patch is needed

Bug#1095223: rmtfs: please make needrestart default to not restarting rmtfs

Package: rmtfs Version: 1.1-1 Severity: normal On the OnePlus6 restarting this daemon causes the system to enter crash dump mode. I don't know if this would be considered a bug by the people who wrote it. To avoid pain for users please make needrestart default to not restarting it with the follo

Bug#1095222: qrtr-tools: please make needrestart default to not restarting qrtr-ns

Package: qrtr-tools Version: 1.1-1+b1 Severity: normal On the OnePlus6 restarting this daemon causes the system to enter crash dump mode. I don't know if this would be considered a bug by the people who wrote it. To avoid pain for users please make needrestart default to not restarting it with t

Bug#1095134: udev: please add support for /dev/megaraid_sas_ioctl_node

Package: udev Version: 257.2-3 Severity: normal The following are 2 options I tried in /etc/udev/rules.d/99mega.rules: DEVPATH=="/module/megaraid_sas" RUN+="/usr/local/sbin/mega" DRIVER=="megaraid_sas" RUN+="/usr/local/sbin/mega" I don't know which of them is preferred but they both work. Below

Bug#1095117: did you use Red Hat documentation?

What do you have in /etc/selinux/config ? The system should be looking for /etc/selinux/default/contexts/dbus_contexts which is provided by selinux-policy-default unless you have the wrong data in /etc/selinux/config . -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp

Bug#555365: already fixed

close 555365 thanks Seems that it doesn't have ply code any more. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1045586: seems to be fixed

close 1045586 thanks Seems like this got fixed along the way, I can't reproduce it. Please reopen if you can reproduce it with 3.7. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#913987: not a bug

close 913987 thanks As Laurent explained this is already going to work automatically. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#943728: the start of this.

severity 943728 wishlist thanks https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899173 This is the original bug. Maybe we could change this to a Recommends, but it's not a high priority. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1094903: another system

I got the below on a Dell T630 with the following card with 6G of RAM running 6.12.10-amd64. 02:00.0 VGA compatible controller: NVIDIA Corporation GA106 [RTX A2000] (rev a1) [ 30.428313] [ cut here ] [ 30.428614] WARNING: CPU: 5 PID: 2426 at drivers/gpu/drm/drm_file

Bug#1094903: more info

The system is a HP z640 with the following video card which has 12G of RAM: 02:00.0 VGA compatible controller: NVIDIA Corporation GM200GL [Quadro M6000] (rev a1) (prog-if 00 [VGA controller]) When I run kernel 6.1.0-30-amd64 it gives no errors. -- My Main Blog http://etbe.coker.com.au/

Bug#1094330: gpm: please use systemd security settings

Package: gpm Version: 1.20.7-11+b2 Severity: normal Tags: security X-Debbugs-Cc: Debian Security Team The following systemd security settings seem to work well, please consider adding them to the default configuration. [Service] CapabilityBoundingSet=CAP_NET_BIND_SERVICE CAP_AUDIT_WRITE CAP_CHOW

Bug#1094328: cups: should use systemd security features

Package: cups Version: 2.4.2-3+deb12u8 Severity: normal I have tested the following settings and they significantly reduce the potential for damage to the system and allows all the normal operations in my tests. Please change the default configuration to include at least some of these. [Service

Bug#813728: still happening 9 years later

This bug still occurs. Could the following idea from 2016 be implemented? One attempt per second doesn't make sense. If we make it once every few minutes it will significantly reduce log noise. > I can just do a poor man's timer with a decrement counter, only > retrying failing DISPLAYs every

Bug#1094322: fail2ban: Please add support for systemd security settings

Package: fail2ban Version: 1.1.0-7 Severity: normal Tags: security X-Debbugs-Cc: Debian Security Team The following systemd security settings have been tested and allow fail2ban to work normally while significantly decreasing it's ability to change things on the sysstem. This program processes d

Bug#1094314: gpsd: should use systemd security features

Package: gpsd Version: 3.25-5 Severity: normal Tags: security X-Debbugs-Cc: Debian Security Team I tested the following systemd security settings and found them to allow normal operation on my system while providing less exposure to the system in the case of security issues. [Service] SystemCall

Bug#1094212: tp-smapi-dkms: postinst fails: Error! DKMS tree already contains: tp_smapi-0.44

Package: tp-smapi-dkms Version: 0.44-1.2 Severity: normal I get this error when installing or upgrading this package: Selecting previously unselected package tp-smapi-dkms. (Reading database ... 319227 files and directories currently installed.) Preparing to unpack .../tp-smapi-dkms_0.44-1.2_amd6

Bug#1093525: another thing

To make this work properly I needed to make a change to SE Linux policy, so when putting in that change please make it conflict with versions of selinux- policy-default < 2:2.20250115-1 -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1093525: postfix won't start on SE Linux systems after upgrade from <=3.9.1-4 to >=3.9.1-5

Package: postfix Version: 3.9.1-10+b1 Severity: normal The method of updating files in /var/spool/postfix/etc has changed from version 3.9.1-4 to 3.9.1-5 and the result is that /var/spool/postfix/etc from previous versions has the type etc_t and the new code runs the cp command as postfix_master_t

Bug#1093473: I misunderstood this

It seems that what is happening is tha interrupting pipewire causes mpv to change to Pulse for the output and then we have the issue that pipewire when running hangs all other forms of output. So just stopping pipewire solves the problem. -- My Main Blog http://etbe.coker.com.au/ My D

Bug#1093473: pipewire hangs all audio output until restarted

Package: pipewire Version: 1.2.7-1+b1 Severity: normal This happens on 2 of mny systems running Unstable. It works fine when playing audio, but when paused it will stop working and hang all attempts to play audio until restarted via "systemctl --user restart pipewire.service". This happens with m

Bug#1093142: more information

I've had the same problem again on that phone but not had it happen on my other OP6. So I think that there may be a hardware issue causing the kernel issue. But I still believe that there is a bug in pipewire. In spite of the kernel misbehaving the daemon should still be able to act in a reas

Bug#1093397: nheko: SEGV on startup mdb.c:2156: Assertion 'rc == 0' failed in mdb_page_dirty()

Package: nheko Version: 0.12.0+~0.10.0+~1.0.0+~0.3.1-4 Severity: normal On startup it hangs and then crashes, the below is the backtrace and the output. Storage: /var/lib/systemd/coredump/core.nheko.1000.863bb36b271346ac96a6fe4ac62501a5.3330.1737169497000> Size on Disk: 177.1M Me

Bug#1093142: more information

I currently can't reproduce the situation of taking more than 1 CPU core. I didn't do anything differently, just rebooted it a day later and got different results. Now I'm seeing the following, not a huge amount of CPU time, but more than expected from an idle system with the screen locked and

Bug#1093142: pipewire-bin: excessive CPU use and errors from pipewire

Package: pipewire-bin Version: 1.2.7-1+b1 Severity: normal On a OnePlus6 running Mobian I get pipewire using 4 CPU cores which results in the phone being hot to the touch and having it's battery drain fast. This only happened after updating to the latest Testing packages and rebooting. I have r

Bug#1093116: plasma-mobile-core: after recent update the square button to get the plasma window list broke

Package: plasma-mobile-core Version: 9 Severity: normal When I press the square icon at the bottom left of the screen to get the window list it doesn't do anything. My recollection is that this first happened a couple of weeks ago on my PinePhonePro running Debian/Unstable and it just happened on

Bug#1070039: how to fix this

This JIT desktop issue occurs with KDE as well as GNOME. Ideally we can address it in some automatic way. We don't want to allow execmem globally because you don't want that. Is there a way we could automatically change the boolean when a package like gdm or sddm is installed? -- My Main Bl

Bug#1049428: how to determine what's needed for this

# sesearch -A -s rpcd_t -c tcp_socket -p name_bind allow nsswitch_domain port_t:tcp_socket name_bind; [ allow_ypbind ]:True allow rpc_domain port_t:tcp_socket name_bind; allow rpc_domain reserved_port_t:tcp_socket name_bind; allow rpc_domain rpc_port_type:tcp_socket name_bind; # sesearch -A -s rpcd

Bug#1068601: is this really a bug?

The program dpkg is very important to Debian, but an unusual mount option (nosuid for /var) isn't so important. You have found a workaround for your issue. The possibilities for this moving forward are: 1) I could change the policy to allow this unconditionally for dpkg and the few other progr

Bug#1012756: fixed in 3.7-2

close 1012756 thanks fixed in 3.7-2 -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1092629: plasma-mobile-initial-start has an excessively long scroll list for locations for Time and Date

Package: plasma-mobile Version: 6.2.4-1 Severity: normal Tags: upstream Even scrolling to Australia takes ages, it must be really bad for people in Zimbabwe! This needs to have a search option or a 2 level menu structure to scroll countries/regions first. -- System Information: Debian Release: t

Bug#1092569: plasma-mobile: should conflict with plasma-settings < 24.02.0-1

Package: plasma-mobile Version: 6.2.4-1 Severity: normal I get the following error from "apt dist-upgrade", it needs to conflict with the old version of plasma-settings as there is a file conflict. Unpacking plasma-mobile (6.2.4-1) over (5.27.10-1+b1) ... dpkg: error processing archive /var/cach

Bug#1091701: debconf: bad error about unable to write templates.dat-new when there is no data to write

Package: debconf Version: 1.5.89 Severity: normal I am writing SE Linux policy for the needrestart utility which runs the debconf frontend program. When it runs I see the following error message: debconf: DbDriver "templatedb": could not write /var/cache/debconf/templates.dat-new: Permission den

Bug#1091464: systemd: tmpfiles produces unhelpful warnings

Package: systemd Version: 257.1-5 Severity: normal Setting up systemd (257.1-5) ... /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring. Setting up systemd-boot (257.1-5) ... I get the above message when upgrading, but it doesn't say what it is a duplicate of so I c

Bug#1089609: qt6-svg-plugins

Installing qt6-svg-plugins fixed it for me too. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1086032: calibre: SEGV when trying to "add books" on a PinePhonePro arm64 architecture

close 1086032 thanks I can no longer reproduce this bug in Debian/Unstable. I think that whatever needed to be recompiled has been recompiled. -- My Main Blog http://etbe.coker.com.au/ My Documents Bloghttp://doc.coker.com.au/

Bug#1073294: more information for comparing with KDE6

Running Debian/Unstable updated this morning I have the KDE screen locker doing 14ms sleeps on the PinePhonePro: ppoll([{fd=4, events=POLLIN}, {fd=18, events=POLLIN}, {fd=26, events=POLLIN}, {fd=27, events=POLLIN}, {fd=34, events=POLLIN}, {fd=35, events=POLLIN}, {fd=37, events=POLLIN}, {fd=38,

Bug#1073294: more information for comparing with KDE6

On Monday, 9 December 2024 08:03:08 AEDT Marco Mattiolo wrote: > latest upstream plasma-settings version (24.02.0) is now in trixie/sid: > can you please check whether this bug report is still valid on last version? > Thank you, kind regards Currently KDE is not yet in a suitably usable state to d

Bug#1089747: plasma-desktop: logout is missing in KDE 6

close 1089747 thanks OK that worked. I had never realised that you can change the size of the menu by dragging it. I will raise an upstream issue of why the "Leave" option was the one that was cut off due to lack of space. On Thursday, 12 December 2024 20:37:27 AEDT Martin Steigerwald wrote:

Bug#1089747: plasma-desktop: logout is missing in KDE 6

Package: plasma-desktop Version: 4:6.2.4-1 Severity: normal After upgrading to the latest packages in Unstable I now have no menu option to logout, only Sleep, Hibernate, Restart, and Shutdown. Is this a design decision by upstream, IE did it detect that it's running on a laptop and decide that l

Bug#1089609: nheko: SEGV on startup

Package: nheko Version: 0.12.0+~0.10.0+~1.0.0+~0.3.1-3 Severity: normal I just start it as normal and it crashes. The only change is updating to latest Unstable packages, so presumably something qt6 related is involved in this. Here is the output of coredumpctl info: Module libb

Bug#1089081: libkscreenlocker6: lockscreen has references to fingerprint and smartcard when no hardware exists

Package: libkscreenlocker6 Version: 6.2.4-1 Severity: normal The new lockscreen has text below the password prompt saying the following: (or scan your fingerprint on the reader) (or scan your smartcard) This occurs on systems without a fingerprint or smartcard reader attached and will confuse use

Bug#1086217: [DSE-Dev] Bug#1086217: setools: diff for NMU version 4.5.1-1.1

On Friday, 1 November 2024 10:02:56 AEDT Boyuan Yang wrote: > I've prepared an NMU for setools (versioned as 4.5.1-1.1) and > uploaded it to DELAYED/14. Please feel free to tell me if I > should delay it longer. That's fine, I would be happier with shorter delays. I'm not any sort of expert on P

Bug#1087348: akonadi-server: doesn't failover to IPv4 address when IPv6 address of IMAP server fails

Package: akonadi-server Version: 4:22.12.3-1+b4 Severity: normal It's not uncommon to have IPv6 networking issues when IPv4 works correctly. If a server has both IPv4 and IPv6 addresses for the DNS name of the IMAP server then Akonadi seems to ALWAYS try the IPv6 address first and then not receiv

Bug#1086482: fwupd: Blocked executable in the ESP error is uninformative even with -v

Package: fwupd Version: 1.9.26-2 Severity: normal When trying to upgrade the UEFI dbx I get the error: Blocked executable in the ESP, ensure grub and shim are up to date: No valid 'EspLocation' specified in /etc/fwupd/fwupd.conf Firstly even with the -v option it doesn't tell me which file alleg

Bug#1086032: calibre: SEGV when trying to "add books" on a PinePhonePro arm64 architecture

Package: calibre Version: 7.20.0+ds-1 Severity: normal Below is the output of "coredumpctl info". This happens every time I try to use "add books" on a PinePhonePro (my only Debian ARM system). It is running Unstable and an AMD64 laptop running Unstable runs Calibre without any problems. This c

Bug#1084883: abcde: please make flac encoding default to -8

Package: abcde Version: 2.9.3-1 Severity: minor CPU speed has been steadily increasing while CD/DVD drive speed hasn't. On a recently purchased DVD drive I can rip a CD in 11 minutes and flac -8 encoding takes about 12 seconds per track giving about 2 minutes of CPU time. At worst that's a 20% i

Bug#1084872: abcde: should not prompt about 2 identical matches

Package: abcde Version: 2.9.3-1 Severity: normal When I rip Plese from the "Please + Actually" set it gives 2 "matches" but they both have the same data. I've saved them to different files and run diff which reports no differences. I think the only reasonable thing for abcde to do in this situat

Bug#1084097: mokutil: should create and import key when package is installed

Package: mokutil Version: 0.6.0-2+b1 Severity: normal https://wiki.debian.org/SecureBoot The Debian wiki page about SecureBoot has the following instructions: # mkdir -p /var/lib/shim-signed/mok/ # cd /var/lib/shim-signed/mok/ # openssl req -nodes -new -x509 -newkey rsa:2048 -keyout MOK.priv -ou

Bug#1083231: ITP: fonts-roboto-mono -- Monospace font from Google developed for Android

Package: wnpp Severity: wishlist Owner: Russell Coker X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: fonts-roboto-mono Version : 20240508-1 Upstream Contact: Christian Robertson * URL : https://github.com/googlefonts/RobotoMono/tree/main * License

Bug#1083161: lollypop: Clicking on the icon doesn't bring a background window to the foreground

Package: lollypop Version: 1.4.40-1 Severity: normal When a graphical program can only have one copy running the expected behaviour is that clicking on the icon to launch it will bring the background copy to the foreground. When running lollypop on KDE on a desktop clicking the icon when it's run

Bug#1083156: juk: doesn't support playing webm, mka, or m4a files

Package: juk Version: 4:23.08.2-1+b1 Severity: normal These are all quite common audio file types and should be supported. -- System Information: Debian Release: trixie/sid Architecture: amd64 (x86_64) Kernel: Linux 6.10.11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=

Bug#1081704: memtest86+: should create an entry for systemd-boot if detected

On Sunday, 15 September 2024 00:53:20 AEST Felix Zielcke wrote: > I just added this to the git repository. > But I don't use systemd-boot, so could you please try and test it if it > works? > > https://salsa.debian.org/debian/memtest86plus/ I built this, installed it on 2 systems and verified tha

Bug#1081754: systemd: "kernel-install add-all" fails due to Debian not having vmlinuz where it expects

Package: systemd Version: 256.6-1 Severity: normal # kernel-install add-all Not adding version '6.10.9-amd64', because kernel image not found. Not adding version '6.9.10-amd64', because kernel image not found. No kernels to install found. The above is what happens in a typical Debian system, what

Bug#1081704: memtest86+: should create an entry for systemd-boot if detected

Package: memtest86+ Version: 7.00-1 Severity: normal If the file /boot/efi/EFI/systemd/systemd-bootx64.efi exists then the postinst should create a file like /boot/efi/loader/entries/memtest.conf with the following contents: title Memtest86+ efi /EFI/memtest86+/memtest86+x64.efi Then copy the ef

Bug#1081703: systemd-boot: should default to having a chain-loading option for GRUB if grubx64.efi is installed

Package: systemd-boot Version: 256.6-1 Severity: normal If systemd-boot is installed on a system that already has GRUB installed then it should install a loader/entries/grub.conf file with contents like the following to chain-load to GRUB: title GRUB efi /EFI/debian/grubx64.efi This means that i

Bug#1081702: systemd-boot: should create recovery entries by default

Package: systemd-boot Version: 256.6-1 Severity: normal The default configuration of GRUB has entries for "recovery mode" which boots with "single" on the kernel command-line. Most users will expect that systemd-boot will operate in an equivalent manner. A configuration option to operate in a mo

Bug#1069754: screenshot

On Friday, 13 September 2024 23:37:21 AEST Aurélien COUDERC wrote: > indeed, I’ve opened a bug upstream for this. > > Though very hidden, you can work around this manually. Thanks for the upstream but report and thanks for putting the work-around here for the next people who want to do it. --

Bug#1081577: gnome-session-bin: should not depend on upower

On Friday, 13 September 2024 09:58:08 AEST Jeremy Bícha wrote: > > The packahe upower doesn't seem to provide any benefit on desktop systems > > and should be a recommended package not a dependency. > > Why? So that daemons which aren't needed don't have to be installed. What is the benefit to a

Bug#1081577: gnome-session-bin: should not depend on upower

Package: gnome-session-bin Version: 46.0-7 Severity: normal The packahe upower doesn't seem to provide any benefit on desktop systems and should be a recommended package not a dependency. -- System Information: Debian Release: trixie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 K

Bug#1081574: kde-plasma-desktop: should not depend on upower

Package: kde-plasma-desktop Version: 5:148 Severity: normal The packahe upower doesn't seem to provide any benefit on desktop systems and should be a recommended package not a dependency. -- System Information: Debian Release: trixie/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 K

Bug#1081514: libcurl-gnutls.so.4: undefined symbol: gnutls_free

On Thursday, 12 September 2024 22:51:39 AEST Simon McVittie wrote: > Looks like a duplicate of which is a > regression in libcurl3t64-gnutls. libcurl4t64 (curl with OpenSSL) looks OK > according to packages.debian.org. Yes the same issue. Thanks for the quick res

  1   2   3   4   5   6   7   8   9   10   >