** Summary changed:
- GTK+ artefact in maverick
+ compositor produces artefacts starting in maverick
** Description changed:
Binary package hint: xorg
Since I migrated my two machines to maverick they experience the same issue,
under certain circonstances I didn't succed to define, there
Hi Brice,
Actually this is not only related to intel as I experience the same
problem with a nvidia powered machine.
--
GTK+ artefact in maverick
https://bugs.launchpad.net/bugs/654768
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-vi
ndard settings there? Is this reproducible under metacity?
>
I'm not running Compiz but metacity with compositing enabled. I should
test without compositing to see if the problem appears also.
--
Baptiste Mille-Mathias
Les gens heureux ne sont pas pressés
[w] http://damnpeople.f
Killing gnome-panel will remove all interfact created by panel menu, but
not all.
--
GTK+ artefact in maverick
https://bugs.launchpad.net/bugs/654768
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
__
To reproduce:
- open a terminal and place it above or below a gnome-panel.
- click on a panel menu, and make sure the menu will hover the terminal.
you should have some artefact.
--
GTK+ artefact in maverick
https://bugs.launchpad.net/bugs/654768
You received this bug notification because you ar
** Attachment added: "An example"
https://bugs.edge.launchpad.net/ubuntu/+source/xorg/+bug/654768/+attachment/1672124/+files/Capture-1.png
--
GTK+ artefact in maverick
https://bugs.launchpad.net/bugs/654768
You received this bug notification because you are a member of Ubuntu-X,
which is sub
** Attachment added: "BootDmesg.txt"
https://bugs.edge.launchpad.net/bugs/654768/+attachment/1671901/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.edge.launchpad.net/bugs/654768/+attachment/1671902/+files/CurrentDmesg.txt
** Attachment added: "Dependencies.txt
Public bug reported:
Binary package hint: xorg
Since I migrated my two machines to maverick they experience the same issue,
under certain circonstances I didn't succed to define, there are some artefacts
created on the display.
On the attached screenshot, you can see the artefact was created on
seems to be a g-p-m bug after a discussion with awesome chriscoulson
** Package changed: xorg (Ubuntu) => gnome-power-manager (Ubuntu)
** Bug watch added: GNOME Bug Tracker #609720
https://bugzilla.gnome.org/show_bug.cgi?id=609720
** Also affects: gnome-power via
https://bugzilla.gnome.org
The only solution is to disable desktop effects.
--
Xorg takes too much memory
https://bugs.launchpad.net/bugs/391511
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailing list: http
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/39667387/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/39667388/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/39667389/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
Like bug 397839, I still see randomly this bug, and an icon in notification
area appears there is a bug (with a link to a Richard Hughes blog post).
I don't know how to trigger this bug on demand.
ProblemType: Bug
Architecture: amd64
Date: Tue Feb
Colin,
does the bug looks likes bug 397839?
--
gnome goes black then back to login screen
https://bugs.launchpad.net/bugs/469552
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
___
Mailin
apport-collect doesn't let me attach information as I'm not the
reporter, great :/
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
__
apport-collect doesn't let me att
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
___
Mailing lis
Rob, you don't provide information like your distro version, and various
versions of your packages related to this bug.
For information, on lucid I still such issue randomly (but not often); I
talked to Martin Pitt (pitti on IRC) today, and asked me to re-open this
bug (and not open a new one). I'
Setting an xorg.conf file with the following content made the trick.
8<---
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
M
changing package according wiki page
** Package changed: xserver-xorg-video-intel (Ubuntu) => xorg (Ubuntu)
--
[KMS] no display with KMS enabled (intel)
https://bugs.launchpad.net/bugs/388032
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-ser
The way I used is given in the wiki
https://wiki.ubuntu.com/X/KernelModeSetting so perhaps it should be
removed.
** Summary changed:
- [KMS] no display with KMS enabled
+ [KMS] no display with KMS enabled (intel)
--
[KMS] no display with KMS enabled (intel)
https://bugs.launchpad.net/bugs/38803
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/27998000/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/27998001/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/27998002/Dependencies.txt
** A
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I enabled the kms at boot time with i915.modeset=1, so I seen usplash boot
screen but I was not able to see gdm login screen.
I was able to see a terminal, and switch between VTs for a while and, no VT
switch was possible (or th
21 matches
Mail list logo
