Can you check whether this could be a CUPS issue?
Check whether the issues happens if you first print into PDF and then
send the PDF to the printer. If the file does not print correctly, then
this is more a CUPS issue.
Background: On Ubuntu 11.04 (and also on 10.04) on CUPS filtering
process call
Are you accessing printers using CUPS?
I had the same problem when printing from a CUPS client (both
Libreoffice and Openoffice).
The cause seems to be CUPS server closing the client connection after
300seconds of idle. When the client tries to print or retrieve printer
list after the connection
Are you sure it freezed in the end of that log file or Xorg.1.log? I
mean do you rebooted after freeze and took new Xorg.0.log file where is
no freezing anymore?
--
suspend does not work on Asus UL30JT
https://bugs.launchpad.net/bugs/619399
You received this bug notification because you are a mem
I would like to see Xorg's log for time when freezing happened. I've
seen infinity loop in X when suspending in UL30vt and it caused total
freeze.
--
suspend does not work on Asus UL30JT
https://bugs.launchpad.net/bugs/619399
You received this bug notification because you are a member of Ubuntu
B
Arand, Thank's for taking care of the patch.
I'm amazed that there are so few reports on this issue, as *everyone*
updating or installing 10.04 will be affected by the issue when fsck is
eventually run ... once a month with journalling FS. My guess is, that
unless released soon, the number of affe
Attached patches containing workarounds / proposed fixes for mountall.c and
libply. These fix the issue for me, at least.
BR
--
Tmo
** Patch added: "45.diff"
http://launchpadlibrarian.net/47524315/45.diff
--
plymouthd crashed with SIGSEGV in ply_event_loop_process_pending_events()
https://
Folks,
I'm back on this old issue again.
FSCK with progress indicator (-C switch) produces a very large number of
progress messages, which all are read, and forwarded to plymouth on
function fsck_reader(), file mountall.c. Plymouthd can't keep up with
hundreds of thousands, perhaps millions, of m
** Changed in: plymouth (Ubuntu Lucid)
Status: Fix Released => Incomplete
--
mountall needs to flush plymouth message queue before emitting upstart events
https://bugs.launchpad.net/bugs/559761
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Folks,
This issue is still present with the following versions:
plymouth: 0.8.2-2ubuntu1
mountall: 2.15~ppa1
Fsck progress displayed at boot screen stops advancing at 70%.
20 seconds after that the login screen appears.
Meanwhile mountall keeps logging: "mountall: Plymouth command failed" on
Hello.
I had this same problem where mountall consumed a lot of CPU cycles (and
appeared to be busy-looping) in case fsck was performed. The program was
not busy-looping, and did eventually exit by itself.
This behaviour was caused by an assertion at libply module, file ply-
list.c, function ply_
10 matches
Mail list logo
