Public bug reported:
Package is now trapped in residual configuration state.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: bandwidthd (not installed)
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic x86_64
ApportVersion: 2.0.1-0ubuntu9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1013428
Title:
package bandwidthd failed to uninstall cleanly: subprocess installed
post-removal script returned error exit status 128
To manage
Thanks, I found it, too, eventually. Sorry for the noise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/645351
Title:
installing libusb-1.0 on x86_64 doesn't install the 32 bit library
To manage
Actually, it doesn't appear to install the 64 bit libraries, either.
In Synaptic, libusb-1.0 (version 2:1.0.8-4) is marked as installed, but
if you open the properties for the package to view the installed files,
you're told The list of installed files is only available for installed
packages.
Public bug reported:
Binary package hint: gnuradio
grc on lucid works fine, on natty launch results in the following traceback:
--
rec@elf11:~/Projects/arftcl/gnuradio$ grc
Welcome to GNU Radio Companion 3.2.2
Error: 'options'
Failue
Traceback (most recent call
Go ahead and toss it.
The problem was in the HID driver for the joystick. I debugged the
problem, submitted a patch at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/618853, went
through the effort to build a second test kernel at the request of
https://launchpad.net/~jeremyfoshee, posted
Tested against linux-
image-2.6.36-999-generic_2.6.36-999.201009281108_amd64.deb and the bug
still exists. Ie, the joystick is detected correctly but does not
produce any input events.
** Tags removed: needs-upstream-testing
--
missing usb hid quirk for CH Products Joystick
Public bug reported:
The CH Products Flightstick Pro USB joystick is recognized by the
system, but produces no input events after the first batch of synthetic
events. Research on the linux-usb mailing list found that several other
CH Products joysticks require a hid quirk to become fully
** Patch added: flightstick.patch
https://bugs.launchpad.net/bugs/618853/+attachment/1494022/+files/flightstick.patch
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/618853/+attachment/1494023/+files/AlsaDevices.txt
** Attachment added: AplayDevices.txt
Public bug reported:
Binary package hint: flightgear
Using the current release of 9.10 and flightgear, this application locks
up my machine. I click on the menu entry or run from a command line
shell, it opens a splash window, reports several stages of
initialization, starts an aircraft engine
Public bug reported:
Binary package hint: os-prober
update-grub2 reports:
r...@elf11:~# update-grub2
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.31-9-generic
Found initrd image: /boot/initrd.img-2.6.31-9-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Microsoft
** Attachment added: one line 5 character patch to /usr/bin/linux-boot-prober
http://launchpadlibrarian.net/31470093/linux-boot-prober.patch
--
linux-boot-prober
https://bugs.launchpad.net/bugs/426061
You received this bug notification because you are a member of Ubuntu
Bugs, which is
My problem with the wacom-tools-0.8.2.2 package with my x200 tablet has
been that it doesn't use the same names for stylus, eraser, and touch
devices so neither xsetwacom nor wacomcpl work at all. As a
consequence, none of the screen rotation scripts work, and I cannot
interactively recalibrate
Same issue on a Thinkpad X200 Tablet.
** Summary changed:
- xsetwacom list dev returns nothing on x61 tablet
+ xsetwacom list dev returns nothing on x61 and other tablet
--
xsetwacom list dev returns nothing on x61 and other tablet
https://bugs.launchpad.net/bugs/358358
You received this
I'm going to confirm this and add the Lenovo X200 Tablet to the machines
referenced by this bug. These hotkey events have been available for
incorporation into acpi-support for years now, yet they still have to be
researched by users and added manually to make them work.
There are also two
Public bug reported:
Binary package hint: hal-info
A patch for
/usr/share/hal/fdi/information/10freedesktop/30-keymap-lenovo.fdi
which adds a subsection for the x200 tablet and maps tablet bezel
buttons, function shift key, and menu key correctly.
Description:Ubuntu jaunty (development
** Attachment added: 30-keymap-lenovo.patch
http://launchpadlibrarian.net/24852593/30-keymap-lenovo.patch
--
30-keymap-lenovo.fdi patch for X200 Tablet
https://bugs.launchpad.net/bugs/356019
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: firefox-3.0
Crashed while loading an applet, but successfully loaded the applet when
apport started firefox to report the bug.
This may be a duplicate of #321043, it has the same title but one
reportee says firefox is still running and another blames
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/23277079/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/23277080/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/23277081/Disassembly.txt
** Attachment
The problem cleared up not many updates after the report date.
-- rec --
On Thu, Dec 11, 2008 at 12:34 PM, Daniel T Chen crim...@fungus.sh.nu wrote:
Is this symptom still reproducible in 8.10 or 9.04?
** Changed in: d-feet (Ubuntu)
Status: New = Incomplete
--
d-feet crashed with
Public bug reported:
This is probably the Wireless-N vs iwlwifi bug from
https://bugs.launchpad.net/ubuntu/+source/linux-backports-
modules-2.6.24/+bug/244429 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/275359 in a new
form. It now just generates a kernel stack backtrace in
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/19803656/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/19803657/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/19803658/Dependencies.txt
**
There's a new bug for this problem filed against the Intrepid Ibex
kernel:
Bug #275359 in linux (Ubuntu): kernel BUG at
/build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198!https://bugs.launchpad.net/ubuntu/+source/linux/+bug/275359
you should let them know of the additional
This bug doesn't turn up when searching for bugs in Intrepid Ibex, even
though it's filed against the Intrepid Ibex kernel.
--
kernel BUG at
/build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198 and
subsequent panic
https://bugs.launchpad.net/bugs/275359
You received this bug
** Attachment added: dmesg.log
http://launchpadlibrarian.net/18093015/dmesg.log
--
kernel BUG at
/build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198!
https://bugs.launchpad.net/bugs/275359
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
kernel oops at random when running wireless. Machine locks up with
flashing caps-lock. No messages in /var/log. Kernel oops collected by
serial console.
No known trigger other than running wireless, but the oops clearly
identifies the line in the iwlwifi sources where it
** Attachment added: uname-a.log
http://launchpadlibrarian.net/18010790/uname-a.log
--
kernel BUG at
/build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198!
https://bugs.launchpad.net/bugs/275359
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: version.log
http://launchpadlibrarian.net/18010795/version.log
--
kernel BUG at
/build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198!
https://bugs.launchpad.net/bugs/275359
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/18010803/lspci-vvnn.log
** Tags added: kernel-oops
--
kernel BUG at
/build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198!
https://bugs.launchpad.net/bugs/275359
You received this bug notification because you
** Attachment added: kernel-oops-1.txt
http://launchpadlibrarian.net/18010866/kernel-oops-1.txt
--
kernel BUG at
/build/buildd/linux-2.6.27/drivers/net/wireless/iwlwifi/iwl-tx.c:1198!
https://bugs.launchpad.net/bugs/275359
You received this bug notification because you are a member of
This problem persists with linux-backports-modules-2.6.24-21 version
2.6.24-21.25, kernel oops attached.
The system ran over 48 hours with the new kernel, without the backports,
with the wireless active, and had not crashed.
With the backports installed, the system lasted less than 3.5 hours
Could we please get some attention paid to this problem?
People with totally generic hardware, Dell Latitudes, are abandoning
Ubuntu because it -- the latest long term support release -- crashes
when they attempt to use the wireless.
There's no sign that any Ubuntu developer has even read this
Because there are iwl4965.ko modules installed for both linux-ubuntu-
modules and linux-backports-modules, I picked the wrong module.
** Changed in: linux-backports-modules-2.6.24 (Ubuntu)
Sourcepackagename: linux-ubuntu-modules-2.6.24 = linux-backports-modules-2.6.24
--
kernel oops: invalid
This problem persists with the linux-backports-
modules-2.6.24-20.23-generic package released today. I attach the
kernel oops generated when this release oopsed.
** Attachment added: kernel-oops-5.txt
http://launchpadlibrarian.net/16537327/kernel-oops-5.txt
--
kernel oops: invalid opcode
linux-backports-modules-2.6.24-20.21 did not fix this problem, even with
the 4965 microcode renamed it generates essentially the same oops.
** Attachment added: kernel-oops-4.txt
http://launchpadlibrarian.net/16495703/kernel-oops-4.txt
--
kernel oops: invalid opcode
Public bug reported:
Binary package hint: linux-backports-modules-2.6.24-20-generic
The latest release of linux-backports-modules (-2.6.24-20.21) installed
a wrongly named microcode file, it generates:
Aug 2 01:19:59 elf5 firmware_helper[6528]: main: error loading
Has not happened in a long time. I'd close it.
-- rec --
On Fri, Aug 1, 2008 at 5:00 AM, Sebastien Bacher [EMAIL PROTECTED]
wrote:
could you try if that's still an issue in hardy?
** Changed in: deskbar-applet (Ubuntu)
Status: New = Incomplete
--
deskbar-applet crashed with
** Attachment added: version.log
http://launchpadlibrarian.net/16479543/version.log
--
kernel oops: kernel NULL pointer :iwl4965:iwl4965_exit+0x10/0x19
https://bugs.launchpad.net/bugs/253990
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/16479567/lspci-vvnn.log
--
kernel oops: kernel NULL pointer :iwl4965:iwl4965_exit+0x10/0x19
https://bugs.launchpad.net/bugs/253990
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: uname-a.log
http://launchpadlibrarian.net/16479540/uname-a.log
--
kernel oops: kernel NULL pointer :iwl4965:iwl4965_exit+0x10/0x19
https://bugs.launchpad.net/bugs/253990
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
I am attempting to work around
https://bugs.launchpad.net/ubuntu/+bug/244429 since no one is responding
to it and I can't put my computer onto wireless until it's fixed.
I downloaded http://linuxwireless.org/en/users/Download compat-
wireless-2.6.24.tar.bz2 on 2008-07-30,
** Attachment added: kernel-oops-2.txt
http://launchpadlibrarian.net/16479516/kernel-oops-2.txt
--
kernel oops: kernel NULL pointer :iwl4965:iwl4965_exit+0x10/0x19
https://bugs.launchpad.net/bugs/253990
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have downloaded the 2008-07-30 release of compat-
wireless-2.6.24.tar.bz2 from http://linuxwireless.org/en/users/Download,
unpacked, built, installed, and rebooted to bring up the new drivers.
The output of /sbin/modprobe -l iwl4965 confirms that the system found
the new drivers.
I get
*** This bug is a duplicate of bug 251252 ***
https://bugs.launchpad.net/bugs/251252
** This bug has been marked a duplicate of bug 251252
linux-backports-modules-2.6.24-20-generic causes kernel panic when unloading
Intel Wireless driver
--
kernel oops: kernel NULL pointer
Hmm, perhaps this bug report is too confusing.
This bug is a kernel oops from intel 4965AGN driver.
Probably started with the 2.6.24-19 kernels, kernel panic text caught
yesterday with 2.6.24-20 kernel.
Description:Ubuntu 8.04.1
Release:8.04
linux-ubuntu-modules-2.6.24-20-generic:
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/16409074/lspci-vvnn.log
--
kernel oops: invalid opcode
https://bugs.launchpad.net/bugs/244429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Summary changed:
- Hardy freezing randomly (Dell issue??)
+ kernel oops: invalid opcode
** Description changed:
- I have posted a thread about random freezing of Hardy here:
http://ubuntuforums.org/showthread.php?t=832383
- From what I read in the subsequent posts that it seems to
** Attachment added: version.log
http://launchpadlibrarian.net/16409063/version.log
--
kernel oops: invalid opcode
https://bugs.launchpad.net/bugs/244429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Here's the text of the kernel panic from my D630. Please escalate, it
is in the iwl4965 code so it will be hitting a lot of machines.
-- rec --
** Attachment added: kernel-panic.txt
http://launchpadlibrarian.net/16369967/kernel-panic.txt
--
Hardy freezing randomly (Dell issue??)
** Changed in: linux-ubuntu-modules-2.6.24 (Ubuntu)
Sourcepackagename: None = linux-ubuntu-modules-2.6.24
--
Hardy freezing randomly (Dell issue??)
https://bugs.launchpad.net/bugs/244429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Binary package hint: pulseaudio
The man page for the pulseaudio config file /etc/pulse/default.pa is
installed in /usr/share/man/pa/man5/default.5.gz, which would make it
part of the Panamanian translation of the man pages, if there were one.
In any case, it makes it very
Public bug reported:
Binary package hint: d-feet
Several sub-process crashes just browsing the session bus, this first
one from looking at org.fredesktop.compiz
The user interface persists and continues to work through all these
crash reports.
I believe apport is attaching the necessary info,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/13345510/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/13345511/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/13345512/ProcStatus.txt
** Attachment
Public bug reported:
Binary package hint: exaile
Apport reports this crash every time exaile is exited by closing its
window.
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Thu Apr 10 18:59:17 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/share/exaile/exaile.py
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/13346064/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/13346065/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/13346066/Disassembly.txt
** Attachment
I believe this bug is fixed.
I just tried a daily livecd build from http://cdimage.ubuntu.com/daily-
live/current/ (specifically http://cdimage.ubuntu.com/daily-live/current
/hardy-desktop-amd64.iso dated April 9 8:34AM) and my laptop comes right
up in its native resolution with no operator
The beta was set before the fix to the usplash was done, and I believe
the usplash bug (https://bugs.launchpad.net/bugs/147623) interfered
with the autodetect.
If there were a simple way to update the packages on the beta livecd
then I'd test this hypothesis, but apparently livecd's are built
Public bug reported:
Binary package hint: synfigstudio
Running synfigstudio (package synfigstudio-0.61.07-1build1) in a console
generates the error:
GThread-ERROR **: GThread system may only be initialized once.
aborting...
Aborted (core dumped)
That is, the program crashes. It also crashes
This bug is still present in Hardy Alpha5.
Please specify what logs I can supply or anything else I can do.
--
livecd gdm failure after low-graphics dialog
https://bugs.launchpad.net/bugs/194187
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm sorry, perhaps the point of my report got lost in the details.
The Hardy Alpha4 amd64 livecd fails to boot to the desktop and dumps the
user into limbo.
I expected the livecd to boot to the desktop or explain why it wasn't
possible.
In what sense is this not a bug?
I have no support
It happens using the CD reliably.
(I suspect the same thing has happened after install, because I have been
put into the low-graphics dialog since installing. But I don't have a way
to reproducibly get to the low graphic mode configuration tool after
install.)
I've just finished verifying the
Public bug reported:
Attempting to install Hardy Alpha4 amd64 on Dell Latitude D630, NVIDIA
Quadro NVS 135M, 1440x900 screen.
If I allow the default Start or install ubuntu entry to run, with or
without specifying a VGA mode of 1440x900x32 using F4, I arrive at a
dialog titled Ubuntu is running
Me, too.
Dell Latitude D630, NVIDIA GPU Quadro NVS 135M, 1440x900 screen, amd64
Hardy Heron Alpha4 + updates to date.
The System Administration Screens and Graphics control currently has
no nvidia driver listed as available (but it's the one that's running
according to /var/log/Xorg.0.log) and
Saïvann Carignan : Thank you for the mentoring.
I just checked this original problem out against the Hardy Alpha4 Livecd
and discovered something even more disturbing.
As above, this is a Dell Latitude D630, NVIDIA Quadro NVS 135M (GeForce
8 series), 1440x900 screen, amd64 Hardy Alpha4.
If
This bug is still present for me in Hardy Alpha5.
I avoid the problems at the Live CD boot prompt by:
Typing F6 to access the boot options,
Typing a space to make the options visible,
Erasing the splash option,
Typing a return to launch the boot.
--
[amd64 + nvidia 8xxx] usplash shows
This should be marked as a duplicate of
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/38442
--
[Hardy] Installer window too big on 800x600 screen.
https://bugs.launchpad.net/bugs/184919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If it's a wiki I can edit myself, then it can't be a bug. There should
be a withdrawn status.
** Changed in: ubuntu
Status: New = Invalid
--
hardy alpha5 release page vs bug #147623
https://bugs.launchpad.net/bugs/194124
You received this bug notification because you are a member of
Public bug reported:
The hardy alpha 5 release page:
https://wiki.ubuntu.com/HardyHeron/Alpha5
lists the following caveat:
Video problems have been reported with the 64-bit (amd64) version of
Edubuntu desktop. As a workaround, users can manually specify a video
resolution at the boot menu.
I think this is a variant of
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/147623.
There are several mentions of unusable livecd installs there dating back
to feisty all involving nvidia 8xxx.
--
hardy 64bit live cd GFX issues
https://bugs.launchpad.net/bugs/173130
You received this
Ah, I see. They're listed in the attached Xorg.log.0 and lspci outputs.
In the first Xorg.log.0 you attached, the NV xserver says:
(--) Chipset Unknown NVIDIA chip found
and the chip detected by PCI probe:
(--) PCI:*(1:0:0) nVidia Corporation GeForce 7100 GS rev 161, Mem @
0xd000/24,
Better, make the window resizable, or at least notice that it's larger
than the screen size.
--
[Hardy] Installer window too big on 800x600 screen.
https://bugs.launchpad.net/bugs/184919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
This package has been unable to cleanly uninstall for for any Hardy
Alpha I've installed.
ProblemType: Package
Architecture: i386
Date: Wed Feb 27 10:24:54 2008
Dependencies:
DistroRelease: Ubuntu 8.04
ErrorMessage: subprocess post-removal script returned error exit status
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/12261265/DpkgTerminalLog.txt
--
package linux-ubuntu-modules-2.6.24-10-rt None failed to install/upgrade:
subprocess post-removal script returned error exit status 1
https://bugs.launchpad.net/bugs/196207
You received
I have installed the latest alpha of Hardy and tomboy was not a problem.
-- rec --
On Feb 15, 2008 6:29 PM, Greg Grossmeier [EMAIL PROTECTED]
wrote:
This bug report is for an older version of tomboy in Hardy. Is this
still an issue for you now?
--
package tomboy 0.9.1-0ubuntu1 failed to
Thanks, but I'm not working on the bug, I just reported it.
And it seems that they have pretty well sorted it out, judging from
the number of 'this is a duplicate of that' messages I've been getting
about it.
-- rec --
On Jan 29, 2008 2:00 PM, edcrumly [EMAIL PROTECTED] wrote:
Forgive my
Public bug reported:
Binary package hint: xserver-xorg
Installing hardy alpha3 amd64 on a latitude D630.
[EMAIL PROTECTED]:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu hardy (development branch)
[EMAIL PROTECTED]:~$ dpkg -l
My failure came doing a partial upgrade after installing hardy-
alpha3-amd64 alternate onto a Latitude D630. There was a series of
failures through mono libraries culminating in fspot and tomboy.
/var/log/dist-upgrade/apt-term.log attached.
-- rec --
** Attachment added: apt-term.log
Happened on partial upgrade following clean install of Hardy alpha3
amd64 alternate on Latitude D630. /var/log/dist-upgrade/apt-term.log
attached to #185667 reporting mono-gac failure to install which was
first of a cascade of failures that ended with fspot.
-- rec --
--
f-spot
My failure came on partial upgrade after installing Hardy-alpha3 amd64
alternate on a Latitude D630. /var/log/dist-upgrade/apt-term.log
attached to #185667 about mono-gac failure to install, which was first
of a cascade of failures which ended with tomboy.
-- rec --
--
package tomboy
I confirm that this bug still exists in 2.6.22-13 on a dell latitude
d630.
I also confirm that it can still be cured by getting ftp://ftp.alsa-
project.org/pub/driver/alsa-driver-1.0.15rc3.tar.bz2, unpacking, and
running configure make sudo make install. (You will need to have
kernel headers
80 matches
Mail list logo
