Sometimes I want to be a debian developer, just to fix annoying issues.
A couple of weeks ago I found out that while the live-debian does not have a password for the user, it still locks the screen after a while. Then it's impossible to unlock it. Yeah, I can get around that, but it's still somewhat annoying the first time it happens.
I'm not sure why it's that way.
1/2
Then today I started one upgrade from bookworm to trixie. The upgrade was going on smoothly, so I left it and came back a bit later to see that the screen lock was not working. There were some instructions on the screen for fixing this, which is great.
However, it said to use the command 'logictl' to fix the issue. It took me some time to figure out that the proper program is 'loginctl'.
A small issue but quite annoying when you can't access the GUI.
Would be nice to fix those.
2/2
@pare Let me know if you want a quick introduction to Debian packaging some day.
@liw I think you gave me one already years ago. It's more about getting those changes to debian proper. :D
@pare I've retired from Debian myself in 2018, but I'm sure https://www.debian.org/devel/join/ is useful for people wanting to join.
@wouter @liw Though I'll point out that 'reportbug' first asks for a package name or 'other', and points to a mailing list if those are not good options.
It does not seem a very helpful bug reporting system. Of course it limits the number of reported bugs, by making more hoops and knowledge needed.
I see why that is - debian seems kind of a not very well paying project and there probably is nobody going through bugs as their main job - but it still annoys me.
- replies
- 0
- announces
- 0
- likes
- 1
There is a 'general' pseudo package which, if used, ends up on the debian-devel mailing list where it is then triaged.
However, it tends to attract the type of bug report that goes "it doesn't work" which is not actionable and better served through other support channels. This is why reportbug encourages you to try those first instead of the general package.
In this case though, it is warranted to use general. You know the bug, just not the package.
@liw
@pare for live images, detailed instructions for reporting bugs are available here: https://live-team.pages.debian.net/live-manual/html/live-manual/bugs.en.html
debian-live or live-config seem to be good targets for this issue. Don't worry too much about finding the right package, the maintainers will reassign if necessary.
Looking at the list of bugs it seems that it has already been reported several times (oldest being #995364).
And no need to be an accredited Debian Developer to help, patches added to bug reports are welcome and useful.