Fedora Linux Support Community & Resources Center
  #1  
Old 15th August 2012, 02:21 AM
joe.pelayo Offline
An ape descendant
 
Join Date: Dec 2006
Location: Mexico City
Age: 30
Posts: 3,105
linuxchrome
Question Last updates of F16 screwed up the network manager

Hello everybody.

It's been a while since the last time I created a thread in this forum, mainly because of the increasing work in my PhD and because my F16-x86_64 has been mostly flawless... until now when the fun returned!

Just yesterday I ran "yum update" and installed the few available updates there (I saw nothing critical like a new kernel), but after that my machine has been giving some problems. They are mainly two: the first one occurs when Fedora starts: few seconds after the login window shows up (usually when I am already typing my password), the graphical mode reverts to text mode and shows some error message about "sendmail" not starting properly; after that I can log in normally in the "restored" graphical mode.

I could live with the problem above, but there is something else: the icon corresponding to the "Network manager" does not show up in the right side of the upper panel, and if I try to invoke it "manually" it gives an error message that in English would translate to something like "The network manager service is incompatible with this version".

Since this is not kernel related I wouldn't think the problem would go away by booting an older one, and even though it could be solved in the next updates I wanted to see if someone has stumbled into this too and if there is any solution.

Thanks,
Joe.
__________________
Notebook: Acer Aspire 5536-5112.
AMD Athlon X2 QL64 @ 2.1GHz, 4GB DDR2 PC2-5300, ATI Radeon HD3200 (256MB), 250GB Toshiba HDD, HL-DT-ST DVDRAM GT20N
Windows 7 Professional, Fedora 20 x86_64
Reply With Quote
  #2  
Old 16th August 2012, 05:44 PM
joe.pelayo Offline
An ape descendant
 
Join Date: Dec 2006
Location: Mexico City
Age: 30
Posts: 3,105
linuxfedorafirefox
Re: Last updates of F16 screwed up the network manager

Anyone? I can't believe my machine is the only one experiencing this!
__________________
Notebook: Acer Aspire 5536-5112.
AMD Athlon X2 QL64 @ 2.1GHz, 4GB DDR2 PC2-5300, ATI Radeon HD3200 (256MB), 250GB Toshiba HDD, HL-DT-ST DVDRAM GT20N
Windows 7 Professional, Fedora 20 x86_64
Reply With Quote
  #3  
Old 17th August 2012, 12:45 AM
jvinla Offline
Registered User
 
Join Date: Apr 2006
Posts: 22
linuxfirefox
Re: Last updates of F16 screwed up the network manager

I tried to help a friend with very similar symptoms. After several days, we gave up and installed Fedora 17 (and everything worked again). I do not remember any messages about sendmail, but did find unspecified problems starting the color-manager. The machine is updated now so we cannot compare details, sorry.
Reply With Quote
  #4  
Old 17th August 2012, 06:49 AM
joe.pelayo Offline
An ape descendant
 
Join Date: Dec 2006
Location: Mexico City
Age: 30
Posts: 3,105
linuxfedorafirefox
Re: Last updates of F16 screwed up the network manager

Quote:
Originally Posted by jvinla View Post
I tried to help a friend with very similar symptoms. After several days, we gave up and installed Fedora 17 (and everything worked again). I do not remember any messages about sendmail, but did find unspecified problems starting the color-manager. The machine is updated now so we cannot compare details, sorry.
Thanks for your reply.

If a fix has not come up when I finally get a break at work (in a week or so), I certainly will be upgrading the machine to F17.

Joe.
__________________
Notebook: Acer Aspire 5536-5112.
AMD Athlon X2 QL64 @ 2.1GHz, 4GB DDR2 PC2-5300, ATI Radeon HD3200 (256MB), 250GB Toshiba HDD, HL-DT-ST DVDRAM GT20N
Windows 7 Professional, Fedora 20 x86_64
Reply With Quote
  #5  
Old 21st August 2012, 10:58 PM
westand Offline
Registered User
 
Join Date: May 2008
Posts: 58
linuxfirefox
Re: Last updates of F16 screwed up the network manager

I'm seeing the exact same thing.

Reading /var/log/messages I thought it might have something to do with the system.d bluetooth service (which fails; so is my akmod.service). Seeing as how bluetooth is part of the networking; maybe this is how it flows into the Network Manager issue?

