Public bug reported:
cat devices
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0
B: PROP=0
B: EV=21
B: SW=1
I: Bus=0019 Vendor= Product=0001 Vers
I just noticed this behavior. "sudo plymouth --quit" is my current
mitigation, as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766095
Title:
plymouthd constantly uses 5% of CPU
To manage n
Public bug reported:
I'm wondering whether this recurrent installation error of colord is
related to the freezes that the system undergoes very regularly
(compatibility with graphical card?).
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: colord 0.1.16-2ubuntu0.1
ProcVersionSignature:
Public bug reported:
E: colord: le sous-processus script post-installation installé a
retourné une erreur de sortie d'état 1
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: colord (not installed)
ProcVersionSignature: Ubuntu 3.2.0-33.52-generic 3.2.31
Uname: Linux 3.2.0-33-generic x86_6
I was also having this issue with Ubuntu 12.04 and encrypted home
directory. I removed the encryption for other reasons, and now
thunderbird is not pegging CPU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Has anyone tried the official (certified) version from the Nvidia
website? It has the same version number (260.19.12) that is known
broken for our machines. I'm guessing it also has the same bug.
Because of this, I'm not hopeful that our issue is going to be resolved
in the near future unfortunat
While I'm able to use the 256 driver, its really slow, so I'd also like
to know if there is any update on this issue. At this point the stack
traces I've seen indicate its a problem inside the nvidia driver itself.
There are also numerous other reports of this bug in different forums as
well.
--
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/659635/+attachment/1689908/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/659635/+attachment/1689909/+files/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http
Public bug reported:
Binary package hint: fglrx
I just fresh installed fglrx via the additional drivers application
(jockey) and for some reason, after installing it, the driver does not
detect and support 1152x864.
Back in 10.04, the driver supports that resolution.
I would like to add that th
Sorry, I meant fresh installed Ubuntu 10.10 Maverick Meerkat. But I did
install fglrx via additional drivers (jockey)
--
fglrx does not detect/support 1152x864 in Ubuntu 10.10
https://bugs.launchpad.net/bugs/659636
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/659636/+attachment/1689931/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/659636/+attachment/1689932/+files/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http
Public bug reported:
Binary package hint: fglrx
I just fresh installed fglrx via the additional drivers application
(jockey) and for some reason, after installing it, the driver does not
detect and support 1152x864.
Back in 10.04, the driver supports that resolution.
I would like to add that th
Same here on fresh Mavrick install. Sony Vaio w/Nvidia 330M. System
locks up right after starting X.
--
NVRM: os_raise_smp_barrier(), invalid context!
https://bugs.launchpad.net/bugs/656279
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I fixed this problem by editing the acpi-support file in /etc/default
and changed ENABLE_LAPTOP_MODE from false to true. Apparently this
didn't get set properly during the upgrade.
I don't know if this problem happens on a clean install, but it
certainly does during a upgrade from dapper.
Hope t
** Attachment added: "acpid log file"
http://librarian.launchpad.net/4936054/acpid
--
Dell B120 Laptop doesn't suspend properly
https://launchpad.net/bugs/68069
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "lshal -l attachment"
http://librarian.launchpad.net/4936050/lshal.output
--
Dell B120 Laptop doesn't suspend properly
https://launchpad.net/bugs/68069
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
lshal -l output attached
--
Dell B120 Laptop doesn't suspend properly
https://launchpad.net/bugs/68069
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Gnome, sorry I forgot to include that. I haven't tried KDE.
--
Dell B120 Laptop doesn't suspend properly
https://launchpad.net/bugs/68069
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I should also mention that performing a manual suspend works, but
setting the power settings to suspend when the lid is closed and running
on battery doesn't. So, I'm guessing that the lid switch handler is to
blame.
This feature had previously worked in dapper.
Hope that helps.
--
Dell B120 L
Public bug reported:
Running kernel 2.6.17. Suspend and hibernate do not work properly when
configured with lid closed. The system remains running. This is on a
system which was upgraded from dapper.
** Affects: Ubuntu
Importance: Undecided
Status: Unconfirmed
--
Dell B120 Lapt
I'm experiencing the same exact problem. The same issue is also being
seen when running the program itself, not only in the registration
screen. Apparently the font that it wants to use appears as only
rectangles.
--
After starting eagle the registration window has broken fonts
https://launchpa
Bump I see it not with just bold, effecting whole columns, and its
really annoying, since I like 8 monospace.
--
Bold fonts do the mambo
https://launchpad.net/bugs/33144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm that this is a SMP related issue. I re-built my kernel
with the only differences being that I changed my CPU to a Pentium-M,
turned off SMP, and modified the ticks to 250/sec.
Performance is back to that of Breezy on my Celeron-M 1.4Ghz laptop, and
I don't think its the different CP
23 matches
Mail list logo
