** Description changed:
Using 4.22 in Oneiric with a dell laptop docked lid closed and with the
internal screen enabled and placed under the external one in the
xrandr capplet (dunno how that happened but it's the config I got on lid
close and I can reproduce it manually by dnding the
Photo showing what this configuration problem looks like.
** Attachment added: 100_2566.JPG
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/868354/+attachment/2636716/+files/100_2566.JPG
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Summary changed:
- black screen when dim scrren to save power
+ black screen when dim screen to save power
** Description changed:
My macbook 2,1 goes to energy saving mode and dims the screen. But when I
touch any key, the screen remains black
- As workaround, I type my password to
** Summary changed:
- Displays utility doesn't offer to use nvidia-settings with proprietary
drivers installed?
+ Display utility doesn't offer to use nvidia-settings with proprietary drivers
installed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Yes, I agree this sounds like it's not gnome-terminal at fault.
Typically issues like these are video driver problems and tend to be
hardware-specific. The fact that several people are seeing it on
different graphics cards and different drivers is likely coincidental.
A lot of different kinds of
*** This bug is a duplicate of bug 877438 ***
https://bugs.launchpad.net/bugs/877438
A couple other details which would help for classifying performance
bugs:
* If you have a multi-head arrangement, are you using twinview or
xinerama (or xrandr for non-nvidia drivers)?
* Do you experience
** Package changed: xorg (Ubuntu) = rhythmbox (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/899141
Title:
anna
To manage notifications about this bug go to:
** Changed in: brasero (Ubuntu)
Status: Incomplete = Opinion
** Changed in: brasero (Ubuntu)
Status: Opinion = Confirmed
** Changed in: brasero (Ubuntu)
Importance: Medium = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a
[I have switched from using CDs to USB sticks so no longer care about
this bug.]
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/419781
Title:
Dialog displays writing to
It's been over a year without any indication of a problem that disabling
acpid in xserver would solve, so I'm going to close this for now. If
anyone can make a case for why to remove it, reopen this bug and let us
know.
** Changed in: xorg-server (Ubuntu)
Status: Triaged = Won't Fix
--
(Or if you can't reopen the bug since it's in state wontfix, please file
a new bug against xorg-server.)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/496859
Title:
MASTER: acpid
Given no one else seems to have complained about this, coupled with it
sounding like getting the doc fix backported would be prohibitively
hard, the lucid task is probably doesn't have a high enough bang for the
buck to do it.
** Changed in: gnome-system-tools (Ubuntu Lucid)
Status:
I do think the docs should be fixed for the upcoming Precise LTS.
Thanks for the invitation to produce a patch for this, but I have only a
fuzzy working knowledge of how time slewing is being implemented.
** Changed in: gnome-system-tools (Ubuntu)
Importance: Undecided = Low
** Changed in:
This does look like a bug we had a few releases ago, which has since
been resolved.
Feel free to reopen bug if you can reproduce it on Oneiric, but since
there's been no recent comments I'm guessing not.
** Changed in: sound-juicer (Ubuntu)
Status: Incomplete = Fix Released
--
You
** Changed in: xchat (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: xchat (Ubuntu)
Status: New = Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/882825
[The Design Team has identified this as a blocker issue for precise, so
setting the Importance to Critical. This may be adjusted down once the
bug has received further design and engineering analysis, if
appropriate.]
** Changed in: gnome-control-center (Ubuntu)
Importance: Medium = Critical
[The Design Team has identified this as a blocker issue for precise, so
setting the Importance to Critical. This may be adjusted down once the
bug has received further design and engineering analysis, if
appropriate.]
** Changed in: gnome-control-center (Ubuntu)
Importance: Low = Critical
--
[The Design Team has identified this as a blocker issue for precise, so
setting the Importance to Critical. This may be adjusted down once the
bug has received further design and engineering analysis, if
appropriate.]
** Changed in: gnome-control-center (Ubuntu)
Importance: High = Critical
[The Design Team has identified this as a blocker issue for precise, so
setting the Importance to Critical. This may be adjusted down once the
bug has received further design and engineering analysis, if
appropriate.]
** Changed in: gnome-control-center (Ubuntu)
Importance: Low = Critical
--
** Description changed:
Binary package hint: gnome-control-center
Following instructions for testing external monitor on a laptop in
http://testcases.qa.ubuntu.com/Hardware/GFX/ExternalPrimary
the resolutions of the external monitor are not detected properly. When I try
to change them,
@Andrea, thanks for your work on this! Could you post a link to the
code you've done, that can be reviewed?
I've added tasks to the Next Actions section of the description.
** Description changed:
Binary package hint: gnome-control-center
in the display manager gnome-control-center, it
The design team flagged this as a possible critical issue for us to
solve in the development release (and SRU to natty and/or oneiric, if
the fixes are suitable and appropriate to backport).
However, I notice this report only has comments from natty users, so I
am wondering if this issue might
Looks like in the recent refactoring work they forgot to check the
rr_outputs pointer before dereferencing it.
Easy enough to check for this situation and bail, but not 100% this is
the right way to solve this bug.
The real question is why screens was undefined to begin with.
** Patch added:
Andrè, are you able to reproduce this bug fairly easily? Can you
describe the steps that lead to this crash?
** Tags added: precise
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryce)
** Description changed:
I just input a HDMI monitor
It would be great if you could; otherwise please outline what you did to
solve it and one of us can try our hand at it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
@Chris, could you list some next actions for this bug (either by you or
others) that would help in moving it towards a solution?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Hi Ben Hearsum,
Hmm... I'm not sure I totally understand your description of the problem.
Could you please elaborate and clarify? You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html or the Ubuntu-X bug
reporting guidelines at
Not enough information has been provided to make this a useful bug
report. See http://wiki.ubuntu.com/X/Reporting for instructions on
reporting X issues.
** Changed in: xorg (Ubuntu)
Status: New = Invalid
** Package changed: xorg (Ubuntu) = gnome-desktop (Ubuntu)
--
You received this
I'm not sure what package controls that, but it's not X...
** Package changed: xserver-xorg-video-intel (Ubuntu) = metacity
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to metacity in Ubuntu.
** This bug is no longer a duplicate of bug 507062
synaptic assert failure: synaptic: ../../src/xcb_io.c:385: _XAllocID:
Assertion `ret != inval_id' failed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-panel in Ubuntu.
As per my comment on bug #507062, unduping this bug until more
definitive evidence can be gathered that this is the same bug; apport
unfortunately could not get a proper stacktrace for this one. Would you
mind collecting one by hand via gdm? I think that would probably help.
Or, if you could
As per the upstream bug report and my last few comments, this was
pinpointed to a bug in metacity rather than X.
I think it may be resolved in metacity, as well, since it's been a long
time since I saw this.
** Changed in: xorg-server (Ubuntu)
Status: Triaged = Invalid
--
You received
Karl, thanks you're right, my script did not check the recent comments.
--
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/868400
Title:
Synaptics touchpad stops working
Hey pretto,
Hi, thanks for reporting this issue during the development period of
Ubuntu.
I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?
Are you still able to reproduce the issue? If not,
Hey sabdfl,
Hi, thanks for reporting this issue during the development period of
Ubuntu.
I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?
Are you still able to reproduce the issue? If not,
Hey alexander-weinert,
You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved
Hey dpm,
You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved in the new
Hey rogz,
You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved in the new
Hey llstarks,
You filed this bug report against natty, but I see it's still open and
doesn't appear to have much activity recently. So, now that oneiric
is released and stable, this may be a good point for you to upgrade
and re-test if this issue is still present there.
If it's solved in the
[Quit using xchat-gnome in favor of regular xchat which doesn't have
this bug]
** Changed in: xchat-gnome (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
[Closing as I no longer use xchat-gnome and no one else is subscribed or
marked as affected. xchat seems to have better options for managing
large lists of server/channels.]
** Changed in: xchat-gnome (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a
It seems upstream is not favorable to this idea. I have stopped using
xchat-gnome so have no plans to implement it myself. Feel free to close
this bug report if no one else wants the functionality.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Also affects: xchat (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/716607
Title:
Scrolls to top of window when started
Affects both xchat and xchat-gnome
** Description changed:
- Binary package hint: xchat-gnome
Steps to reproduce:
- 1. Launch freshly installed (default settings) xchat-gnome
+ 1. Launch freshly installed (default settings) xchat
2. Notice window includes display of timestamps of
Confirmed this is now fixed in natty
** Changed in: gnome-terminal (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/297807
The X driver doesn't control brightness. Might be an issue in the
userspace daemon. Or some ACPI quirkiness.
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-settings-
daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = New
--
You received
The X driver doesn't control brightness. Might be an issue in the
userspace daemon. Or some ACPI quirkiness.
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-settings-
daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = New
--
You received
Sarvatt suggested this patch went in around that time and might be relevant:
http://git.gnome.org/browse/gnome-settings-daemon/commit/?id=67785fa2b1043bd5397669f92abbd210dbf23f24
Also:
Sarvatt * debian/patches/50_add_dell_backlight.patch:
Sarvatt - Add 'dell_backlight' module to
The X driver doesn't control brightness. Might be an issue in the
userspace daemon. Or some ACPI quirkiness.
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-settings-
daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = New
--
You received
Possibly dupe of 872932... similar symptoms around the same time frame.
--
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/876711
Title:
Screen brightness resets to
The X driver doesn't control brightness. Might be an issue in the
userspace daemon. Or some ACPI quirkiness.
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-settings-
daemon (Ubuntu)
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed = New
--
You received
Possibly dupe of 872932... similar symptoms around the same time frame.
--
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/873191
Title:
Ubuntu starts with lowest
)
Importance: Undecided = High
** Changed in: xorg-server (Ubuntu)
Status: New = Triaged
** Changed in: xorg-server (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryce)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in Ubuntu.
https://bugs.launchpad.net/bugs/232078
Title:
The allowed limit of flexible X servers reached
To
Looks likely to be this.
gnome-settings-daemon (3.2.0-0ubuntu4) oneiric; urgency=low
* debian/patches/00git_dont_sleep_on_idle_by_default.patch:
- Don't sleep on idle by default (LP: #860485)
* debian/patches/00git_dont_revert_pre_idle_brigthness.patch:
- Do not revert to the pre-idle
** Package changed: xserver-xorg-video-intel (Ubuntu) = gnome-desktop
(Ubuntu)
** Changed in: gnome-desktop (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
** Changed in: gnome-screensaver (Ubuntu)
Importance: Undecided = Critical
** Changed in: gnome-screensaver (Ubuntu)
Importance: Critical = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
Actually the heuristics that manage what to do when hotplugging is in
the gnome control utilities (gnome-rr.c in gnome-desktop). Sounds like
it's not handling things as you expect; refiling (there is no 'xrandr'
package anymore).
** Package changed: xrandr (Ubuntu) = gnome-desktop (Ubuntu)
--
Hi, you've reported several different (discrete) issues in one bug
report, and some of these I think are already reported on other bugs.
There is no 'xrandr' package anymore (even though one is present in
launchpad), so I'm moving this to xorg to be re-triaged. However at
least some of the
The retracer already attached a full backtrace. If it hadn't deleted
the core file I could have helped more.
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I take it all back. I now have an arrandale laptop on hand for testing
and am able to reproduce the bug exactly as originally reported. I'll
do some diagnostics and report back.
** Tags added: oneiric
** Tags added: rls-mgr-o-tracking
--
You received this bug notification because you are a
** Visibility changed to: Public
** Summary changed:
- gnome-control-center crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
+ gnome-control-center crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
called via gdk_display_get_event ()
** Changed in: gnome-control-center (Ubuntu)
This is a test machine so nothing private in the CoreDump; please don´t
delete it - could be useful.
--
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/860089
Title:
While in broken state:
bryce@clanfield:~$ xrandr --auto
xrandr: cannot find crtc for output LVDS1
bryce@clanfield:~$ xrandr --verbose
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS1 connected (normal left inverted right x axis y axis)
Identifier: 0x41
Working state
bryce@clanfield:~$ xrandr --verbose
Screen 0: minimum 320 x 200, current 1920 x 1848, maximum 8192 x 8192
LVDS1 connected 1366x768+231+1080 (0x44) normal (normal left inverted right x
axis y axis) 293mm x 164mm
Identifier: 0x41
Timestamp: 15385367
Subpixel:
After using xrandr to disable lvds1:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS1 connected (normal left inverted right x axis y axis)
Identifier: 0x41
Timestamp: 32659
Subpixel: horizontal rgb
Clones:
CRTCs: 1
This prints out whenever I do a screen configuration change:
[15844.649388] dell_wmi: Received unknown WMI event (0x11)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/737891
Steps to reproduce for me are slightly different from OP:
1. Connect external monitor to VGA output.
2. Launch gnome-display-properties and make sure LVDS1 is on, VGA1 is off.
3. Turn LVDS1 off, VGA1 on
4. LVDS1 turns off, and VGA1 shows linear corruption pattern (different than
the corruption
[ 417.493074] [drm:i915_get_vblank_timestamp], crtc 0 is disabled
[ 417.504230] [drm:i915_driver_irq_handler], pipe A underrun
[ 417.509705] [drm:i915_get_vblank_timestamp], crtc 0 is disabled
[ 417.520990] [drm:i915_driver_irq_handler], pipe A underrun
--
You received this bug notification
[ 1301.290842] [drm:i915_driver_irq_handler], pipe A underrun
[ 1301.307600] [drm:i915_driver_irq_handler], pipe A underrun
[ 1301.309934] [drm:drm_mode_getconnector], [CONNECTOR:5:?]
[ 1301.309944] [drm:drm_helper_probe_single_connector_modes],
[CONNECTOR:5:LVDS-1]
[ 1301.309967]
Turn on display debug information by running sudo xdiagnose, clicking
the first checkbox, apply, then reboot.
Now collect dmesg output, then reproduce the problem and collect a
second dmesg. You want the data that's in the second dmesg but not the
first.
Possibly this bug is related to bug
*** This bug is a duplicate of bug 828623 ***
https://bugs.launchpad.net/bugs/828623
Alright, after poking around a bit I believe this is the same thing as
bug #828623, which is reported upstream so I'll dupe to that.
** This bug has been marked a duplicate of bug 828623
[Regression]
*** This bug is a duplicate of bug 828623 ***
https://bugs.launchpad.net/bugs/828623
** This bug is no longer a duplicate of bug 737891
[Arrandale] gnome-display-properties unable to correctly enable monitors
connected to VGA
** This bug has been marked a duplicate of bug 828623
** Attachment added: 100_2295.JPG
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/828623/+attachment/2467497/+files/100_2295.JPG
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Attachment added: 100_2294.JPG
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/828623/+attachment/2467496/+files/100_2294.JPG
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Attachment added: Working case - using xrandr
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/828623/+attachment/2467495/+files/xrandr.good.clean.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I think I'm able to reproduce more or less this same bug.
For me, it occurs only when I use gnome-control-center to switch from
VGA-off-and-LVDS-on directly to VGA-on-and-LVDS-off. If I start with
both displays on, and disable LVDS, it works fine. If I use xrandr, it
works fine. See bug
Since the bug is reported as a regression, bumping up to high priority.
** Changed in: gnome-control-center (Ubuntu)
Importance: Low = High
** Also affects: gnome-control-center (Ubuntu Oneiric)
Importance: High
Status: Triaged
--
You received this bug notification because you are
Actually, rather than tasking oneiric on this bug report (which is a bit
stale at this point) I would recommend opening a new bug report, because
so much has changed in arrandale support in oneiric. For instance, mesa
now supports 8k textures on arrandale, so the issue I alluded to still
$ ping irc.amiganet.org
PING irc.amiganet.org (10.0.0.1) 56(84) bytes of data.
^C
--- irc.amiganet.org ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12095ms
Perhaps the server is simply down for a bit? When was this first
noticed?
xchat-gnome also includes
Hi Barry,
It sounds sort of like gnome-settings-daemon is not capturing the
settings properly, so your system is defaulting to 10 minutes. I notice
this in your dmesg which hints perhaps gsd is dying (coincidentally in
some power module):
[22483.782153] gnome-settings-[2178] trap divide error
Barry, btw I noticed a couple other things you might look at...
Your xorg.conf only specifies glx, but that's loaded by default now.
You should be able to entirely delete your xorg.conf with no impact to
X. (In fact we ship without xorg.conf and recommend you run without
one, unless you actually
Another detail that would help me figure this out is whether there have
been /var/lib/xkb/*.xkm files in the past (i.e. the regression is that
they're no longer being generated), or if they've always been missing
(in which case the regression is xvfb is now expecting them when it
didn't).
Also,
No, there seems to be more to it than that.
root@clanfield:~# ls /var/lib/xkb/
server-02D8252E59564A234380F1E5417646A9DB3B7452.xkm
server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm
root@clanfield:~# rm /var/lib/xkb/*
root@clanfield:~# fakeroot Xvfb :99 -noreset -nolisten tcp
[dix] Could not
Nevermind; I found a way to reproduce it locally now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygtk in Ubuntu.
https://bugs.launchpad.net/bugs/829470
Title:
Xvfb fails with empty /var/lib/xkb, causing build failures
To
Test case I'm using is adding the following line to the hello package's
binary-arch target:
Xvfb :99
In particular, the fault is occurring within the X server code for the
xkbcomp call. The call it's trying to make is something like:
xkbcomp -w 1 -R/usr/share/X11/xkb/keymap -xkm xfree86
In fakeroot 1.16-1, Debian added a patch to add access() support, to fix
debian bug #629956.
However, this broke apt (debian bug #630591) and other stuff (debian bug
#630129), and so the patch was reverted in fakeroot 1.17-1:
http://packages.qa.debian.org/f/fakeroot/news/20110818T113211Z.html
Not an X bug after all.
** Package changed: xorg-server (Ubuntu Oneiric) = fakeroot (Ubuntu
Oneiric)
** Changed in: fakeroot (Ubuntu Oneiric)
Milestone: ubuntu-11.10-beta-1 = None
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I believe the solution to this is to sync fakeroot 1.17-1 from debian.
** Changed in: fakeroot (Ubuntu Oneiric)
Milestone: None = ubuntu-11.10-beta-1
** Changed in: fakeroot (Ubuntu Oneiric)
Assignee: Bryce Harrington (bryce) = (unassigned)
--
You received this bug notification
** Bug watch added: Debian Bug tracker #630591
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630591
** Also affects: fakeroot (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630591
Importance: Unknown
Status: Unknown
--
You received this bug notification because
On Tue, Aug 23, 2011 at 05:42:50PM -, Steve Langasek wrote:
Running by hand, I see:
$ fakeroot Xvfb :99 -noreset -nolisten tcp(EE) GLX: could not load software
renderer
So if xvfb thinks it's root (which is the purpose of fakeroot), it fails
to start if it can't write to
** Changed in: xorg-server (Ubuntu Oneiric)
Status: Confirmed = Triaged
** Summary changed:
- pygtk version 2.24.0-2 failed to build in oneiric
+ xvfb failed to start - pygtk version 2.24.0-2 failed to build in oneiric
--
You received this bug notification because you are a member of
Looks like the test is failing while trying to do RANDR operations
within xvfb:
make[3]: Entering directory `/home/bryce/pygtk/pygtk-2.22.0/dbg-build-2.6/tests'
Xlib: extension RANDR missing on display :99.
Traceback (most recent call last):
File
Actually, some light googling shows the 'Xlib: extension RANDR missing
on display :99.' is innocuous and can be ignored.
I'm able to reproduce the same test failure from the pygtk build
directory without xvfb (i.e. DISPLAY=:0), so this seems not to be a bug
in xvfb but just a failing test that
Alright, well both RAOF and I looked at this and agree it seems not to
be an xvfb issue, but rather breakage in the test itself.
The RANDR error is just because xvfb by default does not load that
module; there's options to make it load it if the test does need it, but
I haven't played around with
Lennart, aha, very interesting. I'll send it to nautilus for them to
review, although I wonder if it might be due to some alteration made for
unity so perhaps it ultimately belongs there.
I'm still guessing you and brad are seeing the same issue since both
your reports came in at roughly the
rhythmbox does not list libdvdread as a dependency. If you can
reproduce the bug using a libdvdread-using utility, file a bug against
libdvdread with steps to reproduce (I've not seen this particular error
myself and use libdvdread pretty heavily with a lot of scratched disks.)
** Changed in:
** Changed in: xserver-xgl (Ubuntu Hardy)
Status: New = Won't Fix
--
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/215396
Title:
gnome-display-properties crashed
[Karmic is ancient history at this point]
** Changed in: xorg-server (Ubuntu Karmic)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu.
https://bugs.launchpad.net/bugs/397839
** Changed in: xchat-gnome (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/823335
Title:
xchat-gnome crashed with SIGSEGV in
201 - 300 of 1256 matches
Mail list logo
