I have a 8760w which came with an NVIDIA Quadro 4000M and hat BIOS F.01.
This configuration booted okay, just like Ingo Gerth pointed out. After
upgrading the BIOS to the currently most recent F.21 version, this bug
occured. The "nouveau.modeset=0" workaround works as advertised.
This leads me to
@Mark
The current wireless backports in the Maverick archives also show the problem
unfortunately.
--
unstable wireless with iwlagn
https://bugs.launchpad.net/bugs/583210
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
@Mark
Thanks for the tip, will try the backports. Meanwhile I found this:
http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2214
It appears that a firmware bug could be the root of the problem.
** Bug watch added: bugzilla.intellinuxwireless.org/ #2214
http://bugzilla.intellinuxwireless.o
I had this with Lucid. After upgrading to Maverick Alpha 3 the problem
disappeared for a while. A couple of days ago the problem reappeared
again.
--
unstable wireless with iwlagn
https://bugs.launchpad.net/bugs/583210
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I just tested with this mainline kernel: http://kernel.ubuntu.com
/~kernel-ppa/mainline/v2.6.34-lucid/linux-
image-2.6.34-020634-generic_2.6.34-020634_amd64.deb
The problem remains the same.
** Tags removed: needs-upstream-testing
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb
apport information
** Attachment added: "UdevDb.txt"
http://launchpadlibrarian.net/48604918/UdevDb.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug notifica
apport information
** Attachment added: "WifiSyslog.txt"
http://launchpadlibrarian.net/48604932/WifiSyslog.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug
apport information
** Attachment added: "UdevLog.txt"
http://launchpadlibrarian.net/48604921/UdevLog.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug notifi
apport information
** Attachment added: "RfKill.txt"
http://launchpadlibrarian.net/48604917/RfKill.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug notifica
apport information
** Attachment added: "ProcModules.txt"
http://launchpadlibrarian.net/48604916/ProcModules.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bu
apport information
** Attachment added: "ProcCpuinfo.txt"
http://launchpadlibrarian.net/48604913/ProcCpuinfo.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bu
apport information
** Attachment added: "Card0.Codecs.codec.1.txt"
http://launchpadlibrarian.net/48604805/Card0.Codecs.codec.1.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
Yo
apport information
** Attachment added: "ProcInterrupts.txt"
http://launchpadlibrarian.net/48604914/ProcInterrupts.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received t
apport information
** Attachment added: "PciMultimedia.txt"
http://launchpadlibrarian.net/48604912/PciMultimedia.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received thi
apport information
** Attachment added: "Lsusb.txt"
http://launchpadlibrarian.net/48604911/Lsusb.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug notificati
apport information
** Attachment added: "Lspci.txt"
http://launchpadlibrarian.net/48604909/Lspci.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug notificati
apport information
** Attachment added: "Card0.Amixer.values.txt"
http://launchpadlibrarian.net/48604781/Card0.Amixer.values.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You
apport information
** Tags added: apport-collected
** Description changed:
These kernel warning started to happen pretty consistently after every
reboot somewhere during the lucid alpha cycle and have not stopped
since. I just realized that there might be a connection to a regression
wit
apport information
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/48604870/CurrentDmesg.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this
apport information
** Attachment added: "IwConfig.txt"
http://launchpadlibrarian.net/48604908/IwConfig.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug noti
apport information
** Attachment added: "Card0.Codecs.codec.0.txt"
http://launchpadlibrarian.net/48604782/Card0.Codecs.codec.0.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
Yo
apport information
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/48604779/BootDmesg.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this bug no
apport information
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/48604778/AplayDevices.txt
--
WARNING: at /build/buildd/linux-2.6.32/drivers/usb/serial/usb-serial.c:440
serial_unthrottle+0x8e/0x90 [usbserial]()
https://bugs.launchpad.net/bugs/556317
You received this
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/43229039/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/43229040/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/43229042/BootDmesg.txt
** Att
Public bug reported:
These kernel warning started to happen pretty consistently after every
reboot somewhere during the lucid alpha cycle and have not stopped
since. I just realized that there might be a connection to a regression
with gobi_loader (the firmware loader for the internal gobi WWAN ch
In comment #9 i forgot to mention that I use an Eclipse not from the
Ubuntu repositories but a manually installed one from eclipse.org. The
architecture is amd64.
--
Unable to access Galileo Update and Discovery sites
https://bugs.launchpad.net/bugs/530414
You received this bug notification beca
Starting Eclipse on Lucid using OpenJDK with
eclipse -Djava.net.preferIPv4Stack=true
solves the issue for my system. Apparently the network stack tries to
access the Update and Discovery sites with IPv6 instead.
--
Unable to access Galileo Update and Discovery sites
https://bugs.launchpad.
*** This bug is a duplicate of bug 537885 ***
https://bugs.launchpad.net/bugs/537885
After deleting ~/.local/share/gtg the application starts now. Apparently
I had some old data there from a previous install.
--
gtg crashed with RuntimeError in ()
https://bugs.launchpad.net/bugs/552430
You r
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/4269/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://launchpadlibrarian.net/42633340/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://launchpadlibrarian.net/42633341/ProcStatus.txt
** Visibil
@Tom Jaeger
Thanks again, that explains it. I did put the rules a few lines above
LABEL="wacom_end".
--
Serial Tablet PCs not supported in lucid
https://bugs.launchpad.net/bugs/522318
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@Tom Jaeger
Bingo! Your /etc/udev/rules.d/65-xorg-wacom.rules file did the trick! I
seriously wonder, though, why it hadn't worked before. The situation was that I
had added the udev rules directly into
/lib/udev/rules.d/69-xserver-xorg-input-wacom.rules.
When having it configured that way 'ude
After the update, now that the committed patch has arrived, it still
does not work. The situation appears to be similar to what is described
in comment #8.
I am still unable to find any reference in the log files related to "[Ww]acom"
or "stylus". The only bit of information is in /var/log/udev:
@Tom Jaeger
Er, no, not sure. I was waiting for the patches to arrive and received the xorg
(1:7.5+1ubuntu9) update a couple of days ago. The changelog said (among other
things) "debian/x11-common.links: Add xf86-input-evtouch and -wacom" which
made me believe the patch were included. Sorry if
On my Motion LE1700 tablet pc with a serial wacom digitizer on
/dev/ttyS0 the current patch does not help. It does not matter if the
additional udev rules are applied to /lib/udev/rules.d/69-xserver-xorg-
input-wacom.rules or not. /var/log/Xorg.0.log does not show any entries
including "wacom", "st
Sorry for the stupid status changing. I did not know what I was doing.
Is version 1:0.10.3+20100109-1ubuntu1, published on 2010-01-22
(https://launchpad.net/ubuntu/+source/xf86-input-wacom) the one that
fixes the problem? If so, the fix has no effect on a Motion Computing
LE1700. The stylus has no
** Changed in: xf86-input-wacom (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: xf86-input-wacom (Ubuntu)
Status: Fix Committed => Fix Released
--
xserver-xorg-input-wacom conflicts with xserver-xorg-core
https://bugs.launchpad.net/bugs/501206
You received this bug no
On Karmic you can now position the panels with
$ gconftool --type int --set /apps/panel/toplevels/top_panel_screen0/monitor 1
$ gconftool --type int --set /apps/panel/toplevels/bottom_panel_screen0/monitor
1
On my system this moves the top and bottom panels from LVDS to external
VGA.
--
gnome
This is indeed fixed in version 0.150-3. As of now, this version has not
yet made it into the karmic repositories.
--
Error OAFIID:GNOME_TSClientApplet while adding the applet onto panel
https://bugs.launchpad.net/bugs/399436
You received this bug notification because you are a member of Ubuntu
B
@marcobra
Thanks, that worked.
--
[karmic] impossible to switch from kdm to gdm
https://bugs.launchpad.net/bugs/414140
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://lis
Interesting: I noticed you have filed Bug #414140, which affects me in
the same way. I have ubuntu-desktop and kubuntu-desktop installed.
--
[karmic] system fails to shutdown cleanly
https://bugs.launchpad.net/bugs/419753
You received this bug notification because you are a member of Ubuntu
Bugs,
This error occurs to me since last night when I performed a "update-
manager -d" from jaunty to karmic. The problem remains when I delete the
applet and re-add it. sshmenu-gnome itself works fine when launched via
command-line.
Besides SSHMENU, the only other applet having this problem is
TDClient
While this patch may be an improvement for many users, this does not fix
the original problem: the lack of being able to specify on which screen
the panel should display.
On my setup the external display has a larger resolution (1920x1200)
than the LVDS panel of the laptop (1600x900). Therefore I
Sure.
** Attachment added: "Output of lshal"
http://launchpadlibrarian.net/21481168/lshal.txt
--
Sierra Wireless MC8790 HSUPA Module not detected by NetworkManager
https://bugs.launchpad.net/bugs/318109
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Sorry for not being clear. wlan0 is the internal "Intel Corporation
PRO/Wireless 5300 AGN" wireless card. This is working perfectly well.
$ lspci
(...)
18:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh]
Network Connection
The not working "Sierra Wireless MC8790 HSUPA M
No. Using WIFI I get:
$ ifconfig
eth0 Link encap:Ethernet Hardware Adresse 00:17:42:f5:e3:ed
UP BROADCAST MULTICAST MTU:1500 Metrik:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Kollisione
Public bug reported:
Binary package hint: network-manager
When left-clicking on the NetworkManager applet, the Sierra modem is not
shown and cannot be used.
Not sure if this is a really a NetworkManager problem, or with linux-
usb.
(0) lsb_release -rd
Description: Ubuntu jaunty (development
Sony VAIO VGN-SR19VN running Intrepid 8.10, same problem with Realtek ALC262:
internal microphone not working.
Sound output works, but the internal speakers are not muted when using
headphones so headphones and speakers work simultaneously.
Info of my ALSA setup is here:
http://www.alsa-project.
Andreas, since I don't have the original notebook anymore (see comment
7) does this test still apply? When running chfn on the current
subnotebook there is no error:
[EMAIL PROTECTED]:~# chfn mhuettemann
Ändere Benutzerinformationen für mhuettemann
Geben Sie einen neuen Wert an oder drücken Sie EN
Andreas, I definitely never ran "passwd -l root" on the system.
--
landscape-client 1.0.18-0ubuntu1 install stopped at useradd/chfn
https://bugs.launchpad.net/bugs/268039
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I never unlocked the root account. So, yes, the root account should have
been locked at the time the error ocurred.
--
landscape-client 1.0.18-0ubuntu1 install stopped at useradd/chfn
https://bugs.launchpad.net/bugs/268039
You received this bug notification because you are a member of Ubuntu
Bugs
Unfortunately I had to remove Intrepid from the notebook a few days ago
because it was a loaner and had to be returned. Sorry I can't help any
longer with the original problem. I did test with the new notebook I got
in exchange. There the ubuntu4 version upgraded just fine.
--
package landscape-c
Andreas,
no network users of any type were on that system. Also no nis, ldap or
winbind setup, unless some package sneaked something in behind my back.
I did use smb shares on the network though as a client, but only with my
regular local user account.
--
package landscape-client 1.0.18-0ubuntu
confirm as well.
--
package landscape-common 1.0.18-0ubuntu2 failed to install/upgrade: trying to
overwrite `/usr/lib/python2.5/site-packages/landscape/patch.py', which is also
in package landscape-client
https://bugs.launchpad.net/bugs/271119
You received this bug notification because you are
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/17435219/Dependencies.txt
** Attachment added: "DpkgTerminalLog.txt"
http://launchpadlibrarian.net/17435221/DpkgTerminalLog.txt
--
package landscape-client 1.0.18-0ubuntu1 failed to install/upgrade
https://bugs.launchpa
Public bug reported:
Binary package hint: landscape-client
Using update-manager. At postinstall the package prompted for a password
inside the embedded terminal window. Upon entering the password it was
echoed in clear text. Then the update manager hung for several minutes.
I had to ctrl+c out of
Public bug reported:
Binary package hint: apt-listchanges
This happened after a "apt-get update" / "apt-get upgrade" cycle in
feisty:
[...]
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 28, in
import apt_pkg
ImportError: No module named apt_pkg
[...]
ProblemTyp
** Attachment added: "Dependencies.txt"
http://librarian.launchpad.net/6554142/Dependencies.txt
** Attachment added: "ProcMaps.txt"
http://librarian.launchpad.net/6554143/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
http://librarian.launchpad.net/6554144/ProcStatus.txt
--
apt-li
57 matches
Mail list logo
