| 2013-01-21 17:40:13 |
frizzle21 |
bug |
|
|
added bug |
| 2013-01-21 17:42:52 |
frizzle21 |
description |
on ubuntu 13.04 32 bit , dbus crashes when i do "sudo service networking restart".
unfortunately, this stops unity as well.
the computer keyboard became unresponsive and i had to create a folder on the desktop with the mouse context menu to find compiz in /usr/share/applications and start it with a doubleclick.
this brought back the window decoration and the keyboard, but the overall experience was still extremely slow.
and the internet didn't come back on, even after i started networking again manually, and made sure that network-manager is also running.
when i tried to start the also crashed nm-applet, it told me that it can't reach it's dbus destinations, so i decided to do an "sudo service dbus status", which showed me that dbus had also crashed.
How come dbus depends so heavily on networking, that it will crash, kill the network connection management and the internet connection entirely, when i restart the "networking" system service in the background? |
on ubuntu 13.04 32 bit , dbus crashes when i do "sudo service networking restart".
unfortunately, this stops unity as well.
the computer keyboard became unresponsive and i had to create a folder on the desktop with the mouse context menu to find compiz in /usr/share/applications and start it with a doubleclick.
this brought back the window decoration and the keyboard, but the overall experience was still extremely slow.
and the internet didn't come back on, even after i started networking again manually, and made sure that network-manager is also running.
when i tried to start the also crashed nm-applet, it told me that it can't reach it's dbus destinations, so i decided to do an "sudo service dbus status", which showed me that dbus had also crashed.
How come dbus depends so heavily on networking, that it will crash, kill the network connection management and the internet connection entirely, kill compiz and herewith unity also, just because i restart the "networking" system service in the background? |
|
| 2013-01-21 17:51:46 |
frizzle21 |
description |
on ubuntu 13.04 32 bit , dbus crashes when i do "sudo service networking restart".
unfortunately, this stops unity as well.
the computer keyboard became unresponsive and i had to create a folder on the desktop with the mouse context menu to find compiz in /usr/share/applications and start it with a doubleclick.
this brought back the window decoration and the keyboard, but the overall experience was still extremely slow.
and the internet didn't come back on, even after i started networking again manually, and made sure that network-manager is also running.
when i tried to start the also crashed nm-applet, it told me that it can't reach it's dbus destinations, so i decided to do an "sudo service dbus status", which showed me that dbus had also crashed.
How come dbus depends so heavily on networking, that it will crash, kill the network connection management and the internet connection entirely, kill compiz and herewith unity also, just because i restart the "networking" system service in the background? |
on ubuntu 13.04 32 bit , dbus crashes when i do "sudo service networking restart".
unfortunately, this stops unity as well.
the computer keyboard became unresponsive and i had to create a folder on the desktop via the mouse context menu, open nautilus through that folder, find compiz in /usr/share/applications and restart unity by doubleclicking compiz.
( i think Unity should be in there, not "compiz" )
this brought back the window decoration and the keyboard, but the overall experience was still extremely slow. And the internet didn't come back on, even after i started networking again manually, and made sure that network-manager is also running, obviously because nm-applet had crashed along with dbus.
Starting nm-applet failed with the error message telling me that dbus is unreachable.
After a "sudo service dbus status" showed me that dbus had also crashed, i found my way back to a working system quite soon.
So how to reproduce this bug:
1. /etc/init.d/networking stop
Problems you will encounter immediately:
compiz crashed
dbus crashed
unity gone (window management, window decoration, keyboard navigation/typing/capture/focus)
nm-applet crashed unrecoverable |
|
| 2013-02-05 22:59:10 |
Launchpad Janitor |
dbus (Ubuntu): status |
New |
Confirmed |
|
| 2013-07-11 13:19:05 |
Malcolm Scott |
bug |
|
|
added subscriber Malcolm Scott |
| 2013-10-12 12:20:51 |
Ionut C. |
bug |
|
|
added subscriber Ionut C. |
| 2013-10-27 02:36:16 |
Dolf Schimmel (Freeaqingme) |
bug |
|
|
added subscriber Dolf Schimmel (Freeaqingme) |
| 2013-11-02 08:06:42 |
Raphael Ackermann |
bug |
|
|
added subscriber Raphael Ackermann |
| 2013-11-11 01:49:07 |
Dave Stadnick |
bug |
|
|
added subscriber Dave Stadnick |
| 2013-11-22 08:21:30 |
Arnaud Thevenet |
bug |
|
|
added subscriber Arnaud Thevenet |
| 2013-11-29 11:40:14 |
Ivan Kukobko |
bug |
|
|
added subscriber Ivan Kukobko |
| 2014-01-16 00:11:47 |
HighBomber |
marked as duplicate |
|
1072518 |
|
| 2014-01-24 14:16:36 |
Jorge Morais |
bug |
|
|
added subscriber Jorge Morais |
| 2015-12-28 15:54:21 |
Dmitry G. |
bug |
|
|
added subscriber Dmitry G. |
| 2016-10-21 21:49:01 |
Jared Fernandez |
bug |
|
|
added subscriber Jared Fernandez |
