Still a problem in 10.10.
Seems to be the same as Gnome bug
https://bugzilla.gnome.org/show_bug.cgi?id=559816
** Bug watch added: GNOME Bug Tracker #559816
https://bugzilla.gnome.org/show_bug.cgi?id=559816
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I propose this is a duplicate of
https://bugs.launchpad.net/ubuntu/karmic/+source/linux/+bug/292256 as well as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/459678
Which has been fixed with a recent kernel update (2.6.31-20.57), at least in my
case.
--
thinkpad x40: backlight does not
I experience this daily -- which means exactly once per day: Every morning when
I arrive, the keyboard repeat rate has been reset. I set it again by opening
System Preferences Keyboard, sliding the Repeat Keys/Speed slider a
little and back again and closing.
I have tried using the kdbrate
Sorry for the delay, I was away from the office. I have updated
foomatic-filters from karmic-proposed, installed a new printer (well, pointing
the the same physical printer, I'm not Uncle Scrooge!), which works like a
charm!
Checked /etc/cups/printers.conf, where the new printer has
Filter
Well, if TCP is supported (and even is the default!) I think it should work. I
see switching to UDP as a workaround that I was lucky to find. There is no
sense in accepting that a provided feature (NFS4 over TCP) does not work
reliably. It would be better remove it, so other people don't fall
With
lp -oraw foo-out.ps
I get only the first page of the document. With
lp -oraw foo-in.ps
I get all 4 pages, which is why I changed printers.conf. I have no lpoptions
files:
a...@kapowdk-ac:~$ ls ~/.cups
ls: cannot access /home/ac/.cups: No such file or directory
a...@kapowdk-ac:~$ ls
Forgot to say: I get no complaints from doing:
nc -w1 xerox7245.kapow.dk 9100 /tmp/foo-in.ps
--
Xerox WorkCentre 7245 (7228) prints only first page
https://bugs.launchpad.net/bugs/513690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Answer to comment #13: Commenting out the flushfile makes lp -oraw
... print all the pages.
Answer to comment #15: Yes, with the 7242 PPD, printing works out of the
box, because the following is inserted into /etc/cups/printers.conf for
the added printer:
Filter application/vnd.cups-raw 0 -
Good to see this fixed; thanks for the great support. It's what we need
to further this platform.
--
Xerox WorkCentre 7245 (7228) prints only first page
https://bugs.launchpad.net/bugs/513690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thanks for taking the time to investigate this!
However the fixed foomatic-rip from karmic-proposed makes no difference, I
still get only the first page (I DID remember to undo my changes to
/etc/cups/printers.conf for this test).
I have made another test, snatching the input and output to/from
** Attachment added: foo-in.ps
http://launchpadlibrarian.net/38746529/foo-in.ps
--
Xerox WorkCentre 7245 (7228) prints only first page
https://bugs.launchpad.net/bugs/513690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: foo-out.ps
http://launchpadlibrarian.net/38746787/foo-out.ps
--
Xerox WorkCentre 7245 (7228) prints only first page
https://bugs.launchpad.net/bugs/513690
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: system-config-printer-gnome
r...@kapowdk-ac:/usr/bin# lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
r...@kapowdk-ac:/usr/bin# apt-cache policy system-config-printer-gnome
system-config-printer-gnome:
Installed:
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/38481896/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/38481897/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/38481898/Dependencies.txt
**
** Attachment added: PPD file for Xerox printer, from
/etc/cups/ppd/Xerox-WorkCentre-7245.ppd
http://launchpadlibrarian.net/38481941/Xerox-WorkCentre-7245.ppd
--
Xerox WorkCentre 7245 (7228) prints only first page
https://bugs.launchpad.net/bugs/513690
You received this bug notification
** Attachment added: PPD file for HP printer, from
/etc/cups/ppd/HP-LaserJet-P2015-Series.ppd
http://launchpadlibrarian.net/38481948/HP-LaserJet-P2015-Series.ppd
--
Xerox WorkCentre 7245 (7228) prints only first page
https://bugs.launchpad.net/bugs/513690
You received this bug notification
** Attachment added: Modified and working /etc/cups/printers.conf
http://launchpadlibrarian.net/38481959/printers.conf
--
Xerox WorkCentre 7245 (7228) prints only first page
https://bugs.launchpad.net/bugs/513690
You received this bug notification because you are a member of Ubuntu
Bugs,
After reporting this bug, I switched to using UDP rather than TCP, and I
have not seen the problem for 3 weeks now!
The exact change is that I added ,proto=udp to /etc/fstab on the client like
this:
bbb:/helle-nfs /home/helle nfs4bg,proto=udp0 0
--
nfs: server not
Public bug reported:
Even after applying kernel patches as described in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/379385 I
occasionally experience the following problem on my nfs4 client
computer. Occasionally means that recently (and according to syslog)
it happened on Oct 14, Nov 3,
** Attachment added: uname-a.log
http://launchpadlibrarian.net/35326334/uname-a.log
--
nfs: server not responding, timed out, then nfs4 locks up
https://bugs.launchpad.net/bugs/477711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Output from cat /proc/version_signature
http://launchpadlibrarian.net/35326371/version.log
--
nfs: server not responding, timed out, then nfs4 locks up
https://bugs.launchpad.net/bugs/477711
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Output from dmesg
http://launchpadlibrarian.net/35326408/dmesg.log
--
nfs: server not responding, timed out, then nfs4 locks up
https://bugs.launchpad.net/bugs/477711
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Output from lspci -vnvn
http://launchpadlibrarian.net/35326427/lspci-vnvn.log
--
nfs: server not responding, timed out, then nfs4 locks up
https://bugs.launchpad.net/bugs/477711
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Even after patching the kernel as described I have nfs4 problems.
These look a little different and I have created a new bug report,
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/477711
--
5-minute delay in nfs4 client after suspend/resume
https://bugs.launchpad.net/bugs/379385
You
Yes, it started reappearing for me, too. Sorry for not updating this bug report
accordingly.
Two weeks ago I finally applied the remaining patch
(http://bugzilla.kernel.org/attachment.cgi?id=18427) and rebuilt the kernel
according to the instructions in
** Package changed: nfs-utils (Ubuntu) = linux-meta (Ubuntu)
--
5-minute delay in nfs4 client after suspend/resume
https://bugs.launchpad.net/bugs/379385
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I started digging into the code and found that this is a kernel issue, not a
nfs-common issue. And it is fixed in kernel 2.6.28-13. That is, the first patch
mentioned above:
http://bugzilla.kernel.org/attachment.cgi?id=18426
is included in that kernel, and it has had a good effect. I'm closing
Fix was released before anybody started working on this report.
** Changed in: nfs-utils (Ubuntu)
Status: New = Fix Released
--
5-minute delay in nfs4 client after suspend/resume
https://bugs.launchpad.net/bugs/379385
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: nfs-common
I have two computers, both with a fully-updated Jaunty (09.04). One
working as nfs4 server, the other as client. Software version is
1:1.1.4-1ubuntu1 for both of the packages nfs-common and nfs-kernel-
server (the client does not have
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27050301/Dependencies.txt
** Description changed:
Binary package hint: nfs-common
I have two computers, both with a fully-updated Jaunty (09.04). One
working as nfs4 server, the other as client. Software version is
No, this is not an issue for me any more. I made a fresh install with
07.10. Moreover, I did this fresh installation on the same partition
that contained the remains of the crashed upgrade, and thus I no longer
have any additional information on the problem. I suppose it's no use to
chase this
** Attachment added: apt.log
http://librarian.launchpad.net/7593563/apt.log
--
Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
https://bugs.launchpad.net/bugs/113682
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: main.log
http://librarian.launchpad.net/7593565/main.log
--
Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
https://bugs.launchpad.net/bugs/113682
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
By the way, bugs 108803 and 108272 look similar.
--
Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
https://bugs.launchpad.net/bugs/113682
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: update-manager
Kubuntu upgrade from 06.10 (Edgy) to 07.04 (Feisty) stopped while
Preparing samba (this was the status description in the main
installation window). A dialog popped up with the message:
Could not install
Public bug reported:
I Installed Kubuntu 6.10 on a system with a Samsung SyncMaster 214T
flatpanel display, and found that this particular display was not auto-
detected.
Launching System Settings, selecting Monitor Display, then
Hardware I did not find this particular display in the list
Thanks for a very fast reply. I'm attaching the requested Xorg.0.log and
including the results from xresprobe below. The freq part matches
exactly the numbers that Detect Monitor finds. The rest makes me start
thinking if the 214T is at fault?
[EMAIL PROTECTED]:/var/log# xresprobe i810
id:
I see the problem with the automatic detection. However, there is one
improvement that maybe could be done: The 214T could be added to the monitor
list in the manual configuration GUI. Then anyone would be able to correct the
configuration easily (more easily at least). I have absolutely no
Public bug reported:
I Installed Kubuntu 6.10 on a system with a Samsung SyncMaster 214T
flatpanel display, and found that this particular display was not auto-
detected.
Launching System Settings, selecting Monitor Display, then
Hardware I did not find this particular display in the list
39 matches
Mail list logo
