You are not logged in.
Pages: 1
Fire fox won't start up and only has one output
"bus error"
I tried reinstalling but it didn't help.
Last edited by otacon (2009-02-05 06:26:36)
http://remcycle.net
Cheap Web Hosting and Even Cheaper Domain Registration
Offline
Is DBus running?
/etc/rc.d/dbus (try to stop it, if that fails, it may be stopped - try to start it)
Most people have HAL as an automatic daemon, which starts DBus automatically. Starting both in rc.conf DAEMONS can cause problems.
Offline
[otacon@remcycle ~]$ sudo /etc/rc.d/dbus stop
Password:
:: Stopping D-BUS system messagebus [DONE]
[otacon@remcycle ~]$ sudo /etc/rc.d/dbus start
:: Starting D-BUS system messagebus [DONE]
[otacon@remcycle ~]$ firefox
Bus error
didn't seem to help.
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond alsa hal fam kdm)
As you can see hal is in the daemons and not dbus so it can't be that.
-----------------------------------------------------------------------------------------------
I installed firefox before kde and it worked fine in regular xorg then.
Last edited by otacon (2009-02-05 05:45:06)
http://remcycle.net
Cheap Web Hosting and Even Cheaper Domain Registration
Offline
There are two things that I can think of, and neither are anything but guesses. Try to reinstall xulrunner and see if that helps. If not, rename your ~/.mozilla directory and restart Firefox.
Offline
reinstalling xulrunner worked. ty for your help
http://remcycle.net
Cheap Web Hosting and Even Cheaper Domain Registration
Offline
Same prob here...
Reinstalling didn't help.
The most strange thing - i can browse arch page with no probs...
Wierd thing - it worked in the morning, then ran pacman -Syu - now much got updated and neither was related to FF or dbus...
Tried installing Flock - same no go, but with a bit different error, which points us to run-mozilla.sh
/usr/lib/flock/run-mozilla.sh: line 131: 9293 Bus error
running dmesg gives this related error:
Jun 17 16:16:40 blayder kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 17 16:16:40 blayder kernel: ata1.00: BMDMA stat 0x25
Jun 17 16:16:40 blayder kernel: ata1.00: cmd c8/00:08:80:81:50/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 17 16:16:40 blayder kernel: res 51/40:08:81:81:50/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 17 16:16:40 blayder kernel: ata1.00: status: { DRDY ERR }
Jun 17 16:16:40 blayder kernel: ata1.00: error: { UNC }
Jun 17 16:16:43 blayder kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 17 16:16:43 blayder kernel: ata1.00: BMDMA stat 0x25
Jun 17 16:16:43 blayder kernel: ata1.00: cmd c8/00:08:80:81:50/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 17 16:16:43 blayder kernel: res 51/40:08:81:81:50/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 17 16:16:43 blayder kernel: ata1.00: status: { DRDY ERR }
Jun 17 16:16:43 blayder kernel: ata1.00: error: { UNC }
Jun 17 16:16:52 blayder kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 17 16:16:52 blayder kernel: ata1.00: BMDMA stat 0x25
Jun 17 16:16:52 blayder kernel: ata1.00: cmd c8/00:08:80:81:50/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 17 16:16:52 blayder kernel: res 51/40:08:81:81:50/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 17 16:16:52 blayder kernel: ata1.00: status: { DRDY ERR }
Jun 17 16:16:52 blayder kernel: ata1.00: error: { UNC }
Jun 17 16:16:52 blayder kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 17 16:16:52 blayder kernel: ata1.00: BMDMA stat 0x25
Jun 17 16:16:52 blayder kernel: ata1.00: cmd c8/00:08:80:81:50/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 17 16:16:52 blayder kernel: res 51/40:08:81:81:50/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 17 16:16:52 blayder kernel: ata1.00: status: { DRDY ERR }
Jun 17 16:16:52 blayder kernel: ata1.00: error: { UNC }
Jun 17 16:16:52 blayder kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 17 16:16:52 blayder kernel: ata1.00: BMDMA stat 0x25
Jun 17 16:16:52 blayder kernel: ata1.00: cmd c8/00:08:80:81:50/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 17 16:16:52 blayder kernel: res 51/40:08:81:81:50/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 17 16:16:52 blayder kernel: ata1.00: status: { DRDY ERR }
Jun 17 16:16:52 blayder kernel: ata1.00: error: { UNC }
Jun 17 16:16:52 blayder kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jun 17 16:16:52 blayder kernel: ata1.00: BMDMA stat 0x25
Jun 17 16:16:52 blayder kernel: ata1.00: cmd c8/00:08:80:81:50/00:00:00:00:00/e0 tag 0 dma 4096 in
Jun 17 16:16:52 blayder kernel: res 51/40:08:81:81:50/00:00:00:00:00/e0 Emask 0x9 (media error)
Jun 17 16:16:52 blayder kernel: ata1.00: status: { DRDY ERR }
Jun 17 16:16:52 blayder kernel: ata1.00: error: { UNC }
Jun 17 16:16:52 blayder kernel: end_request: I/O error, dev sda, sector 5276033
I'll give fsck a try, maybe it is somehow related to filesystem error? running / patition on ext4...
P.S. Ow... misread date on posts... necroposting is baaad :'(
P.P.S. Sadly... A bit of thinking and i narrowed it down to flash and JRE... Uninstalled them and all went well. No errors... So i reinstalled them and now everything seems to be working :-/
Pretty odd... But it works...
Last edited by Blayder (2009-06-17 14:51:38)
Offline
Sorry for necroposting, but link to this thread is the first in the google's feed.
I had the same error "bus error", when tried to launch firefox.
It was caused by insufficient free disk space (df -h showed 0, nothing at all). I used suggestion given by Blayder - removed flash plugin and it helped (now i know why it helpled - i had no space on hdd).
Hope this will help somebody. Cheers.
Offline
Pages: 1