Thanks!
It works for me :)
Lenovo Yoga 2 Pro with 32-bit Ubuntu 14.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1287341
Title:
Touchscreen controls both
I can also confirm that 0ubuntu11 solves the problem... thanks for a
quick solution to the problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1136216
Title:
I can confirm that installing gnome-control-center verion
3.4.2-0ubuntu0.9 solves the problem.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1136216
Title:
gnome
*** This bug is a duplicate of bug 1028360 ***
https://bugs.launchpad.net/bugs/1028360
** This bug has been marked a duplicate of bug 1028360
Window has double(?) heigh
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to zenity in
Pedro, I'm sure you are experiencing a bug and that you want to report
it so that it can be fixed. However, in order to do that, please file a
new bug instead of commenting on a bug report for a bug that has already
been fixed.
--
You received this bug notification because you are a member of
I have tested 0.9.7-1ubuntu1.1, and now my iPhone (with iOS 4.2.1) is
detected. It wasn't before upgrading from 0.9.7-1ubuntu1.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu.
This is not an xorg-related issue, but rather a suboptimal behaviour of
some gnome desktop component. I'm therefore reassigning to the gnome-
desktop source package.
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-desktop
(Ubuntu)
--
Desktop keep align
I've run Hardy on a few computers where the home directories were NFS-
mounted. Because of some NFS-problems they would sometimes lose the
connection, and thus the users would have no home directory. In that
case, there would always be a notification box right after login which
said something like
When starting only with xterm instead of gnome, `xset q` has the lines
Keyboard Control:
auto repeat: onkey click percent: 0LED mask:
After running `gnome-session` which starts gnome, it is changed to:
Keyboard Control:
auto repeat: offkey click percent: 0LED
The auto-repeat issue is probably the same as bug 514336. Please only
report one issue per bug report since keeping track of what is fixed and
not gets pretty hard otherwise.
--
auto-repeat stopped, and slider is too sensitive
https://bugs.launchpad.net/bugs/515108
You received this bug
Workaround: In a terminal, write `xset r on`.
--
Key presses repeat when key is held down does not work
https://bugs.launchpad.net/bugs/514336
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in ubuntu.
--
desktop-bugs
*** This bug is a duplicate of bug 514562 ***
https://bugs.launchpad.net/bugs/514562
** This bug has been marked a duplicate of bug 514562
Default values stripped from schemas with empty short_desc attribute
--
auto-repeat stopped, and slider is too sensitive
gconf 2.28-1ubuntu5 did not fix this for me. I tried downgrading gconf2
to 2.28-1ubuntu4 and upgrading again, but to no avail. Running `xset r
on` after each login is a workaround for now. Anything I can run in
order to fix this?
--
Default values stripped from schemas with empty short_desc
Found the problem: During troubleshooting I had turned off keyboard
repetition in System - Keyboard - General, since when this bug was
present, I would get double characters (probably because the delay got
set to zero). For my test user which hadn't messed around with the
settings, it worked again
Public bug reported:
Binary package hint: yelp
When the USB Key for 3G connection is plugged, a message box is comming a few
seconds after:
error mounting: mount exited with exit code 1: helper failed with: mount:
special device /dev/sr0 does not exist
The same USB key was running with the
** Attachment added: result of 'lsb_release -rd command
http://launchpadlibrarian.net/37662872/lsb_release.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/37662873/Dependencies.txt
** Attachment added: ProcMaps.txt
That's strange, my menu.lst wasn't updating for some reason when I
installed new kernels.
I had the same behaviour with an early install of karmic. I thought it
was because I also had windows and Jaunty on other partitions. Next time
I installed karmic it started updating menu.lst after every
** Tags added: 915gm black-screen
--
[i915gm] screen black when clicked
https://bugs.launchpad.net/bugs/302175
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Tags added: gm45 jaunty
--
[GM45, 945] Unable to mirror to external monitor
https://bugs.launchpad.net/bugs/368518
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
--
desktop-bugs mailing list
I have tested with daily-live from 20090708, and the problem is gone
(strangely enough since I have it on the installed system). I have
tested both KMS and UMS and both on the Thinkpad X61 Tablet and HP
Compaq nx7400. There is no sign of any SQUASHFS errors in the dmesg
output anymore.
**
Like for bug 311362, killing gnome-screensaver from the console also
lets med suspend and resume without problems later (resuming directly to
the session without the screensaver kicking in).
** Also affects: gnome-screensaver (Ubuntu)
Importance: Undecided
Status: New
--
[i965] blank
I'm mostly using the installed version or LiveUSB nowadays, but this
problem now occurs even for the installed version (see bug 389968) and
if it is not the same bug the other bug is probably masking this one.
--
[i965, Jaunty] Hung screensaver after resume from suspend (LiveCD only)
** Summary changed:
- Closing and opening lid sometimes leads to screen ENDLESSLY BLINKING
+ [i965gm] Closing and opening lid sometimes leads to screen ENDLESSLY BLINKING
** Description changed:
Binary package hint: gnome-power-manager
Sometimes, on my laptop running latest Jaunty, there
For xorg-related bugs we need the following in order to get anywhere:
- /var/log/Xorg.0.log (the one with the messages you mentioned in the bug
description)
- the output of `lspci -vvnn`
- /etc/X11/xorg.conf (unless unchanged)
Could you please attach those files to this bug report?
** Changed
Stephen, please file a new bug report for your problem. Since you get a
segmentation fault, it should be possible to get a backtrace. See
https://wiki.ubuntu.com/X/Backtracing .
--
[GM45, 945] Unable to mirror to external monitor
https://bugs.launchpad.net/bugs/368518
You received this bug
For completeness and to help people not familiar with xrandr work around
this bug, could you state the exact xrandr command the achieves the
desired outcome?
--
[GM45, 945] Unable to mirror to external monitor
https://bugs.launchpad.net/bugs/368518
You received this bug notification because you
The Display settings GUI dialog is the program gnome-display-properties,
which is part of the gnome-control-center binary and source packages. I
have therefore added gnome-control-center to this bug.
** Also affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
--
*** This bug is a duplicate of bug 367546 ***
https://bugs.launchpad.net/bugs/367546
** This bug has been marked a duplicate of bug 367456
context-menu shows up blank when dual screens in vertical orientation
--
[i865g] video playback fails with (EE) intel(0): Failed to pin xv buffer
Maybe it could be fixed since many people have this intel video card.
Shouldn't it be fixed in xserver-xorg-video-intel?
I don't think everyone with the same video card has this problem, it's
probably specific to the Amilo or even your particular model. I have
the same video chipset as you have
Apparently, there are many ways to control the backlight, and while
using the kernel is the default on your hardware, it is possible to
change that with xrandr. Take a look at bug 367309 for how to do this.
Could you check if you have the same weird behavior with the other
settings?
** Tags
The bugs are similar, but I'm not sure they are duplicate since it seems
to be on different hardware and the default backlight control is
different. I have tagged both bugs with the backlight tag, though, so
if a solution comes up for one, the other bugs with that tag can be
checked.
--
[i965]
** Summary changed:
- [i965] Jaunty: random screen flashes
+ [i965] Wierd backlight brightness behaviour looks like flashes on Amilo Si
2636
--
[i965] Wierd backlight brightness behaviour looks like flashes on Amilo Si 2636
https://bugs.launchpad.net/bugs/356510
You received this bug
Thanks for uploading all the ACPI related information. I have opened
this bug for linux and closed it for xorg and xserver-xorg-video-intel
(FYI: xorg is just a meta-package for people who don't know which xorg-
related package to put a bug into, and as such really makes no sense
together with
Good to know that it does not add anything to Xorg.0.log. That means we
can exclude something calling xrandr as being the source of this bug.
I'm not exactly sure where it belongs, but I guess probably the kernel. Screen
brightness change goes through the ACPI interface and those bugs are filed
Strange... Does the same happen with
/proc/acpi/video/VID/LCD0/brightness? (it goes up to max, drops down,
etc.)
Also, 0 should not be minimum, not maximum... On my computer it is
BACKLIGHT: 12 (0x000c) range: (0,15)
and the value goes from 0 (minimum) to 15 (maximum)
--
For sure you have a /proc/acpi directory. Do you have a video directory in
there? If so, do you have a VID directory in there? If so, a LCD0 directory in
there? If so, what files do you have there? Nothing under /proc are real files,
it's a filesystem the kernel uses to inform/communicate with
TomasHermosilla, on my machine (Thinkpad X61 Tablet with intel 965GM
chipset) suspend and resume works fine from the installed Jaunty, but
not frome the LiveCD. Therefore, this bug is only present in a LiveCD
session.
This means that you are experiencing a different bug from mine, but with
very
The problems with molecule seems to continue in Ubuntu 9.04 (alfa).
But I followed the direrctions above and got rid of the problem.
--
[r128 1002:5446] Selecting the Molecule screensaver makes the PC freeze. It is
completely unresponsive.
https://bugs.launchpad.net/bugs/106060
You received
** Summary changed:
- [i965, Jaunty] Black screen (or hung screensaver) after resume from suspend
+ [i965, Jaunty] Hung screensaver after resume from suspend (LiveCD only)
--
[i965, Jaunty] Hung screensaver after resume from suspend (LiveCD only)
https://bugs.launchpad.net/bugs/311362
You
of `lshal -m` when it goes to sleep,
wakes up for a moment and wakes up permanently, in case this is
useful.
Would it be right to reopen this bug for gnome-power-manager?
Geir Ove
** Attachment added: lshal-m-2cycles.txt
http://launchpadlibrarian.net/21905209/lshal-m-2cycles.txt
--
Resume (from
Stopping acpid before suspend reduces the number of suspend-resume
cycles from 3 to 2 on my Thinkpad X61 Tablet. I guess those for whom
the problem is solved only had 2 cycles to begin with (i.e. the
computer would stay awake after the second wake-up call) (?)
I attach logs from
I should add that I'm running an updated Jaunty.
acpi-support: 0.116
acpid: 1.0.6-9ubuntu4
hal: 0.5.12~rc1+git20090120-0ubuntu1
gnome-power-manager: 2.24.0-0ubuntu14
--
Resume (from memory) goes back to sleep automatically
https://bugs.launchpad.net/bugs/306310
You received this bug notification
Ok, I should have checked the Redhat bug report as well.
I can also confirm this bug on a Compaq nx7400 using a Jaunty alpha-2
LiveCD. In contrast to my Thinkpad, it stays awake after the second
resume (the thinkpad only stays awake after the third resume).
--
Resume (from memory) goes back to
** Tags added: jaunty resume suspend
--
thinkpad repeatedly suspends after lid close/open
https://bugs.launchpad.net/bugs/307986
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing
It turns out that the black screen that I first saw, was actually the
screensaver (which by default is a black screen). When I change the
screensaver this is what comes up on the screen after resume from
suspend. When I press a key the screen goes black and shows the mouse
cursor in a glimpse
*** This bug is a duplicate of bug 306310 ***
https://bugs.launchpad.net/bugs/306310
Thank you for reporting this bug. I'm going to mark this as a duplicate
of bug 306310 as it seems to be the exact same issue. If you find
something in that bug that is not compatible with your behaviour, feel
** Also affects: pm-utils (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-power-manager (Ubuntu)
Importance: Undecided
Status: New
--
Resume (from memory) goes back to sleep automatically
https://bugs.launchpad.net/bugs/306310
You received this bug
** Summary changed:
- [i965, Jaunty] Black screen (or screensaver) after resume from suspend
+ [i965, Jaunty] Black screen (or hung screensaver) after resume from suspend
--
[i965, Jaunty] Black screen (or hung screensaver) after resume from suspend
https://bugs.launchpad.net/bugs/311362
You
I have marked bug 307977 and bug 307986 as duplicates of this bug, and
added the packages that those bugs were reported against. It seems to be
a Lenovo Thinkpad specific problem, since Noel has a T61p (from the
attached HalComputerInfo.txt), Marc has a X200s and Jeffrey has a X61
Tablet. I can
The wiki page https://wiki.ubuntu.com/DebuggingACPI has some
information about what is needed for ACPI related bugs. I attach mine
for the Thinkpad X61 Tablet. Since I'm running from a LiveCD I cannot
reboot and then attach kern.log.0, so I'm rather attaching kern.log
from the current session.
I also ran into this bug, complete root directory in trash. I did not have any
external devices mounted at that time btw.
Using Gutsy x86 32bit.
--
trash lists / content due to .trash_entry_cache value
https://bugs.launchpad.net/bugs/85608
You received this bug notification because you are a
51 matches
Mail list logo