Bug 684754 - Connection to network printer lost after reboot
Summary: Connection to network printer lost after reboot
Keywords:
Status: CLOSED DUPLICATE of bug 647831
Alias: None
Product: Fedora
Classification: Fedora
Component: avahi
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-14 12:44 UTC by Joachim Backes
Modified: 2011-04-03 22:02 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-04-03 22:02:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Joachim Backes 2011-03-14 12:44:05 UTC
Description of problem:
Very often, after a F15 reboot I get lost from my network printer Lexmark e120n.
So printing fails.

I have to do the following:

1. sudo service avahi-daemon [re]start
2. sudo cupsenable <myprinter>

My impression: the interaction between avahi-daemon and NetworkManager is buggy.

Version-Release number of selected component (if applicable):
avahi-0.6.29-1.fc15.x86_64

How reproducible:
Very often after reboot

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

I found in /var/log/messages the following lines:
Mar 14 13:10:04 eule avahi-daemon[10313]: Got SIGTERM, quitting.
Mar 14 13:10:04 eule avahi-daemon[10313]: Leaving mDNS multicast group on interface em1.IPv4 with address 192.168.100.105.
Mar 14 13:10:04 eule avahi-daemon[10313]: avahi-daemon 0.6.29 exiting.
Mar 14 13:32:32 eule dbus-daemon: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.193" (uid=500 pid=4254 comm="/bin/systemctl start avahi-daemon.service ") interface="org.freedesktop.systemd1.Manager" member="StartUnit" error name="(unset)" requested_reply=0 destination="org.freedesktop.systemd1" (uid=0 pid=1 comm="/sbin/init "))

Comment 1 Lennart Poettering 2011-04-02 01:54:31 UTC
I am not sure I understand your problem? is that an mDNS/DNS_SD printer? does it show up in "avahi-browse _ipp._tcp"?

Comment 2 Joachim Backes 2011-04-02 04:45:37 UTC
PLaying a little bit with the avahi-daemon I found out that after reboot no avahi-daemon is running. After entering service avahi-daemon start by hand, the printer can be accessed.

I did not find any avahi-daemon error message in /var/log/messages after reboot!

If I call "avahi-browse _ipp._tcp" after booting, I see:
Failed to create client object: Daemon not running


Is there any additional info I can provide for you? 

"chkconfig --list avahi-daemon" shows "on" for runlevel 3 and 5.

Comment 3 Joachim Backes 2011-04-02 04:47:42 UTC
I forgot: after having started the avahi-daemon, the command

"avahi-browse _ipp._tcp"  shows up:


+    em1 IPv4 Lexmark E120n @ eule                          Internet Printer     local
+    em1 IPv4 Lexmark E120n                                 Internet Printer     local

Comment 4 Lennart Poettering 2011-04-03 22:02:22 UTC

*** This bug has been marked as a duplicate of bug 647831 ***


Note You need to log in before you can comment on or make changes to this bug.