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

today's howtos

KDE/Qt: Qt Contributor Summit 2018, Integrating Cloud Solutions with Qt, FreeBSD, and Konsole

  • Qt Contributor Summit 2018
    One bit especially interesting is the graphics stack. Back in Qt 5.0, Qt took the liberty of limiting the graphics stack to OpenGL, but the world has changed since: On Windows the only proper stack is Direct3D 12, Apple introduced Metal and recently deprecated OpenGL and Vulkan is coming rather strong. It looks like embracing these systems transparently will be one of the most exciting tasks to achieve. From a KDE & Plasma perspective I don’t think this is scary, OpenGL is here to stay on Linux. We will get a Framework based on a more flexible base and we can continue pushing Plasma, Wayland, Plasma Mobile with confidence that the world won’t be crumbling. And with a bit of luck, if we want some parts to use Vulkan, we’ll have it properly abstracted already.
  • Integrating Cloud Solutions with Qt
    These days, using the cloud for predictive maintenance, analytics or feature updates is a de facto standard in the automation space. Basically, any newly designed product has some server communication at its core. However, the majority of solutions in the field were designed and productized when communication technology was not at today’s level. Still, attempts are being made to attach connectivity to such solutions. The mission statement is to “cloudify” an existing solution, which uses some internal protocol or infrastructure.
  • KDE on FreeBSD – June 2018
    It’s been a while since I wrote about KDE on FreeBSD, what with Calamares and third-party software happening as well. We’re better at keeping the IRC topic up-to-date than a lot of other sources of information (e.g. the FreeBSD quarterly reports, or the f.k.o website, which I’ll just dash off and update after writing this).
  • Konsole’s search tool
    Following my konsole’s experiments from the past week I came here to show something that I’m working on with the VDG, This is the current Konsole’s Search Bar. [...] I started to fix all of those bugs and discovered that most of them happened because we had *one* search bar that was shared between every terminal view, and whenever a terminal was activated we would reposition, reparent, repaint, disconnect, reconnect the search bar. Easiest solution: Each Terminal has it’s own search bar. Setuped only once. The one bug I did not fix was the Opening / Closing one as the searchbar is inside of a layout and layouts would reposition things anyway. All of the above bugs got squashed by just moving it to TerminalDisplay, and the code got also much cleaner as there’s no need to manual intervention in many cases. On the review Kurt – the Konsole maintainer – asked me if I could try to make the Search prettier and as an overlay on top of the Terminal so it would not reposition things when being displayed.

LibreOffice 6.0 Is Now Ready for Mainstream Users and Enterprise Deployments

LibreOffice 6.0.5 is here one and a half months after the LibreOffice 6.0.4 point release to mark the open-source office suite as ready for mainstream users and enterprise deployments. The Document Foundation considers that LibreOffice 6.0 has been tested thoroughly and that it's now ready for use in production, enterprise environments. Until now, The Document Foundation only recommended the LibreOffice 6.0 office suite to bleeding-edge users while urging enterprises and mainstream users to use the well-tested LibreOffice LibreOffice 5.4 series, which reached end of life on June 11, 2018, with the last point release, LibreOffice 5.4.7. Read more

LibreOffice 6.0 Is Now Ready for Mainstream Users and Enterprise Deployments

The Document Foundation informed Softpedia today about the general availability of the fifth point release of the LibreOffice 6.0 open-source and cross-platform office suite for all supported operating systems. LibreOffice 6.0.5 is here one and a half months after the LibreOffice 6.0.4 point release to mark the open-source office suite as ready for mainstream users and enterprise deployments. The Document Foundation considers that LibreOffice 6.0 has been tested thoroughly and that it's now ready for use in production, enterprise environments. Read more Direct: The Document Foundation announces LibreOffice 6.0.5