Re: CUPS service not starting after upgrade to F15

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



ok
I erased error_log and started cupsd in the foreground ( cupsd -f)

I got this on error_log:

[root@bloody cups]# cat error_log
I [03/Jun/2011:06:50:25 -0500] Listening to ::1:631 (IPv6)
I [03/Jun/2011:06:50:25 -0500] Listening to 127.0.0.1:631 (IPv4)
I [03/Jun/2011:06:50:25 -0500] Listening to /var/run/cups/cups.sock (Domain)
I [03/Jun/2011:06:50:25 -0500] Remote access is disabled.
D [03/Jun/2011:06:50:25 -0500] Added auto ServerAlias bloody.pphm
D [03/Jun/2011:06:50:25 -0500] Added auto ServerAlias bloody
I [03/Jun/2011:06:50:25 -0500] Loaded configuration file "/etc/cups/cupsd.conf"
I [03/Jun/2011:06:50:25 -0500] Using default TempDir of /var/spool/cups/tmp...
I [03/Jun/2011:06:50:25 -0500] Configured for up to 100 clients.
I [03/Jun/2011:06:50:25 -0500] Allowing up to 100 client connections per host.
I [03/Jun/2011:06:50:25 -0500] Using policy "default" as the default!
I [03/Jun/2011:06:50:25 -0500] Full reload is required.
I [03/Jun/2011:06:50:25 -0500] Loaded MIME database from "/usr/share/cups/mime" and "/etc/cups": 35 types, 45 filters...
D [03/Jun/2011:06:50:25 -0500] Loading printer Canon_IP3000...
D [03/Jun/2011:06:50:25 -0500] load_ppd: Loading /var/cache/cups/Canon_IP3000.ipp4...
D [03/Jun/2011:06:50:25 -0500] Calling DeleteDevice(cups-Canon_IP3000)

Additionally, cupsd -f failed with the following error:

[root@bloody ~]# cupsd -f
process 1461: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3524.
This is normally a bug in some application using the D-Bus library.
  D-Bus not built with -rdynamic so unable to print a backtrace
Aborted

=======================

I hope it means something to someone, it does not tell me much :(
It looks like some problem with D-Bus

JP


On Fri, Jun 3, 2011 at 6:27 AM, Tim Waugh <twaugh@xxxxxxxxxx> wrote:
On Fri, 2011-06-03 at 06:01 -0500, Javier Perez wrote:
> How do I trace what is the problem? Have anyone seen this before?

Take a look in /var/log/cups/error_log.

Tim.
*/


--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines




--
------------------------------
 /\_/\  
 |O O|  pepebuho@xxxxxxxxx
 ~~~~     Javier Perez
 ~~~~          While the night runs
 ~~~~          toward the day...
  m m       Pepebuho watches
                from his high perch.
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux