I've been following this, since I was affected using Arch Linux too. It
seems a commit has been included in 3.10.8 for the workaround of
accepting late URBs submissions:
https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.10.8
commit c72a0e036f9d80c609e608a723751343f1f5e9fc
USB: EHCI:
Public bug reported:
Binary package hint: aptdaemon
The problems occur on login.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.41+bzr646-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Annotation: Installation of
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/799833
Title:
type 'exceptions.AttributeError': 'FileLock' object has no attribute
'gettext'
To manage notifications about this bug go to:
Problem reproduced with Ubuntu 11.04.
Same error screen as the alpha above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
Linux images in Ubuntu 10.10 not compatible with my pc
--
Same problem, Macbook 5,1 with Ubuntu Natty.
Kernel 2.6.38-8-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/544469
Title:
iSight webcam on Macbook Pro does not work
--
ubuntu-bugs mailing
I understand that there are priorities, that Ubuntu is free of charge and so
on...
However, I am disappointed with the support concerning this and the previous
bugs I opened.
I opened this problem about five months ago; I reproduced it multiple
times... and still it is incomplete and
I reproduced the issue with the Ubuntu 11.04 alpha 3 live cd.
** Attachment added: Ubuntu 11.04 screen 1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717100/+attachment/1921176/+files/DSC01623.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: Ubuntu 11.04 screen 2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717100/+attachment/1921208/+files/DSC01624.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
I was finally able to understand a bit more what is happening.
It seems that there is an issue identifying USBs.
I attach two screens of the boot.
** Attachment added: Boot screen 1
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717100/+attachment/1917389/+files/DSC01621.JPG
--
You
** Attachment added: Boot screen 2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717100/+attachment/1917390/+files/DSC01622.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
I also attach an updates lshw and lspci (executed under a working Ubuntu
10.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
Linux images in Ubuntu 10.10 not compatible with my pc
** Attachment added: lshw output
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717100/+attachment/1917391/+files/lshw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
** Attachment added: lspci output
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717100/+attachment/1917392/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
Any update on this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
Linux images in Ubuntu 10.10 not compatible with my pc
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Is the information I submitted enough? How could I help you more?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
Linux images in Ubuntu 10.10 not compatible with my pc
--
ubuntu-bugs
Here you are the initramfs screen.
** Attachment added: DSC01605.JPG
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717100/+attachment/1855579/+files/DSC01605.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
And a video of a (long) reboot cycle (if can be useful):
http://www.multiupload.com/ON12AS53DV
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
Linux images in Ubuntu 10.10 not
Here you are the record: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/590010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/717100
Title:
Linux images in Ubuntu 10.10 not compatible
Public bug reported:
Since I upgraded my Ubuntu from 10.04 to 10.10, I cannot use new linux images
(2.6.35*). After reboot, initramfs console stops boot.
I noticed that even the live CD 10.10 cannot start. I think this is the best
way to reproduce it.
Unfortunately, I do not know how to debug
Here you are another occurrence.
Actually, it is a bit worryingly that this problem has not been
investigated yet. Apart from my configuration, I do not think I am the
only one affected by it.
** Attachment added: Two xorg processes stuck in infinite loop
I believe that the best way to reproduce it is to use the switch from
user function.
First, use an nVidia video card (my second PC using an Intel Graphics
Media Accelerator 950 does not present the same problem... or at least
it is very rare).
Then:
1) Connect using a first account: A1
2) Launch
The problem is still occurring, but less frequently (once per week).
--
X server stuck at 100%, screen black, severe, recovery: reboot from console
https://bugs.launchpad.net/bugs/590010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The switch user action is the best way for reproducing it (but not the
only one).
--
X server stuck at 100%, screen black, severe, recovery: reboot from console
https://bugs.launchpad.net/bugs/590010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The problem is still occurring, but less frequently (once per week).
--
X server stuck at 100%, screen frozen, critical, recovery: manual power off
https://bugs.launchpad.net/bugs/589352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The switch user action is the best way for reproducing it (but not the
only one).
--
X server stuck at 100%, screen frozen, critical, recovery: manual power off
https://bugs.launchpad.net/bugs/589352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
New occurrencies with the last linux-iso.
Frakking nVidia: I will not buy them anymore.
** Attachment added: New apport file
http://launchpadlibrarian.net/51364154/apport.xserver-xorg-core.BUbuXg.apport
--
X server stuck at 100%, screen frozen, critical, recovery: manual power off
Problems happens also without nVidia proprietary driver.
I will open a new bug.
--
X server stuck at 100%, screen frozen, critical, recovery: manual power off
https://bugs.launchpad.net/bugs/589352
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
This problem is closely related to bug Bug #589352
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/589352
It represents the case without nVidia proprietary driver.
I also attach the apport files of the two other Xorg processes.
ProblemType: Bug
DistroRelease:
** Attachment added: second Xorg process
http://launchpadlibrarian.net/49707919/apport.xserver-xorg-core.YT020g.apport
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/49707837/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
** Attachment added: third Xorg process
http://launchpadlibrarian.net/49707964/apport.xserver-xorg-core.I_S6nV.apport
--
X server stuck at 100%, screen black, severe, recovery: reboot from console
https://bugs.launchpad.net/bugs/590010
You received this bug notification because you are a
Please refer to the following bug for the no nVidia case.
Bug #590010
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/590010
--
X server stuck at 100%, screen frozen, critical, recovery: manual power off
https://bugs.launchpad.net/bugs/589352
You received this bug notification
The last action I did was to switch from user (switch user)
--
X server stuck at 100%, screen black, severe, recovery: reboot from console
https://bugs.launchpad.net/bugs/590010
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The problem appears after a few minutes, without any particular reason.
I will try to deactivate the nVidia driver and see if the problem
appears again.
--
X server stuck at 100%, screen frozen, critical, recovery: manual power off
https://bugs.launchpad.net/bugs/589352
You received this bug
Public bug reported:
X server stuck at 100% with screen frozen.
Critical: recovery via manual power off
Process Xorg was stopped manually to be able to run apport-cli. Before,
priority was manually set to minimum 19+20=39.
Problem appeared since the new linux-image update (2 days ago).
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/49625690/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/49625691/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/49625692/Dependencies.txt
**
Public bug reported:
Binary package hint: tex-common
The upgrade ended anyway. Just tex-common 2.06 caused problems.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: tex-common 2.06
ProcVersionSignature: Ubuntu 2.6.31-21.59-generic
Uname: Linux 2.6.31-21-generic x86_64
Architecture:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47924230/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/47924231/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
Same problem here. Further more, at first when I tried to import the
file, it threw an error stating that it wasn't a recognized pptp file.
So I uninstalled pptp network manager, restart nm-applet, and then threw
this same error: Error: does not look like a Cisco Compatible VPN
(vpnc) VPN
Hello, just wanted to confirm this. The time is being set an hour ahead
since Oct 4.
Bests,
--
invalid dst change for Argentina on Oct 5, 2008
https://bugs.launchpad.net/bugs/278850
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
*** This bug is a duplicate of bug 189814 ***
https://bugs.launchpad.net/bugs/189814
Hi,
Just in case someone lands here, the root cuase was discovered in
https://bugs.launchpad.net/ubuntu/+source/libsmbios/+bug/189814 and the
fix is being discussed, as well as some workarounds until it gets
It's on my Latitude D620. I can confirm that. Also as I said, i tried
downgrading to kernel 2.6.22 in Hardy from the Feisty repos and it
doesn't happen with the BIOS password set. So I think it's related
somehow to the kernel version too. Hope this helps.
--
HAL lockups or crashes dell laptops
Hi,
I'm the one of the duplicate bug :) and i do have a BIOS password
set... I'll try later without setting it although it sounds weird.. I'll
be back with the results.
Regards,
--
[hardy]computer and touchpad is buggy when running on battery
https://bugs.launchpad.net/bugs/189814
You
Hi... I can confirm that the problem disappears with no BIOS password.
Keep in mind that this didn't happen to me with kernel 2.6.22 and
started since 2.6.23 or .24... so might be somehow related?
--
[hardy]computer and touchpad is buggy when running on battery
Public bug reported:
Hello,
I'm having the exact same problem as this guy here:
http://www.nabble.com/psmouse.c-resync-failed-td16082494.html
but with my Dell D620 with BIOS version A10 and Ubuntu 8.04. I found out as
that guy, that it may be a bug in the recent kernels... I tried the ones
** Description changed:
Hello,
I'm having the exact same problem as this guy here:
http://www.nabble.com/psmouse.c-resync-failed-td16082494.html
but with my Dell D620 with BIOS version A10 and Ubuntu 8.04. I found out as
that guy, that it may be a bug in the recent kernels... I tried
Hi again
I can confirm that as it was said in the redhat bugzilla works.
Some combination of the latest kernel (2.6.25.6-55.fc9.x86_64), setting both
i8042.nomux=1 and psmouse.proto=imps as kernel parameters, and disabling Dim
display when idle in BOTH on AC and on battery seems to have fixed
46 matches
Mail list logo
