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
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.
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
** 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
*** 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
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
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()
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
** 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
**
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
*** 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
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
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
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
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
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,
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
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
** 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
** 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
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
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
*** 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
** 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
** 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
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
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
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
28 matches
Mail list logo
