** Package changed: linux (Ubuntu) => xserver-xorg-video-ati (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
Resume on glamor cause GPU lockup/screen corruption on Radeon 3100
It looks like (with glamor) that adding:
Option "ShadowPrimary" "on"
is enough to work around the bug on resume.
** Summary changed:
- Resume on glamor cause GPU lockup/screen corruption on Radeon 3100 Graphics"
(ChipID = 0x9611) if some options not used
+ Resume on glamor cause GPU
It looks like suspend-resume works with glamor if I have the next two
lines (I think, still unsure, that both are necessary):
Section "Device"
#Identifier "Configured Video Device"
#Driver "radeon"
#Option "AccelMethod" "EXA"
Identifier "Configured Video Device"
Driver
I see in dmesg log after resume:
oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: debugfs: File
'radeon_ring_gfx' in directory '0' already pr>
Also:
oct 01 16:48:25 client-HP-Compaq-dc5850-Small-Form-Factor kernel: serial 00:04:
disabled
oct 01 16:48:25
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529967/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529970/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529968/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529969/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529966/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529965/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529963/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529961/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529964/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529962/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529960/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529959/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529958/+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/1944991
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529957/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1944991/+attachment/5529956/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
apport information
** Tags added: apport-collected impish
** Description changed:
GPU: ATI Radeon 3100 Graphics (ChipID = 0x9611) (RS780)
GPU Lockup message in dmesg output after resume:
[ 916.000550] radeon :01:05.0: ring 0 stalled for more than 10084msec
[ 916.000569] radeon
I found the following link:
https://forum.manjaro.org/t/new-install-amd-fx-6300-wont-wake-from-suspend/39471/10
Suggesting that setting TearFree on may help (RS780L)
However... I wonder if ShadowPrimary did not help.
Section "Device"
Identifier "Radeon"
Driver "radeon"
Option
I see there is already a proposed patch...
But I'd like to mention https://wiki.ubuntu.com/DebuggingTouchpadDetection for
others.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342561
Title:
[Asus
If you think about using this with amdgpu driver rather than radeon...
use 'Option "AccelMethod" "none"' rather than EXA... because I think,
not sure, amdgpu does not support EXA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Suggested /etc/X11/xorg.conf file.
I just edited it a bit... not really tested.
** Attachment added: "Suggested /etc/X11/xorg.conf file to work around the bug"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+attachment/5527755/+files/xorg.conf
--
You received this bug
** Attachment added: "Dmesg showing errors after resume"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944991/+attachment/5527751/+files/dmesg_after_resume.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm I will not have access to that particular machine...
But maybe I will find an other computer affected by this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
Resume
Added a comment linking here on
https://bugzilla.kernel.org/show_bug.cgi?id=85421
** Bug watch added: Linux Kernel Bug Tracker #85421
https://bugzilla.kernel.org/show_bug.cgi?id=85421
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I am unsure if I will have access again to the computer.
But if that's the case, I intend the suggested apport-collect command.
Also, to do my tests I did use:
sudo su
echo mem > /sys/state/power
to cause suspend to ram.
--
You received this bug notification because you are a member of Ubuntu
The BIOS of that computer have some ACPI bugs: (I believe latest BIOS but
unsure... I did upgrade to 3.14) but still showing as 3.14.
DMI: Hewlett-Packard HP Compaq dc5850 Small Form Factor/3029h, BIOS 786F6
v03.14 11/15/2011
[0.283156] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig
I note that daily Ubuntu [will become Ubuntu 21.10] (of yesterday) was
affected by this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944991
Title:
Resume with glamor cause GPU
Public bug reported:
GPU: ATI Radeon 3100 Graphics (ChipID = 0x9611) (RS780)
GPU Lockup message in dmesg output after resume:
[ 916.000550] radeon :01:05.0: ring 0 stalled for more than 10084msec
[ 916.000569] radeon :01:05.0: GPU lockup (current fence id
0x20cc last fence
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923302
Title:
tumblerd crashed with SIGSEGV (memory leaks detected)
To manage notifications about
Like in my yet private bug #1923302 Stack memory exhausted (SP below
stack segment)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1168558
Title:
tumblerd crashed with SIGSEGV in
The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791312
Title:
ubuntu 18.04 flickering screen with Radeon X1600
To manage
The patch is included in:
Linux 4.14.125
Linux 4.19.50
Linux 5.1.9
I don't have access to the laptop on which I investigated this problem anymore.
But it could be tested from the built kernel packages at:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14.125/
** Patch added: "patch radeon-display.c for latest kernel (5.0.0rc7)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791312/+attachment/5240017/+files/radeon-display.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, It seems to take more than 12 hours ( I did stopped it ) to compile a
kernel (many features deactivated) on my atom based laptop. Will retry.
But the line I wanted to comment out does not seems to exist anymore.
But I found that the function to select PLL values show them before returning
Indeed, the two radeon parameters for PLL mention in previous message
does not seems to appear anymore in modinfo radeon.
paul@paul-NC210-NC110:~/linux-stable$ git log --oneline v3.15-rc1..v3.15-rc2 |
grep radeon
bcddee29b0b8 drm/radeon/ci: make sure mc ucode is loaded before checking the
size
From: https://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/CHANGES
I see the folowing changes for radeon:
Alex Deucher (13):
drm/radeon/dp: handle zero sized i2c over aux transactions (v2)
drm/dp/i2c: send bare addresses to properly reset i2c connections (v4)
Ok, I have access at "work" on a Compaq nx9420, for a few days.
linux 3.15.0-rc2 is first one to flickers, but goes to busybox
linux 3.15.0-rc1 does not flickers, but goes to busybox
I found: mounting /dev/sda1 on /root: invalid argument
and then initrd not mounting.
previous version,
I just retried by installing headers, then reinstall kernel-generic.
This time wifi works.
Note that these packages won't show in Synaptic.
Will show in dpkg -l|grep kernel. Use dpkg -r to remove them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Well, I tested on my laptop with:
paul@paul-NC210-NC110:~$ cat /proc/version
Linux version 3.14.79-031479-generic (kernel@gloin) (gcc version 4.8.4 (Ubuntu
4.8.4-2ubuntu1~14.04.3) ) #20160910530 SMP Sun Sep 11 09:41:06 UTC 2016
When I used gdebi to install the kernel .deb, in the details, there
Thanks for trying the tearfree option! (ok, it don't work)
By reading: https://wiki.ubuntu.com/Kernel/MainlineBuilds
I discovered: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
which would allow to download prebuild .deb for old mwainline kernels.
I am a bit sceptical if new versions
Someone said:
"I tried this with a Ubuntu 17.10 and could not boot. I had to use a rescue
boot and remove the lines again to get it up and running."
from:https://askubuntu.com/questions/794865/16-04-ati-mobility-radeon-x1600-full-resolution-flickering
So, try with care!
--
You received this bug
I guess I would rather add the two option lines (with same indentation) to:
file:///usr/share/X11/xorg.conf.d/10-radeon.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791312
Title:
ubuntu
The bug have been reported upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=108514
https://forums.linuxmint.com/viewtopic.php?t=229387
suggest the bug could be "fixed" by creating
/usr/share/X11/xorg.conf.d/20-radeon.conf with:
Section "Device"
Identifier "Radeon"
Driver
** Project changed: linuxmint => update-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1735067
Title:
upgrade to Mint 18.3 not in edit if system is in french
To manage
I copy here a link to message of someone who seems to have investigated this
quite far:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/686859/comments/15
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: artful beta1
** Tags added: grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1267922
Title:
Installer becomes confused and crashes when grub-install fails
To manage notifications
This is still an issue in 17.10 beta 1 (xubuntu 32 bits).
In my case, I created LVM partitions, and ubiquity suggested to install grub on
dm-0, that sounded
odd to me, but I tried it. Grub failed to install. I could select new
destination in the window,
to try, bug nothing happen when I
I just made the updates, without restarting (because I use 'Try Ubuntu').
Now it does launch!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714634
Title:
starting gnome-software: segfault at 0 ip
Public bug reported:
In: xubuntu-17.10-beta1-desktop-i386.iso, running in 'Try Ubuntu'.
Everytime I try to start gnome-software I get nothing except this error in
dmesg:
[ 388.510237] gnome-software[4251]: segfault at 0 ip b64548e6 sp bffaa1c8
error 4 in libc-2.24.so[b63c4000+1b3000]
[
I have an hypothesis.
I have seen that when I do a grub ls on my bios_boot (flag in GPARTED)
partition, it takes about
3 mins to list it. I believe this is due to the fact that I put clear partition
typed for that
partition in gparted. So I belive that when grub 2.0.2 do a search on that
Public bug reported:
Was trying Lubuntu 16.10 offline.
First I tried intall in Grub, but grub-install failed, and was gone in the
popup window error (which there is no way to close, but a bug for that already
exist).
So I try to install in "Test Ubuntu", but it did the same.
I search for
Think I got the same with Lubuntu 16.10, because grub-install is not present,
grub-pc
is not part of the DVD, and I was offline I got that dialog.
It is responsive (I can select any options) but if I select continue
installation, or
end installation, or close the window with close decoration,
Lubuntu 16.10 (32&64 bits) works fine (install from grub menu).
Seems to have change quite much since 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632184
Title:
image build with
After trying to reboot machine to test, an error occured and system opened me a
session for me
to test what was going on.
In it I just ran "$ gksudo ubiquity gtk_ui" and it worked flawlessly.
Same medium, same answers, but this time in the environment, in root mode.
Which suggests to me that
Indeed I had chosen 'Install' directly in Grub (which seems to suggest
that because it is not run by root, it failed to create a temporary file
in /target/etc/default while installing language pack).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1579454/comments/10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632184
Title:
image build with bodhibuilder crash near end-installation
Now that I look at the end of Syslog, this is probably more relevent:
Oct 10 22:58:33 gl finish-install: Disabling CDROM entries in sources.list
Oct 10 22:58:33 gl ubiquity: sed: impossible d'ouvrir le fichier temporaire
/target/etc/apt/sedP1IjGy: Permission non accordée
Oct 10 22:58:33 gl
Part of my add_info function as it appears on my computer:
def add_info(report, ui):
add_installation_log(report, 'UbiquitySyslog', 'syslog')
syslog = report['UbiquitySyslog']
if 'Buffer I/O error on device' in syslog:
if re.search('Attached .* CD-ROM (\w+)', syslog):
Similar but not identical bug #1495055 in 15.10 resulting in:
ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File
Very similar report reported on VLC 4 years ago:
https://trac.videolan.org/vlc/ticket/7651
** Bug watch added: VLC Trac #7651
http://trac.videolan.org/vlc/ticket/7651
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
I think I got this error most of the time trying to install LXLE 16.04, on many
old computers.
But pretty first time I get apport running fine, and I am on my own computer
having time to
debug and investigate rather than just use LXLE 12.04.5 like we usually do.
This is
I now guess slideshow is/was using debconf at installation time to request
information.
I guess this is ubiquity that use webkit for ... I don t know (don t think it
is the progress bar... maybe for debconf finally).
So probably any package using debconf trigger the problem.
Not sure if it is
Well, I think I made this bug much more complex than it is.
My stacktrace shows no problem with webkit... other bug I mention was having.
Here, the problem is only that the flush need to be inside try catch, because
the write stream have been receive
at class initialisation.
We don't control
I just have this too with Linux Mint 17.1 Cinnamon DVD.
My crash:
/***
Jan 28 06:33:13 mint ubiquity:
Jan 28 06:33:14 mint /plugininstall.py: Exception during installation:
Jan 28 06:33:14 mint /plugininstall.py: Traceback (most recent call last):
Jan 28 06:33:14 mint /plugininstall.py: File
** Attachment added: Paul's /var/log/installer/debug
https://bugs.launchpad.net/linuxmint/+bug/873239/+attachment/4307056/+files/debug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/873239
Title:
I note the following repeated many times in main.log:
2010-05-07 13:43:27,890 WARNING updateStatus: dlFailed on
'http://security.ubuntu.com/ubuntu/dists/karmic-security/main/i18n/Translation-en_US.bz2'
I note the following in apt.log:
Package python-gtksourceview2 has broken Depends on
Do you have xubuntu-desktop installed on this machine?
There is a known bug, bug #57143 that make it problematic to update
ubuntu-desktop if xubuntu-desktop is there.
I doubt this is your problem... but it seems worth to ask.
** Changed in: update-manager (Ubuntu)
Status: New =
** Summary changed:
- can't upgrade to lucid
+ The package 'xubuntu-desktop' is marked for removal but it is in the removal
blacklist karmic2lucid
--
The package 'xubuntu-desktop' is marked for removal but it is in the removal
blacklist karmic2lucid
https://bugs.launchpad.net/bugs/576920
You
Sorry, I meant bug #571743
--
Can not mark 'ubuntu-desktop' for upgrade
https://bugs.launchpad.net/bugs/576953
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http://www.edmondscommerce.co.uk/ubuntu/ubuntu-10-04-upgrade-package-ubuntu-desktop-is-marked-for-removal-but-is-in-the-removal-blacklist-solution/
seems to suggest that:
apt-get remove xubuntu-desktop
then rebooting, then update the problem could work around the problem.
Some similarity,
Hi, thank you for reporting this bug.
Looking at the information given:
DistroRelease: Ubuntu 9.10
...
Package: update-manager 1:0.111.10
I come to the conclusion that you probably did not update the system before
upgrading, since current version of update-manager in karmic (9.10) repository
Marking as Fix Released, since the original poster claim the problem
does not happens anymore in 10.04.
** Changed in: cups (Ubuntu)
Status: Confirmed = Fix Released
--
Brother MFC8840D errors on 1st print job
https://bugs.launchpad.net/bugs/306401
You received this bug notification
Marking my own bug as Invalid, becoming very old, was cleared by
removing cache files, and never rehappened.
** Changed in: firefox-3.0 (Ubuntu)
Status: New = Invalid
--
Firefox 3.0.8 address does not change when changing tab
https://bugs.launchpad.net/bugs/351115
You received this bug
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Confirmed
--
g-p-m brightness not applied anymore after rebooting
https://bugs.launchpad.net/bugs/503577
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
The real issue here is that when pressing the brightness keys, the brightness
value in gconf is not updated
I think you are oversimplifying this bug.
Well you do have much more experience than me but for me, there seems to be 3
sub-bugs in this bug:
1) Normal drivers are unable to update the
I am trying to summarise some info take from other bugs here.
In bug #230421, we learn that the following changed in the acpi-support package
in Ubuntu 9.10:
* Drop events/video_brightness{down,up}, video_brightness{up,down}.sh: at
least some platforms that use these ACPI sequences are
you did the 'sudo update-grub'? Then rebooted?
I would probably try with 'acpi=strict' if I were you.
Did you, or do you intend to update the BIOS?
--
HP DV5 - Can't suspend, get a Lock Screen instad of suspend
https://bugs.launchpad.net/bugs/501323
You received this bug notification because
Just for testing 'acpi=strict' it is easier to just type 'e' after
booting in Grub, then edit the line with 'e', then do Ctrl-X to boot
with the temporarily modified version.
--
HP DV5 - Can't suspend, get a Lock Screen instad of suspend
https://bugs.launchpad.net/bugs/501323
You received this
From bug #503577, on a Dell mini 10, 'apci_backlight=vendor' kernel parameter
seems to make it work.
acpi_backlight=[HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g. thinkpad_acpi, sony_acpi, etc.) instead
of the ACPI video.ko
*** This bug is a duplicate of bug 384304 ***
https://bugs.launchpad.net/bugs/384304
** Also affects: devicekit-power (Ubuntu)
Importance: Undecided
Status: New
** Changed in: devicekit-power (Ubuntu)
Status: New = Confirmed
** Changed in: gnome-power-manager (Ubuntu)
I see from your BootDmesg.txt file:
[0.00] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-17-generic
root=UUID=1257db60-9fbe-4a1c-aad6-9303cbff6640 ro quiet splash noacpi
The noacpi option here is not the default as far as I know, you did add it?
From
I suggest you first try to use 'e' to edit the command line in Grub menu when
you boot first.
Then if you want to do permanent change:
Oh, reading about Grub2 at: http://doc.ubuntu-fr.org/grub-pc (I speak french
too ^^), then I think that the file to be edited is:
gksudo gedit /etc/default/grub
It could be link to relatively old bug #301353, which suggest (from
http://bugzilla.kernel.org/show_bug.cgi?id=12113#c13) that bios update
from HP (F21) solves the problem.
Can you determinate the BIOS version you have?
maybe 'dmidecode' command can help you.
A message on HP forum from May 29,
BTW, it could be a bit like on my computer... when I hibernate, computer
did seems to shut down, but it looks like an event wakes it up less than
1 second after, and then it does resume, and show the lock screen which
is normal after a successfull resume as far as I know.
Since I have changed the
I note the following from BootDMesg.txt:
[0.262168] ACPI: Power Resource [PF0] (on)
[0.262211] ACPI: Power Resource [PF1] (on)
[0.262252] ACPI: Power Resource [PF2] (on)
[0.262293] ACPI: Power Resource [PF3] (on)
[0.262334] ACPI: Power Resource [PF4] (on)
[0.262377] ACPI:
DevkitPower.txt says that the battery is fully-charged (state):
Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT0
native-path:
/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C09:00/PNP0C0A:00/power_supply/BAT0
vendor: SANYO
model:
** Summary changed:
- Gnome power manager ignores screen settings
+ g-p-m brightness not applied anymore after rebooting
--
g-p-m brightness not applied anymore after rebooting
https://bugs.launchpad.net/bugs/503577
You received this bug notification because you are a member of Ubuntu
Bugs,
Could it be:
acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g. thinkpad_acpi, sony_acpi, etc.) instead
Reporter of bug #503577, suggest that adding kernel boot options:
apci_brightness=vendor although I believe it must be:
acpi_backlight=vendor because I don't find acpi_brightness kernel option.
As explained in http://ubuntuforums.org/showpost.php?p=8612908postcount=828
But I guess it has to be
I think it could be a duplicate of bug #384304
That would means your bug would happens when your battery if almost
full.
Also, the output of devkit-power -d would show near the end:
on-battery: no
when in fact you are on-battery (AC unplug).
Could you confirm that?
--
screen doesn't
** Also affects: devicekit-power (Ubuntu)
Importance: Undecided
Status: New
--
wrong charge level computed/reported
https://bugs.launchpad.net/bugs/501500
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
** Changed in: devicekit-power (Ubuntu)
Status: New = Confirmed
--
wrong charge level computed/reported
https://bugs.launchpad.net/bugs/501500
You received this bug notification because you are a member of Ubuntu
As I understand the results you got from 'apport-collect 501323' , a new
window or tab should have opened in your browser executing this, or you
could copy the link to the authorization page; but you did not seems to
have given the permission to apport-collect to run on this web page.
I suggest
I note from http://ubuntuforums.org/showthread.php?t=1282161:
I purchased new Toshiba Satellite M505-S4945 laptop and installed 64-bit
Jaunty. Everything works great except that the fan cannot be turned on due to
broken ACPI tables from Phoenix BIOS. The fan makes a big difference (40C vs
As I have changed the package of this bug to the kernel (from
gnome-power-manager), please type:
apport-collect -p linux 500666
to attach newly needed information to this bug.
--
Toshiba M505-S4972 The Fan does not work unless i suspend and bring it back up
As I read the link you have given (
http://blogs.gnome.org/hughsie/2009/08/17/gnome-power-manager-and-
blanking-removal-of-bodges/ ), then going to:
https://bugs.launchpad.net/bugs/413168
I would suspect that this bug was fixed in:
Well, in http://ubuntuforums.org/showpost.php?p=8612908postcount=828
suggest that: adding nolapic allows to use dell smbios for changing
backlight (brightness) in grub.
Although I have not used gnome-power-manager brightness feature, I believe it
is not a bug.
If I read:
1 - 100 of 1636 matches
Mail list logo
