[Bug 466948] Re: keyboard shortcuts disable requires logout/login
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/466948 Title: keyboard shortcuts disable requires logout/login -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 436230] Re: thinkpad x40: backlight does not work after suspend
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 work after suspend https://bugs.launchpad.net/bugs/436230 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 505029] Re: Keyboard repeat rate is often reset
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 program, which says it does something (Typematic Rate set to 10,9 cps (delay = 250 ms)) but it makes no difference to the keyboard. Hardware: Dell Precision T3400 with a Dell wired keyboard, connected via USB through the monitor. Based on the previous comments to this bug report, I made a few tests, and conclude that the problem is triggered whenever I turn off the monitor. This is completely consistent with the fact that I see the problem every morning and not otherwise. The computer is running during the night because I need to access it remotedly. It is not suspended, hibernated or such. So although I now know how to work around the issue, would it be possible to reinitialize the keyboard (tell it about the desired repeat rate) whenever it is powered up? -- Keyboard repeat rate is often reset https://bugs.launchpad.net/bugs/505029 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
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 application/vnd.cups-postscript 100 foomatic-rip My conclusion: Fix verified. I suppose someone else will change the bug status appropriately, if appropriate :-) Thanks for the support! -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477711] Re: nfs: server not responding, timed out, then nfs4 locks up
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 into this trap (now I'm a bit provocative, I know)! The best would be to keep this bug report open until more data can be gathered which might lead to a proper fix. A fortunate side effect of the present bug report is that it serves as documentation of a workaround for others that just need to get the thing to work. That's part of the reason I wrote a descriptive title. On a side note, I realize that there may be an underlying problem in the TCP implementation, but NFS4 should not block completely even in that case. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
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 /etc/cups/lpoptions ls: cannot access /etc/cups/lpoptions: No such file or directory But see this: a...@kapowdk-ac:~$ nc -w1 xerox7245.kapow.dk 9100 /tmp/foo-out.ps %%[ Error: ioerror; OffendingCommand: flushfile ]%% %%[ Flushing: rest of job (to end-of-file) will be ignored ]%% If I read the PostScript correctly, flushfile is called only from the EndPage (re)definition in line 4120. Might the printer's PostScript implementation be missing something? -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
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 - Filter application/vnd.cups-command 0 commandtops Filter application/vnd.cups-postscript 0 - That is, the same stuff as for the HP printer I tried, and which I put into printers.conf as a workaround before reporting the problem. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
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 foomatic-rip by renaming it and replacing it with a small script: #!/bin/bash echo $* /tmp/foo.log env /tmp/foo.log tee /tmp/foo-in.ps | /usr/bin/foomatic-rip-orig $@ | tee /tmp/foo-out.ps See the attached foo.log, foo-in.ps and foo-out.ps Interestingly, while viewing with gs foo-in.ps is very quick and opens a reasonably sized window with the result, doing the same for the foo-out.ps file is a very slow thing and produces very large-size output. ** Attachment added: Execution environment for foomatic-rip http://launchpadlibrarian.net/38746520/foo.log -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] [NEW] Xerox WorkCentre 7245 (7228) prints only first page
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: 1.1.12+git20090826-0ubuntu8 Candidate: 1.1.12+git20090826-0ubuntu8 Version table: *** 1.1.12+git20090826-0ubuntu8 0 500 http://dk.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status I added a Xerox WorkCentre 7245 printer using system-config-printer. A little research revealed that you need to select the 7228 from the list in that case, which is a sister product (e.g. the printed Xerox manual has both numbers on the front page). The printer sort of worked, but it would print only the first page of everything, where I would expect it to print all pages. This was the case no matter which program I printed from (Firefox, OpenOffice, ...) As the Xerox is a PostScript printer, I installed another (HP) PostScript printer for comparison. It worked as expected. As installed, the /etc/cups/printers.conf has for the Xerox printer: Filter application/vnd.cups-raw 0 - Filter application/vnd.cups-postscript 100 foomatic-rip Filter application/vnd.cups-pdf 0 foomatic-rip Filter application/vnd.apple-pdf 25 foomatic-rip while the HP printer has: Filter application/vnd.cups-raw 0 - Filter application/vnd.cups-command 0 commandtops Filter application/vnd.cups-postscript 0 - (Special thanks to etckeeper for keeping record of these details!) As a test, I printed to a PostScript file, then sent it to the printer with lpr -oraw file.ps. That worked. So now I have modified /etc/cups/printers.conf, using the HP printer's Filter lines also for the Xerox printer. This solves my problem, however the bug should be fixed for the benefit of the next guy with a Xerox WorkCentre 7228/7245. ProblemType: Bug Architecture: amd64 CupsErrorLog: Date: Thu Jan 28 08:47:43 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Lpstat: device for HP-LaserJet-P2015-Series: dnssd://HP%20LaserJet%20P2015%20Series%20(255D20)._pdl-datastream._tcp.local/ device for Xerox-WorkCentre-7245: socket://xerox7245.kapow.dk:9100 MachineType: Dell Inc. Precision WorkStation T3400 NonfreeKernelModules: nvidia Package: system-config-printer-gnome 1.1.12+git20090826-0ubuntu8 PackageArchitecture: all Papersize: a4 PpdFiles: Xerox-WorkCentre-7245: Xerox WorkCentre 7228 Foomatic/Postscript HP-LaserJet-P2015-Series: HP LaserJet P2015 Series Postscript (recommended) ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-17-generic root=UUID=2df9c5b6-9dde-4650-8b67-32c69fb5e6ba ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_DK.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic SourcePackage: system-config-printer Uname: Linux 2.6.31-17-generic x86_64 dmi.bios.date: 03/21/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP412 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/21/2008:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T3400 dmi.sys.vendor: Dell Inc. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
** 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: Locale.txt http://launchpadlibrarian.net/38481900/Locale.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/38481901/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/38481902/Lsusb.txt ** Attachment added: PrintingPackages.txt http://launchpadlibrarian.net/38481903/PrintingPackages.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/38481904/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/38481905/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/38481906/ProcModules.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/38481907/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/38481908/UdevLog.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/38481911/XsessionErrors.txt -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
** 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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513690] Re: Xerox WorkCentre 7245 (7228) prints only first page
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477711] Re: nfs: server not responding, timed out, then nfs4 locks up
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 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477711] [NEW] nfs: server not responding, timed out, then nfs4 locks up
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, Nov 4 and Nov 7. It typically happens after the nfs4 client computer goes out of sleep. I understand why sleep may upset the nfs connection, but it clearly recovers most of the time. The computers serving as nfs4 client and server both run a fully updated Jaunty (09.04). Exception: The client is a few security patches behind because I'm running a home-built kernel with the patch mentioned in http://bugzilla.kernel.org/attachment.cgi?id=18427 (comment #19). The problem is that nfs4 locks up so that all accesses to my nfs4 mount point get delayed indefinitely, with no way of interrupting it. syslog from a typical failure is: Nov 3 07:07:41 helle kernel: [13262.273844] WARNING: at kernel/power/main.c:177 suspend_test_finish+0x80/0x90() Nov 3 07:07:41 helle kernel: [13262.273847] Component: resume devices Nov 3 07:07:41 helle kernel: [13262.273851] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat usb_storage i915 drm binfmt_misc bridge stp bnep input_polldev video output nfsd auth_rpcgss exportfs nfs lockd nfs_acl sunrpc ipt_REJECT ipt_LOG xt_limit xt_tcpudp xt_state ipt_addrtype ip6table_filter ip6_tables nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ftp nf_conntrack iptable_filter ip_tables x_tables lp snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device psmouse iTCO_wdt iTCO_vendor_support intel_agp snd ppdev serio_raw agpgart pcspkr soundcore snd_page_alloc parport_pc parport usbhid r8169 mii Nov 3 07:07:41 helle kernel: [13262.273940] Pid: 11870, comm: pm-suspend Tainted: GW 2.6.28.10-nfspatch.2 #1 Nov 3 07:07:41 helle kernel: [13262.273944] Call Trace: Nov 3 07:07:41 helle kernel: [13262.273955] [c0138c00] warn_slowpath+0x60/0x80 Nov 3 07:07:41 helle kernel: [13262.273965] [c015201a] ? down_trylock+0x2a/0x40 Nov 3 07:07:41 helle anacron[12181]: Anacron 2.3 started on 2009-11-03 Nov 3 07:07:41 helle kernel: [13262.273970] [c013925d] ? try_acquire_console_sem+0xd/0x30 Nov 3 07:07:41 helle kernel: [13262.273979] [c02baab0] ? kobject_put+0x20/0x50 Nov 3 07:07:41 helle kernel: [13262.273988] [c04ee341] ? printk+0x18/0x1f Nov 3 07:07:41 helle anacron[12181]: Will run job `cron.daily' in 5 min. Nov 3 07:07:41 helle kernel: [13262.273993] [c01629f0] suspend_test_finish+0x80/0x90 Nov 3 07:07:41 helle anacron[12181]: Jobs will be executed sequentially Nov 3 07:07:41 helle kernel: [13262.273999] [c0162abe] suspend_devices_and_enter+0xbe/0x1c0 Nov 3 07:07:41 helle kernel: [13262.274004] [c04ee341] ? printk+0x18/0x1f Nov 3 07:07:41 helle kernel: [13262.274009] [c0162d24] enter_state+0x134/0x1a0 Nov 3 07:07:41 helle kernel: [13262.274015] [c0162e0d] state_store+0x7d/0xc0 Nov 3 07:07:41 helle kernel: [13262.274019] [c0162d90] ? state_store+0x0/0xc0 Nov 3 07:07:41 helle kernel: [13262.274025] [c02ba984] kobj_attr_store+0x24/0x30 Nov 3 07:07:41 helle kernel: [13262.274031] [c01fe2d2] sysfs_write_file+0x92/0xf0 Nov 3 07:07:41 helle kernel: [13262.274038] [c01b18dc] vfs_write+0x9c/0x170 Nov 3 07:07:41 helle kernel: [13262.274043] [c01fe240] ? sysfs_write_file+0x0/0xf0 Nov 3 07:07:41 helle kernel: [13262.274048] [c01b1a6d] sys_write+0x3d/0x70 Nov 3 07:07:41 helle kernel: [13262.274055] [c0103eeb] sysenter_do_call+0x12/0x2f Nov 3 07:07:41 helle kernel: [13262.274059] ---[ end trace 208e2da6917d6433 ]--- Nov 3 07:07:41 helle kernel: [13262.274172] PM: Finishing wakeup. Nov 3 07:07:41 helle kernel: [13262.274177] Restarting tasks ... done. Nov 3 07:07:41 helle acpid: client 3045[0:0] has disconnected Nov 3 07:07:41 helle acpid: client connected from 3045[0:0] Nov 3 07:07:41 helle NetworkManager: info Waking up... Nov 3 07:07:41 helle NetworkManager: info (ttyS0): ignoring due to lack of mobile broadband capabilties Nov 3 07:07:41 helle NetworkManager: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Nov 3 07:07:41 helle NetworkManager: info Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889) Nov 3 07:10:01 helle /USR/SBIN/CRON[12341]: (root) CMD ([ -x /usr/sbin/update-motd ] /usr/sbin/update-motd 2/dev/null) Nov 3 07:10:44 helle kernel: [13445.292025] nfs: server bbb not responding, timed out Nov 3 07:10:44 helle kernel: [13445.292052] Error: state recovery failed on NFSv4 server bbb with error 5 Nov 3 07:12:44 helle kernel: [13565.292027] nfs: server bbb not responding, still trying After 46 minutes I may get: Nov 3 07:58:46 helle kernel: [16327.748034] nfs: server bbb not responding, still
[Bug 477711] Re: nfs: server not responding, timed out, then nfs4 locks up
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477711] Re: nfs: server not responding, timed out, then nfs4 locks up
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477711] Re: nfs: server not responding, timed out, then nfs4 locks up
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 477711] Re: nfs: server not responding, timed out, then nfs4 locks up
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379385] Re: 5-minute delay in nfs4 client after suspend/resume
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379385] Re: 5-minute delay in nfs4 client after suspend/resume
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 http://www.howtoforge.com/kernel_compilation_ubuntu (but be sure to read http://ubuntuforums.org/showthread.php?t=417138 first). I have not seen the problem in the two weeks since that. The mentioned patch really ought to go into the distributed kernel! -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379385] Re: 5-minute delay in nfs4 client after suspend/resume
** 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379385] Re: 5-minute delay in nfs4 client after suspend/resume
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 the issue. Thanks, folks! -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379385] Re: 5-minute delay in nfs4 client after suspend/resume
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 Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379385] [NEW] 5-minute delay in nfs4 client after suspend/resume
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 nfs-kernel-server of course). The home directory of the (primary) user on the client is mounted from the nfs4 server. The client suspends to ram when idle. Very often (not every time) when it resumes, the machine is completely unresponsive. It is possible to log in as another user, but this locks up also if you try to access files within the primary users's home directory. It takes exactly 5 minutes for the client to recover. From then on everything works perfectly. dmesg on the client reports: [75482.166199] PM: Finishing wakeup. [75482.166204] Restarting tasks ... done. [75662.192034] nfs: server bbb not responding, still trying [75782.196210] nfs: server bbb not responding, timed out [75782.196275] nfs: server bbb not responding, timed out [75782.200537] nfs: server bbb OK You see the delay of 5 minutes here (to the second). On the server side, logs contain no useful data, but WireShark reports (sorry for the transcript, but my trace contains passwords etc.): Time 77: Client sends nfs4 COMPOUND call to server Time 77: Server responds with a TCP RST TIme 377: Client re-opens socket (the usual SYN, SYN+ACK, ACK sequence) Time 377: Client repeats the same nfs4 COMPOUND call I propose that this is the same problem that is discussed in: http://linux-nfs.org/pipermail/nfsv4/2008-December/009616.html http://marc.info/?l=linux-nfsm=122477622004792w=2 http://bugzilla.kernel.org/show_bug.cgi?id=11154 ... and that the fix might be found in the following two patches attached to the last page: http://bugzilla.kernel.org/attachment.cgi?id=18426 (comment #18) http://bugzilla.kernel.org/attachment.cgi?id=18427 (comment #19) If I'm guessing correctly, it would be nice if this could go into the repositories. I have never built from sources, and I'm kind of lazy (sorry, folks!) ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: nfs-common 1:1.1.4-1ubuntu1 ProcEnviron: LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: nfs-utils Uname: Linux 2.6.28-11-generic i686 ** Affects: nfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: i386 nfs4 suspend -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 379385] Re: 5-minute delay in nfs4 client after suspend/resume
** 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 1:1.1.4-1ubuntu1 for both of the packages nfs-common and nfs-kernel- server (the client does not have nfs-kernel-server of course). The home directory of the (primary) user on the client is mounted from the nfs4 server. The client suspends to ram when idle. Very often (not every time) when it resumes, the machine is completely unresponsive. It is possible to log in as another user, but this locks up also if you try to access files within the primary users's home directory. It takes exactly 5 minutes for the client to recover. From then on everything works perfectly. - dmesg on the clients reports: + dmesg on the client reports: [75482.166199] PM: Finishing wakeup. [75482.166204] Restarting tasks ... done. [75662.192034] nfs: server bbb not responding, still trying [75782.196210] nfs: server bbb not responding, timed out [75782.196275] nfs: server bbb not responding, timed out [75782.200537] nfs: server bbb OK You see the delay of 5 minutes here (to the second). On the server side, logs contain no useful data, but WireShark reports (sorry for the transcript, but my trace contains passwords etc.): Time 77: Client sends nfs4 COMPOUND call to server Time 77: Server responds with a TCP RST TIme 377: Client re-opens socket (the usual SYN, SYN+ACK, ACK sequence) Time 377: Client repeats the same nfs4 COMPOUND call I propose that this is the same problem that is discussed in: http://linux-nfs.org/pipermail/nfsv4/2008-December/009616.html http://marc.info/?l=linux-nfsm=122477622004792w=2 http://bugzilla.kernel.org/show_bug.cgi?id=11154 ... and that the fix might be found in the following two patches attached to the last page: http://bugzilla.kernel.org/attachment.cgi?id=18426 (comment #18) http://bugzilla.kernel.org/attachment.cgi?id=18427 (comment #19) If I'm guessing correctly, it would be nice if this could go into the repositories. I have never built from sources, and I'm kind of lazy (sorry, folks!) - BTW this - ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: nfs-common 1:1.1.4-1ubuntu1 ProcEnviron: LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: nfs-utils Uname: Linux 2.6.28-11-generic i686 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113682] Re: Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
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 particular rabbit any more. -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113682] Re: Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
** 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113682] Re: Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113682] Re: Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 113682] Upgrade Edgy-Feisty failed on samba_3.0.24-2ubuntu1_i386.deb
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 '/var/cache/apt/archives/samba_3.0.24-2ubuntu1_i386.deb' The upgrade aborts now. Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport. subprocess new post-removal script returned error exit status 134 I could now click either Report bug or Close. I was reluctant to start additional processing on a likely half-installed system and chose Close. Now the installation process CONTINUED! However it very quickly got stuck (no progress for a long time). This time the status description was Preparing to configure libadns1. I took some screen dumps of all this before closing the window forcefully and thus stopping the upgrade. Not surprisingly, the system could not be stopped in the usual way, and couldn't later be started. I had some Linux exercise while rolling in my backup on a separate partition... This means I have the damaged system available if you need further information. I will attach the required files from /var/log/dist-upgrade in a second. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: Unconfirmed -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84588] Installer does not detect Samsung SyncMaster 214T
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 either, and it couldn't be auto-detected (that's consistent at least). Detect monitor gives me a Plug'n'play display which gives me a 65 Hz refresh - which causes the 214T to complain every time it is turned on, because this is not the optimal refresh rate. It wants 60 Hz. I finally selected in the list under Generic a Flat panel 1600x1200 and now it's working nicely. By the way I notice that the SyncMaster 244T too is missing in the selection list of displays. Maybe the list is just a bit old? ** Affects: kde-guidance (Ubuntu) Importance: Wishlist Status: Confirmed -- Installer does not detect Samsung SyncMaster 214T https://launchpad.net/bugs/84588 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 84588] Re: Installer does not detect Samsung SyncMaster 214T
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: SyncMaster res: 1600x1200 1280x1024 1280x960 1152x864 1024x768 832x624 800x600 720x400 640x480 freq: 30-81 56-75 disptype: crt ** Attachment added: Xorg.0.log in full http://librarian.launchpad.net/6404178/Xorg.0.log -- Installer does not detect Samsung SyncMaster 214T https://launchpad.net/bugs/84588 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84588] Re: Installer does not detect Samsung SyncMaster 214T
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 idea where that list is found or who might be responsible for maintaining it? (Now I'm thinking of the next guy with a Samsung - part of my reason for installing Kubuntu was to evaluate its usefulness for the less technically minded.) But kudos for an extremely fast response! Thanks for the help. -- Installer does not detect Samsung SyncMaster 214T https://launchpad.net/bugs/84588 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84588] Installer does not detect Samsung SyncMaster 214T
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 either, and it couldn't be auto-detected (that's consistent at least). Detect monitor gives me a Plug'n'play display which gives me a 65 Hz refresh - which causes the 214T to complain every time it is turned on, because this is not the optimal refresh rate. It wants 60 Hz. I finally selected in the list under Generic a Flat panel 1600x1200 and now it's working nicely. By the way I notice that the SyncMaster 244T too is missing in the selection list of displays. Maybe the list is just a bit old? ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Installer does not detect Samsung SyncMaster 214T https://launchpad.net/bugs/84588 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
