** Changed in: linux (Ubuntu Lucid)
Assignee: Chris J Arges (arges) => (unassigned)
** Changed in: linux (Ubuntu Lucid)
Status: In Progress => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Request for stable inclusion sent:
http://www.spinics.net/lists/netdev/msg287462.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1314274
Title:
BUG in nf_nat_cleanup_conntrack
Statu
kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
Title:
Chrome Pixel Second Suspend
So I see that get_data_rates is returning an error, are there
alternative Control USB bytes we need to send? Or do we think this
failure is because of something else (reader clock being stopped.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
I am having the same issue but for an ASUS-u46e with both the 3.13 and
3.14 kernels. I did not have this problem with ubuntu 13.10.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1307797
Hit this same bug on my X220. Will try mainline and see if it happens again.
Similar reports:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1312996
https://bugzilla.redhat.com/show_bug.cgi?id=1060387
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Bug watch added: Red Hat
A way to verify the patch is required for any SRU. A simple reproducer
is always best, but if this problem occurs with high probability within
a known amount of time then running for that known amount of time could
also assist in validating and verifying the fix.
--
You received this bug notifica
Link to upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=65191
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Bug watch added: Linux Kernel Bug Tracker #65191
http://bugzilla.kernel.org/show_bug.cgi?id
Can you test this kernel built with lockdep debugging on and see what
output it provides? It also may be worthwhile to getting a crashdump if
lockdep debugging is inconclusive.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
And the link to the build is here:
http://people.canonical.com/~arges/lp1314274/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1314274
Title:
BUG in nf_nat_cleanup_conntrack
Status in
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu P
** Description changed:
+ SRU Justification:
+
+ Impact:
+ When creating new network namespace dmesg can show the following :
unregister_netdevice: waiting for lo to become free. Usage count = 1
+
+ Fix:
+ Stefan Bader's SAUCE patch has fixed this for Quantal: UBUNTU: SAUCE:
ne
This is related to the bonding mode and _not_ a bug. The bonding module
will drop duplicate frames received on inactive ports, which is normal
behavior. [0] Overall the packets should be getting into the machine
without problems since they are received on the active slave. To confirm
this do the fo
Occurs in trusty as well
** Tags added: trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1278615
Title:
bluetoothd crashed with SIGSEGV in __GI___libc_free()
Status in “bluez” pac
** Description changed:
SRU Justification:
Impact:
Users of the 3.2/3.5/3.8 series kernel will have poor network throughput when
using OpenStack Neutron depending on their setup.
Fix:
These upstream patches are necessary to fix the issue:
2681128f0ced8aa4e66f221197e183cc16d24
** Description changed:
SRU Justification:
Impact:
Users of the 3.2/3.5/3.8 series kernel will have poor network throughput when
using OpenStack Neutron depending on their setup.
Fix:
These upstream patches are necessary to fix the issue:
2681128f0ced8aa4e66f221197e183cc16d24
Ok, after a fun time setting this back up, I was able to verify with the
3.2.0-61 kernel!
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
** Attachment added:
"wireshark-log-during-failure-to-flush-tx-fifo-queues.pcapng"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305406/+attachment/4078765/+files/wireshark-log-during-failure-to-flush-tx-fifo-queues.pcapng
--
You received this bug notification because you are a membe
Public bug reported:
I have a Lenovo ThinkPad X201 Tablet with an Intel Centrino Ultimate-N
6300 AGN wireless card. Ever since I have upgraded to Ubuntu 13.10 from
Ubuntu 12.10, I keep experiencing this annoying issue on wireless
networks with multiple APs: a TX queue gets stuck, and the wireles
Six months have passed since I have tested the 3.12-rc3 mainline kernel,
and I confirm that the USB shutdown issue still exists after testing the
3.14 mainline kernel. (FYI, the system was upgraded from Raring to
Saucy on December 21, 2013.)
--
You received this bug notification because you are
I have just finished testing the latest upstream kernel, and I confirm
that the bug still exists (i.e. I am still occasionally seeing 'fail to
flush all tx fifo queues Q 0' messages).
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
-
Public bug reported:
What happens:
First time Pixel is suspended everything works fine. The second time the
Pixel resumes from standby it reboots. This was documented in previous
releases but a workaround was found by manually loading
tpm_tis force=1 interrupts=0.
In Ubuntu 14.04 loading the tp
I updated the BIOS to version 1004, and this did not change anything.
** Attachment added: "Output of "sudo dmidecode -s bios-version && sudo
dmidecode -s bios-release-date""
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1200204/+attachment/4082055/+files/dmidecode.txt
--
You receive
I meant to say BIOS version 1005, not 1004.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1200204
Title:
2040:7200 SuperSpeed USB failure (and kernel oops) after launching
tvtime: ERR
apport information
** Tags added: apport-collected staging trusty
** Description changed:
What happens:
First time Pixel is suspended everything works fine. The second time the
Pixel resumes from standby it reboots. This was documented in previous
releases but a workaround was found b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082082/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082074/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082079/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082073/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/13
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082085/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/13
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082083/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082071/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
Ti
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082076/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082087/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
Ti
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082072/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082070/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082080/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082077/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082086/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082075/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082081/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082084/+files/WifiSyslog.txt
** Description changed:
What happens:
First time Pixel is suspended everything works fine. The second time the
Pixel resumes from standby it reb
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082078/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082091/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082090/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082096/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082099/+files/UdevLog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082094/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082089/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/13
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082098/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082088/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082093/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082092/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082095/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082100/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1306884/+attachment/4082097/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1306884
I have tested the latest upstream kernel even more, and I have noticed
something that may or may not help. I have found a "degradation effect"
in which the total length of time the connection is hung within a given
time frame increases the longer the system is running. To illustrate
this effect,
For context I found the following thread which looked related:
http://ludovicrousseau.blogspot.fr/2010/10/card-auto-power-on-and-off.html
>From bug 1161882. So I built the following packages with
>DISABLE_ON_DEMAND_POWER_ON defined:
http://people.canonical.com/~arges/lp1307404/
This also failed.
The dmesg corresponding to device removal and power on was related to a
BIOS option that does "Power on if card is present" vs "Always powered
on". If the BIOS option is switched to "Always powered on" these
messages are not present.
** Also affects: pcsc-lite (Ubuntu)
Importance: Undecided
** Changed in: pcsc-lite (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1307109
Title:
Alcor Micro AU9540 keeps powering down when card is prese
An example of a non-working log:
http://pastebin.ubuntu.com/7250315/
An example of a working log:
http://pastebin.ubuntu.com/7250304/
The main differences I see start after here in the log:
0003 winscard.c:261:SCardConnect() Attempting Connect to Alcor Micro AU9540
00 00 using protocol: 3
0
** Changed in: linux (Ubuntu Precise)
Assignee: Louis Bouchard (louis-bouchard) => Chris J Arges (arges)
** Changed in: linux (Ubuntu)
Assignee: Louis Bouchard (louis-bouchard) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, wh
Can those affected by this issue test this build with the patch identified by
@kamatam?
http://people.canonical.com/~arges/lp1233175/
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
A similar case is here:
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg351591.html
It seems like using NUMA with high load MongoDB workloads are factors in
causing this crash.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
in: linux-lts-raring (Ubuntu)
Status: New => Invalid
** Changed in: linux-lts-raring (Ubuntu Precise)
Status: New => Fix Released
** Changed in: linux-lts-raring (Ubuntu Precise)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux-lts-raring (Ubuntu Prec
After upgrading to xubuntu 14.04 the bug is still present. I still get
the following error:
ERROR: Error querying target relations
The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range
Assignee: (unassigned) => Chris J Arges (arges)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1283604
Title:
WARNING: CPU: 0 PID: 5517 at
/build/buildd/linux-3.13.0/fs/sysfs/
Public bug reported:
When connecting a USB device or periodically while using my laptop I get
the following error:
[ 3595.453994] [ cut here ]
[ 3595.454008] WARNING: CPU: 2 PID: 7193 at
/build/buildd/linux-3.13.0/fs/sysfs/group.c:214 sysfs_remove_group+0xc6/0xd0()
[ 3595
Joe, I tested with the latest mainline kernel as of 3/25
(b098d6726bbfb94c06d6e1097466187afddae61f) and can still reproduce this exact
issue. It looks like its an upstream issue as well:
https://bugzilla.kernel.org/show_bug.cgi?id=71021
https://bugzilla.kernel.org/show_bug.cgi?id=69441
http://www
Test build here:
http://people.canonical.com/~arges/lp1283604/
So far it fixes things for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1283604
Title:
WARNING: CPU: 0 PID: 5517 at
** Description changed:
+
+ [Fix]
+
https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=e63ed0d7a98014fdfc2cfeb3f6dada313dcabb59
+
https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=f2495e228fce9f9cec84367547813cbb0d6db15a
+
+ From ups
*** This bug is a duplicate of bug 1283604 ***
https://bugs.launchpad.net/bugs/1283604
** This bug has been marked a duplicate of bug 1283604
WARNING: CPU: 0 PID: 5517 at /build/buildd/linux-3.13.0/fs/sysfs/group.c:214
sysfs_remove_group+0xc6/0xd0()
--
You received this bug notification
oughput is much
higher by almost 3 times. For example with some testing throughput is
3.5 Gbps in pre 3.9-rc1 versions and 9.1 Gbps with these patches
applied.
This has been confirmed on kernels from 3.5.x-3.8.x. (Quantal and Raring
lts backports)
** Changed in: linux (Ubuntu Precise)
** Description changed:
SRU Justification:
Impact:
Users of the 3.2/3.5/3.8 series kernel will have poor network throughput when
using OpenStack Neutron depending on their setup.
Fix:
These upstream patches are necessary to fix the issue:
2681128f0ced8aa4e66f221197e183cc16d24
** Description changed:
+ SRU Justification:
+ Impact: When using VMs with many CPUs on kvm, the module is loaded per CPU
which can cause allocation failures.
+
+ Fix: 8d8022e8aba85192e937f1f0f7450e256d66ae5c solves the issue which is
+ present in 3.8 series and beyond.
+
+ Testcase: Boot a VM
This looks like a similar issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1050964
** Bug watch added: Red Hat Bugzilla #1050964
https://bugzilla.redhat.com/show_bug.cgi?id=1050964
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
This commit is present in the latest 3.2/3.5 kernels for Ubuntu,
therefore I'll ifdef it for 3,2,0.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1262692
Title:
oops using openvswitch 1
) => Chris J Arges (arges)
** Changed in: openvswitch (Ubuntu Quantal)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: openvswitch (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: openvswitch (Ubuntu Quantal)
Importance: Undecided => High
*
This affects and applies to P/Q/R/S/T. Before doing the SRUs we'll have to fix
it in the development Ubuntu release.
However, this also applies to debian. I've submitted a bug to to get this
applied, since the patch is not in a dkms release yet.
** Also affects: dkms (Ubuntu Precise)
Importan
EPLIED
when the 'new ack' packet happened to be the last-ack of a previous,
already timed-out connection.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Precise)
Importance: Medium
Assignee: Chris J Arges (arges)
** Changed in: linux (Ubuntu Saucy)
Assignee: (unassigned) => Chris J Arges (arges)
** Changed in: linux (Ubuntu Saucy)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Saucy)
Assignee: Chris J Arges (arges) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1244627
Title:
Please enable CONFIG_
** Branch linked: lp:~rcj/ubuntu/trusty/open-vm-tools/lp1271669
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1271669
Title:
Move vmware related modules from extras into main kernel pac
** Tags removed: verification-needed-precise verification-needed-quantal
** Tags added: verification-done-precise verification-done-quantal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/12
Hi Michal,
could you please click on "This bug affects me" that we get a higher
rating?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1273652
Title:
"apply" of multi-monitor
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1172755
Title:
13.04 Kernel Panic Not Syncing - Attempted to kill init -
Public bug reported:
After the recent update of nvidia settings, I am not able to apply new monitor
setting via nvidia settings anymore.
After configuration of "X Server Display Configuration" hit hit the "apply"
button and then the program simply quit.
A workaround is to click on "Save to X Co
Public bug reported:
Reproduced on my x220:
ii linux-firmware1.122
all Firmware for Linux kernel drivers
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor
Peak]
[ 20.552702] iwl
That is not possble! My system do not recognize the crash an no report
is created!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1273652
Title:
"apply" of multi-monitor settin
@salvatore-orlando
I've built a test kernel with:
8aac6270 and a pre-req c99fe536
I've been able to boot it but haven't done much testing. Here it is:
http://people.canonical.com/~arges/lp1273386/
If you have time you can try reproducing on this kernel to see if it fixes the
issue as your origi
@salvatore-orlando:
If you've tested with 3.11 then you've tested with the patches identified
(8aac6270 and c99fe536) and thus these patches are not the fixes we're looking
for.
Therefore the next most important experiment would be to get the crash dump as
outlined in #12. This data would tell
Yes apport is configured correctly I tried the test with sh -c 'kill
-SEGV $$' and could successfully produce a crash report...
There is no crash occuring when I hit "apply". It seems the program is
simply closing.
I tried to use to old version 304.88-0ubuntu0.0.2 but could not change
the monitor
5-rc1
[Test Case]
#!/bin/bash
echo 'blah' > /dev/kmsg
tail -n1 /var/log/syslog | grep blah
# This should return 0.
** Affects: linux (Ubuntu)
Importance: Medium
Assignee: Chris J Arges (arges)
Status: In Progress
** Affects: linux (Ubuntu Quantal)
Importance: Me
Indeed I receive an output:
smiddy@3000-N200:~$ nvidia-settings
ERROR: Error querying target relations
The program 'nvidia-settings' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of
** Tags removed: verification-needed-precise
** Tags added: verification-done-precise
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1256988
Title:
netns: crash during namespace destroy
This is easily verified in a VM, did it with both P/Q and the -proposed
kernel works!
** Tags removed: verification-needed-quantal
** Tags added: verification-done-quantal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
** Changed in: nvidia-settings (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1273652
Title:
"apply" of multi-monitor setting re
sponsored
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1271127
Title:
Please merge kexec-tools 1:2.0.4-1 (main) from debian unstable
Status in “kexec-tools” package in Ubuntu:
Public bug reported:
bluetoothd crashes at startup
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu7
ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
Uname: Linux 3.2.0-58-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: a
At this point I'm having a difficult time reproducing on my end. I've
followed the steps above, but it seems that I can't trigger it. Are
there any other suggestions or more simple reproducers I can attempt?
Thanks
--
You received this bug notification because you are a member of Kernel
Packages
601 - 700 of 2376 matches
Mail list logo
