Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk
> I'm slightly worried by this comment though: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885140#77 I have now tried to temporarily upgrade to the wicd-curses, wicd-cli, wicd-daemon and python3-wicd versions present in Debian/experimental. Unfortunately I can only see a fraction of the Wi-Fi SSIDs compared to the version that used to be in Debian/testing. I'm happy to do more testing for that issue (help me find the bug, I can't find it), since that appears to block the resolution of this bug #885140. / Sebastian
Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk
> If nobody steps up to finish the porting, there is (not so nice) plan B: > disable > wicd-gtk and leave wicd-curses (more buggy than it should be, but > usable) and wicd-cli. Sadly it appears no one has stepped up to do the porting in the four years since 2017. As a user of wicd-curses, can I humbly suggest that Debian disables wicd-gtk for the time being so that Debian/testing mapped to bookworm can continue using wicd? I'm slightly worried by this comment though: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885140#77 If wicd-curses is kicked out of Debian entirely, what is the suggested alternative for scanning, connecting to and disconnecting from Wi-Fi in a terminal? / Sebastian
Bug#809997: emscripten not installable on Debian/testing...
Hi! I have been attempting to install emscripten today, and ended up the libstdc++6 breakage. Next I found this bug and I'm simply wondering what I can do to help you guys make progress on this bug? Unfortunately, I'm just a new user of emscripten so I barely know how to use it once it is installed, but if I can assist in any way please let me know. :) / Sebastian
Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...
>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that >> fixes your issue? > Of course, no problem, but it will have to wait a day or so. I can now confirm that upgrading to 1.3.6-5.1 does indeed fix the issue I was experiencing. From my perspective that means that you may mark this bug as resolved, but you might want to tie it to to the 1.3.6-5.1 release some how. Thanks for being responsive and helpful! :) / Sebastian
Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...
Of course, no problem, but it will have to wait a day or so. I didn't notice that there was a new version in /unstable or /experimental when I checked the other day so it is likely fairly recent. /Sebastian
Bug#862052: Latest slim upgrade caused involuntary crashes/logouts...
Package: slim Version: 1.3.6-5 Severity: serious When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my window manager appeared to suddenly "crash" and logged me out. However I had not changed anything related to that but I had recently upgraded slim so I investigated it a bit. I compiled 1.3.6-5 without the fix for 860465 as mentioned in the -5 debian patch (but keeping all other additions from -4+b2 to -5 the same). Without this "fix" my desktop no longer had problems. Could this be because I don't have plymouth installed (whatever that is)? I'm happy to do further testing if you can provide something for me to test. Besides this minor mishap I'm actually a happy slim user, thanks for putting in the effort. :) / Sebastian
