[Bug 1140716] Re: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge
I was still having this bug on a fresh install of 14.04 (kernel 3.13.0-24-generic). Strangely, since setting i915.semaphores=1 (suggested at http://askubuntu.com/questions/50033/unity-gui-pauses- freezes-for-less-than-a-few-seconds/ all the way back in 2011) I no longer get hangs. The default value of i915.semaphores seems to be -1 (according to `cat /sys/module/i915/parameters/semaphores`) and the advice elsewhere of setting i915.semaphores=0 had no effect for me. Hardware: i3-2120 (Sandy Bridge HD 2000 graphics) + Asus P8H61-M PRO motherboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1140716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 476455] Re: Broken new launcher dialog in quick-lounge-applet
This bug is *still* present in Maverick, which is unsurprising since it's the exact same package. -- Broken new launcher dialog in quick-lounge-applet https://bugs.launchpad.net/bugs/476455 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 631030] [NEW] No input for hostname during installation
Public bug reported: Binary package hint: ubiquity The installer on the Maverick amd64 beta CD has no input for hostname in the installer. Instead, the default of username-laptop or username-desktop is used. Previously an input for the hostname was supplied pre-filled with this default hostname. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic x86_64 Architecture: amd64 Date: Sun Sep 5 19:13:33 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) ProcEnviron: PATH=(custom, no user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: ubiquity ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- No input for hostname during installation https://bugs.launchpad.net/bugs/631030 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 631030] Re: No input for hostname during installation
** Attachment added: Casper.gz https://bugs.launchpad.net/bugs/631030/+attachment/1547072/+files/Casper.gz ** Attachment added: UbiquityDebug.gz https://bugs.launchpad.net/bugs/631030/+attachment/1547073/+files/UbiquityDebug.gz ** Attachment added: UbiquityPartman.gz https://bugs.launchpad.net/bugs/631030/+attachment/1547074/+files/UbiquityPartman.gz ** Attachment added: UbiquitySyslog.gz https://bugs.launchpad.net/bugs/631030/+attachment/1547075/+files/UbiquitySyslog.gz -- No input for hostname during installation https://bugs.launchpad.net/bugs/631030 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 631030] Re: No input for hostname during installation
*** This bug is a duplicate of bug 628087 *** https://bugs.launchpad.net/bugs/628087 ** This bug has been marked a duplicate of bug 628087 Maverick ubiquity lacks option to change computer name -- No input for hostname during installation https://bugs.launchpad.net/bugs/631030 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 628087] Re: Maverick ubiquity lacks option to change computer name
Having to change the hostname post-install is made more awkward by the fact that it's not just one place it needs to be changed. At the very least you need to change it in /etc/hosts and /etc/hostname, but also some programs (I think postfix is one that springs to mind, but there might be others less server-oriented) like to make copies of whatever the hostname is at the time of installation, making it much more likely to have an inconsistent setup. Having multiple computers with the same name certainly has opportunities to be a real pain, especially when casually sharing files between computers on a network (which alan-desktop do I click on?). And while I understand wanting to make the install process easy and streamlined, I think Lucid had it just right - set a default, but allow it to be changed right there and then. Hide it behind something if necessary, but don't remove it. I think this should be higher priority than it is. It's a trivial UI change (if it's time that's the problem, I know I'd be happy to write a patch), and more importantly the consequence of not fixing it is frustrating installs for anybody who might slightly care about this setting for 6 months. It's fine to say it'll be fixed in the next release, but that doesn't help for the half a year in the meantime! -- Maverick ubiquity lacks option to change computer name https://bugs.launchpad.net/bugs/628087 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 575066] Re: Xorg crashed with SIGSEGV in XIChangeDeviceProperty()
Oh well, another bug successfully waited out... The bug wasn't present in Fedora 13 (which froze on more recent packages than Lucid) and it isn't present in Maverick beta. Looks like Lucid just happened to sync a buggy version. -- Xorg crashed with SIGSEGV in XIChangeDeviceProperty() https://bugs.launchpad.net/bugs/575066 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 575052] [NEW] Xorg segfault on xsetwacom rotate
Public bug reported: I'm attempting to set up some form of auto-screen-rotate script on my Lenovo X200 tablet, but whenever I attempt to execute xsetwacom set stylus rotate cw Xorg segfaults, leaving the following message in logs: [ 638.519704] Xorg[2216]: segfault at 18 ip 7fece33247ce sp 7fffd00b7980 error 4 in wacom_drv.so[7fece331c000+12000] ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 Date: Tue May 4 11:54:39 2010 DkmsStatus: vboxnetadp, 3.1.6, 2.6.32-21-generic, x86_64: installed vboxnetflt, 3.1.6, 2.6.32-21-generic, x86_64: installed vboxdrv, 3.1.6, 2.6.32-21-generic, x86_64: installed InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) MachineType: LENOVO 7448CTO ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=5f4225f1-a2bd-436b-b88b-2a69a4c29c79 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display Title: Xorg crash dmi.bios.date: 09/03/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7WET59WW (3.09 ) dmi.board.name: 7448CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7WET59WW(3.09):bd09/03/2009:svnLENOVO:pn7448CTO:pvrThinkPadX200T:rvnLENOVO:rn7448CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7448CTO dmi.product.version: ThinkPad X200T dmi.sys.vendor: LENOVO glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-generic ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash lucid -- Xorg segfault on xsetwacom rotate https://bugs.launchpad.net/bugs/575052 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 575052] Re: Xorg segfault on xsetwacom rotate
** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/47785794/BootDmesg.txt ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/47785795/CurrentDmesg.txt ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/47785796/Dependencies.txt ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/47785797/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/47785798/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/47785799/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/47785800/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/47785801/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/47785802/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/47785803/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/47785804/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/47785805/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/47785806/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/47785807/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/47785808/UdevLog.txt ** Attachment added: XorgConf.txt http://launchpadlibrarian.net/47785809/XorgConf.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/47785810/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/47785811/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/47785812/Xrandr.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/47785813/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/47785814/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/47785815/xkbcomp.txt -- Xorg segfault on xsetwacom rotate https://bugs.launchpad.net/bugs/575052 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 476455] Re: Broken new launcher dialog in quick-lounge-applet
This bug is still present in Lucid. -- Broken new launcher dialog in quick-lounge-applet https://bugs.launchpad.net/bugs/476455 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 575052] Re: Xorg segfault on xsetwacom rotate
*** This bug is a duplicate of bug 575066 *** https://bugs.launchpad.net/bugs/575066 ** This bug has been marked a duplicate of bug 575066 Xorg crashed with SIGSEGV in XIChangeDeviceProperty() ** Changed in: xf86-input-wacom (Ubuntu) Status: New = Invalid -- Xorg segfault on xsetwacom rotate https://bugs.launchpad.net/bugs/575052 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 556373] Re: Ubiquity shows no partition table changes warning despite selecting use entire disk
This bug is still present in the Beta 2 installer, even after running update this installer. The exact circumstances are using Erase and use the entire disk when the disk has no partition layout. If Erase and use the entire disk is selected when the disk already has partitions, then the correct breakdown of actions is displayed. This is very much an edge case, since it's rare to install on a completely blank disk, EXCEPT in the case of Virtual machines for testing purposes (how I found it). This also probably explains why Erick was unable to reproduce the bug - once his disk had a partition table, the bug no longer appeared. ** Attachment added: no-partition-changes.png http://launchpadlibrarian.net/43545283/no-partition-changes.png -- Ubiquity shows no partition table changes warning despite selecting use entire disk https://bugs.launchpad.net/bugs/556373 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 476455] Re: Broken new launcher dialog in quick-lounge-applet
I also cannot reproduce the bug either in Jaunty or running the Jaunty version of the package in Karmic. -- Broken new launcher dialog in quick-lounge-applet https://bugs.launchpad.net/bugs/476455 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 366428] Re: Logitech MX1000 mouse generating XF86Audio* keypress events
I'm not sure when or why, but this problem seems to be fixed now... ** Changed in: xserver-xorg-input-evdev (Ubuntu) Status: New = Invalid -- Logitech MX1000 mouse generating XF86Audio* keypress events https://bugs.launchpad.net/bugs/366428 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 366428] [NEW] Logitech MX1000 mouse generating XF86Audio* keypress events
Public bug reported: Binary package hint: xorg Since Jaunty, I've found that my Logitech MX1000 wireless mouse generates key events for some mouse button clicks, rather than the expected button events. For example, when clicking the middle of the three buttons on the left side of the mouse (previously button 9) generates XF86AudioPlay KeyPress events. Here is the output from xev when I click the button: - KeyPress event, serial 30, synthetic NO, window 0x3e1, root 0x13c, subw 0x0, time 3416337, (1,174), root:(1292,220), state 0x10, keycode 208 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES, XKeysymToKeycode returns keycode: 172 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 34, synthetic NO, window 0x3e1, root 0x13c, subw 0x0, time 3416497, (1,174), root:(1292,220), state 0x10, keycode 208 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES, XKeysymToKeycode returns keycode: 172 XLookupString gives 0 bytes: XFilterEvent returns: False - When I press the *real* play/pause button, this is what I get (pretty much exactly the same!): - KeyPress event, serial 37, synthetic NO, window 0x181, root 0x13c, subw 0x0, time 3673352, (3,160), root:(1294,206), state 0x10, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x181, root 0x13c, subw 0x0, time 3673440, (3,160), root:(1294,206), state 0x10, keycode 172 (keysym 0x1008ff14, XF86AudioPlay), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False - Also, the horizontal scrolling generates XF86AudioRaiseVolume and XF86AudioLowerVolume for left and right respectively. All other mouse buttons correctly generate ButtonPress events with the correct button numbers. What's even more interesting is that I use xbindkeys to map my audio keys to mpc commands, and these events aren't caught by xbindkeys, but they are caught by GNOME's keyboard shortcut mechanism if I set something to use them there. I have no other mouse- or keyboard- mangling utilities installed. I'm running a fresh install of Jaunty 64-bit with all updates applied. This bug was present in the beta, RC and final releases, but not in Intrepid. If anybody knows of a way to trace where the mouse button event goes, let me know and I'll see what other information I can dig up! ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- Logitech MX1000 mouse generating XF86Audio* keypress events https://bugs.launchpad.net/bugs/366428 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 227033] Re: linux kernel socket deadlock (ndiswrapper?)
The issue was not solved by any version of ndiswrapper (also, the latest in Hardy is newer than 1.52). I tried running ndiswrapper with a higher debug setting, but because of the seeming randomness of the bug, the log files filled and caused problems before the ndiswrapper bug manifested itself, so I still had no debug output from the actual breakage when it occurred. -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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 227033] Re: linux kernel socket deadlock (ndiswrapper?)
This bug should possibly be closed - I wanted to move to 64-bit, where a (possibly different) bug was causing a kernel panic for me (but definitely related to the wireless card), so I've bought a more Linux- compatible device, using neither ndiswrapper nor a Marvell chipset. -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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 227033] Re: linux kernel socket deadlock (ndiswrapper?)
I'll give the latest ndiswrapper a try and report back when I can tell if the bug still exists or not. Thanks =) -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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 227033] Re: linux kernel socket deadlock (ndiswrapper?)
** Attachment added: lspci -vvnn http://launchpadlibrarian.net/14234248/lspci-vvnn.log ** Description changed: The occurrence of this bug is seemingly random, but happens to me on average once a day (but twice while writing this). Effectively, all of my TCP connections do nothing, and any new programs I start which use sockets in any way hang until I resolve the problem. Solving the problem involves making NetworkManager stop the network connection (usually by telling it to reconnect). When I do this I get the following in dmesg: [15824.027472] ndiswrapper (set_scan:1212): scanning failed (C001) [15824.277080] ndiswrapper (set_essid:59): setting essid failed (C001) [15825.861715] ndiswrapper (set_essid:59): setting essid failed (C001) [15826.111890] ndiswrapper (set_essid:59): setting essid failed (C001) However all of the processes that hung before catch up when I do this. To regain use of my wireless I have to reload the ndiswrapper module (rmmod ndiswrapper ; modprobe ndiswrapper). At this point, everything is back to normal. I say that it's anything using sockets because most programs that are self-contained work fine when in this state, but things that fail to work tend to be using networking, or GNOME settings daemon (e.g. gnome- terminal, nautilus), or some other form of socket-based thing (I never knew sudo used sockets, but apparently it does!). It took me quite a while to consider the networking to be the problem, but everything started working again when I killed the network connection. I'm thinking maybe this is some kind of deadlock somewhere to do with socket handling, which only gets resolves when a load of TCP connections get dropped. Unfortunately I'm not intimately familiar with the Linux kernel so I'm not sure where to look. Uname: Linux iapetus 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux Version: Ubuntu 2.6.24-16.30-generic + Using ndiswrapper with Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03) device Let me know what else is needed (I'll attach the usual dmesg and lspci info). -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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 227033] Re: linux kernel socket deadlock (ndiswrapper?)
** Attachment added: dmesg http://launchpadlibrarian.net/14234235/dmesg.log -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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 227033] [NEW] linux kernel socket deadlock (ndiswrapper?)
Public bug reported: The occurrence of this bug is seemingly random, but happens to me on average once a day (but twice while writing this). Effectively, all of my TCP connections do nothing, and any new programs I start which use sockets in any way hang until I resolve the problem. Solving the problem involves making NetworkManager stop the network connection (usually by telling it to reconnect). When I do this I get the following in dmesg: [15824.027472] ndiswrapper (set_scan:1212): scanning failed (C001) [15824.277080] ndiswrapper (set_essid:59): setting essid failed (C001) [15825.861715] ndiswrapper (set_essid:59): setting essid failed (C001) [15826.111890] ndiswrapper (set_essid:59): setting essid failed (C001) However all of the processes that hung before catch up when I do this. To regain use of my wireless I have to reload the ndiswrapper module (rmmod ndiswrapper ; modprobe ndiswrapper). At this point, everything is back to normal. I say that it's anything using sockets because most programs that are self-contained work fine when in this state, but things that fail to work tend to be using networking, or GNOME settings daemon (e.g. gnome- terminal, nautilus), or some other form of socket-based thing (I never knew sudo used sockets, but apparently it does!). It took me quite a while to consider the networking to be the problem, but everything started working again when I killed the network connection. I'm thinking maybe this is some kind of deadlock somewhere to do with socket handling, which only gets resolves when a load of TCP connections get dropped. Unfortunately I'm not intimately familiar with the Linux kernel so I'm not sure where to look. Uname: Linux iapetus 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux Version: Ubuntu 2.6.24-16.30-generic Using ndiswrapper with Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03) device Let me know what else is needed (I'll attach the usual dmesg and lspci info). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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 227033] Re: linux kernel socket deadlock (ndiswrapper?)
I haven't noticed any particular correlation between events and the bug occurring, so there are no steps I know of which will definitely reproduce this bug. I'll keep an eye out for any common factors. This is a desktop machine, and as far as I can tell I've only had this problem since using wireless (in both Gutsy and Hardy). Like I said, I still have use of the machine after fixing the problem, so let me know of any information I should gather the next time it happens that would help narrow it down. -- linux kernel socket deadlock (ndiswrapper?) https://bugs.launchpad.net/bugs/227033 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 117947] Re: Smart battery doesn't work with feisty
*** This bug is a duplicate of bug 117773 *** https://bugs.launchpad.net/bugs/117773 ** This bug has been marked a duplicate of bug 117773 Kernel 2.6.20-16 breaks Toshiba battery ACPI support -- Smart battery doesn't work with feisty https://bugs.launchpad.net/bugs/117947 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 117773] Re: Kernel 2.6.20-16 breaks Toshiba battery ACPI support
** Attachment added: dmesg for 2.6.20-15-386 http://librarian.launchpad.net/7880393/dmesg-2.6.20-15-386.txt -- Kernel 2.6.20-16 breaks Toshiba battery ACPI support https://bugs.launchpad.net/bugs/117773 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 117773] Re: Kernel 2.6.20-16 breaks Toshiba battery ACPI support
** Attachment added: dmesg for 2.6.20-16-386 http://librarian.launchpad.net/7880404/dmesg-2.6.20-16-386.txt -- Kernel 2.6.20-16 breaks Toshiba battery ACPI support https://bugs.launchpad.net/bugs/117773 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 117773] Kernel 2.6.20-16 breaks Toshiba battery ACPI support
Public bug reported: Binary package hint: linux-image-2.6.20-16-386 Using the 2.6.20-16-386 kernel for some reason stops ACPI battery details from turning up in /proc/acpi/battery/ , which in turn removes functionality from things such as gnome-power-manager because no battery information can be determined. Booting on 2.6.20-15-386 kernel does result in this information being available. I'll attach a dmesg for both boots. ** Affects: linux-source-2.6.20 (Ubuntu) Importance: Undecided Status: Unconfirmed -- Kernel 2.6.20-16 breaks Toshiba battery ACPI support https://bugs.launchpad.net/bugs/117773 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 117773] Re: Kernel 2.6.20-16 breaks Toshiba battery ACPI support
Did that, still no different. -- Kernel 2.6.20-16 breaks Toshiba battery ACPI support https://bugs.launchpad.net/bugs/117773 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 82466] Re: Important improvements in new upstream stable version (0.4.0) - please update package for Ubuntu 7.04
It might be worth noting that the 0.2.x flumotion is non-working with Twisted 2.5 (bug #86573), therefore there is no working stable flumotion for an up-to-date system. -- Important improvements in new upstream stable version (0.4.0) - please update package for Ubuntu 7.04 https://bugs.launchpad.net/bugs/82466 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
