Bug#1059787: src:xfce4-power-manager: fails to migrate to testing for too long: uploader built arch:all binaries
Source: xfce4-power-manager Version: 4.18.2-1 Severity: serious Control: close -1 4.18.3-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:xfce4-power-manager has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable has arch:all binaries built by the uploader. Unfortunately the binNMU infrastructure doesn't support binNMU'ing arch:all (and DAK still doesn't throw away uploaded binaries). Hence, a source-only upload is required. Normally I do that (a no-change source-only NMU) for packages in this state, but given the large amount of open bugs, I don't feel comfortable taking that responsibility. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and trixie, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=xfce4-power-manager OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1039957: light-locker: Bug 1039957: light-locker: coredump from light-locker
Hi, On 24-07-2023 15:27, Yves-Alexis Perez wrote: so what you're saying is that you're a KDE user (not Xfce) Indeed. but you're still using LightDM (not KDM), and light-locker is still started as part of your desktop session. I'm not aware that I ever did that actively. It seems that also nothing obvious changed for me since I deinstalled light-locker. So everything *looks* like before. In any case, if you don't use it on your box it's quite ok to remove it. I tried to say in my previous message that I already did that. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1039957: light-locker: Bug 1039957: light-locker: coredump from light-locker
Package: light-locker Version: 1.8.0-3 Followup-For: Bug #1039957 Hi, I just found this coredump in my journal. Like the original reporter, I'm a user of KDE (on trixie). I removed light-locker to see if I spotted any change and I'm not seeing it yet. Paul Here's the dump: jul 23 20:11:29 mulciber systemd-coredump[2250]: Process 2157 (light-locker) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-253.5-1.amd64 Stack trace of thread 2157: #0 0x7f43ad4f6557 g_log_structured_array (libglib-2.0.so.0 + 0x61557) #1 0x7f43ad4f69ae g_log_default_handler (libglib-2.0.so.0 + 0x619ae) #2 0x7f43ad4f6c20 g_logv (libglib-2.0.so.0 + 0x61c20) #3 0x7f43ad4f6ecf g_log (libglib-2.0.so.0 + 0x61ecf) #4 0x5570baa14085 n/a (light-locker + 0xb085) #5 0x7f43ad61015b g_type_create_instance (libgobject-2.0.so.0 + 0x3815b) #6 0x7f43ad5f3e60 n/a (libgobject-2.0.so.0 + 0x1be60) #7 0x7f43ad5f5496 g_object_new_with_properties (libgobject-2.0.so.0 + 0x1d496) #8 0x7f43ad5f6311 g_object_new (libgobject-2.0.so.0 + 0x1e311) #9 0x5570baa168e2 gs_listener_new (light-locker + 0xd8e2) #10 0x5570baa124c2 n/a (light-locker + 0x94c2) #11 0x7f43ad61015b g_type_create_instance (libgobject-2.0.so.0 + 0x3815b) #12 0x7f43ad5f3e60 n/a (libgobject-2.0.so.0 + 0x1be60) #13 0x7f43ad5f5496 g_object_new_with_properties (libgobject-2.0.so.0 + 0x1d496) #14 0x7f43ad5f6311 g_object_new (libgobject-2.0.so.0 + 0x1e311) #15 0x5570baa12b02 gs_monitor_new (light-locker + 0x9b02) #16 0x5570baa113fa main (light-locker + 0x83fa) #17 0x7f43ad2056ca __libc_start_call_main (libc.so.6 + 0x276ca) #18 0x7f43ad205785 __libc_start_main_impl (libc.so.6 + 0x27785) #19 0x5570baa1154a _start (light-locker + 0x854a) Stack trace of thread 2196: #0 0x7f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156) #1 0x7f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818) #2 0x7f439a50c059 n/a (iris_dri.so + 0x10c059) #3 0x7f439a4be17b n/a (iris_dri.so + 0xbe17b) #4 0x7f439a50bf97 n/a (iris_dri.so + 0x10bf97) #5 0x7f43ad2663ec start_thread (libc.so.6 + 0x883ec) #6 0x7f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c) Stack trace of thread 2199: #0 0x7f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156) #1 0x7f43ad265818 __pthread_cond_wait_common (libc.so.6 + 0x87818) #2 0x7f439a50c059 n/a (iris_dri.so + 0x10c059) #3 0x7f439a4be17b n/a (iris_dri.so + 0xbe17b) #4 0x7f439a50bf97 n/a (iris_dri.so + 0x10bf97) #5 0x7f43ad2663ec start_thread (libc.so.6 + 0x883ec) #6 0x7f43ad2e6a1c __clone3 (libc.so.6 + 0x108a1c) Stack trace of thread 2200: #0 0x7f43ad263156 __futex_abstimed_wait_common64 (libc.so.6 + 0x85156)
Re: Bug#1004680: upgrade-reports: beep when selecting logout
Control: reassign -1 src:xfce4 Control: found -1 4.16 Control: retitle -1 xfce logout beeps after upgrade to bullseye Hi Roger, I am reassiging the bug to xfce4. The maintainers can take a look and see if it need further reassigning. Paul On 01-02-2022 19:17, slow_sp...@att.net wrote: Sure, do whatever you think is best. On 2/1/22 13:06, Paul Gevers wrote: Hi Roger, Please reply to the bug. I'm now wondering if I can forward this information there (it's valuable, as it help reassign to a package where they can further investigate). Paul On 01-02-2022 00:30, slow_sp...@att.net wrote: Xfce 4.16. I go to what should be the Whisker menu, but it just says Applications now. I select the lowest item on the list, which is Log Out. As soon as it is selected, it beeps. The sound comes from the computer's internal speaker. AlsaMixer has not such settings to address that. But still, the odd thing is that it started after upgrade from Buster and Xfce 4.12. On 1/31/22 14:34, Paul Gevers wrote: Hi Roger, How do you logout? Are you in a terminal or are you running some desktop environment? Which one? Paul OpenPGP_signature Description: OpenPGP digital signature
