I believe this sequence of events works consistently to duplicate the
problem:
1. Delete a group
2. Sort Groups
This leads to the software crashing and exiting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
I can fairly consistently crash keepassx by making a change to the
database, and then sorting groups.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/806582
Title:
keepassx crashed with SIGSEGV in QTr
This is fixed with VMware Workstation Release 7.1.4:
"When the latest NVIDIA 270.x drivers are installed on a Linux host
system, users could not run virtual machines with 3D acceleration
enabled."
https://www.vmware.com/support/ws71/doc/releasenotes_ws714.html
--
You received this bug notificat
I also had crashes in Maverick when I attempted to copy CDs. Installing
cdrdao fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/646377
Title:
Brasero crashes on any video project
--
I can confirm that reverting to an earlier nvidia driver allows me to
successfully re-enable 3d acceleration for the VM.
:~$ apt-cache policy nvidia-current
nvidia-current:
Installed: 260.19.06-0ubuntu1
Candidate: 270.18-0ubuntu1~maverick~xup1
Version table:
270.18-0ubuntu1~maverick~xup
** Attachment added: "VMWare Crash Log"
https://bugs.launchpad.net/bugs/709331/+attachment/1812690/+files/vmware-1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/709331
Title:
VMWare crashes
Public bug reported:
Binary package hint: nvidia-current
I'm running VMWare Workstation 7.1.3 build-324285 on Ubuntu Maverick. I
use the nvidia-current driver from the x-updates ppa. I'm using a
"nVidia Corporation G96 [Quadro FX 580] (rev a1)" video card, according
to lspci.
I recently rebooted
I filed this bug two years ago. It took you guys a year to respond to it
with promises of corrective action. It's taken you a year again to
realize that you still haven't even checked it out yet.
I quit using Ubuntu because of this bug.
I have no intentions to check whether or not this bug is fix
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
Please enable CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG
https://bugs.launchpad.net/bugs/226593
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I'm still getting firmware errors, and my computer is still freezing
every few times I reload the module and try using it.
I've requested it in bug 226593, and I'll say it here. Can someone
please enable debugging of the iwl* modules? This bug will go nowhere if
debugging remains disabled. All it
All right, what does it take to get a bug even looked at. I've pointed
out the two relevant config options. Is there some reason why this issue
is getting entirely ignored? Is there active opposition to being able
to debug a flaky module? Do you all like having broken iwlwifi modules?
Please, ena
Debugging of the iwl* modules is still not enabled in the kernel. The
various microcode errors that happen in these modules are nigh
impossible to debug without the information reported with debugging
enabled.
CONFIG_IWL3945_DEBUG and CONFIG_IWLWIFI_DEBUG should be enabled in the
kernel.
** Also
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
iwl4965 does not report debug information
https://bugs.launchpad.net/bugs/226593
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Well the freezing issue isn't gone, but if the firmware errors are fixed
(another bug) then they're a non-issue.
--
iwlagn segmentation fault and firmware errors
https://bugs.launchpad.net/bugs/282355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The freezing issue appears to be because something called "events/1" is
using 100% of the CPU, interspersed with "iwlagn/1" taking some of the
CPU.
--
iwl4965: Microcode SW error detected. Restarting 0x200
https://bugs.launchpad.net/bugs/200509
You received this bug notification because you
'options iwlagn debug=0x43fff' doesn't work.
The kernel configuration for the iwl* modules is unacceptable. These
modules cause problems on a large number of computers, but debugging is
disabled. I would be willing to accept a module that is 100k larger for
the ability to debug these issues. It's
I've had these messages in the past, and I also have never seen a lock-
up because of them -- until Intrepid.
The version in LBM is much worse than the main kernel. It caused
frequent microcode errors and frequent lockups when I tried to recover.
I still see both with the main kernel, but not near
I've put the following into /etc/modprobe.d/iwlagn
options iwlagn debug=0x43fff
Hopefully I can give more useful information the next time it crashes.
--
iwl4965: Microcode SW error detected. Restarting 0x200
https://bugs.launchpad.net/bugs/200509
You received this bug notification because
In fact, that last post was followed quickly by a microcode error. I got
the dmesg. This time, I accidentally left clicked on the network manager
icon and my computer solidly froze, responding to nothing.
How do you enable debugging output for iwlagn? Does it even work with
the ubuntu compile? I r
I can confirm that the problem still exists in Ibex. I get regular
Microcode errors. To recover I have to unload and reload the module.
Also, on occasion, when I unload and reload the module, my computer
mostly freezes. I can't start programs and shutting down doesn't work.
This may just be genera
I'm continuing to get firmware errors, but my computer hasn't become
unresponsive. I'm posting a new dmesg full of firmware errors. My
network came back up without prompting after each error.
It may be that the freezing issue is gone. I'll give it a few days time
to be sure.
** Attachment added:
I have had at least one kernel panic. However, the freeze that I get is
often not a complete freeze. I can minimally interact with X, bringing
up menus and such, but I can't start programs or switch to a virtual
terminal.
Next time this problem rears its ugly head, I'll see what I can pull off
the
** Attachment added: "Dmesg"
http://launchpadlibrarian.net/18468919/dmesg
--
iwlagn segmentation fault and firmware errors
https://bugs.launchpad.net/bugs/282355
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
I've been getting firmware errors with the iwlagn module recently. (Will
they never go away?) After getting some firmware errors, I did 'modprobe
-r iwlagn; modprobe iwlagn' to recover, and I got a segmentation fault.
Furthermore, on occasion after having a firmware error and
/sys/module/iwl4965/parameters/debug has the correct value, so I can
confirm that the module is getting called correctly. Something is wrong
with the module itself, then.
--
iwl4965 does not report debug information
https://bugs.launchpad.net/bugs/226593
You received this bug notification because
I found the same problem with debug=0x43fff not working, and have
reported it as Bug #226593.
--
iwl4965: Microcode SW error detected. Restarting 0x200
https://bugs.launchpad.net/bugs/200509
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
Binary package hint: linux-backports-modules
Using Ubuntu Hardy.
The iwl4965 module does not respond to 'options iwl4965 debug=0x43fff'
in /etc/modprobe.d/options. After getting a microcode error, nothing
extra was reported in dmesg. Insmod is getting called correctly, so it
I've been trying to capture debug information about the microcode
errors, but I haven't had one in a while.
Can someone who is regularly having the errors add this to
/etc/modprobe.d/options?
options iwl4965 debug=0x43fff
It should give more information in dmesg on the nature of the bug, so
that
I can confirm that this bug still exists with the latest backports
version. I'm seeing it a few times each day. One of my errors was an HW
error, I'm not sure what this means.
Here are some excerpts from my logs. All of these showed up with nothing
else in the logs for about 20 minutes beforehand,
I am still seeing infrequent microcode errors with version of iwl4965
that you posted.
I have attached my dmesg
** Attachment added: "dmesg"
http://launchpadlibrarian.net/10945805/dmesg
--
iwl4965 drops out from time to time (Santa Rosa)
https://bugs.launchpad.net/bugs/144621
You received t
Whoops. Wrong dmesg file. Here's the right one
** Attachment added: "dmesg (correct copy)"
http://launchpadlibrarian.net/10905364/dmesg
--
iwl4965 drops out from time to time (Santa Rosa)
https://bugs.launchpad.net/bugs/144621
You received this bug notification because you are a member of Ubu
I've attached my /var/log/dmesg. Here is the order of events:
Boot with the old module. (I had downgraded to the old package)
Install the new package.
sudo modprobe -r iwl4965; sudo modprobe iwl4965
Wait a little bit and then look at dmesg.
** Attachment added: "dmesg"
http://launchpadlibrarian
I should also mention that I'm running the amd64 kernel.
--
iwl4965 drops out from time to time (Santa Rosa)
https://bugs.launchpad.net/bugs/144621
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
I began seeing the same message in dmesg as Matteo Colina when I
upgraded to 1.2.0 with iwl4965. I was not getting it before I installed
the new package.
--
iwl4965 drops out from time to time (Santa Rosa)
https://bugs.launchpad.net/bugs/144621
You received this bug notification because you are a
1.2.0 is available now.
As I understand it, the deadline for updating linux-ubuntu-modules is
the new year. It doesn't look like there will be a fix soon.
Also, it does look like it's gone from the git tree. Anybody know why?
--
[Gutsy] Update iwlwifi driver to 1.1.21 from 1.1.0 (originally 1.1
It's looks like 1.1.21 is a code-cleanup as opposed to a bugfix. Might I
suggest releasing 1.1.20 soon, and waiting for any kinks in 1.1.21 to
get ironed out?
--
[Gutsy] Update iwlwifi driver to 1.1.20 from 1.1.0 (originally 1.1.17 req) -
Updated Nov. 5
https://bugs.launchpad.net/bugs/151627
You
I believe this is related to bug 149214.
I and others are having intermittent failures with the "Error setting Tx
power (-11) " message.
John
--
iwl4965 drops out from time to time (Santa Rosa)
https://bugs.launchpad.net/bugs/144621
You received this bug notification because you are a member of
Same here with a 4965AGN on an IBM R61. The connection seems to randomly
die, and I usually can't reconnect until I remove the module and reload
it.
DMESG:
[ 232.870279] iwl4965: TX Power requested while scanning!
[ 232.870286] iwl4965: Error setting Tx power (-11).
[ 232.871635] iwl4965: TX P
38 matches
Mail list logo
