I can trigger a screen blanking (apart from the ones regularly happening
by themselves) by just executing xrandr without any parameters. Note
that only the external display (DVI) blanks when I do that, the internal
display of my Latitude E6400 works without any problems.
--
[Intrepid] Screen
Absolutely. I had no idea what this option might do before I found this bug
report.
What made it even more difficult is that it is (apparently wrongly) translated
to Systemeinstellungen (german), which means System settings (plural).
At least an explanation should be displayed when you hover
Public bug reported:
Binary package hint: xorg
I'm using a Dell Latitude E6400 (Intel 4500MHD) with a docking station. When
booting up while docked, the external monitor is enabled but using the wrong
resolution. When booting undocked and then docking the laptop, the correct
resolution for
** Attachment added: xrandr output after docking (undocked boot)
http://launchpadlibrarian.net/18697263/xrandr-output
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: Xorg.0.log after docking (undocked boot)
http://launchpadlibrarian.net/18697297/Xorg.0.log-undocked_boot
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of
** Attachment added: Output of lspci -nv
http://launchpadlibrarian.net/18697359/lspci
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log after docked boot
http://launchpadlibrarian.net/18697535/Xorg.0.log-docked_boot
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Version: Ubuntu 8.10 64bit
xserver-sorg-video-intel 2:2.4.1-1ubuntu10
I am running a Dell Latitude E6400 with the E-Port simple (docking
station). When using only the DVI-output of the docking station, the
attached Samsung
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/18927311/Xorg.0.log-flickering
--
Intel 4500MHD on Dell Latitude E6400 flickers on external display
https://bugs.launchpad.net/bugs/289657
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 275152 ***
https://bugs.launchpad.net/bugs/275152
** This bug has been marked a duplicate of bug 275152
[Intrepid] Screen flicker/resync on X4500HD
--
Intel 4500MHD on Dell Latitude E6400 flickers on external display
Also broken on my E6400. Neither suspend to RAM nor suspend to disk are working
with Ubuntu 8.10 beta. The machine is suspending and shutting down, but crashes
on resume (magic-sysreq keys don't work) in either case.
Attaching output of lspci -nv.
** Attachment added: lspci
Public bug reported:
Using Ubuntu 8.10 beta, the virtual terminals are not usable on a Dell Latitude
E6400. Usplash works fine, but after X is started the display blanks when
switching to a virtual terminal. I can however login blindly and execute
commands. The problem also exists when booting
** Attachment added: lspci -nv
http://launchpadlibrarian.net/18764782/lspci
--
Virtual terminal not working on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286904
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Strange! I just tried suspend to ram with /etc/acpi/sleep.sh force in order to
obtain further debug information. The first suspend did not resume correctly,
the second one apparently did (I am writing from the resumed system). Sound
however does not work again, I'm just getting distorted
Disregard the sound problem, apparently sound broke completely after
some update. Deleting personal configuration files resolved that.
--
suspend/resume broken on dell Latitude E6400 kernel 2.6.27-3
https://bugs.launchpad.net/bugs/269490
You received this bug notification because you are a
Suspend broke again after rebooting. I can't think of anything I did
differently this time, once it worked I could suspend/resume multiple
times in a row.
--
suspend/resume broken on dell Latitude E6400 kernel 2.6.27-3
https://bugs.launchpad.net/bugs/269490
You received this bug notification
** Description changed:
+ When the laptop is docked and connected to an external monitor:
Using Ubuntu 8.10 beta, the virtual terminals are not usable on a Dell
Latitude E6400. Usplash works fine, but after X is started the display blanks
when switching to a virtual terminal. I can however
X just crashed after clicking on the view button..
(K)Ubuntu 8.04
Kernel 2.6.24-16-generic
NVidia 169.12 (with GeForce FX 5600 NV31)
X.Org X Server 1.4.0.90
Kopete 0.12.7
** Attachment added: gdm logfile
http://launchpadlibrarian.net/14429132/%3A0.log
--
Kopete crashes desktop when trying
Still an issue in Ubuntu 9.04.
If you create a share writable by everyone through nautilus, the files uploaded
by anonymous users belong to nobody:nogroup with 0744, thus preventing the user
from editing the files without manually fixing the ownership via sudo.
| $ ls -l ~/test
| -rwxr--r-- 1
** Description changed:
Binary package hint: xorg
I'm using a Dell Latitude E6400 (Intel 4500MHD) with a docking station. When
booting up while docked, the external monitor is enabled but using the wrong
resolution. When booting undocked and then docking the laptop, the correct
I booted the Jaunty 64-bit Alpha 5 LiveCD and attached an encrypted disk
via USB. I was asked to enter the password to unlock it, but because the
cryptsetup package is missing it failed:
Unable to set up crypto device
Error org.freedesktop.Hal.Device.Volume.Crypto.CryptSetupMissing
Error setting
*** This bug is a duplicate of bug 334863 ***
https://bugs.launchpad.net/bugs/334863
** This bug has been marked a duplicate of bug 334863
[jaunty] notification are partially off-screen on res change
--
not always on the far-right of the screen
https://bugs.launchpad.net/bugs/337437
You
I just tried the Alpha 5 LiveCD.
- Booted docked with closed lid
- Internal and external display are enabled when X comes up (and although the
lid is closed, the backlight of the internal display stays on, but I guess
that's another bug)
- Both are automatically configured to run at 1152x864
** Attachment added: Xorg.0.log_afterboot
http://launchpadlibrarian.net/23511072/Xorg.0.log_afterboot
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: xrandr_afterboot
http://launchpadlibrarian.net/23511096/xrandr_afterboot
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Xorg.0.log_lvdsoff
http://launchpadlibrarian.net/23511082/Xorg.0.log_lvdsoff
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: xrandr_lvdsoff
http://launchpadlibrarian.net/23511101/xrandr_lvdsoff
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: Xorg.0.log_manual
http://launchpadlibrarian.net/23511095/Xorg.0.log_manual
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: xrandr_manual
http://launchpadlibrarian.net/2355/xrandr_manual
--
Incorrect resolution when docked on Dell Latitude E6400
https://bugs.launchpad.net/bugs/286001
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm this bug on Ubuntu 9.04. Hovering over something that pops up a
tooltip causes flickering. Evince is affected in fullscreen and presentation
mode (both are fullscreen modes), firefox in fullscreen mode.
Not using compiz solves the problem, no flickering with metacity.
evince:
Still reproducible in Ubuntu 9.04, reopening the bug.
** Changed in: compiz (Ubuntu)
Status: Invalid = New
--
firefox and evince in fullscreen mode flickers
https://bugs.launchpad.net/bugs/243318
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: nautilus-cd-burner
Steps to reproduce:
- Open CD/DVD Creator
- Add files or directories with url-encoded characters (e.g. %20, %21, ...) in
their names to the CD
- Click burn
Expected behaviour:
- The files and directories are successfully burned onto
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/24808790/Dependencies.txt
--
Files containing percent-encoded characters cannot be added to CD
https://bugs.launchpad.net/bugs/355147
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Done.
--
Files containing percent-encoded characters cannot be added to CD
https://bugs.launchpad.net/bugs/355147
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
** Bug watch added: GNOME Bug Tracker #578348
http://bugzilla.gnome.org/show_bug.cgi?id=578348
** Also affects: nautilus-cd-burner via
http://bugzilla.gnome.org/show_bug.cgi?id=578348
Importance: Unknown
Status: Unknown
--
Files containing percent-encoded characters cannot be
Fn-F8 (switch video output) is working in Jaunty:
keycode 235 = (keysym 0x1008ff59, XF86Display), state = 0x10
--
Dell Latitude E6400: Fn Hotkeys don't work
https://bugs.launchpad.net/bugs/341604
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I ran
xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode
\2 = \3, state = \1/p'
according to https://wiki.ubuntu.com/Hotkeys/Troubleshooting and pressed Fn-F8
on a Dell Latitude E6400 with Intel Graphics and BIOS version A09.
If I press Fn-F8 once, xev outputs:
Update: Now the internal display is correctly disabled and the external
display is set to its correct native resolution when gnome has started
up (docked boot, haven't tried an undocked boot). The login screen still
exhibits the original wrong behaviour, but this is far better than
before.
--
I was able to stop the flickering with my Samsung SyncMaster 214T (connected
via DVI) and the X4500HD.
xrandr --verbose lists two modes for 1600x1200. Using the preferred one
(which is selected automatically on startup) causes flickering, using the other
one has worked fine for the last 40
I just tried petri0's script on a Dell Latitude E6400 (X4500HD). Both suspend
and hibernate worked, it resumed successfully.
However, sound didn't work until /etc/init.d/alsa-utils was restarted. Fiddling
with the volume controls in gnome-volume-control before restarting alsa-utils
had no
I've been using mode 0x4a for over an hour now. The flickering is not
completely gone, but significantly reduced. It happened only a few times
in over an hour as opposed to every few minutes with mode 0x49.
--
[Intrepid] Screen flicker/resync on X4500HD
https://bugs.launchpad.net/bugs/275152
You
I just installed xserver-xorg-video-intel 2:2.5.1-1ubuntu5~intrepid and can
confirm Craig's findings. Attaching logs for docked/undocked boot.
One thing changed though: After an undocked boot, the correct resolutions for
the external monitor are now being detected and listed by xrandr after
Just booted 2.6.27-10 from proposed, unfortunately it didn't change anything on
my Latitude E6400. I can barely hear anything with master set to 65% (while
everything else is at 100%), rapidly getting louder when turning it up from
there.
Note that this is only true for the integrated headphone
** Changed in: eclipse-cdt (Ubuntu)
Status: Incomplete = Confirmed
--
CDT content assist extremely slow
https://bugs.launchpad.net/bugs/196203
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Still reproducible in 8.10. With openjdk-6-jdk 6b12-0ubuntu6 and eclipse-cdt
3.1.2-2 content assist blocks the UI for 5-10 seconds before the content assist
list is displayed.
Using sun-java6-jdk 6-10-0ubuntu2 the content assist list is displayed after
~100-200ms.
--
CDT content assist
This is fixed in Lucid (kernel 2.6.32). Plugging speakers into the
docking station now correctly disables the internal speakers and enables
them again after unplugging.
--
Internal speakers are not disabled if speakers are plugged into E-Port docking
station (Dell Latitude E6400) 8086:293e
Public bug reported:
Binary package hint: nautilus
The sidepane is a few pixels too high compared to the main pane (buttons and
pane itself) since the last nautilus update.
Attaching a screenshot with the misalignment marked.
ProblemType: Bug
Architecture: amd64
Date: Thu Jan 7 11:11:50 2010
** Attachment added: nautilus.png
http://launchpadlibrarian.net/37536846/nautilus.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37536847/Dependencies.txt
** Attachment added: usr_lib_nautilus.txt
http://launchpadlibrarian.net/37536848/usr_lib_nautilus.txt
--
** Attachment added: eog.png
http://launchpadlibrarian.net/37537079/eog.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37537080/Dependencies.txt
--
Inline error message truncated if too long
https://bugs.launchpad.net/bugs/504187
You received this bug
Public bug reported:
Binary package hint: eog
If eog displays an error message that is too long to fit into the width
of the window, it gets truncated.
It probably should either use multiple lines to display the error
message or use ellipses to indicate that there is more text that just
doesn't
Your screenshot shows an older version of nautilus, mine looked the same before
the update to 2.29.1-0ubuntu1 (I'm using Lucid).
There apparently were some UI changes upstream:
https://launchpad.net/ubuntu/+source/nautilus/1:2.29.1-0ubuntu1
My customizations only include disabling the toolbar,
Also happening on Lucid with:
pulseaudio 0.9.21-0ubuntu6
gnome-media 2.28.1-1ubuntu2
--
Changing volume resets balance
https://bugs.launchpad.net/bugs/413457
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
It's also working with the default version in lucid (Banshee 1.6 Beta 2
(1.5.1)), package version 1.5.1-1.
--
Default smart playlist Recently Added not working
https://bugs.launchpad.net/bugs/428388
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I redirected gdm's output to a logfile in /etc/init/gdm.conf (since it
wasn't logging anything anywhere when it failed), this is what I get
when it fails to start:
** (gdm-binary:1261): WARNING **: Couldn't connect to system bus: Failed
to connect to socket /var/run/dbus/system_bus_socket: No
According to dbus.conf and gdm.conf they both start at roughly the same time if
no remote filesystems are to be mounted.
Sometimes dbus is fast enough and sets itself up before gdm, sometimes gdm is
faster. When gdm starts and dbus is not yet ready, it just bails out (see
Robert, removing /lib/udev/rules.d/40-xserver-xorg-video-intel.rules
didn't fix it for me. Same thing as before, gdm-binary unable to connect
to the system bus and bailing out because of it.
--
gdm starts too early, X.org/VTs fail
https://bugs.launchpad.net/bugs/502838
You received this bug
Another way to trigger this crash:
1. Select any username
2. Hit cancel
3. Select any username
- gdm-simple-server segfaults and another xserver is started on the next
available vt (vt8 in my case) along with gdm-simple-slave, because the old
xserver is still running on vt7 (showing the login
** Attachment added: :0.log
http://launchpadlibrarian.net/37654026/%3A0.log
--
[lucid] gdm crashes after selecting a username twice
https://bugs.launchpad.net/bugs/503314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: :0-greeter.log
http://launchpadlibrarian.net/37654031/%3A0-greeter.log
--
[lucid] gdm crashes after selecting a username twice
https://bugs.launchpad.net/bugs/503314
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: :0-slave.log
http://launchpadlibrarian.net/37654038/%3A0-slave.log
** Changed in: gdm (Ubuntu)
Status: New = Confirmed
** Summary changed:
- [lucid] gdm crashes after wrong password given
+ [lucid] gdm crashes after selecting a username twice
--
[lucid] gdm
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37657619/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/37657620/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37657621/Dependencies.txt
**
dmesg after opening the lid again
** Attachment added: dmesg
http://launchpadlibrarian.net/37657686/dmesg
--
[gm45] *ERROR* Execbuf while wedged when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of
This may be a duplicate of https://bugs.launchpad.net/ubuntu/+source
/xserver-xorg-video-intel/+bug/503255, but since I can't reproduce this
by running xrandr, I filed a new bug.
--
[gm45] *ERROR* Execbuf while wedged when closing laptop lid with compiz
running
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Steps to reproduce:
1. Log in and have compiz activated in your user session
2. Close the laptop lid (gnome-power-manager is configured to blank the display
on lid close)
3. Open the laptop lid again
Expected result:
Display
** Bug watch added: GNOME Bug Tracker #606514
https://bugzilla.gnome.org/show_bug.cgi?id=606514
** Also affects: nautilus via
https://bugzilla.gnome.org/show_bug.cgi?id=606514
Importance: Unknown
Status: Unknown
--
Sidepane misaligned (a few pixels too high)
I followed the instructions on https://wiki.ubuntu.com/X/Troubleshooting/Freeze
on how to get a batchbuffer dump, unfortunately i915_batchbuffers is empty.
I inserted export INTEL_DEBUG=batch into /etc/init/gdm.conf, right before
exec gdm-binary $CONFIG_FILE, does this suffice?
** Attachment
Public bug reported:
Binary package hint: nautilus
1. Open any directory with files in it (e.g. Places (gnome-panel) - Desktop)
2. Drop-down menu of the sidebar has focus instead of the directory contents.
You first have to click somewhere in the content area or on a file/directory
before you
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37687659/Dependencies.txt
** Attachment added: usr_lib_nautilus.txt
http://launchpadlibrarian.net/37687660/usr_lib_nautilus.txt
--
Initial focus on sidebar menu instead of directory content, preventing
type-to-search
** Description changed:
Binary package hint: nautilus
1. Open any directory with files in it (e.g. Places (gnome-panel) - Desktop)
2. Drop-down menu of the sidebar has focus instead of the directory contents.
- You first have to click somewhere in the content area or on a
-
It's recoverable with xorg-edgers (either that, or the update to kernel
2.6.32-10)! The display is still blank (backlight off) after opening the lid
again, but vt-switching makes the display usable again, with compiz and
everything.
Attaching dmesg output and Xorg.0.log.
--
[gm45] *ERROR*
** Attachment added: dmesg
http://launchpadlibrarian.net/37714889/dmesg
--
[gm45] *ERROR* Execbuf while wedged when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: Xorg.0.log
http://launchpadlibrarian.net/37714949/Xorg.0.log
--
[gm45] *ERROR* Execbuf while wedged when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu
Bugs, which is
xserver-xorg-video-intel 2.10.0+git20100108.4902f546-0ubuntu0sarvatt
--
[gm45] *ERROR* Execbuf while wedged when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Alright, crashing with 2.9.1-1ubuntu1 as usual, recoverable with
2.10.0+git20100108.4902f546-0ubuntu0sarvatt by switching VTs.
--
[gm45] *ERROR* Execbuf while wedged when closing laptop lid with compiz
running
https://bugs.launchpad.net/bugs/505271
You received this bug notification because you
Public bug reported:
Binary package hint: human-theme
The shutdown icon is only provided in 22x22px and 24x24px, the shutdown dialog
however uses 48x48px icons.
This is visible when you hit your power button when you are in GDM (see
attached screenshot).
$ find
** Attachment added: screenshot.png
http://launchpadlibrarian.net/33396237/screenshot.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33396238/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33396239/XsessionErrors.txt
--
This is on a fresh and up-to-date installation of karmic.
** Attachment added: gdm.ogg
http://launchpadlibrarian.net/33400262/gdm.ogg
--
system-shutdown.png too small in HumanLoginIcons
https://bugs.launchpad.net/bugs/447850
You received this bug notification because you are a member of
According to the output of totem --gst-debug=2, it tries to use ffmpeg
to decode the video file (youtube (now?) uses compressed swf). ffmpeg
apparently doesn't support compressed swf files directly, they first
have to be decompressed by cws2fws.
--
Unable to play video from Youtube plugin
Public bug reported:
After usplash exits and before X is started, I'm seeing the following
message:
[ 19.483135] mmc1: Hardware doesn't specify base clock frequency.
ProblemType: Bug
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel],
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33315643/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33315645/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33315646/BootDmesg.txt
**
@Robbie in #13:
While adding console=tty6 to GRUB_CMDLINE_LINUX_DEFAULT does indeed hide any
non-kernel messages, it also hides the emergency shell one gets if a manual
fsck is necessary. usplash leaves you on tty1 when it exits, but the emergency
shell is waiting for you on tty6.
--
Boot
This is how it looks with xsplash_0.8.3+r85+200910091650 (this monitor
is being set to 1600x1200 from the 1152x864 it had during login, the
laptop display is being disabled).
** Attachment added: ppa_short.ogg
http://launchpadlibrarian.net/33379418/ppa_short.ogg
--
Xsplash image sized to
I ran totem with --gst-debug-level=2, ffmpeg complains:
Compressed SWF format not supported.
I downloaded the file it tried to play back, file states: Macromedia Flash
data (compressed), version 8
Apparently ffmpeg can deal with those files if they are decompressed with
cws2fws first (I did
Muting PC Beep (really muting, not just completely turning it down) in
alsamixer on each boot helps as a workaround in my case.
$ cat /proc/asound/card0/codec#* | grep -i codec
Codec: IDT 92HD71B7X
Codec: Intel G45 DEVCTG
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
*** This bug is a duplicate of bug 449940 ***
https://bugs.launchpad.net/bugs/449940
** This bug has been marked a duplicate of bug 449940
System beeps very loud and annoying if when muted.
--
Karmic uses normal speakers as PC-beep
https://bugs.launchpad.net/bugs/451575
You received this
Public bug reported:
Binary package hint: gnome-power-manager
My laptop display backlight has 16 brightness values (0-15). If
gnome-power-manager is not running and I set it all the way down to 0 (via
fn-brightness-down) and watch
/sys/class/backlight/acpi_video0/actual_brightness as I
** Attachment added: gpm_wrongvalues.txt
http://launchpadlibrarian.net/33820204/gpm_wrongvalues.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33820205/Dependencies.txt
** Attachment added: DevkitPower.txt
http://launchpadlibrarian.net/33820206/DevkitPower.txt
Public bug reported:
I suspended my laptop to ram and resumed it several hours later.
Everything seems to be working fine, but the kernel apparently was
complaining.
ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be
restarted.
Architecture: amd64
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/32454901/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/32454902/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/32454903/BootDmesg.txt
**
The behavior has changed: Pressing fn-brightness-up/down while
gnome-power-manager is running still causes actual_brightness to jump up/down
two levels on each keypress, but it now represents the correct brightness (i.e.
my display backlight really increases or decreases its brightness by two
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33942607/XsessionErrors.txt
** Tags added: apport-collected
--
sets wrong brightness value with xrandr
https://bugs.launchpad.net/bugs/453748
You received this bug notification because you are a member of Ubuntu
Bugs,
Architecture: amd64
Dependencies:
DistroRelease: Ubuntu 9.10
Package: hal-info 20090716-0ubuntu1
PackageArchitecture: all
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Uname: Linux 2.6.31-14-generic x86_64
UserGroups: adm
@AlexHofbauer
If http://en.wikipedia.org/wiki/Pointing_stick#Problems is right, then this
isn't a driver problem but a hardware problem.
--
ALPS DualPoint Touchpad flaky performance
https://bugs.launchpad.net/bugs/296610
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Binary package hint: evince
Evince can't open compressed PDFs because apparmor doesn't let it
execute bzip2.
[172782.885301] type=1503 audit(1257885293.523:55): operation=exec
pid=22803 parent=22802 profile=/usr/bin/evince requested_mask=::x
denied_mask=::x fsuid=1000
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35498109/Dependencies.txt
** Attachment added: KernLog.txt
http://launchpadlibrarian.net/35498110/KernLog.txt
** Attachment added: RelatedPackageVersions.txt
@Martin-Éric Racine
The version from your ppa works just fine, I tried several videos from
different searches and had no problems.
--
Unable to play video from Youtube plugin results
https://bugs.launchpad.net/bugs/459423
You received this bug notification because you are a member of Ubuntu
03:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
Adapter (rev 21)
03:01.2 SD Host controller: Ricoh Co Ltd R5C843 MMC Host Controller (rev 11)
--
MMC cards no longer auto mount
https://bugs.launchpad.net/bugs/429257
You received this bug notification because you are a
Confirmed on a Dell Latitude E6400. The kernel detects the card and udev
creates /dev/mmcblk0 and /dev/mmcblk0p1. Gnome doesn't list it anywhere,
but I can mount it manually as root. It was working a few weeks ago.
KERNEL[1256317077.981652] add
Still an issue in Ubuntu 9.04. Scrolling when the mouse cursor is
between GTK widgets and compiz is active causes a workspace switch.
I don't know whether compiz really is to blame here as metacity (to my
knowledge) doesn't support changing the workspace by scrolling while
hovering over the
Apr 26 09:26:38 tezra kernel: [26405.940556] BUG: unable to handle kernel NULL
pointer dereference at 0008
Apr 26 09:26:38 tezra kernel: [26405.940587] IP: [a0448d7c]
nfs_readpage_release_full+0x2c/0x60 [nfs]
Apr 26 09:26:38 tezra kernel: [26405.940634] PGD 0
Apr 26 09:26:38
1 - 100 of 378 matches
Mail list logo
