** Changed in: opensuse
Status: Unknown = Fix Released
** Changed in: opensuse
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/444597
Title:
After upgrade to
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Hello.
Is this problem present with the latest updated packages of Lucid ?
Thanks in advance
Fabio
** Changed in: ubuntu
Status: New = Incomplete
** Tags added: jaunty-to-karmic
** Tags added: thinkpad-x300
--
After upgrade to karmic cups server do not start.
** Bug watch added: Novell/SUSE Bugzilla #339443
https://bugzilla.novell.com/show_bug.cgi?id=339443
** Also affects: opensuse via
https://bugzilla.novell.com/show_bug.cgi?id=339443
Importance: Unknown
Status: Unknown
--
After upgrade to karmic cups server do not start.
Check this out, it solved my cups problem:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/500520/comments/8
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Bug watch removed: Novell/SUSE Bugzilla #339443
https://bugzilla.novell.com/show_bug.cgi?id=339443
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Still no way to make it work on my main system but I've discovered that
also vboxdrv does not start upon boot. This is definitely not a CUPS
problem alone so I'm now following bug #500520 in stead plus some
related threads on the Ubuntu fora.
--
After upgrade to karmic cups server do not start.
I got it working on one of my two computers by using sysv-rc-conf to add
run level S to the CUPS entry. It didn't work on my main system, though.
While fooling around, I broke my older system (the one where i got CUPS
working) and had to reinstall Karmic. Before any updates are loaded, I
now see
After two rounds of updates and HW driver installs, still no problem
with CUPS on the old machine despite not being set to run at run level
S. Strange, and why doesn't it work on my main system. Hope I don't need
to reinstall that too.
--
After upgrade to karmic cups server do not start.
Yes, I have upgraded from 9.04 to 9.10 (64bit) and experiencing the
same as PWM. above.
dpkg -l |grep HP for printing gives;
ii hpijs 3.9.8-1ubuntu2 HP
Linux Printing and Imaging - gs IJS drive
ii hpijs-ppds 3.9.8-1ubuntu2
Update : Unfortunately the fix wasn't permanent.
After the first boot everything was working OK. But then cups doesn't start
after subsequent boots.
Meanwhile /var/spool/cups/tmp/.hplip has emerged from somewhere. And
/var/log/cups/error_log now contains Unable to remove temporary file
I was able to fix one case according to this :
http://joeb454.ubuntuforums.org/showthread.php?p=8455909 I.e. By
changing cups start-up status with sysv-rc-conf. Similarly this could
also fix some other of those init issues.
Must be some glitch in some install scripts ..
I must advice against the
Welcome to the brave new world of Ubuntu==Microsoft Windows. In the old
days, I could simply watch the system boot. Any hickup would be noticed
easily and the cause could be investigated. Today, karmic covers
everything with a boot splash, things go wrong underneath badly but we
pretend everything
Ok, found it myself:
apt-get install startupmanager
Run it, get rid of the boot splash and make sure to activate show text
during boot.
Harald.
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a
I also have this problem. CUPS doesn't start on boot. It happened after
one of the more recent updates (I now have CUPS 1.4.1) on both my
desktops running Karmic (fresh installs). No problems until less than a
week ago.
I've searched the web and found this and other threads about people
having
Ditto: In fact, looking at BootUp-Manager, only ntp and pulseaudio
start; every other daemon (including cups and samba) fail to do so, but
will if called directly by sudo. So (in my case at least) this appears
to be a fairly wide-reaching problem.
I'm running a fresh install of 32-bit Karmic,
Simon, after some work we found this:
- With upstart there is no boot logging (it's not supported yet!;
/var/log/bootlog is empty), so if some daemon from /etc/init.d fails
to load it may leave no trace.
- With upstart in Karmic, some services (scripts in /etc/init) run in parallel.
But scripts
I'm also affect:
no automatic start of the cups server, but no problem if I start it manually.
It appears with karmic
I noticed the problem after rebooting with my new printer (samsung laser color
with samsung linux driver) that I added to a HP PSC1210 that i still continue
to use as scanner
I am hit by this bug too, but I think it is not related to cups only.
see bug #453473
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/453473?comments=all
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because
We have a customer with this bug: since he updated some packages on
2009-12-03 cups won't start on boot (he hadn't updated since
2009-11-09).
If we run sudo /etc/init.d/cups start it starts without problems. We
found that the /etc/init.d/cups script is simply not run on boot!
(there is no
eZFlow's method does not work for me. I am also affected, but in my
/etc/init.d/rc Concurrency is already set to none.
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is
correction:
for me the problem is actually twofold: sharing printers via cups over the
local network does not work any more since the upgrade from jaunty to karmic
but the cups service seems to be running.
sharing printers via samba does not work, because samba complains that it
cannot find the
another addition, sorry:
I found out, that for me the first problem mentioned above was actually not
with cups but, that avahi does not announce the cups printers properly any more.
the samba problem remains
--
After upgrade to karmic cups server do not start.
i found what was causing my problem.
enter: sudo gedit /etc/init.d/rc
change CONCURRENCY to none, not startpar or shell because that doesnt
work in karmic.
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you
affected, subscribing. Would it be a possible fix to simply rename the
cups start script so that it starts later? As, after all, it does seem
to start just fine manually...
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug
Hello workaholics,
I have this problem like you. What should I do next ???
Output is looking as if there is missing a library ???
Here:
-
nux-76c3:/home/dschinn/Desktop/hplip-3.9.8 # make
/bin/sh ./libtool --tag=CC
Mmhhh... I shouldn't have post this as uninstalling upstart, sysv-rc and
insserv may break your system. Here is more or less what I did:
$ sudo dpkg --purge --force-all upstart sysv-rc insserv
Notice the --force-all flag so you should really know what you are
doing.
sysv-rc complained about
Ha, yeah...well...I just did a dual boot with a fresh version of Karmic
and am transfering my files over. Its definitely beyond me, plus I now
have the ultrafast ext4 file system. Thanks anyway!
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You
This is a bug with the October 26th updates
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Today I purged upstart, sysv-rc and insserv, reinstall them and it now
works as expected. cups, ondemand, virtualbox-ose, etc are started
during the boot process. Something went probably wrong during the alpha
phases.
--
After upgrade to karmic cups server do not start.
Hmm, I'll try Cyril's fix and post back.. I just upgraded from Jaunty.
This WILL BE a major showstopper for a lot of people.
EDIT: Cyril, how did you manage to do this without uninstalling the
entire O/S? Please post a workaround.
- CH
--
After
Hi Cyril,
Need some help. I tried a reinstallation of the three packages
(upstart, sysv-rc and insserv) and got and Error 2 sysv-rc. Now during
a reboot there is a very long pause - 5 minutes where the machine is
trying to find a list of modules to load a boot. How do I fix this?
Thanks,
Hitting this bug now along with pulseaudio not starting (and others??).
Seems like a serious issue to me. Is this going to be fixed before the
final release? I don't see how 9.10 can break all of the old services
and still be released as is??
--
After upgrade to karmic cups server do not start.
I opened a new bug against the sysv-rc package. Bug #453473.
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm also affected by this bug in karmic since a few days/weeks. I
strongly suspect upstart (or another package related to the new boot
process). I noticed that some if not all scripts in /etc/rc2.d/ are not
executed on boot.
ondemand is not executed. The governor is now set to performance instead
Cyril, thank you for your comment. This looks really like the reason for
the bug.
As many services which did not get migrated to upstart do not start on
your system, the problem seems to be upstart's default configuration and
not bugs in the individual services. This is not a CUPS bug.
I have moved the HPLIP discussion to bug 452134, please continue that
discussion there.
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have no time to investigate this, and I don't see any evidence of an
Upstart problem here - all of the services you're referring to are
sysvinit services/initscripts still
** Changed in: ubuntu
Assignee: Scott James Remnant (scott) = (unassigned)
--
After upgrade to karmic cups server do
I too have this problem. Subscribing to bug ;-)
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The 'Unable to remove temporary file /var/spool/cups/tmp/.hplip - Is a
directory' is not the reason why CUPS does not start. On my system the
directory also exists and also the error in error_log but CUPS started
without problems after every update of the CUPS package.
--
After upgrade to karmic
And guess what there is on my openSUSE 11.1 workstation:
--
l...@host $ ls -la ~
total 16
drwxr-xr-x 3 lp lp 4096 2009-10-07 10:15 .
drwxr-xr-x 13 root root 4096 2009-08-12 15:15 ..
-rw--- 1 lp lp 17 2009-10-07
FYI, we have had a similar issue, compare
https://bugzilla.novell.com/show_bug.cgi?id=339443
Usually a .hplip directory is created by whatever hp* program
in the home directory of the user who runs it (if this directory
does not yet exist).
If the user lp runs whatever such hp* program,
a .hplip
From my current point of view there are two bugs:
1.
Backends and filters in HPLIP should not leave any
files and/or directories in the system (i.e. clean up all
what tey might have created).
2.
CUPS should do a more rigorous clenaup of his own
directories (i.e. rm -rf instead of only a plain
My /var/spool/lpd/.hplip directory was created a longer time ago.
I cannot remember which HPLIP version I did run at 2009-01-13.
Currently I run HPLIP 3.9.8.
I removed the /var/spool/lpd/.hplip directory manually.
It did not re-appear,
neither after running /usr/lib/cups/backend/hp
nor after
Under Jaunty and Karmic there are no CUPS filters, backends, or PPD
generators which call any command line tools of HPLIP (grep hp-
/usr/lib/cups/*/*). system-config-printer calls hp-info and hp-
makeuri, both are called as the user who called system-config-printer
(interactive GUI mode) or root
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33124075/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/33124076/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33124077/Dependencies.txt
**
** Package changed: cups (Ubuntu) = hplip (Ubuntu)
** Also affects: hplip
Importance: Undecided
Status: New
--
After upgrade to karmic cups server do not start.
https://bugs.launchpad.net/bugs/444597
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This is an upstream problem of HPLIP. The hp backend of HPLIP creates
a directory in the /var/spool/cups/tmp/ directory, probably to save
configuration data there. This breaks the start-up process of CUPS.
To the developers at HP: This is a design bug. CUPS filters and backends
should never
Till,
The hp backend creats no .hplip directory.
Something (hal_lpadmin?) must be calling a hp-xxx command which probably
creates the .hplip directory at cups restart.
The commands hp-makeuri and hp-info are intended to be run by users
only. I would try to use the hp-mkuri command for system
49 matches
Mail list logo
