I'm interested to know where Mathieu Trudel-Lapierre (mathieu-tl) and
Sebastien Bacher (seb128) get their information. If that is the case
that it brings down dbus (and is supposed to bring down dbus), then I
should see my desktop crash whenever I run this command on whatever
machine I run it on?
Definitely can confirm this issue. sudo service networking restart
completely destroys my window session with the only option left forcing
shutdown on tty1. Breaks 13.10 for me as I'm constantly re-configuring
my interfaces.
--
You received this bug notification because you are a member of Ubuntu
Hi thread.
Sebastien, personally, I attempted to use that command several times
already with the intent to reset my networking subsystem state. Because
of some other bug, my system stops resolving hostnames at some point,
and redoing the connection is the easiest way to make network
operational ag
** Changed in: ubuntu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Title:
Restarting network crashes (apparently) the desktop manager
To manage notif
The issue is not a desktop/unity/gnome-settings-daemon/... one,
restarting the network that way shouldn't be down (it takes down the
dbus system bus which makes basically most modern softwares unhappy).
Why are you using that command?
** Package changed: gnome-settings-daemon (Ubuntu) => ubuntu
*
** Description changed:
=== WARNING ===
Doing:
sudo restart networking
or
sudo /etc/init.d/networking restart.
WILL TEAR DOWN MOST OF YOUR DESKTOP =
Networking is a generic job which brings up all networking interfaces in
** Description changed:
- The unity UI and windows decorations dissappear when I do one of the
- following:
+ === WARNING ===
+
+ Doing:
sudo restart networking
or
sudo /etc/init.d/networking restart.
- This renders me unable to focus any of the open windows
Came to the same result, when i tried to set up kvm networking.
https://help.ubuntu.com/community/KVM/Networking recommends to stop
networking, i did, and swooosh, everything is gone. :-) Yay!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
The same on Unity on 13.10 ( like this since 13.04 )
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Title:
Restarting network crashes (apparently) the desktop manager
To manage notifications
Same behavior for gnome-shell in 13.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Title:
Restarting network crashes (apparently) the desktop manager
To manage notifications about this b
the same problem with:
Linux fernando-pc 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
# is a critical issue as well as impossible to configure the network in
the shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
I have the same problem with 13.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Title:
Restarting network crashes (apparently) the desktop manager
To manage notifications about this bug g
Happening to me as well. I have a thread opened on ubuntuforums as well
http://ubuntuforums.org/showthread.php?t=2139490
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Title:
Restarting netwo
How does networking -stop differ from killing dbus? If for the sake of
argument I wanted to stop dbus without sigkilling it, how would I do that?
And how would I bring down all of my ifaces at the same time without
writing another script, which would bring them down sequentially at best?
This last
It's just the way things are done for the shutdown procedure.
As I mentioned above, you shouldn't need to run "restart networking" (in
fact, it probably needs to be renamed to something else to avoid
confusion), using ifdown and ifup to bring up and down network
interfaces directly will do the rig
the same problem with:
Linux ginetto-tablet 3.5.0-26-generic #42-Ubuntu SMP Fri Mar 8 23:20:06 UTC
2013 i686 i686 i686 GNU/Linux
what data do you need to be helped to solve?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Hey, thanks for the tip, but we still need a proper solution. Why is dbus
brought down when networking stop is called?
On Apr 5, 2013 3:41 PM, "Mathieu Trudel-Lapierre"
wrote:
> If you're looking to restart network-manager, you'll want to do 'sudo
> restart network-manager', not 'sudo restart net
If you're looking to restart network-manager, you'll want to do 'sudo
restart network-manager', not 'sudo restart networking'.
If you're making changes to /etc/network/interfaces, running "ifup -a"
will usually suffice to apply the changes. (or you can "ifdown
", then "ifup ".
--
You received th
gnome-settings-daemon indeed crashes in that case, which breaks a load
of things, including the desktop manager in general.
The reason for this is that when you restart the networking job, it
kills off the system dbus bus, which brings down quite a lot of stuff
with it.
** Package changed: ubuntu
I had that same problem, it would crash each time I tried to restart the
network-manager. Finally I restarted it from the root and it worked,
afterwords I could restart for any user, but for some reason the changes
that i had made in interfaces did not show up when executing the
command: ifconfig.
/etc/init.d/networking stop is supposed to bring down your network
interfaces. It's not crashing your network connection, it's doing what it's
supposed to. The bug we're talking about is that it also brings down your
display manager, which it's not supposed to do. After you issue the stop
command,
Same here. It also crashes my network connection and I have to reboot manually
with sudo reboot.
I don't need to go to a virtual terminal though. My xterminal comes back (with
a different background color) and I can issue the reboot command.
--
You received this bug notification because you are
same happens on current image of 13.04 i386 desktop live environment
right after restarting networking service, so basically in my case steps
to reproduce look like this:
1. --2013-03-04 16:19:34--
http://cdimage.ubuntu.com/daily-live/current/raring-desktop-i386.iso (gmt +3)
2. boot into system
I don't know if this helps, but here is a stacktrace from unity when the
crash happens:
$ unity --advanced-debug
Starting program: /usr/bin/compiz --replace
[...]
Program received signal SIGTERM, Terminated.
0x7727a425 in __GI_raise (sig=) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
64
This is also a big problem for me.
Using ubuntu 12.10 i386 and amd64, both fully updated final releases,
both are affected both have very different hardware.
I have gnome-shell installed but it also happens in the unity desktop
too!
I have been unable to simply restart gnome-shell as it either r
Same occurs with:
sudo service networking restart
All running apps including the panel are closed. The terminal window
from where the command was launched remains visible but is unresponsive.
As reported by tbys, the only recovery I have found is to drop to a non
graphic tty and reboot.
This is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1072518
Title:
27 matches
Mail list logo
