*** This bug is a duplicate of bug 71368 ***
https://bugs.launchpad.net/bugs/71368
This is still broken after a suspend/resume cycle (S3). Things are
working correctly before suspend/resume.
--
LCD panel won't stay powered off
https://bugs.launchpad.net/bugs/55648
You received this bug
Still a problem after suspend/resume. Works from initial boot until
before suspend/resume (S3).
** Changed in: xorg (Ubuntu)
Status: Fix Released = Unconfirmed
--
Laptop backlight stays always on
https://bugs.launchpad.net/bugs/71368
You received this bug notification because you are a
I ran the latest BIOS update, but there was no improvement.
--
cpuinfo_max_freq is (really) wrong
https://bugs.launchpad.net/bugs/91553
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Ok, I'll check to see if there is an update BIOS. For future reference,
what hints that the BIOS is wrong?
Also, I hadn't spotted that oops, thanks.
--
cpuinfo_max_freq is (really) wrong
https://launchpad.net/bugs/91553
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: cpuinfo
http://librarian.launchpad.net/6879972/cpuinfo.txt
--
cpuinfo_max_freq is (really) wrong
https://launchpad.net/bugs/91553
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: dmesg
http://librarian.launchpad.net/6879973/dmesg.txt
--
cpuinfo_max_freq is (really) wrong
https://launchpad.net/bugs/91553
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Certainly exists in 2.6.20-9-generic, have seen it in previous kernels
too. Possibly in all Feisty 2.6.20 kernels.
--
cpuinfo_max_freq is (really) wrong
https://launchpad.net/bugs/91553
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: linux-image-2.6-686
[EMAIL PROTECTED] cpufreq]$ pwd
/sys/devices/system/cpu/cpu0/cpufreq
[EMAIL PROTECTED] cpufreq]$ cat cpuinfo_max_freq
65535000
Should be the same as:
[EMAIL PROTECTED] cpufreq]$ cat scaling_max_freq
120
but:
[EMAIL
Oh, for reference:
[EMAIL PROTECTED] cpufreq]$ cat scaling_driver
acpi-cpufreq
[EMAIL PROTECTED] cpufreq]$ cat scaling_governor
conservative
--
cpuinfo_max_freq is (really) wrong
https://launchpad.net/bugs/91553
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It's worth noting that on Fedora 6 they display no tooltip.
--
tooltip on desktop switcher behaves incorrectly
https://launchpad.net/bugs/63483
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: cupsys
When printed at A0, the fonts on the border of the CUPS test page are
too large and overlap/run off the page. This is especially obvious on
the borders that measure in length in centimeters. It would be good if
the CUPS test page choose the size
** Attachment added: example photo
http://librarian.launchpad.net/6440839/cups-page-broken.jpg
--
CUPS test page does not look very good at A0
https://launchpad.net/bugs/85339
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Oops, wrong button.
** Changed in: gnome-panel (Ubuntu)
Status: Unconfirmed = Rejected
--
tooltip on desktop switcher behaves incorrectly
https://launchpad.net/bugs/63483
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Yep. Will also strace during next dist-upgrade.
Applets present are: notification-area, gweather, netstatus (x2),
cpufreq, battstat, multiload, clock, mixer, wncklet (x4), charpick,
tomboy and trashapplet.
--
gnome-panel freezes after dist-upgrade
https://launchpad.net/bugs/63481
--
Move from x.org to kernel.
** Changed in: xorg (Ubuntu)
Sourcepackagename: xorg = linux-meta
--
Xorg D-states on initialisation
https://launchpad.net/bugs/62113
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This is a bug between madwifi-ng and hermesAP, moving to l-r-m
** Changed in: dhcp3 (Ubuntu)
Sourcepackagename: dhcp3 = linux-restricted-modules-2.6.17
Status: Needs Info = Unconfirmed
--
Can no longer aquire IP address from certain DHCP servers
https://launchpad.net/bugs/57403
--
Public bug reported:
This is apparently the result of an Ubuntu patch in Edgy, not something
upstream.
In the desktop switcher, when you hover over a desktop it says Switch
between workspaces as expected. When you move between workspaces, the
tooltip flickers as if it is trying to display the
Public bug reported:
Binary package hint: gnome-panel
In Edgy, sometimes when dist-upgrading, gnome-panel freezes completely.
Not sure why yet, but this has happened three times.
** Affects: gnome-panel (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
gnome-panel freezes
** Bug watch added: Freedesktop Bugzilla #5665
https://bugs.freedesktop.org/show_bug.cgi?id=5665
** Also affects: xorg-server (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=5665
Importance: Unknown
Status: Unknown
--
LCD panel won't stay powered off
This also happens with -10, I am wondering if the tosh_acpi module is
somehow implicated.
--
Xorg D-states on initialisation
https://launchpad.net/bugs/62113
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Blacklisting toshiba_acpi, resolves this issue and allows me to boot -10
(of course, now I can't change my LCD brightness).
--
Xorg D-states on initialisation
https://launchpad.net/bugs/62113
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
More on this, you need to restart acpid after every suspend/resume
cycle. Noticed this in the X log:
When X starts up:
(II) Open ACPI successful (/var/run/acpid.socket)
After restarting acpid:
(WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused)
After resuming:
(II) Open ACPI
Restarting acpid without toshiba_acpi blacklisted wrote this backtrace
into the syslog.
** Attachment added: backtrace from syslog
http://librarian.launchpad.net/4521836/toshiba_acpi.txt
--
Xorg D-states on initialisation
https://launchpad.net/bugs/62113
--
ubuntu-bugs mailing list
Booting without splash does nothing.
But booting 2.6.17-7-generic (instead of -9-generic) fixes it fine.
Having had a more indepth look at -9-generic, a lot of things seem to be
doing a lot of complaining in dmesg.
--
Xorg D-states on initialisation
https://launchpad.net/bugs/62113
--
Public bug reported:
Binary package hint: xorg
Can't start X server. X server appears to have D-stated. This started
happening with one of the recent (around 23 Sept) X updates.
** Affects: xorg (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
--
Xorg D-states on
Including X log.
** Attachment added: X log
http://librarian.launchpad.net/4416484/Xorg.0.log
--
Xorg D-states on initialisation
https://launchpad.net/bugs/62113
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have completed a more in depth analysis. Things work correctly from
wired ethernet ports and from wireless using the identical dhcp server
version.
It seems that while the wireless is reporting signal/noise statistics,
it's not actually associating correctly to the AP (but the AP, running
Restarting acpid seems to solve this problem.
mjg59 davyd_: In that case, I suspect it has something to do with
faked key events
--
LCD panel won't stay powered off
https://launchpad.net/bugs/55648
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: dhcp-client
(Using NetworkManager, but last time I checked, I could replicate this
with NetworkManager turned off)
Since upgrading to Edgy, I can no longer seem to get IP addresses from
specific DHCP servers. This used to work without troubles. Other
This is still present:
[EMAIL PROTECTED] ~]$ apt-cache policy xserver-xorg-video-i810
xserver-xorg-video-i810:
Installed: 1:1.6.5-0ubuntu3
Candidate: 1:1.6.5-0ubuntu3
Version table:
*** 1:1.6.5-0ubuntu3 0
500 http://archive.ubuntu.com edgy/main Packages
100
Public bug reported:
Binary package hint: xorg
In Edgy:
Using `xset dpms force off` the LCD on my laptop (Toshiba Portege R200)
will turn off and then turn back on with the screen blanked about 20
seconds later.
This happens with and without gnome-screensaver and gnome-power-manager
running.
31 matches
Mail list logo