Confirming issue exists on Kubuntu 20.04.4 LTS.
Every attempt to login from the graphical login screen makes this error
appear in authlog:
/var/log/auth.log:Apr 27 13:56:16 kcheckpass[3516]:
pam_ecryptfs: seteuid error
Quick "fix" of the symptom, i.e. make the error go away is to add the
Just two little suggestions to make the software more friendly:
$ strings /usr/bin/dbus-daemon | grep 'Unknown username "%s" in'
Unknown username "%s" in message bus configuration file
It would be nice if the printer of this error message (dbus-daemon)
would change the error message so:
Confirming that this upgrade fixes the problem for me.
clang++ now links successfully vs. system boost libs.
Thanks to all involved!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.8 in Ubuntu.
*** This bug is a duplicate of bug 1605291 ***
https://bugs.launchpad.net/bugs/1605291
** This bug has been marked a duplicate of bug 1605291
please merge llvm-toolchain-3.8 from Debian
--
You received this bug notification because you are a member of Desktop
Packages, which is
clang in 15.04 and 16.04 LTS is pretty unusable without this patch.
Linking against precompiled (with the gcc toolchain) system libraries
fails.
There are also multiple affected users in this closely related bug:
https://bugs.launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/+bug/1488254
--
Oops, sorry for the 'geany' package setting. Fixing this to clang-3.8
** Package changed: geany (Ubuntu) => llvm-toolchain-3.8 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to llvm-toolchain-3.8 in Ubuntu.
I started getting these about a week ago (Jul 2015)
They now happen several times a day in bursts (at the same second, same
error, but multiple process or thread ids)
I'm on 14.04.2 LTS
Here are some examples from syslog:
Jul 29 10:41:48 xxx kernel: [2065316.058955] traps:
Sorry I have to correct my comment #10 above.
I found the direct reason for my session hangs and they are unrelated to
this Glib-CRITICAL messages. Just conincidental.
The Glib-CRITICAL errors are annoying and indicate some incorrect calls
from various apps to Glib, but not a serious issue as
Quote from an upstream (bugzilla.gnome.org) comment:
https://bugzilla.gnome.org/show_bug.cgi?id=721369
GLib recently started throwing a warning when g_source_remove()
is passed garbage (as per warning). Your applications have probably been
broken
for a while, and there's no telling
Also affecting console-kit-daemon:
Apr 21 18:15:22 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 462 was
not found when attempting to remove it
Apr 21 18:15:22 xx console-kit-daemon[3357]: GLib-CRITICAL: Source ID 48 was
not found when attempting to remove it
Apr 21 18:15:22 xx
10 matches
Mail list logo
