dbus daemon: segmentation fault
Martin Byttebier
Since a day or two my sons laptop running Suse 10.1/KDE has a
serious problem with the dbus-daemon. When he fires up the laptop he gets
this warning: The Dbus daemon is not running ...
A look at the boot.msg reveals me this:
Starting D-BUS daemonstartproc: signal catched /usr/bin/dbus-daemon:
Segmentation fault. Failed
Due this lots of others things, like Networkmanager, powersave , ...
doesn't work either.
I suppose the impossiblity to auto mount USB pendrives is also caused by
this.
Any idea how to fix this?
Thanks,
Martin
Mark Brand
I see this problem too on a laptop with Suse 10.1 and KDE 3.5.6. The
problem started after a recent round of updates. I haven't had a chance
to dive into this, but at least I can confirm the problem.
Mark
Martin Byttebier
> Martin Byttebier wrote:
>> Hello,
>>
>> Since a day or two my sons laptop running Suse 10.1/KDE has a
>> serious problem with the dbus-daemon. When he fires up the laptop he gets
>> this warning: The Dbus daemon is not running ...
>>
>> A look at the boot.msg reveals me this:
>> Starting D-BUS daemonstartproc: signal catched /usr/bin/dbus-daemon:
>> Segmentation fault. Failed
>>
>> Due this lots of others things, like Networkmanager, powersave , ...
>> doesn't work either.
> I see this problem too on a laptop with Suse 10.1 and KDE 3.5.6. The
> problem started after a recent round of updates. I haven't had a chance
> to dive into this, but at least I can confirm the problem.
I'm glad to see others has this problem too. I was suspecting my son he
had done something wrong.
I did make some updates the last few days.
TTFN,
Martin
John A. Bailo
> I'm glad to see others has this problem too. I was suspecting my son he
> had done something wrong.
> I did make some updates the last few days.
I get this problem too (see my other thread)...and same message about
'segmentation fault'
Also, all my USB devices stopped being recognized by Suse 10.1
They must have updated something that screwed up the USB support service.
firef...@gmail.com
I've got exactly the same bug!
It appeared right after I updated with yum yesterday.
My system is SuSE 10.1, right now I am trying to roll-back to some
previous version of dbus-1
On Jan 27, 5:21 am, Martin Byttebier
firef...@gmail.com
I solved the problem!
The cause for this segmentation fault is not dbus, but config file: /
etc/dbus-1/system.d/avahi-dbus.conf
If you move that file out of that folder, dbus will start work again!
Just do
# mv /etc/dbus-1/system.d/avahi-dbus.conf /tmp/avahi-dbus.conf
# /etc/init.d/dbus start
Enjoy! :-)
On Jan 28, 10:14 am, firefox...@gmail.com wrote:
> Hi,
>
> I've got exactly the same bug!
> It appeared right after I updated with yum yesterday.
>
> My system is SuSE 10.1, right now I am trying to roll-back to some
> previous version ofdbus-1
>
> On Jan 27, 5:21 am, Martin Byttebier
>
> <donotusethisaddr...@pandora.be.invalid> wrote:
> > Hello,
>
> > Since a day or two my sons laptop running Suse 10.1/KDE has a
> > serious problem with thedbus-daemon. When he fires up the laptop he gets
> > this warning: TheDbusdaemon is not running ...
>
> > A look at the boot.msg reveals me this:
> > Starting D-BUS daemonstartproc: signal catched /usr/bin/dbus-daemon:
> >Segmentationfault. Failed
dbg...@gmail.com
John A. Bailo
> I'm glad to see others has this problem too. I was suspecting my son he
> had done something wrong.
You can let him out of the cage in the basement now.
John A. Bailo
> Hi everyone,
>
> I solved the problem!
> The cause for this segmentation fault is not dbus, but config file: /
> etc/dbus-1/system.d/avahi-dbus.conf
> If you move that file out of that folder, dbus will start work again!
> Just do
> # mv /etc/dbus-1/system.d/avahi-dbus.conf /tmp/avahi-dbus.conf
> # /etc/init.d/dbus start
Fantastic! That also solved my problem with USB recognition! Now my
camera et all are working!
Questions:
How did you figure this out?
Did avahi-bus.conf just get installed? Or did the latest update
misconfigure it....what does it /do/ ?
Martin Byttebier
>
> On Jan 28, 10:31 am, firefox...@gmail.com wrote:
>> Hi everyone,
>>
>> I solved the problem!
>> The cause for this segmentation fault is not dbus, but config file: /
>> etc/dbus-1/system.d/avahi-dbus.conf
>> If you move that file out of that folder, dbus will start work again!
>> Just do
>> # mv /etc/dbus-1/system.d/avahi-dbus.conf /tmp/avahi-dbus.conf
>> # /etc/init.d/dbus start
> Yes that worked for me to Thanks firefox...
Many thanks. The laptop runs like a charm again.
TTFN,
Martin
John A. Bailo
> Hi everyone,
>
> I solved the problem!
> The cause for this segmentation fault is not dbus, but config file: /
> etc/dbus-1/system.d/avahi-dbus.conf
> If you move that file out of that folder, dbus will start work again!
> Just do
> # mv /etc/dbus-1/system.d/avahi-dbus.conf /tmp/avahi-dbus.conf
> # /etc/init.d/dbus start
I updated both Novell mozilla support tickets with your fix, and made a
reference to your post using a link to Google Groups so you can get the
credit.
na...@hutchingsfamily.net
Nate
On Jan 28, 12:48 pm, "John A. Bailo" <jaba...@texeme.com> wrote:
> firefox...@gmail.com wrote:
> > Hi everyone,
>
> > I solved the problem!
> > The cause for this segmentation fault is not dbus, but config file: /
> > etc/dbus-1/system.d/avahi-dbus.conf
> > If you move that file out of that folder, dbus will start work again!
> > Just do
> > # mv /etc/dbus-1/system.d/avahi-dbus.conf /tmp/avahi-dbus.conf
> > # /etc/init.d/dbus startFantastic! That also solved my problem with USB recognition! Now my
firef...@gmail.com
Glad it worked for you guys!
Answering John's question: fortunately, that was fast:
1) At first I blamed dbus, but then realized that dbus didn't get
updated during my last update
2) Since dbus executable stayed the same, but now it was crashing ---
something probably went wrong with configs
3) I went to dbus config dir and saw avahi config that I think I never
saw there before. I also remembered that avahi was exactly the thing
that got updated (well, I could have checked /var/log/yum.log instead
of remembering that :-)
4) I removed the file and it worked! :-)
I am going to update my small ugly recipe site with this. http://
suse10.narod.ru
Unfortunately, it is very slow to access from the US.
Good luck everyone!
houghi
> Thanks fixed mine too.
<snip>
This is not a flame. This is advice on how to get better help and keep
this newsgroup clean
Short story: Please read http://www.safalra.com/special/googlegroupsreply/
Long story:
Google unfortunately decided not to use the standards of quoting on
Usenet. There are several solutions to this problem. The best is to use a
newsreader. For Windows there is e.g. FreeAgent and for Linux there is
Pan, Knode or slrn, among others.
Just point your newsreader to your providers Usenet server. If they do not
have a Usenetserver, look up a payserver, like http://giganews.com or a
free server like news.sunsite.dk (registration required)
Now what if you are not at home all the time and that is your reason to
select google? Glad you asked.
If you have a fixed connection, you can use a dyndns server to make a
connection to your home linux machine over ssl and use anything that is
on your home computer.
e.g. ssh home.example.com and then run slrn. GUI interfaces are possible
as well on any OS.
If you are unable to keep a connection up, you can register at
http://www.rootshell.be and then connect to there and use slrn on that
machine. slrn is textbased and might be scary at first. As Usenet is
text anyway, you will very fast learn how to use it and configure it.
Only if all else fails and you have no option in using Usnet in any other
way, including waiting till you get home, you can use Google. You can
still quote correctly as described on the following page:
http://www.safalra.com/special/googlegroupsreply/
Understand that many people already filter out google postings. So best
look for an alternative. Usenet is not WWW. If you want WWW, look up
a webforum. This is not a webforum.
I sympathize with your problems, and am more than willing to help you
solve them. To do so you should follow the correct quoting principles
and good Netiquette explained in this FAQ available at;
http://www.plainfaqs.org/linux/
Untill then I and many other regulars who could give you good advice
won't do so. So in the interest of solcing your problems, quote correctly
and ask Google to reinstate the correct way of quoting.
Remember: this was not a flame, this was helping you to get the best
response and help possible.
houghi
--
They say pesticides have been linked to low sperm counts.
In my opinion if you have bugs down there that are so bad
you need to use a pesticide, you're not gonna get laid anyway.