i been getting errors when trying to use zypper from the console. This happens in 2 pcs, and errors seem to be the same,
One has 11.4 + gnome 2, standar installation (with gnome) from 11.4 DVD. The error i get whenever i run something like zypper install xxxyyy.rpm or zypper update is:
GConf Error: Failed to contact configuration server; the most common cause is a missing or misconfigured D-Bus session bus daemon. See GConf configuration system for information. (Details - 1: Failed to get connection to session: The connection is closed)
I dont know if its related, but the one with gnome 3 constantly gives me (what i think is) a kernel panic when i shut down the system, it happens fast and the text on the screen is not “linear” but spread all over the screen, so i cant read the whole message, but it does say something about glib and corruption.
This is actually the first time(s) ibe seen a kernel panic ever since i used ubuntu.
Any idea of what might be wrong? or how i can fix it?
yep, i was just using su instead of su -
ran su - and problem dissapeared.
Apparently im not the only one that ignores i have to use su - hehe i found this
[Bug 672793] New: GLib-GIO:ERROR:gdbusconnection.c:2279:initable_init: a](http://lists.opensuse.org/opensuse-bugs/2011-02/msg03139.html)
on a sligthly diferent topic, im still getting the kernel panic when i log out of the gnome 3 netbook, but it happens so fast i cant read the message, i want to open a thread to see if anyone else has this problem, but i want to paste the full error message, is there a log where this message would be saved, so i can go open it and paste the error in a new thread?
it just did it again, but i looked at boot.omsg and found no errors.
Somehow i think the error occurs before boot.omsg is created, because i noted the error included the system time, and it was 00:31:37, and the earliest time i find in boot.omsg is 00:31:39
I did manage to see something like “clib detected. xorg double free or corruption”, then theres a bunch of numbers that seem like memory addresses all over the screen, not “lined up” one below the other, but rather spread all over the screen.
and then more messages, but dint get to read those.
On 2011-07-01 08:06, ErnestoRD wrote:
>
> it just did it again, but i looked at boot.omsg and found no errors.
That log is for booting messages, and your problem is when halting. There
will be nothing there.
There might be something in /var/log/messages. But if the system crashes,
nothing will be written - so you have to make a photo or a video with a camera.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Youre probably right. The system is working perfectly, so there is really nothing “broken” that needs fixing.
I think im bothered not by the error itself, but by not knowing what it is or why it happens. I HATE not knowing things! hehe
Thanks Carlos, but isnt boot.msg the log for booting, and boot.omsg the one for shutdown?
In boot.omsg i do see the “Broadcast message from… System is goin for a restart now” messages.
I will take a quick look at the other logs to see if i find anything.
> Thanks Carlos, but isnt boot.msg the log for booting, and boot.omsg the
> one for shutdown?
Nope
boot.msg is the current log, boot.omsg is the Old one, previous boot. Thus,
if the system was halted, on next boot you look at boot.omsg to see what
happened before.
> In boot.omsg i do see the “Broadcast message from… System is goin
> for a restart now” messages.
That is weird.
The last paragraph I see on mine is this:
Master Resource Control: Running /etc/init.d/after.local
/etc/init.d/after.local: line 10: /dev/audio: Device or resource busy
doneMaster Resource Control: runlevel 5 has been reached
Skipped services in runlevel 5: nfs
<notice – Jun 22 02:46:50.982603000>
killproc: kill(6628,3)
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
