Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
When systemd sees "debug" as part of the kernel command-line, it will spit out so much informaiton about the system that it fails to boot... The init system just collapses the system with too much information being sent to the dmesg when seeing the debug option as part of the kernel command-line parameter. Within the systemd bug report it was suggested for systemd not to look for a simple "debug" string to go into its debug mode but perhaps something like "systemd.debug" or other namespaced alternatives. The debug kernel command-line parameter has been used by upstream Linux kernel developers for many years. However, upstream systemd developers don't agree about changing their debug code detection. Kay Sievers of Red Hat wrote, "Generic terms are generic, not the first user owns them."
- Login or register to post comments
- Printer-friendly version
- 3824 reads
- PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
digiKam 7.7.0 is releasedAfter three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. |
Dilution and Misuse of the "Linux" Brand
|
Samsung, Red Hat to Work on Linux Drivers for Future TechThe metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. |
today's howtos
|
systemd bug locks xorg after resume
I used to think it was a bug in the catalyst driver, which was rock solid until opensuse switched to systemd- since then I consistently experienced locking after a suspend/resume. It is random and you can resume a dozen times before it finally locks up.
I thought it may be a bug in catalyst driver so I switched to the open source radeon driver, with the same behaviour- random lock-ups after resume.
Interestingly, even hibernate behaves like that - it can work a few times and then suddenly, one hibernate will boot to a blank screen.
Wonder WHEN they will fix the bug, if ever.
systemd
Generally systemd needs a stabilization period. It took ages for 209 to be released because they added so many features followed by quick 210,211,212 bugfix releases.
If you look at the git tree, the TODO is growing very quickly.
I understand systemd is still in very early development and they are far from the "vision" they are going after.
They more or less admitted this by creating a systemd-stable branch.
http://cgit.freedesktop.org/systemd/systemd-stable/
Pulseaudio
The same developer put a half-baked Pulseaudio in some distros (or backly-packaged Pulseaudio in Ubuntu, Mandriva etc.) and it caused many users -- myself included -- to get frustrated/angry/less productive around 2008-2010.
Pulseaudio
That's why I recompile kde/mplayer/ffmpeg, etc.. without pulseaudio support
Pulseaudio
Pulseaudio has worked well for a number of years now.
Pulseaudio
I scrubbed pulseaudio off my system after getting sound errors in video screen recording. Errors stopped immediately--this was a couple of weeks ago.
Luckily it is optional in
Luckily it is optional in most places outside Gnome.
KDE
When I used Mandriva 2008.1 (Spring), which came with KDE, it was not really optional. The same goes for Kubuntu. I actually have many problems with KMix these days. I regularly need to kill/close it and start it again, but the problem may be caused by laptop volume controls (kmix bug).
KDE
optional at build time
Gentoo or Arch
So I guess you use something like Gentoo or Arch.
Arch
Yes, Arch. There are some things I like such as the flexibility.
Others thinks such as "optional dependencies" I'm not so fond of
So it has its pros and cons
But I have been using it since 2006 on old computer on since 2009 on this one
Arch
Arch has impressed me in recent years, but I stick to Debian.