Ubuntu
network-manager-applet package

After upgrade from 13.04 to 13.10 no auto mount, unable to shutdown/reboot from menu, empty network list, etc ...

Bug #1248211 reported by Jaison Daniel
42
This bug affects 9 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned
network-manager-applet (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Recently I upgraded my laptop from 13.04 to 13.10. After that I am facing the following issues.

. No automount for usb devices
. Unable to shutdown/reboot from the menu (unless from commandline with sudo)
. Network list is empty (but via sudo the network list are there (nm-connection-editor))
. In the notification panel(systray) the network icon is missing.
. unable to edit User manager, the unlock button is grayed out always.

While opening "Network" from gnome-control-center, it showing the following error message.
"The system network services are not compatible with this version."

In the terminal the following error messages printed while running gnome-control-center => Network
(gnome-control-center:3748): Clutter-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.

** (gnome-control-center:3748): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 3 matched rules; type="method_call", sender=":1.88" (uid=1000 pid=3748 comm="gnome-control-center ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1666 comm="NetworkManager ")

(gnome-control-center:3748): network-cc-panel-WARNING **: Could not open RFKILL control device, please verify your installation

** (gnome-control-center:3748): WARNING **: _nm_remote_settings_ensure_inited: (NMRemoteSettings) error initializing: Rejected send message, 3 matched rules; type="method_call", sender=":1.88" (uid=1000 pid=3748 comm="gnome-control-center ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=1666 comm="NetworkManager ")

If I open the Software Updater, its showing this error
"You are not allowed to perform this action
You don't have the required privileges to perform this action"

jj@jjux64:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 13.10
Release: 13.10
Codename: saucy

jj@jjux64:~$ id
uid=1000(jj) gid=1000(jj) groups=1000(jj),4(adm),20(dialout),21(fax),24(cdrom),25(floppy),26(tape),27(sudo),29(audio),30(dip),44(video),46(plugdev),104(fuse),109(lpadmin),119(pulse),120(pulse-access),124(sambashare),130(vboxusers),131(nm-openconnect)

Please let me know, if any more info required from my side.

Jaison Daniel (jjaison-daniel)
tags: added: saucy upgrade-software-version
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1248211/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Jaison Daniel (jjaison-daniel)
affects: ubuntu → network-manager-applet (Ubuntu)
Jaison Daniel (jjaison-daniel)
summary: - After upgrade from 13.04 to 13.10 no auto mount, shutdown, empty network
- list
+ After upgrade from 13.04 to 13.10 no auto mount, unable to
+ shutdown/reboot from menu, empty network list, etc ...
Revision history for this message
Sebastien Bacher (seb128) wrote :

That's not a gnome-control-center bug, also don't mix issues in a same report like that

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Changed in network-manager-applet (Ubuntu):
status: New → Confirmed
Jaison Daniel (jjaison-daniel)
no longer affects: gnome-control-center (Ubuntu)
Robert Ancell (robert-ancell)
tags: removed: upgrade-software-version
Revision history for this message
Alex Kurilo (kamazee) wrote :

Are there separate bugs for these issues?
I experience them all and looking for a fix or workaround.

Revision history for this message
Jeff Balderson (jbalders) wrote :

This affects me too in exactly the same way.

Based on my digging, there are more than a few people experiencing this particular combination of issues after the 13.10 upgrade (NM issues, User Account management "unlock" is greyed out, drive mounting/unmounting issues, shutdown/reboot issues).

I've seen it suggested this may actually be a policykit issue, since these are all things that require elevated permissions and only occurs in the GUI. This particular system I'm on may have been upgraded more than once, but I'm not sure since I don't recall whether I did a clean install of 13.04 or upgraded from 12.10 (and more). So, it may be something that doesn't present unless you've gone through multiple chained upgrades.

Revision history for this message
Tim Band (tim-band) wrote :

Yes, I'm experiencing the same thing. Also pulseaudio is reporting only Dummy Output, which I assume is connected.
None of the googleable solutions to the pulseaudio problem fix it. I understand that I'm supposed to see my user ID when I type "getfacl /dev/snd/*"
Instead I get this:
tim@sileo:~$ getfacl /dev/snd/*
getfacl: Removing leading '/' from absolute path names
# file: dev/snd/by-id
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

# file: dev/snd/by-path
# owner: root
# group: root
user::rwx
group::r-x
other::r-x

# file: dev/snd/controlC0
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/controlC1
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/controlC2
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/hwC0D2
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/midiC1D0
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D0c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D0p
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D1c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D1p
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC0D2c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC1D0c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC1D0p
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/pcmC2D0c
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/seq
# owner: root
# group: audio
user::rw-
group::rw-
other::---

# file: dev/snd/timer
# owner: root
# group: audio
user::rw-
group::rw-
other::---

Does this help?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.