---------- Post added at 04:58 PM ---------- Previous post was at 04:35 PM ----------

Code:
Aug 21 17:33:25 localhost dbus[1128]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
Aug 21 17:33:25 localhost dbus-daemon[1128]: dbus[1128]: [system] Failed to activate service 'org.freedesktop.ColorManager': timed out
Aug 21 17:33:25 localhost dbus[1128]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Aug 21 17:33:25 localhost dbus-daemon[1128]: dbus[1128]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Aug 21 17:33:25 localhost dbus-daemon[1128]: process 1128: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1009.
Aug 21 17:33:25 localhost dbus-daemon[1128]: This is normally a bug in some application using the D-Bus library.
Aug 21 17:33:25 localhost dbus-daemon[1128]: D-Bus not built with -rdynamic so unable to print a backtrace
Aug 21 17:33:25 localhost avahi-daemon[1100]: Disconnected from D-Bus, exiting.
Aug 21 17:33:25 localhost avahi-daemon[1100]: Got SIGTERM, quitting.
Aug 21 17:33:25 localhost systemd[1]: systemd-logind.service: main process exited, code=exited, status=1
Aug 21 17:33:25 localhost avahi-daemon[1100]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.7.200.
Aug 21 17:33:25 localhost NetworkManager[1068]: <warn> disconnected by the system bus.
Aug 21 17:33:25 localhost accounts-daemon[1252]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Aug 21 17:33:25 localhost console-kit-daemon[1250]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Aug 21 17:33:25 localhost rtkit-daemon[1391]: Demoting known real-time threads.
Aug 21 17:33:25 localhost rtkit-daemon[1391]: Successfully demoted thread 1396 of process 1389 (/usr/bin/pulseaudio).
Aug 21 17:33:25 localhost rtkit-daemon[1391]: Successfully demoted thread 1395 of process 1389 (/usr/bin/pulseaudio).
Aug 21 17:33:25 localhost rtkit-daemon[1391]: Successfully demoted thread 1394 of process 1389 (/usr/bin/pulseaudio).
Aug 21 17:33:25 localhost rtkit-daemon[1391]: Successfully demoted thread 1389 of process 1389 (/usr/bin/pulseaudio).
Aug 21 17:33:25 localhost rtkit-daemon[1391]: Demoted 4 threads.
Aug 21 17:33:25 localhost NetworkManager[1068]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Aug 21 17:33:25 localhost dbus-daemon[1128]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Aug 21 17:33:25 localhost systemd[1]: Unit systemd-logind.service entered failed state.
Aug 21 17:33:25 localhost systemd[1]: dbus.service: main process exited, code=killed, status=6
Aug 21 17:33:25 localhost avahi-daemon[1100]: avahi-daemon 0.6.30 exiting.
Aug 21 17:33:25 localhost systemd[1]: bluetooth.service: main process exited, code=exited, status=1
Aug 21 17:33:25 localhost systemd[1]: Unit bluetooth.service entered failed state.
Aug 21 17:33:25 localhost systemd[1]: Unit dbus.service entered failed state.
Aug 21 17:33:25 localhost dbus-daemon[1486]: dbus[1486]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Aug 21 17:33:25 localhost dbus[1486]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Aug 21 17:33:25 localhost avahi-daemon[1488]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
Aug 21 17:33:25 localhost avahi-daemon[1488]: Successfully dropped root privileges.
Aug 21 17:33:25 localhost avahi-daemon[1488]: avahi-daemon 0.6.30 starting up.
Aug 21 17:33:25 localhost avahi-daemon[1488]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Aug 21 17:33:25 localhost dbus[1486]: [system] Successfully activated service 'org.freedesktop.Avahi'
Aug 21 17:33:25 localhost dbus-daemon[1486]: dbus[1486]: [system] Successfully activated service 'org.freedesktop.Avahi'
Aug 21 17:33:25 localhost avahi-daemon[1488]: Successfully called chroot().
Aug 21 17:33:25 localhost avahi-daemon[1488]: Successfully dropped remaining capabilities.
Aug 21 17:33:25 localhost avahi-daemon[1488]: Loading service file /services/ssh.service.
Aug 21 17:33:25 localhost avahi-daemon[1488]: Loading service file /services/udisks.service.
Aug 21 17:33:25 localhost avahi-daemon[1488]: System host name is set to 'localhost'. This is not a suitable mDNS host name, looking for alternatives.
Aug 21 17:33:25 localhost avahi-daemon[1488]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.7.200.
Aug 21 17:33:25 localhost avahi-daemon[1488]: New relevant interface wlan0.IPv4 for mDNS.
Aug 21 17:33:25 localhost avahi-daemon[1488]: Network interface enumeration completed.
Aug 21 17:33:25 localhost avahi-daemon[1488]: Registering new address record for fe80::2677:3ff:fe11:35e0 on wlan0.*.
Aug 21 17:33:25 localhost avahi-daemon[1488]: Registering new address record for 192.168.7.200 on wlan0.IPv4.
Aug 21 17:33:25 localhost avahi-daemon[1488]: Registering HINFO record with values 'X86_64'/'LINUX'.
Aug 21 17:33:26 localhost avahi-daemon[1488]: Server startup complete. Host name is linux.local. Local service cookie is 3036587918.
Aug 21 17:33:27 localhost avahi-daemon[1488]: Service "linux" (/services/udisks.service) successfully established.
Aug 21 17:33:27 localhost avahi-daemon[1488]: Service "linux" (/services/ssh.service) successfully established.
Aug 21 17:33:27 localhost NetworkManager[1068]: dbus_g_proxy_begin_call: assertion `!DBUS_G_PROXY_DESTROYED (proxy)' failed
Aug 21 17:33:27 localhost NetworkManager[1068]: nm_supplicant_info_set_call: assertion `call != NULL' failed
Aug 21 17:33:27 localhost NetworkManager[1068]: <info> (wlan0): IP6 addrconf timed out or failed.
Aug 21 17:33:27 localhost NetworkManager[1068]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Aug 21 17:33:27 localhost NetworkManager[1068]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Aug 21 17:33:27 localhost NetworkManager[1068]: <info> Activation (wlan0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Aug 21 17:33:28 localhost NetworkManager[1068]: <info> reconnected to the system bus.
Aug 21 17:33:28 localhost dbus[1486]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Aug 21 17:33:28 localhost dbus-daemon[1486]: dbus[1486]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
Aug 21 17:33:28 localhost bluetoothd[1494]: Bluetooth daemon 4.96
Aug 21 17:33:28 localhost bluetoothd[1494]: bluetoothd[1494]: Bluetooth daemon 4.96
Aug 21 17:33:28 localhost dbus[1486]: [system] Successfully activated service 'org.bluez'
Aug 21 17:33:28 localhost dbus-daemon[1486]: dbus[1486]: [system] Successfully activated service 'org.bluez'

Last edited by westand; 21st August 2012 at 11:43 PM.
Reply With Quote
  #6  
Old 22nd August 2012, 12:37 AM
Dan Offline
Administrator
 
Join Date: Jun 2006
Location: Paris, TX
Posts: 23,279
linuxfirefox
Re: Last updates of F16 screwed up the network manager

Aw, DANG!

Of all the things I've lost ... I miss my mind the most.

I had this problem about a month and a half ago, or so, and the fix was really simple, but all I clearly remember about it was after doing something, then I rebooted into an earlier kernel, ran updates from Runlevel 3, and booted back into the GUI which was then trouble free. But for the life of me ... I can't remember what I did before I rebooted and ran updates again. <....>


*Sigh!*

Gettin' old ain't for wimps. <....>
Reply With Quote
  #7  
Old 22nd August 2012, 12:47 AM
westand Offline
Registered User
 
Join Date: May 2008
Posts: 58
linuxfirefox
Re: Last updates of F16 screwed up the network manager

FIXED: I just needed to downgrade "colord". Thanks, -AW
Reply With Quote
Reply

Tags
f16, manager, network, screwed, updates

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Latest update on F15 screwed up network manager egr Using Fedora 10 6th July 2011 02:06 PM
mesa-lib updates screwed my gui manojabala Using Fedora 0 20th January 2010 02:58 PM
Is it safe to apply recent updates for Network Manager, kernel? sdunbar1 Using Fedora 1 15th March 2009 04:46 PM
latest updates screwed my box :( mckechan Using Fedora 4 15th April 2008 11:28 AM
FC5 updates screwed up gdm ElRealistico Using Fedora 0 22nd April 2006 01:58 AM


Current GMT-time: 02:48 (Monday, 24-11-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat
Pitt Meadows Photos - Nandaime Photos - Baoding Photos on Instagram