Arch Linux

Lykve

Member

Registered: 2013-03-17

Posts: 3

Error messages

There are several error messages in the log files that are puzzling me. When i see an error message i expect something to be broken or not working correctly and i want to report that upstream. I'm looking for some feedback in order to make sure the problem isn't me and any info on these observations.

Running the following as root:

journalctl -b -p err

...gives this output

mars 17 17:28:38 cudabox kernel: sd 7:0:0:0: [sdb] No Caching mode page present
mars 17 17:28:38 cudabox kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
mars 17 17:28:38 cudabox kernel: sd 7:0:0:0: [sdb] No Caching mode page present
mars 17 17:28:38 cudabox kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
mars 17 17:28:39 cudabox gdm-launch-environment][348]: GLib-CRITICAL: g_variant_compare: assertion `!g_variant_is_container (a)' failed
mars 17 17:28:39 cudabox gdm-launch-environment][348]: GLib-CRITICAL: g_variant_compare: assertion `!g_variant_is_container (a)' failed
mars 17 17:28:39 cudabox ntpd_intres[339]: host name not found: 0.pool.ntp.org
mars 17 17:28:39 cudabox ntpd_intres[339]: host name not found: 1.pool.ntp.org
mars 17 17:28:39 cudabox ntpd_intres[339]: host name not found: 2.pool.ntp.org
mars 17 17:28:40 cudabox kernel: sd 7:0:0:0: [sdb] No Caching mode page present
mars 17 17:28:40 cudabox kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through
mars 17 17:28:40 cudabox pulseaudio[445]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
mars 17 17:28:48 cudabox gnome-session[354]: CRITICAL: gsm_manager_set_phase: assertion `GSM_IS_MANAGER (manager)' failed
mars 17 17:28:49 cudabox pulseaudio[551]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.GetProperties() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
mars 17 17:28:49 cudabox pulseaudio[586]: [pulseaudio] pid.c: Daemon already running.

Error 1: No caching mode page
This doesn't look like an error to me this should be a warning? From what i have understood usb drives don't have to have this.

Error 2: gdm-launch-environment
Seems to be a sanity check in gdm that's failing but i'm rather clueless about this one.

Error 3: ntpd
ntpd is trying to sync before the network has been brought up. The networkmanager-dispatcher-ntpd package is recommended against in the ntp page on the wiki. If that is still the case then this is probably a ntpd setting i've not set correctly, or a missing feature in ntpd.

Error 4: pulseaudio bluez
This looks like a non-critical pulseaudio bug. It should probably check if a bluetooth manager is available before trying to get a list of bluetooth devices.

Error 5: gnome-session
Looks like another sanity check, not sure what's going on here.

Error 6: pulse is allready running
Seems like gnome isn't checking whether pulseaudio is running or not before starting it. It should probably call "pulseaudio --check" before starting it.

Kinda longwinded so i'll repeat what i'm looking for. Sanity check that these are actual upstream bugs and info on where to report them.

WonderWoofy

Member

From: Los Gatos, CA

Registered: 2012-05-19

Posts: 8,414

Re: Error messages

All the non gdm/gnome ones are totally normal.  The gdm/gnomes one I simply have no idea, because I don't use either.  You're doing pretty well though, as I have a couple errors in my logs that I just totally can't figure out.

hoschi

Member

From: Ulm (Germany)

Registered: 2008-11-03

Posts: 458

Re: Error messages

I can solve number four pulseaudio and bluetooth

Pulseaudio simply tries to use bluetooth, even when there is not bluetooth-hardware. This is itself not an error-message, just an information. I my point of view this message should be more concise and tell the user, that this is not an error or a problem. The maintainer has told me, that I should ignore this message.

Take a look at comments and history:
https://bugs.archlinux.org/task/33646
https://bugs.archlinux.org/task/32427

Solution: Ignore message or install bluetooth.
https://wiki.archlinux.org/index.php/Bluetooth

Notes:
On my laptop this message wasn't never printed, because it has some bluetooth hardware and therefore bluetooth.service is available. On my desktop I've choosen solution two and installed bluez, I prefer clean logs.

Last edited by hoschi (2013-03-25 13:06:26)

hoschi

Member

From: Ulm (Germany)

Registered: 2008-11-03

Posts: 458

Re: Error messages

Error 2: gdm-launch-environment // here to
Error 5: gnome-session // here to
Error 6: pulse is allready running // here to

Upstream (here GNOME and Pulseaudio) shoud take a look a the issues behind them, especially because the look like false positives. If they are false positives they are not just scary, but also misleading during investigation of other issues.

Last edited by hoschi (2013-03-25 13:26:17)