Language Selection

English French German Italian Portuguese Spanish

Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd

Filed under
Linux
Red Hat

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."

Read more ►

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 Smile

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 Smile

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 Smile
So it has its pros and cons Smile
But I have been using it since 2006 on old computer on since 2009 on this one Smile

Arch

Arch has impressed me in recent years, but I stick to Debian.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

How Linux became my job

I've been using open source since what seems like prehistoric times. Back then, there was nothing called social media. There was no Firefox, no Google Chrome (not even a Google), no Amazon, barely an internet. In fact, the hot topic of the day was the new Linux 2.0 kernel. The big technical challenges in those days? Well, the ELF format was replacing the old a.out format in binary Linux distributions, and the upgrade could be tricky on some installs of Linux. Read more

Linux 4.16-rc2

It's been a quiet week, and rc2 is out. I take the fairly quiet rc be a good sign for 4.16, but honestly, rc2 is often fairly calm. That's probably because people are taking a breather after the merge window, but also simply because it might take a while to find any issues. But let's be optimistic, and just assume - at least for now - that it's because all is well. The diffstat is fairly odd, but that often happens with small rc's just because then just a couple of pulls will skew things easily in one or two directions. This time the patch is about one third architecture updates (arm64, x86, powerpc), one third tooling (mostly 'perf') and one third "rest". And yes, the bulk of that rest is drivers (gpu, nvme, sound, misc), but those drivers are still distinctly *not* the bulk of the whole patch. Go out and test, it all looks fine. Read more Also: Linux 4.16-rc2 Kernel Released

OpenStreetMap in IkiWiki and Why OpenStreetMap is in Serious Trouble

  • OSM in IkiWiki
    Since about 15 years ago, I have been thinking of creating a geo-referenced wiki of pubs, with loads of structured data to help searching. I don't know if that would be useful for anybody else, but I know I would use it! Sadly, the many times I started coding something towards that goal, I ended blocked by something, and I keep postponing my dream project.
  • Why OpenStreetMap is in Serious Trouble
    That said, while I still believe in the goals of OpenStreetMap, I feel the OpenStreetMap project is currently unable to fulfill that mission due to poor technical decisions, poor political decisions, and a general malaise in the project. I'm going to outline in this article what I think OpenStreetMap has gotten wrong. It's entirely possible that OSM will reform and address the impediments to its success- and I hope it does. We need a Free as in Freedom geographic dataset.

Linux KPI-Based DRM Modules Now Working On FreeBSD 11

Thanks to work done by Hans Petter Selasky and others, this drm-next-kmod port is working on FreeBSD 11 stable. What's different with this package from the ports collection versus the ported-from-Linux Direct Rendering Modules found within the FreeBSD 11 kernel is that these DRM modules are using the linuxkpi interface. Read more