[Bug 1291459] Re: ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4 card
Not seeing the issue on linux-image-generic-lts-raring v3.8.0.37.37 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291459 Title: ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4 card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1291459] Re: ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4 card
I see the same firmware loading issue. I assumed the problem was in tuner_xc2028, as I don't see any related messages in dmesg after the firmware blob fails to load: Mar 26 22:03:20 localhost kernel: [ 11.567369] xc2028 0-0061: Loading firmware for type=BASE F8MHZ (3), id 0 000. Mar 26 22:03:20 localhost kernel: [ 11.576247] cxusb: i2c wr: len=64 is too big! Mar 26 22:03:20 localhost kernel: [ 11.576247] Mar 26 22:03:20 localhost kernel: [ 11.576253] xc2028 0-0061: i2c output error: rc = -95 (should be 64) Mar 26 22:03:20 localhost kernel: [ 11.576255] xc2028 0-0061: -95 returned from send Mar 26 22:03:20 localhost kernel: [ 11.576258] xc2028 0-0061: Error -22 while loading base firmware Mar 26 22:03:20 localhost kernel: [ 11.648380] xc2028 0-0061: Loading firmware for type=BASE F8MHZ (3), id . This is from the linux-image-generic-lts-saucy v3.11.0.18.17 running on a Precise LTS system (amd64). cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04.4 LTS" At the risk of starting a wild goose chase this _might_ be related to: http://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=e9812be28ce0f4e4bf5586f1a542551c8fc80ffa which has been merged into the saucy kernel, as far as I can tell, http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-saucy.git;a=commit;h=d1ba3eb8a51b2ebb09bdfd7277fde2c8ff679f87 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1291459 Title: ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4 card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1291459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 506367] Re: streamtuner crashed with SIGSEGV (Lucid a1)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION="Ubuntu 10.04.3 LTS"
$ version 0.99.99-15ubuntu2
$ strace streamtuner
click on 'local' tab and the last part of the strace output is:
read(3,
"\34\0\317\4[\0\340\5\36\1\0\0W\371\227?\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
4096) = 256
writev(3, [{"\22\0\30\0[\0\340\5(\0\0\0)\0\0\0
\0\0\0\22\0\0\0\20\2\0\0\0\0\0\0"..., 10420}, {NULL, 0}, {"", 0}], 3) = 10420
read(3, 0x9053b40, 4096)= -1 EAGAIN (Resource temporarily
unavailable)
futex(0x903f290, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x903f290, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x903f290, FUTEX_WAIT_PRIVATE, 2, NULL) = 0
futex(0x903f290, FUTEX_WAIT_PRIVATE, 2, NULL
+++ killed by SIGSEGV +++
Segmentation fault
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/506367
Title:
streamtuner crashed with SIGSEGV (Lucid a1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/streamtuner/+bug/506367/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665168] Re: Rhythmbox fails to connect to DAAP share
I see this in 0.12.8-0ubuntu7 (lucid version, i386).
The server is mt-daap (0.9~r1696.dfsg-15build1) running on lucid i386 also.
iTunes on a mac sees it just fine and plays songs fine.
I am able to play files from the server with VLC and the http: access
method.
I don't see the DAAP server automatically. As it happens there are two on my
network but
one has no content. As above, I start rhythmbox, go to Music->Connect to DAAP
Share... in the menu. Enter a hostname and port number in the syntax specified
in the dialog. Nothing further happens.
With tcpdump I can see the MDNS requests going out and responses coming back.
But there are no further queries, for eg /server-info.
Stracing shows the queries appear to be getting received but I can't see
any further attempts to connect to the server.
recvfrom(25, "M-SEARCH * HTTP/1.1\r\nHOST: 239.2"..., 8192, 0,
{sa_family=AF_INET, sin_port=htons(58188), sin_addr=inet_addr("192.168.1.6")},
[16]) = 94
gettimeofday({1314074035, 21569}, NULL) = 0
gettimeofday({1314074035, 21744}, NULL) = 0
recvfrom(25, "M-SEARCH * HTTP/1.1\r\nHOST: 239.2"..., 8192, 0,
{sa_family=AF_INET, sin_port=htons(58188), sin_addr=inet_addr("192.168.13.6")},
[16]) = 94
gettimeofday({1314074035, 23090}, NULL) = 0
gettimeofday({1314074035, 23372}, NULL) = 0
recvfrom(25, 0xa7e6304, 8192, 0, 0xbfba613c, 0xbfba6138) = -1 EAGAIN (Resource
temporarily unavailable)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665168
Title:
Rhythmbox fails to connect to DAAP share
To manage notifications about this bug go to:
https://bugs.launchpad.net/rhythmbox/+bug/665168/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665168] Re: Rhythmbox fails to connect to DAAP share
** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665168 Title: Rhythmbox fails to connect to DAAP share To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/665168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824245] Re: tcsh: missing /etc/csh files
closing. got the paths wrong. nevermind. ** Changed in: tcsh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824245 Title: tcsh: missing /etc/csh files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcsh/+bug/824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 824245] [NEW] tcsh: missing /etc/csh files
Public bug reported: The immediate issue I have is: I have my login shell set to tcsh. However .cshrc is not getting executed on login via gdm. However on investigating I could not find the expected system-wide cshrc and login files. dpkg claims they are there but I can't see them (I did a remove (no --purge) & install cycle). I can't see anything in the package pre/post scripts that would remove these files. # dpkg -L tcsh |grep etc /etc /etc/csh /etc/csh/login.d /etc/csh.cshrc /etc/csh.login /etc/csh.logout /etc/complete.tcsh % ls -al /etc/csh drwxr-xr-x 3 root root 4096 2011-08-10 17:20 . drwxr-xr-x 133 root root 12288 2011-08-10 17:20 .. drwxr-xr-x 2 root root 4096 2010-03-22 17:07 login.d # lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 # apt-cache policy tcsh tcsh: Installed: 6.17.00-3 Candidate: 6.17.00-3 Version table: *** 6.17.00-3 0 500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages 100 /var/lib/dpkg/status ** Affects: tcsh (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/824245 Title: tcsh: missing /etc/csh files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcsh/+bug/824245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
No further problems here, so it seems it is fixed for me. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690798 Title: arduino USB serial device breaks on lucid kernel upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
After watching & waiting a bit, I've seen no more errors of the type I described in #16. I've rebooted and done a replugging test or two and it's all been solid. Coincidentally one of my 1-wire sensors died but I got quite different error messages from that and it seems clear that the ftdi_sio module was not at fault. I'll give it a few more days and let you know if I see a recurrence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690798 Title: arduino USB serial device breaks on lucid kernel upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
Hm. The changelog in the package I installed (linux- image-2.6.32-28-generic 2.6.32-28.55) shows this: linux (2.6.32-28.50) lucid-proposed; urgency=low [ Tim Gardner ] ... [ Upstream Kernel Changes ] ... * USB: ftdi_sio: revert "USB: ftdi_sio: fix DTR/RTS line modes" - LP: #688669 and does not mention this bug at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690798 Title: arduino USB serial device breaks on lucid kernel upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
oops - re #17 - the trace attached there is for 2.6.32-22-generic, well before this whole mess started. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690798 Title: arduino USB serial device breaks on lucid kernel upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
strace on 2.6.32-28-generic with device working ** Attachment added: "digitemp.strace.2.6.32-28.working" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/690798/+attachment/1814331/+files/digitemp.strace.2.6.32-28.working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690798 Title: arduino USB serial device breaks on lucid kernel upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
strace on 2.6.32-28-generic with device not working ** Attachment added: "digitemp.strace.2.6.32-28" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/690798/+attachment/1814321/+files/digitemp.strace.2.6.32-28 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690798 Title: arduino USB serial device breaks on lucid kernel upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
strace of digitemp to illustrate the behaviour: * on 2.6.32-26-generic with 55b5b5448771f964776a716227afd3ddef2c860e reverted ** Attachment added: "strace.digitemp.works.2.6.32-22-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/690798/+attachment/1814320/+files/strace.digitemp.works.2.6.32-22-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/690798 Title: arduino USB serial device breaks on lucid kernel upgrade -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 690798] Re: arduino USB serial device breaks on lucid kernel upgrade
Unfortunately the fix seems to be incomplete for me. $ cat /proc/version_signature Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12 $ uname -a Linux ubuntu 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01 UTC 2011 i686 GNU/Linux Reverting the commit 55b5b5448771f964776a716227afd3ddef2c860e does help, but it appears that another regression has appeared in the meantime. After about 18h I start getting this error from digitemp (I am calling it from cron once every 15min) Error 5: DS2480B Adapter Not Detected Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Once the system gets into this state, it persists until reboot. I do not see this problem with 2.6.32-26-generic, patched so that 55b5b5448771f964776a716227afd3ddef2c860e is reverted. lsusb still sees the device: $ lsusb Bus 005 Device 003: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard Bus 002 Device 002: ID 03f0:3611 Hewlett-Packard PSC 2410 PhotoSmart Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub $ sudo lsusb -v -d 0403:6001 Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0403 Future Technology Devices International, Ltd idProduct 0x6001 FT232 USB-Serial (UART) IC bcdDevice6.00 iManufacturer 1 FTDI iProduct2 FT232R USB UART iSerial 3 A900a3DX bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 90mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 255 Vendor Specific Class bInterfaceSubClass255 Vendor Specific Subclass bInterfaceProtocol255 Vendor Specific Protocol iInterface 2 FT232R USB UART Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 0 Device Status: 0x (Bus Powered) The device node seems to have normal permissions $ ls -l /dev/ttyUSB0 0 crw-rw 1 root dialout 188, 0 2011-01-29 20:50 /dev/ttyUSB0 stracing with the device in this state shows digitemp (3.5.0ds1-1ubuntu1) trying to select() a file descriptor (with the same arguments as in the working case,) and timing out. straces for both kernels are attached. If I unplug and replug the device I see this in syslog: [71833.368048] usb 5-1: USB disconnect, address 2 [71833.368231] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [71833.368252] ftdi_sio 5-1:1.0: device disconnected [71837.328016] usb 5-1: new full speed USB device using uhci_hcd and address 4 [71837.526685] usb 5-1: configuration #1 chosen from 1 choice [71837.534634] ftdi_sio 5-1:1.0: FTDI USB Serial Device converter detected [71837.534671] usb 5-1: Detected FT232RL [71837.534674] usb 5-1: Number of endpoints 2 [71837.534676] usb 5-1: Endpoint 1 MaxPacketSize 64 [71837.534679] usb 5-1: Endpoint 2 MaxPacketSize 64 [71837.534681] usb 5-1: Setting MaxPacketSize 64 [71837.535923] usb 5-1: FTDI USB Serial Device converter now attached to ttyUSB0 and the device is working again. -- You received this
[Bug 215802] Re: rtl8187 link quality poor
With the patched kernel iwconfig reports a bit rate of 36Mbit/s. Non- optimal tests (rsync over ssh within the wireless LAN) showed a real throughput of at least 2.7Mbit/s, ie well over 1Mbit/s. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/215802 Title: rtl8187 link quality poor -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 215802] Re: rtl8187 link quality poor
I tested this device: $ sudo lsusb -d 0846:4260 Bus 001 Device 004: ID 0846:4260 NetGear, Inc. WG111(v3) 54 Mbps Wireless [RealTek RTL8187B] Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize064 idVendor 0x0846 NetGear, Inc. idProduct 0x4260 WG111(v3) 54 Mbps Wireless [RealTek RTL8187B] bcdDevice2.00 iManufacturer 1 Manufacturer_NETGEAR iProduct2 NETGEAR WG111v3 iSerial 3 bNumConfigurations 1 against: * ubuntu 2.6.32-26-generic * http://people.canonical.com/~sforshee/lp215802/linux-image-2.6.32-28-generic_2.6.32-28.55+LP215802v1_i386.deb (md5sum 3578ab4e4757ea2c5f53b3d43fa75c78). With 2.6.32-26-generic, the device fell over after about an hour, with Jan 15 00:25:14 ubuntu kernel: [279647.500012] No probe response from AP after 500ms, disconnecting. The signal strength was pretty good, -38db, link quality 70/70. With the test kernel, the device has been solidly up for nearly 24h. Signal strength similar, -38db +/- a few db, quality 65/70. Looks like this fixes it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/215802 Title: rtl8187 link quality poor -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 655868] Re: FTDI based USB to serial adapter no longer works
** Tags added: patch ** Summary changed: - FTDI based USB to serial adapter no longer works + [lucid regression] FTDI based USB to serial adapter no longer works -- [lucid regression] FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 655868] Re: FTDI based USB to serial adapter no longer works
I rebuilt tag Ubuntu-2.6.32-25.43 (3db80d04abba8cf8ab670ddd6435de1ad8287c39) with 55b5b5448771f964776a716227afd3ddef2c860e reverted. My device now works correctly. Yay. -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 655868] Re: FTDI based USB to serial adapter no longer works
The change I bisected to (55b5b5448771f964776a716227afd3ddef2c860e) is 6a1a82df91fa0eb1cc76069a9efe5714d087eccd from upstream. That commit was reverted recently: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=677aeafe19e88c282af74564048243ccabb1c590;hp=1f8dd0154e09220be346819b85d195c791bb0f0b Please could you also revert it in the next release of 2.6.32. I've added patch-accepted-upstream because of this, is that the correct thing to do? ** Tags added: patch-accepted-upstream -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 650731] Re: Auto Update to Linux 2.6.32.25.27 broke Digitemp
I am seeing exactly the same issue, on i386. I have the same version of digitemp, 3.5.0ds1-1. I found a kernel commit which I think causes this, see LP#655868. It's unclear if the kernel was wrong before and got fixed (so digitemp needs to be changed too) or if the kernel change was wrong somehow. These two bugs may be the same issue. -- Auto Update to Linux 2.6.32.25.27 broke Digitemp https://bugs.launchpad.net/bugs/650731 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 655868] Re: FTDI based USB to serial adapter no longer works
See also LP#650731 -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 215802] Re: rtl8187 link quality poor
I think the patch is discussed here: https://patchwork.kernel.org/patch/139191/ and http://www.spinics.net/lists/linux-wireless/msg58213.html See also later discussion of a further series of patches for this hardware http://www.spinics.net/lists/linux-wireless/msg58361.html -- rtl8187 link quality poor https://bugs.launchpad.net/bugs/215802 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 655868] Re: FTDI based USB to serial adapter no longer works
I've bisected this, down to this commit. What now? git bisect bad b81cce9f4a8ebd3332063d4cda1b87384d5e33fd Bisecting: 0 revisions left to test after this (roughly 0 steps) [55b5b5448771f964776a716227afd3ddef2c860e] USB: ftdi_sio: fix DTR/RTS line modes ** Tags added: i386 ** Tags removed: needs-upstream-testing -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 669886] [NEW] KernelCompile - incorrect instructions for usage of AUTOBUILD
Public bug reported: Binary package hint: ubuntu-docs This is a report about help.ubuntu.com/community/Kernel/Compile. I didn't just dive in and change it because I wanted to check I wasn't making things worse. If you think I'm right let me know & I'll go fix the page. I think the information on this page regarding building ubuntu kernels from the ubuntu git repository has some errors. I may be doing some thing wrong but here is what I observe. I want to build a checkout somewhere between two tags, eg revision 47309c6a6af8cce3586c735788fc978bbcd7249f. Setting the AUTOBUILD variable is supposed to make the build process append a string to the ABI number, instead of packages named like linux-image-2.6.32-25-generic I should get linux-image-2.6.32-25-47349f-generic. To make this happen I have to run the build like this: fakeroot debian/rules clean AUTOBUILD=1 fakeroot debian/rules binary-generic AUTOBUILD=1 Doing it as described in the page fakeroot debian/rules clean AUTOBUILD=1 fakeroot debian/rules binary-generic does not work, for two reasons. 1. if AUTOBUILD is not set when you run debian/rules clean, the ABI number is not given the extra suffix when debian/control is created. So the kernel build goes ahead but the packaging step fails with an error like this: dpkg-gencontrol: error: package linux-image-2.6.32-24-47349f-generic not in control info 2. I find that placing the AUTOBUILD=1 before the 'fakeroot' does not work, neither this way: AUTOBUILD=1 fakeroot debian/rules ... nor this way export AUTOBUILD=1 ; fakeroot debian/rules ... Doing it with AUTOBUILD=1 given after the makefile name (debian/rules) does work. To reproduce: * check out the kernel git as per https://wiki.ubuntu.com/KernelTeam/KernelGitGuide * run the 'printenv' target of debian/rules with AUTOBUILD set or not set. Here are my results: $ git remote -v origin git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git (fetch) origin git://kernel.ubuntu.com/ubuntu/ubuntu-lucid.git (push) $ git show commit 47309c6a6af8cce3586c735788fc978bbcd7249f ... $ echo $SHELL /bin/bash $ fakeroot debian/rules printenv|grep abinum abinum= 25 $ AUTOBUILD=1 fakeroot debian/rules printenv|grep abinum abinum= 25 $ fakeroot debian/rules printenv AUTOBUILD=1 |grep abinum abinum= 25-47349f $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION="Ubuntu 10.04.1 LTS" ** Affects: ubuntu-docs (Ubuntu) Importance: Undecided Status: New -- KernelCompile - incorrect instructions for usage of AUTOBUILD https://bugs.launchpad.net/bugs/669886 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 655868] Re: FTDI based USB to serial adapter no longer works
Further checking. Below is the output of cat /proc/version_signature' and whether the device works: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 OK Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 OK Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 BAD These are all i386 kernels. -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 655868] Re: FTDI based USB to serial adapter no longer works
A bit of eyeball comparison of the repository for the two kernels suggests two commits that might be at fault - just because the changes occur in the right time frame, it's hard to see why they could cause the problem. http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- lucid.git;a=commitdiff;h=47309c6a6af8cce3586c735788fc978bbcd7249f http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- lucid.git;a=commitdiff;h=55b5b5448771f964776a716227afd3ddef2c860e Comparison was between http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=history;f=drivers/usb/serial;hb=9b670926f42419456004af7527e0a3dfa85453f2 and http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=tree;f=drivers/usb/serial;hb=7fd5c4f3ed5ad63d8b8511bfc90afa0792bc68a1 -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 369005] Re: ath5k : disconnection / slow network - "unsupported jumbo" error
PS. this host is running 'lucid'. -- ath5k : disconnection / slow network - "unsupported jumbo" error https://bugs.launchpad.net/bugs/369005 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 369005] Re: ath5k : disconnection / slow network - "unsupported jumbo" error
I'm still seeing occasional "unsupported jumbo" messages, but the card does appear to work fairly reliably, I have not seen it fall over in days. Thanks Maxim. I haven't made speed tests but it's not irritatingly slow. Not seeing any "noise floor" messages. $ uptime 21:17:49 up 2 days, 11:48, 7 users, load average: 0.04, 0.15, 0.15 $ dmesg | grep jumbo [37027.685432] ath5k phy0: unsupported jumbo [38462.863102] ath5k phy0: unsupported jumbo [44390.762941] ath5k phy0: unsupported jumbo [49163.566162] ath5k phy0: unsupported jumbo [72370.910940] ath5k phy0: unsupported jumbo [76083.488713] ath5k phy0: unsupported jumbo [168572.002078] ath5k phy0: unsupported jumbo [192528.656123] ath5k phy0: unsupported jumbo $ uname -a Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux Note that this kernel doesn't have PCIEASPM enabled $ grep PCIEASPM /boot/config-2.6.32-25-generic # CONFIG_PCIEASPM is not set $ lspci -knn ... 04:02.0 Ethernet controller [0200]: Atheros Communications Inc. AR5007G Wireless Network Adapter [168c:001d] (rev 01) Kernel driver in use: ath5k Kernel modules: ath5k $ sudo lspci -vvv ... 04:02.0 Ethernet controller: Atheros Communications Inc. AR5007G Wireless Network Adapter (rev 01) Subsystem: Atheros Communications Inc. Device 2055 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- https://bugs.launchpad.net/bugs/369005 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 655868] Re: FTDI based USB to serial adapter no longer works
** Attachment added: "strace.digitemp.works.2.6.32-22-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655868/+attachment/1681323/+files/strace.digitemp.works.2.6.32-22-generic -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 655868] Re: FTDI based USB to serial adapter no longer works
** Attachment added: "strace.digitemp.2.6.32-25-generic" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655868/+attachment/1681322/+files/strace.digitemp.2.6.32-25-generic -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 655868] Re: FTDI based USB to serial adapter no longer works
I have one of these devices too: $ lsusb Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 03f0:3611 Hewlett-Packard PSC 2410 PhotoSmart Bus 002 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub but I don't see this precise problem. $ dmesg |grep latency [0.540690] pci :00:01.0: setting latency timer to 64 [0.540704] pci :00:1c.0: setting latency timer to 64 [0.540723] pci :00:1c.1: setting latency timer to 64 [0.540730] pci :00:1e.0: setting latency timer to 64 [0.572644] pcieport :00:01.0: setting latency timer to 64 [0.572778] pcieport :00:1c.0: setting latency timer to 64 [0.572926] pcieport :00:1c.1: setting latency timer to 64 [0.642441] ata_piix :00:1f.1: setting latency timer to 64 [0.863461] ata_piix :00:1f.2: setting latency timer to 64 [0.868809] ehci_hcd :00:1d.7: setting latency timer to 64 [0.888362] uhci_hcd :00:1d.0: setting latency timer to 64 [0.888640] uhci_hcd :00:1d.1: setting latency timer to 64 [0.888915] uhci_hcd :00:1d.2: setting latency timer to 64 [0.889195] uhci_hcd :00:1d.3: setting latency timer to 64 [2.984776] tg3 :02:00.0: setting latency timer to 64 [ 15.215316] nouveau :01:00.0: setting latency timer to 64 [ 18.011806] Intel ICH :00:1e.2: setting latency timer to 64 This is with linux-image-2.6.32-25-generic version 2.6.32-25.44 $ uname -a Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux I do have a problem with the device, however. It is not responding properly when queried by /usr/bin/digitemp_DS9097U. Let me know if you want me to file a separate bug, but for now here's the problem: What I used to get was $ digitemp_DS9097U -s /dev/ttyUSB0 -a -q Sep 28 20:01:25 Sensor 0 C: 21.56 F: 70.81 Sep 28 20:01:26 Sensor 1 C: 23.06 F: 73.51 ie there are two one-wire temperature sensors plugged into the usb serial device. Now what I get is: $ digitemp_DS9097U -s /dev/ttyUSB0 -a -q Error 5: DS2480B Adapter Not Detected Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed This works ok on: Linux ubuntu 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux It also worked ok on: Linux ubuntu 2.6.32-24-generic #43-Ubuntu SMP Thu Sep 16 14:17:33 UTC 2010 i686 GNU/Linux It does not work on either of these mainline builds: 2.6.32-0206322109-generic 2.6.36-999.201009261124 The same error seems to be occurring. Shortly I'll attach two straces - one where the digitemp program works (2.6.32-22-generic) and another where it does not (2.6.24-25-generic). -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 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 550010] Re: Unable to transfer digital video content from SONY camcorder to PC
Since Stefan mentioned h/w failure, I changed which port I was using on the firewire card. Interesting results. It appears one of the ports on the card is faulty, while the other is ok. Sorry for the noise. Results appended below in case they are helpful. $ uname -a Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux Plug in camera, switch on. dmesg gives [180490.798143] firewire_ohci: IRQ 00020010 AR_req busReset [180490.798151] firewire_ohci: AR evt_bus_reset, generation 5 [180490.798156] firewire_ohci: IRQ 0002 busReset [180490.798167] firewire_ohci: IRQ 0002 busReset [180490.798176] firewire_ohci: IRQ 0002 busReset [180490.798186] firewire_ohci: IRQ 0002 busReset [180490.798195] firewire_ohci: IRQ 0002 busReset [180490.798205] firewire_ohci: IRQ 0002 busReset [180490.798214] firewire_ohci: IRQ 0002 busReset [180490.798223] firewire_ohci: IRQ 0002 busReset [180490.798233] firewire_ohci: IRQ 0002 busReset [180490.798242] firewire_ohci: IRQ 0002 busReset [180490.798251] firewire_ohci: IRQ 0002 busReset [180490.798261] firewire_ohci: IRQ 0002 busReset [180490.798270] firewire_ohci: IRQ 0002 busReset [180490.798280] firewire_ohci: IRQ 0002 busReset [180490.798289] firewire_ohci: IRQ 0002 busReset [180490.798298] firewire_ohci: IRQ 0002 busReset [180490.798308] firewire_ohci: IRQ 0002 busReset [180490.798317] firewire_ohci: IRQ 0003 selfID busReset [180490.798327] firewire_ohci: IRQ 0002 busReset [180490.798339] firewire_ohci: 2 selfIDs, generation 5, local node ID ffc1 [180490.798344] firewire_ohci: selfID 0: 807f0882, phy 0 [p..] S100 gc=63 +0W Lci [180490.798347] firewire_ohci: selfID 0: 817f8974, phy 1 [-c-] S400 gc=63 +15W Lc [180490.798369] firewire_core: phy config: card 1, new root=ffc1, gap_count=5 [180490.798395] firewire_ohci: IRQ 0001 AT_req [180490.798401] firewire_ohci: AT ack_complete, phy config packet, 01c5 [180490.804019] firewire_ohci: IRQ 00020010 AR_req busReset [180490.804025] firewire_ohci: AR evt_bus_reset, generation 6 [180490.804030] firewire_ohci: IRQ 0002 busReset [180490.804040] firewire_ohci: IRQ 0002 busReset [180490.804049] firewire_ohci: IRQ 0002 busReset [180490.804058] firewire_ohci: IRQ 0002 busReset [180490.804067] firewire_ohci: IRQ 0002 busReset [180490.804077] firewire_ohci: IRQ 0002 busReset [180490.804086] firewire_ohci: IRQ 0002 busReset [180490.804096] firewire_ohci: IRQ 0002 busReset [180490.804105] firewire_ohci: IRQ 0002 busReset [180490.804114] firewire_ohci: IRQ 0002 busReset [180490.804124] firewire_ohci: IRQ 0002 busReset [180490.804133] firewire_ohci: IRQ 0002 busReset [180490.804142] firewire_ohci: IRQ 0002 busReset [180490.804152] firewire_ohci: IRQ 0002 busReset [180490.804161] firewire_ohci: IRQ 0002 busReset [180490.804171] firewire_ohci: IRQ 0002 busReset [180490.804180] firewire_ohci: IRQ 0002 busReset [180490.804190] firewire_ohci: IRQ 0003 selfID busReset [180490.804198] firewire_ohci: IRQ 0002 busReset [180490.804210] firewire_ohci: 2 selfIDs, generation 6, local node ID ffc1 [180490.804214] firewire_ohci: selfID 0: 80450880, phy 0 [p..] S100 gc=5 +0W Lc [180490.804218] firewire_ohci: selfID 0: 81458976, phy 1 [-c-] S400 gc=5 +15W Lci [180491.296035] firewire_ohci: IRQ 0001 AT_req [180491.296045] firewire_ohci: AT spd 0 tl 1d, ffc1 -> ffc0, ack_pending , QR req, f400 [180491.296051] firewire_ohci: IRQ 0020 AR_resp [180491.296059] firewire_ohci: AR spd 0 tl 1d, ffc0 -> ffc1, ack_complete, QR resp = 0404c0e7 [180491.296081] firewire_ohci: IRQ 0001 AT_req [180491.296088] firewire_ohci: AT spd 0 tl 1e, ffc1 -> ffc0, ack_pending , QR req, f404 [180491.296093] firewire_ohci: IRQ 0020 AR_resp [180491.296099] firewire_ohci: AR spd 0 tl 1e, ffc0 -> ffc1, ack_complete, QR resp = 31333934 [180491.296119] firewire_ohci: IRQ 0001 AT_req [180491.296126] firewire_ohci: AT spd 0 tl 1f, ffc1 -> ffc0, ack_pending , QR req, f408 [180491.296131] firewire_ohci: IRQ 0020 AR_resp [180491.296137] firewire_ohci: AR spd 0 tl 1f, ffc0 -> ffc1, ack_complete, QR resp = e0644000 [180491.296156] firewire_ohci: IRQ 0001 AT_req [180491.296162] firewire_ohci: AT spd 0 tl 20, ffc1 -> ffc0, ack_pending , QR req, f40c [180491.296167] firewire_ohci: IRQ 0020 AR_resp [180491.296173] firewire_ohci: AR spd 0 tl 20, ffc0 -> ffc1, ack_complete, QR resp = 08004601 [180491.296192] firewire_ohci: IRQ 0001 AT_req [180491.296198] firewire_ohci: AT spd 0 tl 21, ffc1 -> ffc0, ack_pending , QR req, f410 [180491.296203] firewire_ohci: IRQ 0020 AR_resp [180491.296209] firewire_ohci: AR spd 0 tl 21, ffc0 -> ffc1, ack_complete, QR resp = 04000296 [180491.296228] firewire_ohci: IRQ 0001 AT_req [180491.296234] firewire_ohci: AT spd 0 tl 22, ffc1 -> ffc0, ack_pending , QR req, f414 [180491.298321]
[Bug 550010] Re: Unable to transfer digital video content from SONY camcorder to PC
I tried the debug test above. # uname -a Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux # modprobe -r firewire-ohci # modprobe firewire-ohci debug=-1 dmesg shows [170508.165254] firewire_ohci :04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [170508.244045] firewire_ohci: Added fw-ohci device :04:00.0, OHCI version 1.0 [170508.244057] firewire_ohci: IRQ 00030010 selfID AR_req busReset [170508.244069] firewire_ohci: IRQ 0002 busReset [170508.244082] firewire_ohci: 1 selfIDs, generation 1, local node ID ffc0 [170508.244087] firewire_ohci: selfID 0: 807f8956, phy 0 [---] S400 gc=63 +15W Lci [170508.244105] firewire_ohci: AR evt_bus_reset, generation 1 [170508.744124] firewire_core: created device fw0: GUID 0040630005db, S400 Now plug camera in and switch it on. [170515.212135] firewire_ohci: IRQ 0020 cycle64Seconds [170521.254659] firewire_ohci: IRQ 00020010 AR_req busReset [170521.254667] firewire_ohci: AR evt_bus_reset, generation 2 [170521.254672] firewire_ohci: IRQ 0002 busReset [170521.254682] firewire_ohci: IRQ 0002 busReset [170521.254692] firewire_ohci: IRQ 0002 busReset [170521.254701] firewire_ohci: IRQ 0002 busReset [170521.254710] firewire_ohci: IRQ 0002 busReset [170521.254720] firewire_ohci: IRQ 0002 busReset [170521.254729] firewire_ohci: IRQ 0002 busReset [170521.254739] firewire_ohci: IRQ 0002 busReset [170521.254748] firewire_ohci: IRQ 0002 busReset [170521.254757] firewire_ohci: IRQ 0002 busReset [170521.254767] firewire_ohci: IRQ 0002 busReset [170521.254776] firewire_ohci: IRQ 0002 busReset [170521.254786] firewire_ohci: IRQ 0002 busReset [170521.254795] firewire_ohci: IRQ 0002 busReset [170521.254804] firewire_ohci: IRQ 0002 busReset [170521.254814] firewire_ohci: IRQ 0002 busReset [170521.254823] firewire_ohci: IRQ 0002 busReset [170521.254832] firewire_ohci: IRQ 0002 busReset [170521.254842] firewire_ohci: IRQ 0003 selfID busReset [170521.254851] firewire_ohci: IRQ 0002 busReset [170521.254864] firewire_ohci: 2 selfIDs, generation 2, local node ID ffc1 [170521.254868] firewire_ohci: selfID 0: 807f0882, phy 0 [p..] S100 gc=63 +0W Lci [170521.254871] firewire_ohci: selfID 0: 817f89d4, phy 1 [c--] S400 gc=63 +15W Lc [170521.254894] firewire_core: phy config: card 1, new root=ffc1, gap_count=5 [170521.254914] firewire_ohci: IRQ 0001 AT_req [170521.254920] firewire_ohci: AT ack_complete, phy config packet, 01c5 [170521.258441] firewire_ohci: IRQ 0200 cycleTooLong [170521.258446] firewire_ohci: isochronous cycle too long [170521.258575] firewire_ohci: IRQ 00020010 AR_req busReset [170521.258580] firewire_ohci: AR evt_bus_reset, generation 3 [170521.258585] firewire_ohci: IRQ 0002 busReset [170521.258594] firewire_ohci: IRQ 0002 busReset [170521.258604] firewire_ohci: IRQ 0002 busReset [170521.258613] firewire_ohci: IRQ 0002 busReset [170521.258622] firewire_ohci: IRQ 0002 busReset [170521.258632] firewire_ohci: IRQ 0002 busReset [170521.258641] firewire_ohci: IRQ 0002 busReset [170521.258650] firewire_ohci: IRQ 0002 busReset [170521.258660] firewire_ohci: IRQ 0002 busReset [170521.258669] firewire_ohci: IRQ 0002 busReset [170521.258679] firewire_ohci: IRQ 0002 busReset [170521.258688] firewire_ohci: IRQ 0002 busReset [170521.258697] firewire_ohci: IRQ 0002 busReset [170521.258707] firewire_ohci: IRQ 0002 busReset [170521.258716] firewire_ohci: IRQ 0002 busReset [170521.258726] firewire_ohci: IRQ 0002 busReset [170521.258735] firewire_ohci: IRQ 0002 busReset [170521.258744] firewire_ohci: IRQ 0003 selfID busReset [170521.258754] firewire_ohci: IRQ 0002 busReset [170521.258765] firewire_ohci: 2 selfIDs, generation 3, local node ID ffc1 [170521.258769] firewire_ohci: selfID 0: 80450882, phy 0 [p..] S100 gc=5 +0W Lci [170521.258772] firewire_ohci: selfID 0: 814589d4, phy 1 [c--] S400 gc=5 +15W Lc [170521.259689] firewire_ohci: IRQ 0200 cycleTooLong [170521.259693] firewire_ohci: isochronous cycle too long [170521.259825] firewire_ohci: IRQ 00020010 AR_req busReset [170521.259830] firewire_ohci: AR evt_bus_reset, generation 4 [170521.259835] firewire_ohci: IRQ 0002 busReset [170521.259844] firewire_ohci: IRQ 0002 busReset [170521.259853] firewire_ohci: IRQ 0002 busReset [170521.259862] firewire_ohci: IRQ 0002 busReset ... This continues until generation 255 when the generation counter resets to 0. When I switch off the camera I get ... [176843.613137] firewire_ohci: IRQ 0002 busReset [176843.613147] firewire_ohci: IRQ 0002 busReset [176843.613156] firewire_ohci: IRQ 0002 busReset [176843.613165] firewire_ohci: IRQ 0002 busReset [176843.613175] firewire_ohci: IRQ 0002 busReset [176843.613184] firewire_ohci: IRQ 0003 selfID busReset [176843.613193] firewire_ohci: IRQ 0002 busReset [176843.613205] firewire_ohci:
[Bug 550010] Re: Unable to transfer digital video content from SONY camcorder to PC
I got some feedback that the quirks entries were only added in 2.6.34. I tried copying some data to a disk containing an ext3 filesystem, connected via this firewire card. Worked fine. $ uname -a Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux $ lsmod |grep fire firewire_sbp2 12598 1 firewire_ohci 21002 0 firewire_core 44510 2 firewire_sbp2,firewire_ohci crc_itu_t 1371 1 firewire_core $ dmesg [83666.798542] firewire_core: phy config: card 0, new root=ffc1, gap_count=5 [83677.283987] firewire_core: phy config: card 0, new root=ffc1, gap_count=5 [83679.301412] firewire_core: created device fw1: GUID 0030e108e024901c, S400, 4 config ROM retries [83679.319055] scsi7 : SBP-2 IEEE-1394 [83679.522476] firewire_sbp2: fw1.0: logged in to LUN (0 retries) [83679.524276] scsi 7:0:0:0: Direct-Access ST315003 41AS CC1H PQ: 0 ANSI: 4 [83679.526043] sd 7:0:0:0: Attached scsi generic sg4 type 0 [83679.540810] sd 7:0:0:0: [sdd] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) [83679.541522] sd 7:0:0:0: [sdd] Write Protect is off [83679.541526] sd 7:0:0:0: [sdd] Mode Sense: 11 00 00 00 [83679.542034] sd 7:0:0:0: [sdd] Cache data unavailable [83679.542037] sd 7:0:0:0: [sdd] Assuming drive cache: write through [83679.544946] sd 7:0:0:0: [sdd] Cache data unavailable [83679.544950] sd 7:0:0:0: [sdd] Assuming drive cache: write through [83679.544953] sdd: sdd1 [83679.582131] sd 7:0:0:0: [sdd] Cache data unavailable [83679.582140] sd 7:0:0:0: [sdd] Assuming drive cache: write through [83679.582151] sd 7:0:0:0: [sdd] Attached SCSI disk [83679.894653] kjournald starting. Commit interval 5 seconds [83679.894663] EXT3-fs warning: checktime reached, running e2fsck is recommended [83679.896542] EXT3 FS on sdd1, internal journal [83679.896548] EXT3-fs: mounted filesystem with ordered data mode. -- Unable to transfer digital video content from SONY camcorder to PC https://bugs.launchpad.net/bugs/550010 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 550010] Re: Unable to transfer digital video content from SONY camcorder to PC
Despite the reassurances about bus reset loops in https://ieee1394.wiki.kernel.org/index.php/Release_Notes#Linux_2.6.35 it appears there is some work for upstream to do here. I found http://user.in-berlin.de/~s5r6/linux1394/utils/ and ran the test_cycle_time_v20100125.c utility. This reports: 004063 VIA TECHNOLOGIES, INC. 33231 cycleOffset backwards out of 20357581 samples (1.63e-03) 0 cycleCount backwards (0.00e+00) 0 cycleSeconds backwards (0.00e+00) Which suggests the firewire card I am using needs a quirks entry. Unclear why it worked before, then. Anyway I reported this to linux1394-de...@lists.sourceforge.net. -- Unable to transfer digital video content from SONY camcorder to PC https://bugs.launchpad.net/bugs/550010 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 550010] Re: Unable to transfer digital video content from SONY camcorder to PC
This affects Lucid as well. Since this is a long-term release it would
be nice if we could figure out a way forward for users of firewire
cameras (and Kino).
I have a Sony DSR-PDX10P. In Karmic I was able to use Kino to capture
DV, it worked reasonably well.
I upgraded to Lucid a couple of months ago and tried capturing video
today.
First I tried with the old firewire stack.
$ uname -a
Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686
GNU/Linux
$ cat /etc/modprobe.d/blacklist-firewire.conf
# Select the legacy firewire stack over the new CONFIG_FIREWIRE one.
#blacklist ohci1394
#blacklist sbp2
#blacklist dv1394
#blacklist raw1394
#blacklist video1394
blacklist firewire-ohci
blacklist firewire-sbp2
Probe in the raw1394 module since it doesn't happen automatically for some
reason.
$ modprobe raw1394
In dmesg I get
[ 226.909428] ieee1394: raw1394: /dev/raw1394 device initialized
When I plug the camera in using the firewire interface and then turn it on I
get messages like this spewing in dmesg:
[ 241.256574] ohci1394: fw-host0: isochronous cycle too long
[ 241.260572] ohci1394: fw-host0: isochronous cycle too long
[ 241.264571] ohci1394: fw-host0: isochronous cycle too long
[ 241.268571] ohci1394: fw-host0: isochronous cycle too long
[ 241.269946] ohci1394: fw-host0: isochronous cycle too long
[ 241.272571] ohci1394: fw-host0: isochronous cycle too long
[ 241.273946] ohci1394: fw-host0: isochronous cycle too long
The /dev/raw1394 file has the wrong ownerships as well, group owner is
root, not video.
I hacked /lib/udev/rules.d/50-udev-default.rules, guided by LP300239#4:
KERNEL=="video1394-[0-9]*", NAME="video1394/%n", GROUP="video"
+KERNEL=="raw1394", GROUP="video"
and rebooted.
Try again - plug in firewire cable, turn on camera. Same spew in dmesg.
I started up Kino, and clicked on the 'Capture' icon.
The interface prints two sets of messages, alternating every second or less;
one about being unable to address /dev/raw1394 and the other about not being
able to find an AV/C compliant camera. The spew in dmesg continues.
Second test - I changed to the new stack as per
https://ieee1394.wiki.kernel.org/index.php/Juju_Migration
$ uname -a
Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686
GNU/Linux
$ cat /etc/modprobe.d/blacklist-firewire.conf
# comment these out to use the old stack
blacklist ohci1394
blacklist sbp2
blacklist dv1394
blacklist raw1394
blacklist video1394
# comment these out to use the new stack
#blacklist firewire-ohci
#blacklist firewire-sbp2
Update initramfs
$ sudo update-initramfs -k all -u
Edit /lib/udev/rules.d/50-udev-default.rules to force the group ownership
SUBSYSTEM=="firewire", ATTR{units}=="*0x00a02d:0x010001*", GROUP="video"
+ SUBSYSTEM=="firewire", GROUP="video"
Check library versions
$ apt-show-versions |grep libdc1394
libdc1394-22/lucid uptodate 2.1.2-2
$ apt-show-versions |grep libraw
libraw1394-11/lucid uptodate 2.0.4-1ubuntu2
$ sudo reboot
$ uname -a
Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686
GNU/Linux
$ lsmod |grep fire
firewire_ohci 21002 0
firewire_core 44510 1 firewire_ohci
crc_itu_t 1371 1 firewire_core
$ lsmod |grep 1394
$
So far so good. Plug in camera, turn it on. Pretty much the same result
in dmesg:
[ 67.171233] firewire_core: phy config: card 0, new root=ffc1, gap_count=5
[ 67.173285] firewire_ohci: isochronous cycle too long
[ 67.179910] firewire_ohci: isochronous cycle too long
[ 67.182534] firewire_ohci: isochronous cycle too long
[ 67.191784] firewire_ohci: isochronous cycle too long
[ 67.195784] firewire_ohci: isochronous cycle too long
[ 67.198409] firewire_ohci: isochronous cycle too long
[ 67.201034] firewire_ohci: isochronous cycle too long
[ 67.203659] firewire_ohci: isochronous cycle too long
[ 67.207659] firewire_ohci: isochronous cycle too long
[ 70.768046] firewire_core: Unsolicited response (source ffc0, tlabel 2f)
[ 72.178124] __ratelimit: 1294 callbacks suppressed
[ 72.178128] firewire_ohci: isochronous cycle too long
[ 72.182121] firewire_ohci: isochronous cycle too long
[ 72.184746] firewire_ohci: isochronous cycle too long
[ 72.193996] firewire_ohci: isochronous cycle too long
[ 72.196621] firewire_ohci: isochronous cycle too long
[ 72.200620] firewire_ohci: isochronous cycle too long
[ 72.203245] firewire_ohci: isochronous cycle too long
[ 72.205870] firewire_ohci: isochronous cycle too long
[ 72.209870] firewire_ohci: isochronous cycle too long
[ 72.212495] firewire_ohci: isochronous cycle too long
[ 73.768147] firewire_core: Unsolicited response (source ffc0, tlabel 32)
[ 76.768047] firewire_core: Unsolicited response (source ffc0, tlabel 33)
[ 77.187585] __ratelimit: 1320 callbacks suppressed
[ 77.187589] firewire_ohci: isochronous cycle too long
[ 77.194208] firewire_ohci: isochronous cycle too long
[ 77.196
[Bug 625265] Re: rtl8187: spontaneously disassociates
I omitted to remove the needs-upstream-testing tag, I'm not that familiar with all the LP functions. I noted in the bug I that tested with linux-image-2.6.35-020635rc1-generic. That has the same problems. I tested again, with linux-image-2.6.32-0206322109-generic_2.6.32-0206322109.201008271507_i386.deb from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.32.21.9-lucid/ $ uname -a Linux ubuntu 2.6.32-0206322109-generic #201008271507 SMP Fri Aug 27 16:10:51 UTC 2010 i686 GNU/Linux I tried this for a couple of days. The interface falls over after a few minutes to a few hours. Here's what dmesg says about the insertion (hot-plug) of the device with that kernel: [ 1212.644016] usb 1-2: new high speed USB device using ehci_hcd and address 4 [ 1212.783305] usb 1-2: configuration #1 chosen from 1 choice [ 1213.131068] phy1: Selected rate control algorithm 'minstrel' [ 1213.132204] phy1: hwaddr 00:1e:2a:d0:49:db, RTL8187BvE V0 + rtl8225z2, rfkill mask 2 [ 1213.153627] rtl8187: Customer ID is 0x00 [ 1213.155570] Registered led device: rtl8187-phy1::tx [ 1213.156396] Registered led device: rtl8187-phy1::rx [ 1213.157119] rtl8187: wireless switch is on [ 1213.157397] usbcore: registered new interface driver rtl8187 [ 1213.197568] udev: renamed network interface wlan0 to wlan1 [ 1217.014780] ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 1219.117222] wlan1: direct probe to AP 00:04:ed:b9:1c:d7 (try 1) [ 1219.120218] wlan1: direct probe responded [ 1219.120222] wlan1: authenticate with AP 00:04:ed:b9:1c:d7 (try 1) [ 1219.121967] wlan1: authenticated [ 1219.121984] wlan1: associate with AP 00:04:ed:b9:1c:d7 (try 1) [ 1219.124965] wlan1: RX AssocResp from 00:04:ed:b9:1c:d7 (capab=0x431 status=0 aid=4) [ 1219.124968] wlan1: associated [ 1219.130471] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready And then I get only these items in dmesg: [ 1986.324027] [drm] nouveau :01:00.0: Setting dpms mode 1 on vga encoder (output 1) [ 7582.500014] No probe response from AP 00:04:ed:b9:1c:d7 after 500ms, disconnecting. After bringing the interface up (again static IP config, WEP encryption) iwconfig reports this ubuntu$ sudo iwconfig wlan1 wlan1 IEEE 802.11bg ESSID:"My Net's home" Mode:Managed Frequency:2.412 GHz Access Point: 00:04:ED:B9:1C:D7 Bit Rate=1 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:F43E-D0B4-6B Power Management:off Link Quality=64/70 Signal level=-46 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 While waiting for a response to the initial report I added a pci-based wireless card to the system, which reports about -80 dBm vs -50 dBm from the netgear. Not clear why the difference is so large, they are less than a metre apart, (not too close, in case of interference). The pci card antenna is connected fine, the system case is not metal (Dell). I shut down this interface and started another test with just the netgear. It failed in exactly the same way as before. here's dmesg for when the interface comes up: [90153.178570] ADDRCONF(NETDEV_UP): wlan1: link is not ready [90155.261318] wlan1: direct probe to AP 00:04:ed:b9:1c:d7 (try 1) [90155.263699] wlan1: direct probe responded [90155.263703] wlan1: authenticate with AP 00:04:ed:b9:1c:d7 (try 1) [90155.267184] wlan1: authenticated [90155.267201] wlan1: associate with AP 00:04:ed:b9:1c:d7 (try 1) [90155.269187] wlan1: RX AssocResp from 00:04:ed:b9:1c:d7 (capab=0x431 status=0 aid=4) [90155.269191] wlan1: associated [90155.274688] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready later I find the interface in this state: wlan1 IEEE 802.11bg ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:F43E-D0B4-6B Power Management:off and this in dmesg: [90767.052019] [drm] nouveau :01:00.0: Setting dpms mode 1 on vga encoder (output 1) [91104.500017] No probe response from AP 00:04:ed:b9:1c:d7 after 500ms, disconnecting. Reporting on this is being complicated by something strange happening with logging using this kernel. dmesg is updating, but I am not getting kernel messages in the other logs. Every time I restart rsyslogd I get in /var/log/kern.log: Sep 17 21:17:11 ubuntu kernel: imklog: Cannot read proc file system, 1. I see syslog messages for cron jobs etc but not kernel-related things. Not sure if there is anything I can do about this, please advise. ** Tags removed: needs-upstream-testing -- rtl8187: spontaneously disassociates https://bugs.launchpad.net/bugs/625265 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 434799] Re: X11 forwarding via SSH does not work after upgrade to karmic
p.s. I was able to connect to other servers and tunnel X11 to them, at the same time as I was experiencing this issue with lucid. $ grep -i family /etc/ssh/sshd_config $ $ grep 127 /etc/hosts 127.0.0.1 localhost 127.0.1.1 ubuntu $ ifconfig lo loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:297 errors:0 dropped:0 overruns:0 frame:0 TX packets:297 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:80576 (80.5 KB) TX bytes:80576 (80.5 KB) -- X11 forwarding via SSH does not work after upgrade to karmic https://bugs.launchpad.net/bugs/434799 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 434799] Re: X11 forwarding via SSH does not work after upgrade to karmic
This bug affected me on Lucid as well. $ apt-show-versions |grep ssh openssh-client/lucid-updates uptodate 1:5.3p1-3ubuntu4 openssh-server/lucid-updates uptodate 1:5.3p1-3ubuntu4 ssh-askpass-gnome/lucid-updates uptodate 1:5.3p1-3ubuntu4 $ grep X11 /etc/ssh/sshd_config X11Forwarding yes X11DisplayOffset 10 The only setting I needed to change was to set SSH_OPTS=-4 in /etc/defaults/ssh and /etc/init.d/ssh restart. Then I logged out and logged in again, and echo $DISPLAY localhost:10 I was connecting from a Mac running OSX 10.6.4 with the stock apple X11 and xterm. -- X11 forwarding via SSH does not work after upgrade to karmic https://bugs.launchpad.net/bugs/434799 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 625265] Re: rtl8187: spontaneously disassociates
Went back to 2.6.32-22-generic, since that fixed other issues (LP:459732). I installed linux-image-2.6.32-22-generic (version 2.6.32-22.36) and linux-backports-modules-wireless-2.6.32-33-generic (version 2.6.32-22.13) and rebooted, then selected this kernel from the grub list. The same failure occurs, with the same error message. However I don't see the message about the bogus regulatory domain on this kernel. So something has changed there. I haven't messed about with 'wireless-crda', the version installed is 1.12, installed 2010-04-16. Here's the timeline of associations and disassociations with 2.6.32-22-generic: Aug 31 22:43:03 ubuntu kernel: [ 25.199388] wlan1: associated Sep 1 00:55:01 ubuntu kernel: [ 7943.304273] wlan1: deauthenticating from 00:04:ed:00:00:00 by local choice (reason=3) ... Sep 1 00:55:20 ubuntu kernel: [ 7962.289140] wlan1: associated Sep 1 12:10:37 ubuntu kernel: [48479.500014] No probe response from AP 00:04:ed:00:00:00 after 500ms, disconnecting. Sep 2 00:55:19 ubuntu kernel: [94361.630495] ADDRCONF(NETDEV_UP): wlan1: link is not ready ... Sep 2 00:55:19 ubuntu kernel: [94361.704978] wlan1: associated Sep 2 00:55:20 ubuntu kernel: [94361.710490] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready Sep 2 06:44:59 ubuntu kernel: [115343.500012] No probe response from AP 00:04:ed:00:00:00 after 500ms, disconnecting. As I was poking at this, I got a faster failure, within a few minutes. Here's the link being established: Sep 2 21:57:21 ubuntu kernel: [170085.954566] ADDRCONF(NETDEV_UP): wlan1: link is not ready Sep 2 21:57:21 ubuntu kernel: [170086.021295] wlan1: direct probe to AP 00:04:ed:00:00:00 (try 1) Sep 2 21:57:21 ubuntu kernel: [170086.023801] wlan1: direct probe responded Sep 2 21:57:21 ubuntu kernel: [170086.023805] wlan1: authenticate with AP 00:04:ed:00:00:00 (try 1) Sep 2 21:57:21 ubuntu kernel: [170086.026038] wlan1: authenticated Sep 2 21:57:21 ubuntu kernel: [170086.026061] wlan1: associate with AP 00:04:ed:00:00:00 (try 1) Sep 2 21:57:21 ubuntu kernel: [170086.028671] wlan1: RX AssocResp from 00:04:ed:00:00:00 (capab=0x431 status=0 aid=4) Sep 2 21:57:21 ubuntu kernel: [170086.028674] wlan1: associated Sep 2 21:57:21 ubuntu kernel: [170086.034310] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready and failing Sep 2 22:00:37 ubuntu kernel: [170284.500014] No probe response from AP 00:04:ed:00:00:00 after 500ms, disconnecting. With regard to the regulatory domain, for 2.6.32-22-generic I see this in 'grep cfg80211 /var/log/kern.log': Aug 31 22:43:01 ubuntu kernel: [ 16.169152] cfg80211: Calling CRDA to update world regulatory domain Aug 31 22:43:01 ubuntu kernel: [ 16.673469] cfg80211: World regulatory domain updated: then nothing further for three days. With later kernels, I see a lot more chatter. Here's the output of 'grep cfg80211 /var/log/kern.log' for 2.6.32-24-generic, . Aug 30 00:55:01 ubuntu kernel: [186302.842327] cfg80211: All devices are disconnected, going to restore regulatory settings Aug 30 00:55:01 ubuntu kernel: [186302.842333] cfg80211: Restoring regulatory settings Aug 30 00:55:01 ubuntu kernel: [186302.842336] cfg80211: Calling CRDA to update world regulatory domain Aug 30 00:55:01 ubuntu kernel: [186302.846620] cfg80211: World regulatory domain updated: Aug 30 00:55:20 ubuntu kernel: [186321.879945] cfg80211: Ignoring bogus country IE Aug 30 08:43:33 ubuntu kernel: [214414.573252] cfg80211: All devices are disconnected, going to restore regulatory settings Aug 30 08:43:33 ubuntu kernel: [214414.573258] cfg80211: Restoring regulatory settings Aug 30 08:43:33 ubuntu kernel: [214414.573261] cfg80211: Calling CRDA to update world regulatory domain Aug 30 08:43:33 ubuntu kernel: [214414.576633] cfg80211: World regulatory domain updated: Aug 31 00:55:20 ubuntu kernel: [272721.460713] cfg80211: Ignoring bogus country IE (nothing futher, which is odd) Aug 31 22:25:52 ubuntu kernel: [350144.398418] cfg80211: All devices are disconnected, going to restore regulatory settings Aug 31 22:25:52 ubuntu kernel: [350144.398424] cfg80211: Restoring regulatory settings Aug 31 22:25:52 ubuntu kernel: [350144.398427] cfg80211: Calling CRDA to update world regulatory domain Aug 31 22:25:52 ubuntu kernel: [350144.402698] cfg80211: World regulatory domain updated: Aug 31 22:26:01 ubuntu kernel: [350153.140755] cfg80211: Ignoring bogus country IE -- rtl8187: spontaneously disassociates https://bugs.launchpad.net/bugs/625265 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 625265] Re: rtl8187: spontaneously disassociates
** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522758/+files/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522759/+files/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522760/+files/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522761/+files/BootDmesg.txt ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522762/+files/CRDA.txt ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522763/+files/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522764/+files/Card0.Codecs.codec97.0.ac97.0.0.txt ** Attachment added: "Card0.Codecs.codec97.0.ac97.0.0.regs.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522765/+files/Card0.Codecs.codec97.0.ac97.0.0.regs.txt ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522766/+files/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522767/+files/Dependencies.txt ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522768/+files/IwConfig.txt ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522769/+files/Lspci.txt ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522770/+files/Lsusb.txt ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522771/+files/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522772/+files/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522773/+files/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522774/+files/ProcModules.txt ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522775/+files/UdevDb.txt ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522776/+files/UdevLog.txt ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/625265/+attachment/1522777/+files/WifiSyslog.txt -- rtl8187: spontaneously disassociates https://bugs.launchpad.net/bugs/625265 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 625265] [NEW] rtl8187: spontaneously disassociates
Public bug reported: I have a Netgear WG111(v3) USB dongle, lsusb id is 0846:4260. The device is configured with a static IP address, and connects to an access point using WEP encryption. The machine it is connected to is a Dell PC, located under a desk. Normally nobody is logged in via GDM, network-manager is not running and it is not managing the interface. The computer collects syslog information sent to it over the wireless interface, at present from only one host. After a few hours the device disconnects with this message: Aug 26 18:12:24 ubuntu kernel: [606323.620015] No probe response from AP 00:04:ed:00:00:00 after 500ms, disconnecting. Aug 26 18:12:24 ubuntu kernel: [606323.761271] cfg80211: All devices are disconnected, going to restore regulatory settings Aug 26 18:12:24 ubuntu kernel: [606323.761277] cfg80211: Restoring regulatory settings Aug 26 18:12:24 ubuntu kernel: [606323.761282] cfg80211: Calling CRDA to update world regulatory domain Aug 26 18:12:24 ubuntu kernel: [606323.764770] cfg80211: World regulatory domain updated: Aug 26 18:12:24 ubuntu kernel: [606323.764775] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) Aug 26 18:12:24 ubuntu kernel: [606323.764779] (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) Aug 26 18:12:24 ubuntu kernel: [606323.764783] (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Aug 26 18:12:24 ubuntu kernel: [606323.764786] (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) Aug 26 18:12:24 ubuntu kernel: [606323.764790] (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) Aug 26 18:12:24 ubuntu kernel: [606323.764793] (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) The interval before disconnection is variable, but usually more than 1 hour. I have a cron job that stops and starts the interface once per day $ cat /etc/cron.d/wireless-restart 55 0 * * * root (/sbin/ifdown wlan1; sleep 15; /sbin/ifup wlan1) 1>/dev/null 2>&1 This always works, ie the interface comes up, but it disconnects again after a few hours. Notes: The AP MAC address looks bogus but it is in fact ok. Signal strength is reasonable, according to iwconfig: iwconfig wlan1 wlan1 IEEE 802.11bg ESSID:"My Net's home" Mode:Managed Frequency:2.412 GHz Access Point: 00:04:ED:00:00:00 Bit Rate=11 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=64/70 Signal level=-46 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 /etc/network/interfaces is configured like this: iface wlan1 inet static address 192.168.13.12 netmask 255.255.255.0 gateway 192.168.13.1 network 192.168.13.0 broadcast 192.168.13.255 wireless-essid My Net's home wireless-key f43e-d0b4-6b wireless-mode managed I am usually running the generic lucid kernel, at present linux-image-2.6.32-24-generic (2.6.32-24.41) $ uname -a Linux ubuntu 2.6.32-24-generic #41-Ubuntu SMP Thu Aug 19 01:12:52 UTC 2010 i686 GNU/Linux I've tried this setup for a few days with a mainline build, linux-image-2.6.35-020635rc1-generic. I see the same behaviour. The only other thing I have noticed is on ifup I see a message about the wrong country code in syslog ... Aug 27 21:02:27 ubuntu kernel: [702927.383547] wlan1: RX AssocResp from 00:04:ed:00:00:00 (capab=0x431 status=0 aid=1) Aug 27 21:02:27 ubuntu kernel: [702927.383551] wlan1: associated Aug 27 21:02:28 ubuntu kernel: [702927.457481] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready Aug 27 21:02:28 ubuntu kernel: [702927.457646] cfg80211: Ignoring bogus country IE However I don't set this anywhere and don't see any config files setting it. The locale is: LANG=en_AU.UTF-8 LC_CTYPE="en_AU.UTF-8" LC_NUMERIC="en_AU.UTF-8" LC_TIME="en_AU.UTF-8" LC_COLLATE="en_AU.UTF-8" LC_MONETARY="en_AU.UTF-8" LC_MESSAGES="en_AU.UTF-8" LC_PAPER="en_AU.UTF-8" LC_NAME="en_AU.UTF-8" LC_ADDRESS="en_AU.UTF-8" LC_TELEPHONE="en_AU.UTF-8" LC_MEASUREMENT="en_AU.UTF-8" LC_IDENTIFICATION="en_AU.UTF-8" LC_ALL= $ sudo iw reg get country 00: (2402 - 2472 @ 40), (3, 20) (2457 - 2482 @ 20), (3, 20), PASSIVE-SCAN, NO-IBSS (2474 - 2494 @ 20), (3, 20), NO-OFDM, PASSIVE-SCAN, NO-IBSS (5170 - 5250 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS (5735 - 5835 @ 40), (3, 20), PASSIVE-SCAN, NO-IBSS ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-24-generic 2.6.32-24.41 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-24.41-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vjm1669 F pulseaudio Card0.Amixer.info: Card hw:0 '
[Bug 459732] Re: wireless internet problem on WG111v3 (RTL8187b)
I don't see what more I can say but here goes: * This machine is a clean install of lucid, I did not dist-upgrade from karmic. * Before upgrading, to keep the network up some of the time I had a cron job that did 'ifdown wlan1 && sleep 10 && ifup wlan1' every 4 minutes (the disassociation occured every 5 minutes). I disabled this cron job. * I did an aptitude full-upgrade on 2010-05-10 (or 09, not sure), which pulled in the packages noted in #12. * I rebooted, with the USB device attached. * The system is normally left running with nobody logged in to a gnome session. I did not try logging in to gnome and looking for instability. * I don't have wicd or network-manager installed. I have an entry for the device in /etc/network/interfaces, so it should be getting configured by 'ifupdown' (see #10). * As far as I can tell from 'dbus-monitor --system' dbus is not controlling the device, although there is a control file for network interfaces in /etc/dbus-1/. This might change if I start a gnome session but I haven't tried this. Questions for tarung1793: * Do you have the linux-backports-modules-wireless-lucid-generic package installed. I suspect that is where the fix was applied. * When you say 'not always working' what exactly do you mean - for example: - "it works every other boot", or - "it works one boot in 10", or - "it randomly fails and resumes even without rebooting." * I think it would help to post some dmesg or syslog excerpts of boots where the device is working and where the device failing (while you are running 2.6.32-22), to help the maintainers understand what is happening differently in the "works" and "not working" cases. * What is controlling the network device - wicd, nm, ifupdown? * Is your machine running a fresh install of lucid or did you dist-upgrade? It could be there is some cruft left behind by the upgrade. -- wireless internet problem on WG111v3 (RTL8187b) https://bugs.launchpad.net/bugs/459732 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 566811] Re: gnome-nettool: documentation describes a removed feature (connections tab)
The comment about not installing the package at all is odd. I didn't manually select the package for installation. As far as I can tell it's part of the default install. I installed the Ubuntu Studio flavour, so perhaps that's why it is still being installed. I've been dist-upgrading every few days and gnome-nettool is still there. To clarify which documentation I was looking at - the help button from within network tool. #575694 is referring to more or less the same issue but refers to the 'gnome-network-admin' package. I am reporting an issue with 'gnome-nettool'. Strangely there is no Source: line in the package description for this package, so I'm not sure if it belongs with gnome-system-tools, but perhaps it does. $ apt-cache show gnome-nettool Package: gnome-nettool Priority: optional Section: gnome Installed-Size: 2820 Maintainer: Ubuntu Desktop Team Original-Maintainer: Debian GNOME Maintainers Architecture: i386 Version: 2.30.0-0ubuntu1 Replaces: gnome-network (<= 1.99.5) Depends: libc6 (>= 2.7), libgconf2-4 (>= 2.27.0), libglib2.0-0 (>= 2.23.5), libg tk2.0-0 (>= 2.14.0), libgtop2-7 (>= 2.20.0), liblaunchpad-integration1 (>= 0.1.1 7), libpango1.0-0 (>= 1.14.0), dnsutils, net-tools, iputils-ping | ping, iputils-tracepath, whois Suggests: gnome-system-tools Conflicts: gnome-network (<= 1.99.5) Filename: pool/main/g/gnome-nettool/gnome-nettool_2.30.0-0ubuntu1_i386.deb Size: 111392 MD5sum: fd807fc5b0250d260d46bc7572fed856 SHA1: 6b5cc1a5b66201039d600692849a4ef72352e186 SHA256: c8a54d3fde28dbafb830be619df156214e360be74a008fdf60900c46422c09d0 I don't particularly care if this is fixed. I thought I might give back to Ubuntu by reporting that something seemed to be wrong. -- gnome-nettool: documentation describes a removed feature (connections tab) https://bugs.launchpad.net/bugs/566811 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 459732] Re: wireless internet problem on WG111v3 (RTL8187b)
This appears to be fixed for me, after the following upgrades (excerpted from /var/log/apt/history.log) Install: linux-headers-2.6.32-22 (2.6.32-22.33), linux-image-2.6.32-22-generic (2.6.32-22.33), linux-backports-modules-wireless-2.6.32-22-generic (2.6.32-22.13) linux-headers-2.6.32-22-generic (2.6.32-22.33) Upgrade: linux-headers-generic (2.6.32.21.22, 2.6.32.22.23) linux-image-generic (2.6.32.21.22, 2.6.32.22.23) linux-backports-modules-wireless-lucid-generic (2.6.32.21.22, 2.6.32.22.23), linux-libc-dev (2.6.32-21.32, 2.6.32-22.33) linux-generic (2.6.32.21.22, 2.6.32.22.23) linux-source-2.6.32 (2.6.32-21.32, 2.6.32-22.33) There were other upgrades but I doubt they were relevant. The changelogs were not especially helpful, there was one reference to #567016 which addresses another realtek driver (rtl8192se). The relevant bit of git history _may_ be here somewhere: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=history;f=drivers/net/wireless/rtl818x;h=f0819aaf4948e34a44d9d685615ddee74271cd70;hb=f0819aaf4948e34a44d9d685615ddee74271cd70 In particular, the rfkill patch, at a guess: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-lucid.git;a=commit;h=1abb41521040db929998e107a067879978c3ec9b Thanks folks! -- wireless internet problem on WG111v3 (RTL8187b) https://bugs.launchpad.net/bugs/459732 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 566811] Re: gnome-nettool: does not show 'connections' tab
*** This bug is a duplicate of bug 574067 *** https://bugs.launchpad.net/bugs/574067 Setting this to duplicate status is wrong. I reported this bug because the documentation was at odds with what I saw in the tool. So with the new information that the tool was changed on purpose (was this mentioned in the package README??), this bug should be retitled - 'gnome-nettool: documentation describes a removed feature (connections tab)'. Why is this package even in the release? In the default list of packages that get installed with the desktop and are accessible from the desktop menu? Thank you for wasting my time. Not. ** Summary changed: - gnome-nettool: does not show 'connections' tab + nome-nettool: documentation describes a removed feature (connections tab) ** Summary changed: - nome-nettool: documentation describes a removed feature (connections tab) + gnome-nettool: documentation describes a removed feature (connections tab) -- gnome-nettool: documentation describes a removed feature (connections tab) https://bugs.launchpad.net/bugs/566811 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 566811] Re: gnome-nettool: does not show 'connections' tab
$ apt-show-versions gnome-nettool gnome-nettool/lucid uptodate 2.30.0-0ubuntu1 -- gnome-nettool: does not show 'connections' tab https://bugs.launchpad.net/bugs/566811 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 566811] Re: gnome-nettool: does not show 'connections' tab
I don't understand why you think this is incomplete. 1. I already gave you this. 2. Let me spell it out for you: I opened the tool and expected to see four tabs, as is documented in the help pages for the tool. 3. Again, rehashing what I already told you: Instead, I see three tabs, 'General', 'DNS' and 'Hosts'. The 'Connections' tab noted in the manual is completely absent. I don't see what more detail I can provide. I used ubuntu-bug to report this, that is where Dependencies.txt came from. I don't have any control over how much information ubuntu-bug decides to put in the job. I tried the 'report a bug' item in the help menu but that didn't appear to do anything, I'm guessing this is because gnome-nettool doesn't have proper 'apport' support in it. Perhaps you could tell me precisely what you think is missing instead of cutting&pasting the 'how to report text'. -- gnome-nettool: does not show 'connections' tab https://bugs.launchpad.net/bugs/566811 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 566811] Re: gnome-nettool: does not show 'connections' tab
** Summary changed: - does not show 'connections' tab + gnome-nettool: does not show 'connections' tab -- gnome-nettool: does not show 'connections' tab https://bugs.launchpad.net/bugs/566811 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 459732] Re: wireless internet problem on WG111v3 (RTL8187b)
PS. There is nothing wrong with the access point I am using, the other machines on the network (including one sitting on the desk the affected machine is located under) don't see this problem. -- wireless internet problem on WG111v3 (RTL8187b) https://bugs.launchpad.net/bugs/459732 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 459732] Re: wireless internet problem on WG111v3 (RTL8187b)
I am seeing similar things. $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 $ uname -a Linux ubuntu 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 i686 GNU/Linux $ lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 003: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 004 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 03f0:3611 Hewlett-Packard PSC 2410 PhotoSmart Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 413c:2003 Dell Computer Corp. Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 006: ID 0846:4260 NetGear, Inc. WG111(v3) 54 Mbps Wireless [RealTek RTL8187B] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub What I observe in syslog is the card deauthenticating from the wireless network, every 5 minutes or less, with 'Reason: 4), e.g. Apr 19 07:45:10 ubuntu kernel: [149791.540484] wlan1: associated Apr 19 07:45:10 ubuntu kernel: [149791.546125] ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready Apr 19 07:45:13 ubuntu dhclient: DHCPDISCOVER on wlan1 to 255.255.255.255 port 67 interval 6 Apr 19 07:45:13 ubuntu dhclient: DHCPREQUEST of 192.168.13.12 on wlan1 to 255.255.255.255 port 67 Apr 19 07:45:20 ubuntu kernel: [149801.892009] wlan1: no IPv6 routers present Apr 19 07:48:49 ubuntu kernel: [150010.760375] wlan1: deauthenticated from 00:09:5b:dd:8f:3a (Reason: 4) This appears to be some kind of activity timeout, if the code is an official 80211 code. The message appears to be coming from /usr/src/linux-source-2.6.32/net/mac80211/mlme.c The timeout seems to be defined in /usr/src/linux-source-2.6.32/drivers/net/wireless/hostap/hostap_ap.c This is weird because I am sending syslog packets (udp) to this machine, ie there is wireless network traffic directed to that interface, every 10-60 seconds. I set up a cron job to do an outbound ping (box -> router) every 4 minutes. Made no difference. I changed the cron job to do an ifdown wlan1; sleep 5; ifup wlan1; every 4 minutes. This at least kept the interface up most of the time, but I still got (Reason: 4). I don't have network-manager or wicd installed. I do have wpasupplicant but I am using wep, so that should not matter, correct. /etc/network/interfaces contains: auto wlan1 iface wlan1 inet dhcp wireless-ap any wireless-essid mylittlenet wireless-key d00b-ed00-6b wireless-mode managed I installed linux-backports-modules-wireless-lucid-generic, made no difference. The normal mode for this system is to sit quietly under a desk with nobody logged in. I don't know why that should matter. I had a deauthentication while collating this report. -- wireless internet problem on WG111v3 (RTL8187b) https://bugs.launchpad.net/bugs/459732 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 566811] Re: does not show 'connections' tab
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/44835510/Dependencies.txt -- does not show 'connections' tab https://bugs.launchpad.net/bugs/566811 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 566811] [NEW] does not show 'connections' tab
Public bug reported: Binary package hint: gnome-nettool running ubuntustudio lucid/i386, up to date as at 2010-04-20. In the desktop I go to System->Administration->Network. The gnome-nettool opens. It shows 'General', 'DNS' and 'Hosts' info, all correct. There is no Connections tab. The help pages are almost entirely devoted to this tab, so there must be something seriously wrong here. The interfaces in the machine are shown below. $ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:0f:1f:df:66:49 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Interrupt:16 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:93 errors:0 dropped:0 overruns:0 frame:0 TX packets:93 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10065 (10.0 KB) TX bytes:10065 (10.0 KB) wlan1 Link encap:Ethernet HWaddr 00:1e:2a:d0:49:db inet addr:192.168.13.12 Bcast:192.168.13.255 Mask:255.255.255.0 inet6 addr: fe80::21e:2aff:fed0:49db/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:16422 errors:0 dropped:0 overruns:0 frame:0 TX packets:10450 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:21006929 (21.0 MB) TX bytes:1240665 (1.2 MB) $ lsb_release -rd Description:Ubuntu lucid (development branch) Release:10.04 $ apt-cache policy gnome-nettool gnome-nettool: Installed: 2.30.0-0ubuntu1 Candidate: 2.30.0-0ubuntu1 Version table: *** 2.30.0-0ubuntu1 0 500 http://au.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-nettool 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 Date: Tue Apr 20 03:21:05 2010 InstallationMedia: Ubuntu-Studio 10.04 "Lucid Lynx" - Beta i386 (20100406.1) ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-nettool ** Affects: gnome-nettool (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- does not show 'connections' tab https://bugs.launchpad.net/bugs/566811 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 459523] Re: regression: support for dvico dual digital 4 card
Rob's fix went in to v4l as this commit: http://git.linuxtv.org/v4l- dvb.git?a=commit;h=0bc3518019f917a370935055f07698a4e9b3ea20 It was added to the karmic kernel git in January: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-karmic.git;a=history;f=drivers/media/dvb/dvb-usb/cxusb.c;h=f32b332ba76dfc945989457a039741b11d057bd0;hb=HEAD -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
Hi Damien are you using "stock" ubuntu or did you compile more recent v4l-dvb drivers yourself? Could you post dmesg output from booting up the working version? It would be particularly helpful if you could boot, then try to tune the receiver with dvbscan or equivalently try to watch live tv in mythtv, then run dmesg. -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
** Attachment added: "strace of dvbscan, with 2.6.31-14-generic + v4l tip drivers" http://launchpadlibrarian.net/34749121/log.dvbscan.20091031 -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
I was able to get 2.6.31-14-generic to boot. I did not try tuning with this, I doubt it will make any difference. I tried building the v4l tree: $ cd v4l-dvb $ make update; make ; The build dies on the FiredTV driver for some reason, so turn it off. $ sed -ie 's/CONFIG_DVB_FIREDTV=m/CONFIG_DVB_FIREDTV=n/' v4l/.config; $ make clean; make; sudo make install Then I shut down, and pulled the power to get a cold boot. Boot, and try to tune, stracing as we do $ sudo strace -t -F -ff dvbscan /usr/share/dvb/dvb-t/au-Sydney_North_Shore | tee northshore.conf It fails with "Unable to query frontend status". $ dmesg The log file is attached as log.dvbscan.20091031 -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
Found a simple workaround:
{{{
$ sudo dpkg-reconfigure linux-image-2.6.31-14-generic
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.31-14-generic
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.31-14.48 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.31-14.48 was configured last, according to dpkg)
Running postinst hook script /usr/sbin/update-grub.
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.31-14-generic
Found initrd image: /boot/initrd.img-2.6.31-14-generic
Found linux image: /boot/vmlinuz-2.6.31-13-generic
Found initrd image: /boot/initrd.img-2.6.31-13-generic
Found linux image: /boot/vmlinuz-2.6.31-9-rt
Found initrd image: /boot/initrd.img-2.6.31-9-rt
Found linux image: /boot/vmlinuz-2.6.31-6-rt
Found initrd image: /boot/initrd.img-2.6.31-6-rt
Found memtest86+ image: /boot/memtest86+.bin
done
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/nvidia-common
}}}
after which I can boot this kernel.
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
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 459523] Re: regression: support for dvico dual digital 4 card
Hi Bob it would probably help people processing this report quite a bit to have the output of a working Jaunty system. Could you post 'dmesg' from the following sequence of events: * disable mythtv if you have it installed (rename the /etc/init.d scripts) * shut down, pull the power. * boot * try a dvbscan, as shown above. * sudo dmesg >jaunty.dmesg It would also help to clarify the exact kernel package you're running: * uname -r > jaunty.kernel-version * dpkg -l linux-image\* >> jaunty.kernel-version Could you also say if you are using any self-compiled modules from the v4l mercurial tree? It would also help to know the kernel version you are using in karmic: * uname -a > karmic.kernel-version * dpkg -l linux-image\* >> karmic.kernel-version * are you using self-compiled v4l modules? I am about to try this. -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
/etc/lsb-release for working system: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=8.04 DISTRIB_CODENAME=hardy DISTRIB_DESCRIPTION="Ubuntu 8.04.3 LTS" -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
regarding the rmmod/modprobe experiment I described. The module is of course dvb_usb_cxusb, not 'cxusb'. -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
details of the working system:
it's the same hardware, with an earlier version of ubuntu installed on a
separate hard disk.
$ uname -a
Linux wellington 2.6.24-23-rt #1 SMP PREEMPT RT Wed Apr 1 23:40:34 UTC 2009
i686 GNU/Linux
The kernel I am using is linux-image-2.6.24-23-rt, package version 2.6.24-23.52.
I have had problems with linux-image-2.6.24-24-rt but have not had time to
characterise or report them.
On this setup I am running dvb drivers from the v4l hg,
{{{
$ sudo modinfo dvb_usb_cxusb
filename:
/lib/modules/2.6.24-23-rt/kernel/drivers/media/dvb/dvb-usb/dvb-usb-cxusb.ko
license:GPL
version:1.0-alpha
description:Driver for Conexant USB2.0 hybrid reference design
author: Chris Pascoe
author: Michael Krufky
author: Patrick Boettcher
srcversion: 42696397EE37DD79A9589B7
alias: usb:v0572p86D6d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB98d*dc*dsc*dp*ic*isc*ip*
alias: usb:v07CApA868d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB71d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB70d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB78d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB59d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB58d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB55d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB54d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB11d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB10d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB01d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB00d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB51d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pDB50d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pD501d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FE9pD500d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1660p0932d*dc*dsc*dp*ic*isc*ip*
depends:dvb-usb,dib0070,usbcore,dib7000p
vermagic: 2.6.24-23-rt SMP preempt mod_unload 586
parm: debug:set debugging level (1=rc (or-able)). (int)
parm: adapter_nr:DVB adapter numbers (array of short)
}}}
The last time I pulled and built (Sat Sep 5 11:00:22 EST 2009), I got:
2b49813f8482 tip
See dmesg.working for dmesg output while the system boots, tunes to a
live tv channel and then I log out.
** Attachment added: "dmesg.working"
http://launchpadlibrarian.net/34306742/dmesg.working
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
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 459523] Re: regression: support for dvico dual digital 4 card
I tried stracing the dvbscan, see attached (log.dvbscan) ** Attachment added: "log.dvbscan" http://launchpadlibrarian.net/34306455/log.dvbscan -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
and kept the syslog of what occured then (syslog.dvbscan). it stops when I typed 'halt'. ** Attachment added: "syslog.dvbscan" http://launchpadlibrarian.net/34306522/syslog.dvbscan -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] Re: regression: support for dvico dual digital 4 card
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/34302610/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/34302611/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/34302612/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/34302613/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/34302614/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.2.txt" http://launchpadlibrarian.net/34302615/Card0.Codecs.codec.2.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/34302616/CurrentDmesg.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/34302617/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/34302618/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/34302619/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/34302620/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/34302621/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/34302622/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/34302623/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/34302624/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/34302625/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/34302626/WifiSyslog.txt -- regression: support for dvico dual digital 4 card https://bugs.launchpad.net/bugs/459523 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 459523] [NEW] regression: support for dvico dual digital 4 card
Public bug reported: Binary package hint: linux-image Hi symptom: I have two dvico cards in this machine, dual digital4 and dual digtial express, see lspci data. Both work on 'hardy', with v4l modules from the v4l mercurial repository. I'll provide more details of that setup shortly. On karmic the kernel recognizes this card but appears to be unable to make it tune. When I try to tune with 'dvb-utils' 'scan' program, I get syslog spew: kernel: [ 315.032076] dvb-usb: bulk message failed: -110 (4/0) kernel: [ 315.032080] cxusb: i2c read failed kernel: [ 317.132138] dvb-usb: bulk message failed: -110 (4/0) kernel: [ 317.132143] cxusb: i2c read failed ... and the card is unable to tune. Initially the spew is slow, about 1 per second. If I rmmod cxusb, the spew stops. If I then modprobe -v cxusb module, the spew resumes at a dramatically higher rate. To reproduce: -- cold-boot the machine. the power supply must be off. unplug if unsure. To make the kernel initialise it properly I had to add some firmware (/lib/firmware/xc3028-v27.fw, md5sum 293dc5e915d9a0f74a368f8a2ce3cc10). This is normal for this card and seems to work ok. $ /bin/ls -lRF /dev/dvb /dev/dvb: total 0 drwxr-xr-x 2 root root 120 2009-10-24 22:15 adapter0/ drwxr-xr-x 2 root root 120 2009-10-24 22:15 adapter1/ drwxr-xr-x 2 root root 120 2009-10-24 22:15 adapter2/ drwxr-xr-x 2 root root 120 2009-10-24 22:15 adapter3/ /dev/dvb/adapter0: total 0 crw-rw+ 1 root video 212, 0 2009-10-24 22:15 demux0 crw-rw+ 1 root video 212, 1 2009-10-24 22:15 dvr0 crw-rw+ 1 root video 212, 3 2009-10-24 22:15 frontend0 crw-rw+ 1 root video 212, 2 2009-10-24 22:15 net0 /dev/dvb/adapter1: total 0 crw-rw+ 1 root video 212, 5 2009-10-24 22:15 demux0 crw-rw+ 1 root video 212, 6 2009-10-24 22:15 dvr0 crw-rw+ 1 root video 212, 4 2009-10-24 22:15 frontend0 crw-rw+ 1 root video 212, 7 2009-10-24 22:15 net0 /dev/dvb/adapter2: total 0 crw-rw+ 1 root video 212, 9 2009-10-24 22:15 demux0 crw-rw+ 1 root video 212, 10 2009-10-24 22:15 dvr0 crw-rw+ 1 root video 212, 8 2009-10-24 22:15 frontend0 crw-rw+ 1 root video 212, 11 2009-10-24 22:15 net0 /dev/dvb/adapter3: total 0 crw-rw+ 1 root video 212, 12 2009-10-24 22:15 demux0 crw-rw+ 1 root video 212, 13 2009-10-24 22:15 dvr0 crw-rw+ 1 root video 212, 15 2009-10-24 22:15 frontend0 crw-rw+ 1 root video 212, 14 2009-10-24 22:15 net0 Try to tune with: $ dvbscan /usr/share/dvb/dvb-t/au-Sydney_North_Shore | tee northshore.conf and see how far you get. Things I tried: - I tried to install the latest generic kernel (2.6.31-14.48) but there is some other bug preventing it from booting. I tried ubuntu-bug -p, but got a warning $ ubuntu-bug -p linux Warning: The options -p/-P are deprecated, please do not use them. See /usr/bin/ubuntu-bug --help so I gave up on that approach and will append the requested details shortly. Perhaps the linux-meta guidelines should be updated? There are several reports of this kind of problem, going back to the hardy kernel, I'll try to provide a summary. In fact on that setup I get similar kinds of syslog spew when shutting down and sometimes when I warm-boot, but the cards do at least work if I cold boot. Unfortunately nobody on the linux-media/linux-dvb list who could do something about this seems to care. Perhaps they are waiting for a good bug report, I dunno. ProblemType: Bug Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vjm2175 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x905a irq 22' Mixer name : 'Realtek ALC888' Components : 'HDA:10ec0888,80860001,0011' Controls : 38 Simple ctrls : 21 Date: Sat Oct 24 12:31:01 2009 DistroRelease: Ubuntu 9.10 HibernationDevice: RESUME=/dev/mapper/vgb-swap Package: linux-image (not installed) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic root=UUID=9ecccb04-4b5b-4017-a49d-80dca283631d ro quiet splash ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.43-generic RelatedPackageVersions: linux-firmware 1.24 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux-meta Uname: Linux 2.6.31-13-generic i686 XsessionErrors: (gnome-settings-daemon:2188): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2188): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:2241): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:2231): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed dmi.bios.date: 10/02/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0293.2007.1002.1519 dmi.board.asset.tag: Base Bo
[Bug 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
{{{
$ sudo blkid -p /dev/sdb1
/dev/sdb1: LABEL="newroot" UUID="9ecccb04-4b5b-4017-a49d-80dca283631d"
VERSION="1.0" TYPE="ext4" USAGE="filesystem"
The system has /, swap and an LVM partition for /usr, /var, /home, etc.
sudo fdisk -l /dev/sdb
Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00049b91
Device Boot Start End Blocks Id System
/dev/sdb1 1 243 1951866 83 Linux
/dev/sdb2 244 729 3903795 82 Linux swap / Solaris
/dev/sdb3 730 182401 1459280340 8e Linux LVM
}}}
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
** Attachment added: "hardware summary from lspci" http://launchpadlibrarian.net/33871581/lspci-vnvn.log -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
Managed to get some more detailed info.
grub versions: grub* got upgraded along with the kernel.
{{{
grep grub /var/log/dpkg.log
2009-10-18 12:06:48 upgrade grub-pc 1.97~beta3-1ubuntu8 1.97~beta4-1ubuntu2
2009-10-18 12:06:48 status half-configured grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48 status unpacked grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48 status half-installed grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48 status half-installed grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 upgrade grub-common 1.97~beta3-1ubuntu8 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 status half-configured grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status unpacked grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status triggers-pending install-info 4.13a.dfsg.1-4
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 status unpacked grub-common 1.97~beta4-1ubuntu2
...
2009-10-18 12:06:58 configure grub-common 1.97~beta4-1ubuntu2
1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:59 status half-configured grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:59 status installed grub-common 1.97~beta4-1ubuntu2
...
2009-10-18 12:07:16 configure grub-pc 1.97~beta4-1ubuntu2 1.97~beta4-1ubuntu2
2009-10-18 12:07:16 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:07:16 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:07:16 status half-configured grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:07:33 status installed grub-pc 1.97~beta4-1ubuntu2
...
}}}
kernel package version (working kernel)
Ubuntu 2.6.31-13.43-generic
various other bits attached.
** Attachment added: "grub config"
http://launchpadlibrarian.net/33871485/grub.cfg
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
** Attachment added: "dmesg from a cold boot of the working kernel" http://launchpadlibrarian.net/33871571/dmesg.log.gz -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
** Attachment added: "version of the working kernel" http://launchpadlibrarian.net/33871490/version.log -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
Managed to get some more detailed info.
grub versions: grub* got upgraded along with the kernel.
{{{
grep grub /var/log/dpkg.log
2009-10-18 12:06:48 upgrade grub-pc 1.97~beta3-1ubuntu8 1.97~beta4-1ubuntu2
2009-10-18 12:06:48 status half-configured grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48 status unpacked grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48 status half-installed grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48 status half-installed grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 upgrade grub-common 1.97~beta3-1ubuntu8 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 status half-configured grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status unpacked grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status triggers-pending install-info 4.13a.dfsg.1-4
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status half-installed grub-common 1.97~beta3-1ubuntu8
2009-10-18 12:06:49 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:49 status unpacked grub-common 1.97~beta4-1ubuntu2
...
2009-10-18 12:06:58 configure grub-common 1.97~beta4-1ubuntu2
1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:58 status unpacked grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:59 status half-configured grub-common 1.97~beta4-1ubuntu2
2009-10-18 12:06:59 status installed grub-common 1.97~beta4-1ubuntu2
...
2009-10-18 12:07:16 configure grub-pc 1.97~beta4-1ubuntu2 1.97~beta4-1ubuntu2
2009-10-18 12:07:16 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:07:16 status unpacked grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:07:16 status half-configured grub-pc 1.97~beta4-1ubuntu2
2009-10-18 12:07:33 status installed grub-pc 1.97~beta4-1ubuntu2
...
}}}
kernel package version (working kernel)
Ubuntu 2.6.31-13.43-generic
various other bits attached.
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
system is also able to boot an old setup (hardy) on the other hard disk. -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
The boot line in syslog (from the working kernel) is Linux version 2.6.31-13-generic (bui...@rothera) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu7) ) #43-Ubuntu SMP Fri Oct 9 17:42:36 UTC 2009 (Ubuntu 2.6.31-13.43-generic) -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 454418] Re: grub misconfigured after upgrade to linux-image-2.6.31-14-generic
I should have added to 'what happened' - from the initramfs shell, I halted the machine - power off, wait, power on. - boot 2.6.31-13-generic - it booted fine. I did not gather a lot more detail as I was looking at other issues when this cropped up. -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 454418] [NEW] grub misconfigured after upgrade to linux-image-2.6.31-14-generic
Public bug reported: Binary package hint: grub-pc What happened: I was running linux-image-2.6.31-13-generic. I upgraded to linux-image-2.6.31-14-generic using sudo aptitude safe-upgrade There was a minor issue with linux-firmware which might be related, but a second safe-upgrade fixed the linux-firmware package and did not appear to trigger any grub-related activity. (I'd point to the comments I made in another bug but I can't find it with any search I do on bugs in 'linux-firmware') I shut down the system, and powered off. Waited 10-20sec. I powered up the system, got the grub menu and the new kernel was listed first in the list, as expected. I hit return to boot it and it started - I saw the bootsplash screen etc. Then I saw these lines on screen udevadm trigger is not permitted while udev is unconfigured udevadm settle is not permitted while udev is unconfigured svgalib: cannot open /dev/mem ... some lines with advice about what to do... /dev/disk/by-uuid/9eccc..etc.. does not exist! Dropping to a shell. The uuid shown was the correct uuid for the root of the installation (the same as used by the 2.6.31-13-generic kernel) It appears that something has gone awry with the grub entry for this kernel. I don't have access to more detail (eg grub versions) right now. The box has two hard disk, with hardy on one and karmic on the other and it is back in production. I can get more details as required in a few days' time. What I was expecting to see: a normal boot Steps to reproduce It appears all that is required is to safe-upgrade when you have linux-image-2.6.31-13-generic installed and linux-image-2.6.31-14-generic pending for install. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- grub misconfigured after upgrade to linux-image-2.6.31-14-generic https://bugs.launchpad.net/bugs/454418 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 450736] Re: package linux-firmware 1.21 failed to install/upgrade: trying to overwrite '/lib/firmware/dvb-usb-dib0700-1.20.fw', which is also in package linux-firmware-nonfree 0:1.0
I got a crash report on upgrading from 1.21 to 1.24 (along with a heap - about
2weeks of updates).
I started the upgrade at about 2009-10-18T00:30:00 GMT, local time 11:30.
dpkg.log contained this
{{{
2009-10-18 12:06:19 upgrade linux-firmware 1.21 1.24
2009-10-18 12:06:19 status half-configured linux-firmware 1.21
2009-10-18 12:06:19 status unpacked linux-firmware 1.21
2009-10-18 12:06:19 status half-installed linux-firmware 1.21
2009-10-18 12:06:19 status unpacked linux-firmware 1.21
2009-10-18 12:06:19 status installed linux-firmware 1.21
2009-10-18 12:06:19 upgrade linux-firmware-nonfree 1.0 1.1
2009-10-18 12:06:19 status half-configured linux-firmware-nonfree 1.0
2009-10-18 12:06:19 status unpacked linux-firmware-nonfree 1.0
2009-10-18 12:06:19 status half-installed linux-firmware-nonfree 1.0
2009-10-18 12:06:19 status half-installed linux-firmware-nonfree 1.0
2009-10-18 12:06:19 status unpacked linux-firmware-nonfree 1.1
2009-10-18 12:06:19 status unpacked linux-firmware-nonfree 1.1
...
2009-10-18 12:07:15 configure linux-firmware-nonfree 1.1 1.1
2009-10-18 12:07:15 status unpacked linux-firmware-nonfree 1.1
2009-10-18 12:07:15 status half-configured linux-firmware-nonfree 1.1
2009-10-18 12:07:15 status installed linux-firmware-nonfree 1.1
}}}
I didn't catch the error message, if there was one.
Couldn't see anything in /var/log{syslog,messages,debug.daemon.log}
/var/log/aptitude contained only this of interest..
{{{
[UPGRADE] linux-firmware 1.21 -> 1.24
[UPGRADE] linux-firmware-nonfree 1.0 -> 1.1
...
[UPGRADE] linux-firmware 1.21 -> 1.24
}}}
/var/log/apt/term.log had this:
{{{
Preparing to replace linux-firmware 1.21 (using
.../linux-firmware_1.24_all.deb) ...
Unpacking replacement linux-firmware ...
dpkg: error processing /var/cache/apt/archives/linux-firmware_1.24_all.deb
(--unpack):
trying to overwrite '/lib/firmware/dvb-usb-dib0700-1.20.fw', which is also in
package linux-firmware-nonfree 0:1.0
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Preparing to replace linux-firmware-nonfree 1.0 (using
.../linux-firmware-nonfree_1.1_all.deb) ...
Unpacking replacement linux-firmware-nonfree ...
}}}
Rerunning safe-upgrade seemed to fix the issue
{{{
sudo aptitude safe-upgrade
[sudo] password for vjm:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following packages will be upgraded:
linux-firmware
1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/5,714kB of archives. After unpacking 2,925kB will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 150293 files and directories currently installed.)
Preparing to replace linux-firmware 1.21 (using
.../linux-firmware_1.24_all.deb) ...
Unpacking replacement linux-firmware ...
Setting up linux-firmware (1.24) ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Current status: 0 updates [-1].
}}}
dpkg.log
{{{
2009-10-18 12:12:39 upgrade linux-firmware 1.21 1.24
2009-10-18 12:12:39 status half-configured linux-firmware 1.21
2009-10-18 12:12:39 status unpacked linux-firmware 1.21
2009-10-18 12:12:39 status half-installed linux-firmware 1.21
2009-10-18 12:12:39 status half-installed linux-firmware 1.21
2009-10-18 12:12:40 status unpacked linux-firmware 1.24
2009-10-18 12:12:40 status unpacked linux-firmware 1.24
2009-10-18 12:12:40 startup packages configure
2009-10-18 12:12:40 configure linux-firmware 1.24 1.24
2009-10-18 12:12:40 status unpacked linux-firmware 1.24
2009-10-18 12:12:40 status half-configured linux-firmware 1.24
2009-10-18 12:12:40 status installed linux-firmware 1.24
}}}
/var/log/apt/term.log
{{{
Preparing to replace linux-firmware 1.21 (using
.../linux-firmware_1.24_all.deb) ...
Unpacking replacement linux-firmware ...
Setting up linux-firmware (1.24) ...
}}}
My system:
uname -a
Linux mythbox 2.6.31-13-generic #43-Ubuntu SMP Fri Oct 9 17:42:36 UTC 2009 i686
GNU/Linux
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=9.10
DISTRIB_CODENAME=karmic
DISTRIB_DESCRIPTION="Ubuntu karmic (development branch)"
--
package linux-firmware 1.21 failed to install/upgrade: trying to overwrite
'/lib/firmware/dvb-usb-dib0700-1.20.fw', which is also in package
linux-firmware-nonfree 0:1.0
https://bugs.launchpad.net/bugs/450736
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 309877] Re: cupsd fails to restart on upgrade
The system was under heavy CPU load at the time (numerical simulations). Not sure if that's relevant, hopefully not. -- cupsd fails to restart on upgrade https://bugs.launchpad.net/bugs/309877 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 309877] Re: cupsd fails to restart on upgrade
** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/20587133/Dependencies.txt ** Attachment added: "DpkgTerminalLog.gz" http://launchpadlibrarian.net/20587134/DpkgTerminalLog.gz -- cupsd fails to restart on upgrade https://bugs.launchpad.net/bugs/309877 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 309877] [NEW] cupsd fails to restart on upgrade
Public bug reported: Binary package hint: cups This is probably the same underlying issue as https://bugs.launchpad.net/bugs/304039, but I see different symptoms. My system is currently working ok but the upgrade process was not as smooth as it should be. I did a 'sudo aptitude update; sudo aptitude safe-upgrade;' and during the upgrade of the 'cups' package aptitude seemed to hang. I hit ^c to skip it, but had to do this twice. I then got a message as in #304039, E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. I tried that, but things still seemed to get stuck. ^c again. I found with 'top' that there were now 3 cupsd processes running, so I killed them (kill -KILL, also tried killall cupsd) and tried dpkg --configure -a again. No obvious improvement. Apologies that this report is a little vague, as I was in a bit of a hurry and did not make detailed notes. I had to leave the system, but when I came back to it 12 hours later, things seemed to be working. I reran 'dpkg --configure -a' but got no output on the terminal, it's unclear that the command did anything. It's possible this is related to the flaky USB connection to the printer. The electrical contact is not always good, though I have taken steps to ensure the USB connector has reasonable contact and doesn't jiggle around. I can't recall if the device was showing as connected at the time. /var/log/kern.log contained these lines, which may be of use. Dec 19 10:06:04 ubuntu kernel: [1719265.271037] type=1505 audit(1229641564.644:27): operation="profile_replace" name="/usr/share/gdm/guest-session/Xsession" name2="default" pid=29147 Dec 19 10:06:04 ubuntu kernel: [1719265.495352] type=1505 audit(1229641564.868:28): operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=29152 Dec 19 10:06:04 ubuntu kernel: [1719265.498068] type=1505 audit(1229641564.872:29): operation="profile_replace" name="/usr/sbin/cupsd" name2="default" pid=29152 Dec 19 10:16:54 ubuntu kernel: [1719915.297126] type=1505 audit(1229642214.672:32): operation="profile_replace" name="/usr/sbin/cupsd" name2="default" pid=490 Dec 19 10:19:44 ubuntu kernel: [1720085.067577] type=1505 audit(1229642384.440:33): operation="profile_replace" name="/usr/share/gdm/guest-session/Xsession" name2="default" pid=697 Dec 19 10:19:45 ubuntu kernel: [1720086.325419] type=1505 audit(1229642385.700:34): operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=702 Dec 19 10:19:45 ubuntu kernel: [1720086.327127] type=1505 audit(1229642385.700:35): operation="profile_replace" name="/usr/sbin/cupsd" name2="default" pid=702 Dec 19 10:21:03 ubuntu kernel: [1720163.894603] type=1505 audit(1229642463.268:36): operation="profile_replace" name="/usr/share/gdm/guest-session/Xsession" name2="default" pid=829 Dec 19 10:21:03 ubuntu kernel: [1720164.128615] type=1505 audit(1229642463.504:37): operation="profile_replace" name="/usr/lib/cups/backend/cups-pdf" name2="default" pid=834 Dec 19 10:21:03 ubuntu kernel: [1720164.131235] type=1505 audit(1229642463.504:38): operation="profile_replace" name="/usr/sbin/cupsd" name2="default" pid=834 lsusb shows the device as Bus 001 Device 006: ID 03f0:3611 Hewlett-Packard PSC 2410 Photosmart When the system detects the device I get this in dmesg: [45168.656042] usb 1-1: new full speed USB device using uhci_hcd and address 5 [45168.861809] usb 1-1: configuration #1 chosen from 1 choice [45168.867969] scsi5 : SCSI emulation for USB Mass Storage devices [45168.870479] usb-storage: device found at 5 [45168.870486] usb-storage: waiting for device to settle before scanning [45169.025278] usb 1-1: USB disconnect, address 5 [45169.520201] usbcore: registered new interface driver usblp [45169.888024] usb 1-1: new full speed USB device using uhci_hcd and address 6 [45170.090339] usb 1-1: configuration #1 chosen from 1 choice [45170.102142] usblp0: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x03F0 pid 0x3611 [45170.115404] scsi6 : SCSI emulation for USB Mass Storage devices [45170.116124] usb-storage: device found at 6 [45170.116131] usb-storage: waiting for device to settle before scanning [45173.635616] usblp0: removed [45175.117242] usb-storage: device scan complete [45175.120241] scsi 6:0:0:0: Direct-Access HP psc 2410 1.00 PQ: 0 ANSI: 2 [45175.144993] sd 6:0:0:0: [sdc] Attached SCSI removable disk [45175.145466] sd 6:0:0:0: Attached scsi generic sg3 type 0 [45175.278292] type=1503 audit(1229733410.439:5): operation="inode_permission" requested_mask="::rw" denied_mask="::rw" fsuid=7 name="/dev/tty" pid=9872 profile="/usr/sbin/cupsd" my current package state - dpkg -l |grep ^ii |grep cups gives this list: ii bluez-cups4.12-0ubuntu5 Bluetooth printer driver for CUPS ii cups 1.3.9-2ubuntu4
[Bug 301596] Re: crashes with "pure virtual method called; terminate called without an active exception"
The 'Also affects project' link was new to me, I thought it was a way to flag the same bug affects other packages. I can't see any need to link this to upstream projects at this time. The other packages I noticed this affecting were epiphany-browser2.24.1-0ubuntu1 firefox 3.0.4+nobinonly-0ubuntu0.8.10.1 -- crashes with "pure virtual method called;terminate called without an active exception" https://bugs.launchpad.net/bugs/301596 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 301596] Re: crashes with "pure virtual method called; terminate called without an active exception"
As I was attempting (in galeon) to add an 'Also affects project' link, I got _another_ crash. This time the error from galeon as 'Segmentation fault'. I haven't seen this behaviour before, the machine has been quite stable since the release in October, even though I have been updating regularly as new packages for Intrepid come out. -- crashes with "pure virtual method called;terminate called without an active exception" https://bugs.launchpad.net/bugs/301596 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 301596] [NEW] crashes with "pure virtual method called; terminate called without an active exception"
Public bug reported: version is 2.0.6-2 on i386. System is running the Intrepid release, all packages up to date. I was connected to an HTTPS site. After a few form submissions, the browser crashes and burns, On the terminal I launched the program from was this message: pure virtual method called terminate called without an active exception The startup sequence: ub$ /bin/rm -rf ~/.galeon ub$ galeon& ** (galeon:11973): WARNING **: I could not load the bookmarks file, will load the default bookmarks from /usr/share/galeon/default-bookmarks.xbel. I'm reporting this because I was getting the same kind of problem (sudden crash) with firefox, which I finally got sick of and uninstalled. I didn't see any error messages from firefox. This also happens with epiphany, it fails with 'Segmentation fault'. ** Affects: galeon (Ubuntu) Importance: Undecided Status: New -- crashes with "pure virtual method called;terminate called without an active exception" https://bugs.launchpad.net/bugs/301596 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 243504] Re: mythtv-setup: unable to connect to database
ugh - i hate launchpad. it just lost my entire post. I went back through my notes. They leave a little to be desired... At the time I installed the "mythtv" metapackage, I did not have support for my DVB-T card working. It is a Dvico model that is not yet supported by the mainline v4l tree. (I got it working with the branch made available by Chris Pascoe back in December 2007). So, I would probably have answered many debconf questions by taking the default. I don't think I would have given unusable inputs. I would not have had mysql-5.0-server installed at the time, I would have let the installation of mythtv pull it in as a dependency. My notes tell me: * I installed "mythtv" and debconf told me I need to run "mythtv-setup" as a member of the mythtv group. * I added my unpriviledged account to that group * I ran sudo /etc/init.d/mythtv-backend start I answered "no" to the question about "remote access" * I installed mythexport * I installed mythwe I did not set a mythweb password. * Something prompted me for a "mythtv p/w", which was stored in /etc/mythtv/mysql.txt. This appears to be the user for the mythtv tables in the database. I do not recall getting prompted for a mysql 'administrator/root' user at this time; my notes would have recorded the password. * I ran dpkg-reconfigure lirc I also went and poked at my debconf database; below I show the output of debconf-get-selections | grep -A 0 -B 1 mythtv; debconf-get-selections | grep -A 0 -B 1 mysql Most of these would be the original answers; the only dpkg-reconfigure changes I have made should be in the posts I have already made to this bug. In particular - mythtv-common:mythtv/mysql_mythtv_password was the value I have in my notes on paper, but mythtv-database:mythtv/mysql_admin_password is the value I set when I ran dpkg-reconfigure. I don't recall having to set it before and would not have used the same value. Hope this sheds some light. Vince -- debconf data --- $ debconf-get-selections | grep -A 0 -B 1 mythtv; # What password should MythTV use to access its database: mythtv-common mythtv/mysql_mythtv_passwordpassword -- # What is the password for the MySQL administrator account 'root': mythtv-database mythtv/mysql_admin_password password -- # Choices: NTSC, PAL, SECAM, PAL-NC, PAL-M, PAL-N, NTSC-JP mythtv-common mythtv/tv_formatselect NTSC -- # Update the system MOTD? mythtv-status mythtv-status/enableboolean true -- # A backup of your database will be made mythtv-database mythtv/backup_dbnote -- # What is the name of the MySQL administrator account: mythtv-database mythtv/mysql_admin_user string root -- # Is it OK to create the video4linux device nodes? mythtv-backend mythtv/create_v4l_devs boolean true -- # Will you be using other computers running MythTV? mythtv-database mythtv/public_bind boolean false -- # Warning! These packages are experimental! Install? mythtv-common mythtv/svn_warning boolean -- # The Ubuntu MythTV packages generate a random MySQL password. mythtv-common mythtv/display_password note # On what host does the MySQL server reside: mythtv-common mythtv/mysql_host string localhost -- tzdata tzdata/Zones/Europe select # mythtv-setup must be run in order to complete MythTV installation mythtv-backend mythtv/run_setupnote mythtv-common mythtv/run_setupnote -- # Install canceled! mythtv-common mythtv/abort_svn_installnote -- # Choices: tv_grab_de, tv_grab_na, tv_grab_sn, tv_grab_uk, tv_grab_uk_rt mythtv-common mythtv/grabber select tv_grab_na -- # MythTV backend to check: mythtv-status mythtv-status/host string localhost -- # What username should MythTV use to access its database: mythtv-common mythtv/mysql_mythtv_userstring mythtv -- # Send email status to: mythtv-status mythtv-status/email string none -- # WARNING: old MythTV binaries found mythtv-common mythtv/old_bins note -- # Choices: us-bcast, us-cable, us-cable-hrc, japan-bcast, japan-cable, europe-west, europe-east, italy, newzealand, australia, ireland, france, china-bcast, southafrica, argentina, canada-cable, australia-optus mythtv-common mythtv/freqtableselect us-cable # What database should be used to hold MythTV data: mythtv-common mythtv/mysql_mythtv_dbname string mythconverg $ debconf-get-selections | grep -A 0 -B 1 mysql # Repeat password for the MySQL "root" user: mysql-server-5.0mysql-server/root_password_againpassword # What password should MythTV use to access its database: mythtv-common mythtv/mysql_mythtv_passwordpassword -- # New password for the MySQL "root" user: mysql-server-5.0mysql-server/root_password password # What is the password for the MySQL administrator account 'root': mythtv-database mythtv/mysql_admin_password passwo
[Bug 243504] Re: mythtv-setup: unable to connect to database
$ sudo aptitude --purge remove mythtv-database
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are BROKEN:
mythtv
The following packages will be REMOVED:
mythtv-database
0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 279kB will be freed.
The following packages have unmet dependencies:
mythtv: Depends: mythtv-database (= 0.21.0+fixes16838-0ubuntu3.1) but it is
not installable
Resolving dependencies...
The following actions will resolve these dependencies:
Remove the following packages:
mythtv
Score is 119
Accept this solution? [Y/n/q/?]
The following packages are unused and will be REMOVED:
libfame-0.9{p} libhtml-template-perl{p} liblzo1{p} libmjpegtools0c2a{p}
libpvm3{p} mjpegtools{p} mysql-server{p} mysql-server-5.0{p}
mythtv-backend{p} mythtv-themes{p} mythtv-transcode-utils{p} ntp{p}
pvm{p} toolame{p} transcode{p} transcode-doc{p}
The following packages will be automatically REMOVED:
mythtv
The following packages will be REMOVED:
mythtv mythtv-database
0 packages upgraded, 0 newly installed, 18 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 101MB will be freed.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
(Reading database ... 150712 files and directories currently installed.)
Removing mythtv ...
(Reading database ... 150703 files and directories currently installed.)
Removing mythtv-backend ...
* Stopping MythTV server: mythbackend [ OK ]
Purging configuration files for mythtv-backend ...
Removing mythtv-transcode-utils ...
Removing transcode ...
Removing libfame-0.9 ...
Purging configuration files for libfame-0.9 ...
Removing libhtml-template-perl ...
Removing liblzo1 ...
Purging configuration files for liblzo1 ...
Removing mjpegtools ...
Removing libmjpegtools0c2a ...
Purging configuration files for libmjpegtools0c2a ...
Removing pvm ...
Removing libpvm3 ...
Removing mysql-server ...
Removing mysql-server-5.0 ...
* Stopping MySQL database server mysqld [ OK ]
Purging configuration files for mysql-server-5.0 ...
Processing triggers for libc6 ...
ldconfig deferred processing now taking place
(Reading database ... 148202 files and directories currently installed.)
Removing mythtv-database ...
(Reading database ... 148189 files and directories currently installed.)
Removing mythtv-themes ...
Removing ntp ...
* Stopping NTP server ntpd [ OK ]
Purging configuration files for ntp ...
Removing toolame ...
Removing transcode-doc ...
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Building tag database... Done
(I said 'yes' when prompted about removing all mysql databases.)
~$ sudo aptitude install mythtv
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following NEW packages will be automatically installed:
libfame-0.9 libhtml-template-perl liblzo1 libmjpegtools0c2a libpvm3
mjpegtools mysql-server mysql-server-5.0 mythtv-backend mythtv-themes
mythtv-transcode-utils ntp pvm toolame transcode transcode-doc
The following NEW packages will be installed:
libfame-0.9 libhtml-template-perl liblzo1 libmjpegtools0c2a libpvm3
mjpegtools mysql-server mysql-server-5.0 mythtv mythtv-backend
mythtv-themes mythtv-transcode-utils ntp pvm toolame transcode
transcode-doc
0 packages upgraded, 17 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B/33.3MB of archives. After unpacking 101MB will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Preconfiguring packages ...
Selecting previously deselected package mysql-server-5.0.
(Reading database ... 148071 files and directories currently installed.)
Unpacking mysql-server-5.0 (from
.../mysql-server-5.0_5.0.51a-3ubuntu5.1_i386.deb) ...
Selecting previously deselected package libfame-0.9.
Unpacking libfame-0.9 (from .../libfame-0.9_0.9.1-0.2_i386.deb) ...
Selecting previously deselected package liblzo1.
Unpacking liblzo1 (from .../liblzo1_1.08-3_i386.deb) ...
Selecting previously deselected package libmjpegtools0c2a.
Unpacking libmjpegtools0c2a (from
.../libmjpegtools0c2a_1%3a1.8.0-0.2ubuntu5_i386.deb) ...
Selecting previously deselected package libpvm3.
Unpacking libpvm3 (from .../libpvm3_3.4.5-10_i386.deb) ...
Selecting previously deselected package transcode.
Unpacking transcode (from .../transcode_2%3a1.
[Bug 243504] [NEW] mythtv-setup: unable to connect to database
Public bug reported: Binary package hint: mythtv-backend $ dpkg -l mythtv-backend ii mythtv-backend 0.21.0+fixes16838-0 A personal video recorder application (server) $ lsb_release -rd Description:Ubuntu 8.04 Release:8.04 what happens - I cannot complete the configuration of mythtv with mythtv-setup. This appears to be because the mysql database is not fully populated. what should happen - I should be able to set up mythtv. Background information $ id uid=1000(vjm) gid=1000(vjm) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),107(fuse),110(lpadmin),120(admin),125(mysql),126(mythtv),1000(vjm) $ sudo /etc/init.d/mysql status * /usr/bin/mysqladmin Ver 8.41 Distrib 5.0.51a, for debian-linux-gnu on i486 Copyright (C) 2000-2006 MySQL AB This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to modify and redistribute it under the GPL license Server version 5.0.51a-3ubuntu5.1 Protocol version10 Connection Localhost via UNIX socket UNIX socket /var/run/mysqld/mysqld.sock Uptime: 1 hour 25 min 56 sec Threads: 1 Questions: 43 Slow queries: 0 Opens: 23 Flush tables: 1 Open tables: 17 Queries per second avg: 0.008 $ ps -fade|grep myth mythtv8983 1 0 22:22 ?00:00:06 /usr/bin/mythbackend --daemon --logfile /var/log/mythtv/mythbackend.log --pidfile /var/run/mythtv/mythbackend.pid vjm 9178 6809 0 22:34 pts/000:00:00 grep myth What I tried to do: $ mythtv-setup (I get a popup asking to close any running mythbackends. I say OK) (I get a small xterm with error messages in it, saying unable to connect to database. Could not capture this for you, because a fullscreen display suddenly appears) The fullscreen display prompts for things like database name, user , password. I left these as defaults, and hit immediately. (Oh, and it shows "No UPnP devices available", to which I say "OK" since there is nothing else to say. On the original terminal I get: * Stopping MythTV server: mythbackend [ OK ] * Restarting MythTV server: mythbackend No /usr/bin/mythbackend found running; none killed. [ OK ] (I get another popup, would you like to run mythfilldatabase?) yet, I am able to connect to mysql as [EMAIL PROTECTED], with no password. $ mysql -u [EMAIL PROTECTED] Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 87923 Server version: 5.0.51a-3ubuntu5.1 (Ubuntu) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> show databases; ++ | Database | ++ | information_schema | ++ 1 row in set (0.00 sec) mysql> use mythconverg; ERROR 1044 (42000): Access denied for user ''@'localhost' to database 'mythconverg' mysql> quit Bye I checked for .my.cnf files and so forth, could find none in my home dir nor in /home/mythtv. The closest thing was the .mythtv/mysql.txt file; $ grep -v ^# /home/mythtv/.mythtv/mysql.txt DBHostName=localhost DBHostPing=no DBUserName=mythtv DBName=mythconverg DBType= DBPassword=0ciB7wRh $ sudo dpkg-reconfigure mythtv < does nothing.> $ sudo dpkg-reconfigure mythtv-backend Then it asks me to run mythtv-setup. oh. Well that's going to be a problem. Then I have to start mythtv-backend again. Try that anyway: $ /etc/init.d/mythtv-backend stop $ /etc/init.d/mythtv-backend start (no errors, let's stop again) $ /etc/init.d/mythtv-backend stop $ mythtv-setup does not seem to help. ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- mythtv-setup: unable to connect to database https://bugs.launchpad.net/bugs/243504 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 243504] Re: mythtv-setup: unable to connect to database
I tried a complete purge/reinstall cycle. $ sudo aptitide --purge remove mythtv $ sudo aptitude --purge remove mythtv-backend $ sudo aptitude --purge remove mythtv-frontend $ sudo aptitude --purge remove mythtv-common $ sudo aptitude update $ sudo aptitude upgrade $ sudo aptitude install mythtv $ mythtv-setup I get the same behaviour. NB: If I say OK to the "mythfilldatabase" popup prompt, I got the fllowing in an xterm titled "running mythfilldatabase" - 2008-06-27 23:12:05.490 Using runtime prefix = /usr, libdir = /usr/lib 2008-06-27 23:12:05.491 Using localhost value of wellington 2008-06-27 23:12:05.497 New DB connection, total: 1 2008-06-27 23:12:05.500 Unable to connect to database! 2008-06-27 23:12:05.500 Driver error was [1/1045]: QMYSQL3: Unable to connect Database error was: Access denied for user 'mythtv'@'localhost' (using password: YES) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2008-06-27 23:12:05.550 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... QServerSocket: failed to bind or listen to the socket 2008-06-27 23:12:05.601 MCP::InitUPnP() - HttpServer Create Error 2008-06-27 23:12:05.601 Deleting UPnP client... 2008-06-27 23:12:05.601 No UPnP backends found No UPnP backends found Would you like to configure the database connection now? [yes] Database host name: [localhost] Should I test connectivity to this host using the ping command? [yes] Database non-default port: [0] Database name: [mythconverg] Database user name: [mythtv] Database password: [0ciB7wRh] Unique identifier for this machine (if empty, the local host name will be used): [wellington] Would you like to use Wake-On-LAN to retry database connections? [no] 2008-06-27 23:13:31.942 Unable to connect to database! 2008-06-27 23:13:31.942 Driver error was [1/1045]: QMYSQL3: Unable to connect Database error was: Access denied for user 'mythtv'@'localhost' (using password: YES) QSqlQuery::exec: database not open QSqlQuery::exec: database not open 2008-06-27 23:13:31.993 DB Error (KickDatabase): Query was: SELECT NULL; No error type from QSqlError? Strange... 2008-06-27 23:13:32.043 Cannot login to database? 2008-06-27 23:13:32.043 Cannot login to database? Cannot login to database? Would you like to configure the database connection now? [yes] and so on, endlessly... -- mythtv-setup: unable to connect to database https://bugs.launchpad.net/bugs/243504 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 154630] virtualbox-ose-modules-2.6.22-14-generic: fails to create /dev/vboxdrv
Public bug reported: Summary: On install I get an error message about an invalid group, which seems incorrect. The actual problem is the /dev device is not created. Possibly because there is a missing 'modprobe' call? Here's what actually happened: $ sudo apt-get upgrade (nothing to do) $ sudo apt-get install virtualbox ... The following extra packages will be installed: libxalan110 libxerces27 virtualbox-ose virtualbox-ose-modules-2.6.22-14-generic ... Unpacking virtualbox-ose-modules-2.6.22-14-generic (from .../virtualbox-ose-modules-2.6.22-14-generic_6_i386.deb) ... Selecting previously deselected package virtualbox-ose. Unpacking virtualbox-ose (from .../virtualbox-ose_1.5.0-dfsg2-1ubuntu3_i386.deb) ... Setting up libxerces27 (2.7.0-3) ... Setting up libxalan110 (1.10-3.1) ... Setting up virtualbox-ose-modules-2.6.22-14-generic (6) ... * Starting VirtualBox kernel module vboxdrv chown: `:vboxusers': invalid group * Cannot change owner vboxusers for device /dev/vboxdrv. Setting up virtualbox-ose (1.5.0-dfsg2-1ubuntu3) ... Processing triggers for libc6 ... ldconfig deferred processing now taking place $ grep vbox /etc/group vboxusers:x:120: $ ls -l /dev/vboxdrv ls: /dev/vboxdrv: No such file or directory $ ls -l /dev/vb* ls: /dev/vb*: No such file or directory $ lsmod|grep -c vb 0 $ find /lib/modules/2.6.22-14-generic/ -type f -name "*vbo*" /lib/modules/2.6.22-14-generic/misc/vboxdrv.ko $ sudo modprobe -v vboxdrv insmod /lib/modules/2.6.22-14-generic/misc/vboxdrv.ko ~$ ls -l /dev/vb* crw-rw 1 root root 10, 62 2007-10-20 09:09 /dev/vboxdrv $ sudo chgrp vboxusers /dev/vboxdrv $ ls -l /dev/vb* crw-rw 1 root vboxusers 10, 62 2007-10-20 09:09 /dev/vboxdrv running gutsy $ uname -a Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux ** Affects: ubuntu Importance: Undecided Status: New -- virtualbox-ose-modules-2.6.22-14-generic: fails to create /dev/vboxdrv https://bugs.launchpad.net/bugs/154630 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 149106] Re: package cupsys 1.3.2-1ubuntu4 failed to install/upgrade: trying to overwrite `/usr/share/doc/libcupsys2/CREDITS.txt', which is also in package libcupsys2
I had the same error as the initial report. However when trying to install the .deb by force, I get further errors, see below. So that method won't work for all cases. $ sudo dpkg -i --force-overwrite /var/cache/apt/archives/cupsys_1.3.2-1ubuntu4_i386.deb (Reading database ... 162129 files and directories currently installed.) Preparing to replace cupsys 1.3.2-1ubuntu1 (using .../cupsys_1.3.2-1ubuntu4_i386.deb) ... Ignoring nonregistered document cupsys * Stopping Common Unix Printing System: cupsd [ OK ] Unpacking replacement cupsys ... dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/doc/libcupsys2/CREDITS.txt', which is also in package libcupsys2 dpkg - warning, overriding problem because --force enabled: trying to overwrite `/usr/share/doc/libcupsys2/README.txt.gz', which is also in package libcupsys2 dpkg: dependency problems prevent configuration of cupsys: cupsys depends on libavahi-compat-libdnssd1 (>= 0.6.13); however: Package libavahi-compat-libdnssd1 is not configured yet. cupsys depends on libcupsimage2 (>= 1.3.0); however: Package libcupsimage2 is not configured yet. cupsys depends on libcupsys2 (>= 1.3.0); however: Package libcupsys2 is not configured yet. cupsys depends on cupsys-common; however: Package cupsys-common is not configured yet. dpkg: error processing cupsys (--install): dependency problems - leaving unconfigured Errors were encountered while processing: cupsys -- package cupsys 1.3.2-1ubuntu4 failed to install/upgrade: trying to overwrite `/usr/share/doc/libcupsys2/CREDITS.txt', which is also in package libcupsys2 https://bugs.launchpad.net/bugs/149106 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 141391] postinstall fails if /usr/local is readonly
Public bug reported: Binary package hint: python2.5-dbg Version: 2.5-2ubuntu2 Severity: normal Hi, this was a problem with TeTex for a while too, but they worked around it. The /usr/local partition is an NFS mount and is not writeable by all hosts, including the one showing this issue. I can probably just create the directory it wants and have the update succeed but I thought the policy was to leave /usr/local alone. Here's what happens # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: linux-headers-server linux-image-generic linux-restricted-modules-generic 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? Setting up python2.5-dbg (2.5-2ubuntu2) ... mkdir: cannot create directory `/usr/local/lib/python2.5': Read-only file system dpkg: error processing python2.5-dbg (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: python2.5-dbg E: Sub-process /usr/bin/dpkg returned an error code (1) Thanks for your time, Vince -- System Information: Debian Release: testing/unstable APT prefers edgy-updates APT policy: (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy-backports'), (500, 'edgy') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-11-generic Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) ** Affects: python2.5 (Ubuntu) Importance: Undecided Status: New -- postinstall fails if /usr/local is readonly https://bugs.launchpad.net/bugs/141391 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 71599] doesn't create /var/crash (?)
Public bug reported: This occurred on a machine that has been dist-upgraded from breezy to etch and all the points in between, with official sources. If apport is installed, the /etc/cron.daily/apport script tries to run a find over /var/crash and that directory may not actually be there. This generates irritating emails to root. If the other bits of apport create /var/crash at the time of the first crash after installation, then perhaps the cron.daily needs this patch: --- apport.old 2006-10-10 00:49:47.0 +1000 +++ apport 2006-11-13 15:50:17.0 +1100 @@ -1,4 +1,5 @@ #!/bin/sh -e # clean all crash reports which are older than a week. +[ -d /var/crash ] || exit 0 find /var/crash -mindepth 1 -mtime +7 -print0 | xargs -0 rm -f find /var/crash -mindepth 1 -empty -print0 | xargs -0 rm -f dpkg -l python-problem-report python-apport-utils apport ii apport 0.28 automatically generate crash reports for deb ii python-apport- 0.28 apport crash report handling functions ii python-problem 0.28 python library to handle problem reports ** Affects: apport (Ubuntu) Importance: Undecided Status: Unconfirmed -- doesn't create /var/crash (?) https://launchpad.net/bugs/71599 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
