apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606974/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
back
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606975/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606976/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/116
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606977/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606978/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
ba
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606979/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
ba
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606980/+files/UdevLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1162026/+attachment/3606981/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1162026
Ti
I've tested with the latest upstream kernel.
test@test-Dell-System-XPS-L322X:~$ uname -a
Linux test-Dell-System-XPS-L322X 3.9.0-030900rc4-generic #201303232035 SMP Sun
Mar 24 00:36:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
** Tags added: kernel-bug-exists-upstream
--
You received this bug not
** Description changed:
- On both versions of the XPS 13 (L322X and L321X) running Ubuntu Raring with
the latest 3.8 kernel, letting the screen turn off and then back on causes the
backlight to go to maximum brightness and become not adjustable. This behavior
is not seen with suspend/resume or
upstream defect https://bugzilla.gnome.org/show_bug.cgi?id=695947
** Bug watch added: GNOME Bug Tracker #695947
https://bugzilla.gnome.org/show_bug.cgi?id=695947
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
/controlC0: jared 2293 F pulseaudio
Date: Fri May 10 14:02:23 2013
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20120703-2
Ecryptfs
I've encountered the same problem. I installed Ubuntu 12.10 without any
network access from a USB stick created with "usb-creator-gtk -n". I
also notice that there are no linux-signed* packages on the live CD
install media, although grub2-signed (actually grub-efi-amd64-signed)
and shim-signed are
** Bug watch added: Debian Bug tracker #692406
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692406
** Also affects: debian via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692406
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a m
My packaging of wsl 0.2.1 is in Debian's ftpmaster queue. I'd like for
it to be pulled into Ubuntu from Debian. I've tested it on Lucid and
Precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106879
I see the same issue when using Evolution 3.2.3 on Ubuntu 12.04 with the
MAPI connector to an Exchange server.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010349
Title:
Evolution address book ina
Public bug reported:
I'm trying to get Steam working, but apparently my OpenGL drivers are
not installed / supported.
I was attempting to install OpenGL using the Synaptic Package Manager
when I received several failed error reports.
This is one of them...
ProblemType: Package
DistroRelease: Ub
I think it might have something to do with the fact that I'm running a
32 bit OS. A year ago when I originally installed Ubuntu that was the
recommendation.
I'll try upgrading to the 64 bit 12.10 and see if that solves the
problem.
I consider this bug completed / resolved.
** Changed in: linux
I am seeing this issue on an XPS 13 as well. It also uses the Centrino
Advanced-N 6230.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/901410
Title:
[Dell XPS L502X] Applying soft block to bluetooth
Public bug reported:
In the pre-up script in this package, eth* device names are hardcoded.
This affects machines with biosdevname enabled.
See line 135 of this script in ifenslave-2.6 (1.1.0-19ubuntu5):
BOND_SLAVES=`sed -ne 's/ *\(eth[^:]*\):.*/\1/p'
/proc/net/dev`
This
Public bug reported:
In the bridge-utils.sh script in this package, eth* NIC names are
hardcoded. This affects systems with biosdevname enabled, as they use
em* and p*p* instead.
See line 11 of this script in bridge-utils (0.9.2-1):
set regex eth.\* noregex "$@"
This appears to be the o
Public bug reported:
eth* device names are hardcoded. This affects systems with biosdevname
enabled, as they use em* and p*p* instead.
Places where this is hardcoded are:
1. contrib/network
2. if-pre/post scripts
3. vlan_test{,2}.pl
** Affects: vlan (Ubuntu)
Importance: Undecided
S
Clarification: Systems with biosdevname enabled use em* and p*p* instead
of eth*.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948538
Title:
eth* device names hardcoded in debian/pre-up script
To
Public bug reported:
resolvconf is unaware of how to handle biosdevname NIC names, which are
of the form em* and p*p*.
In the resolvconf (1.63ubuntu9) source package, bin/list-records lacks
these entries, and line 27 of etc/resolvconf/interface-order lacks them
as well:
PATTERNS="lo* eth* ath* w
The portion including and after the "_" is only for Network Partitioning
(NPAR) enabled NICs when the NPAR feature is enabled. On a typical
machine with biosdevname enabled without NPAR, you will see em* and
p*p*. For one with an NPAR-enabled NIC, you may see em*_* or p*p*_*.
--
You received this
I agree with Stéphane that bridges and bonds probably should be
supported. Also, while I don't think there are any systems with more
than ten embedded NICs, PCI slots, ports per PCI card or NPAR virtual
interfaces, it might be a good idea to support this.
--
You received this bug notification bec
Thank you Thomas and Steve!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/949473
Title:
resolvconf is unaware of biosdevname NIC names
To manage notifications about this bug go to:
https://bugs.lau
Michael: Before switching to an unsupported kernel, please use first try
the linux-image-generic-lts-raring kernel. Since you're using an old
BIOS version, please update that as well. Also, if you bought the XPS 13
Developer Edition, note that you are entitled to help from Dell
ProSupport. (I am wi
Public bug reported:
Precise's udev package doesn't detect that the Dell Latitude 6430U or
3330 need keyboard force release synthesis. This causes undesirable
behavior on these two systems. Quantal and upstream udev have an updated
rule to handle the 6430U. Neither have such a rule to handle the 3
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193147
Title:
[keymap] Touchpad key broken on Dell Latitude 6430U and 3330
To manage notifications about this bug go to:
https://bugs.launchpa
i have this problem and nothing i try helps. i tried the fix on the one
comment, but, seeing as you have to use dpkg to fix dpkg, it didn't
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/798793
T
running on a V130 Dell Vostro.
- Jared
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/532518
Title:
Brightness Applet is not usable via Mouse
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Howdy! We have noticed that when running 'kexec' on Azure VM's running the
'6.8.0-1017.20~22.04.1' linux-azure kernel we will see kernel panics. Each
panic doesn't have the exact same trace which is confusing to me. Here are a
few I've collected:
* https://paste.ubuntu.com
1001 - 1033 of 1033 matches
Mail list logo
