[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1555396
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1555136
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1556008
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1556318
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/128
See also 15801302 about monitor blanking. You can get the monitor back
on with xrandr --output DP1 --auto *if* you do that from an SSH session
(not from one of the alternate terminals)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubunt
** Changed in: xorg (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574732
Title:
# /etc/default/grub
...
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.modeset=1 radeon.drm=1
radeon.runpm=0"
...
Result of `DRI_PRIME=1 glxgears -info` attached. Visible and smooth
animation runs (no black window).
** Attachment added: "glxgears-2"
https://bugs.launchpad.net/ubuntu/+source
** Changed in: xorg (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1568429
Title:
Radeon won't work with KMS enabled
To manage notifications about
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1581277
Title:
fglrx failed to upgrade
To manage notifications about this bug go to:
https://bugs
** Changed in: xinit (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xinit in Ubuntu.
https://bugs.launchpad.net/bugs/1562219
Title:
xinit will not work as non-root.
To manage notifications about this
Public bug reported:
I was running apt-get update && apt-get upgrade && apt-get dist-upgrade
on a friend's ubuntu system (Trusty). The system had not been updated in
a long time, so the list of packages to be downloaded was huge (~500MB
for updates and ~300MB for upgrades) and due to a slow intern
** Description changed:
dmesg shows issues with being able to use the discrete graphics card
(relevant dmesg lines attached).
- Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
- I've tried all combinations and same results occur.
+ Grub does pass "radeon.modeset=1" b
** Attachment added: "glxgears"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661633/+files/glxgears
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581270
Title:
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581270/+attachment/4661631/+files/syslog
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1581270
Title:
Hybr
Public bug reported:
dmesg shows issues with being able to use the discrete graphics card
(relevant dmesg lines attached).
Grub does pass "radeon.modeset=1" and "radeon.startpm=1" to the kernel.
I've tried all combinations and same results occur.
Attached are relevant dmesg lines, grep'd with 'd
this is the patch in the link above:
diff --git a/src/drmmode_display.c b/src/drmmode_display.c
index 4c66ca7..a848345 100644
--- a/src/drmmode_display.c
+++ b/src/drmmode_display.c
@@ -288,6 +288,7 @@ static void
drmmode_do_crtc_dpms(xf86CrtcPtr crtc, int mode)
{
drmmode_crtc_private_pt
tabs were lost in translation.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1577170
Title:
[solved] screen cannot be turned back on after being switched off
after some tim
Thanks to the guys in the #radeon channel on irc, I found a way to solve the
problem.
You have to apply this patch to the source of the video driver
(xfree86-video-ati-7.7.0) : https://paste.debian.net/plain/682956
and compile then install it (using --prefix=/usr for the configure process).
**
I fixed my problem on Dell laptop by changing Screensaver (XScreenSaver 5.34)
settings.
Display Modes
Mode: Blank Screen Only or Disable Screen Saver
I guess the screen saver program was not working well. I glimpsed the
monitor had weird colors.
Laptop Lid is closed: both Switch off display and
Right, so is there anything we can do to build OSMesa for 14.04.x users
to resolve this? Or do we say sorry, don't mix OSMesa with OpenGL,
hopefully it will be better in the next LTS? IOW do you see this moving
towards "In Progress" or "Won't Fix"?
I completely understand the reasoning in bug #142
** Package changed: xorg (Ubuntu) => xserver-xorg-video-intel (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1579403
Title:
Random characters in screen text suddenl
most likely a kernel bug
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1574238
Title:
Stand-by/sleep mode 16.04
To manage notifications abo
install xdiagnose and run 'apport-collect 1580786'
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1580786
Title:
abnormal CPU-usage
sounds like the nouveau kernel module fails to drive them properly,
please provide dmesg when booting without nomodeset & nvidia installed
** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu)
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New => Incomplete
[ 133.381] Kernel command line:
BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=1628c3f9-dc94-42dd-
951b-971689ff1cb0 ro recovery nomodeset
don't use nomodeset
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1551028
Title:
glGenFramebuffers fails when linked with OSMesa AND X11
To manage notifications about this bug go to:
https:
what would fix these issues for good would be to let mesa roll forward
unrenamed, that might actually happen for 16.04.x
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1551028
Title:
glGenFrame
and reverting -0ubuntu0.5 would then result in
https://bugs.launchpad.net/ubuntu/trusty/+source/mesa/+bug/1424059
again..
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1551028
Title:
glGenFra
Just for completeness, since this bug report only mentions Ubuntu
release numbers, the working version of libosmesa6 in 14.04.3 is
10.1.3-0ubuntu0.4, the version that fails in 14.04.4 is
10.1.3-0ubuntu0.6.
For my part, I am interested in how this affects Octave users because
Octave links with both
I think this bug is due to the change in the mesa package to build
osmesa without using the shared glapi. I have seen similar errors using
libosmesa6 10.1.3-0ubuntu0.6, when a program is linked with both libGL
and libOSMesa. If the libosmesa6 packages are downgraded to
10.1.3-0ubuntu0.4, the errors
Public bug reported:
ATI Mobility Radeon™ HD 5000 ubuntu16.04 It can not be found
** Affects: xserver-xorg-video-ati (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati
Public bug reported:
running xenial + stable-phone-overlay, unity8
had hexchat open and focused, terminal app and browser also open
closed lid, seemed to enter retention fine
open lid, ui responded for a bit, i toggled apps to terminal then back to
hexchat
then ui/cursor froze, eventual reboot on
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1581076
Title:
Xorg segfaults on start-up on Big Endian PPC hardware
To manage no
Public bug reported:
On my Big Endian PowerPC machine, Xorg segfaults when starting. I have
been able to confirm that this does not happen when building Xorg from
upstream source, and then further confirmed that the source of the
segfault appears to be caused by a non-upstreamed, ubuntu specific
p
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-304 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
The version of nvidia-settings-experimental-310 in the proposed pocket
of Precise that was purported to fix this bug report has been removed
because the bugs that were to be fixed by the upload were not verified
in a timely (105 days) fashion.
--
You received this bug notification because you are
@unrud: Your hunch was right. Increasing the delay (even to 2 seconds is
enough) resolves the issue. Even on your fresh installation, do check if
it works correctly with suspend/hibernate as well when the delay is not
more than one second.
I have gone back to gnome-screensaver for the time being,
@pitti,
There is bug in the Xkb patch in Xmir that has been fixed and is in the
Vivid overlay. I think Robert will need to respin the Xmir patch to fix
the bug.
That said, I'll mark this verification-failed.
** Tags removed: verification-needed
** Tags added: verification-failed
--
You receiv
Did you upgrade from 14.04? This is a systemd issue, which was
introduced after 14.04 LTS
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1439440
Title:
Laptop does not go to sleep when closing l
xorg.conf file edit
** Attachment added: "xorg.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1580949/+attachment/4661205/+files/xorg.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
1024x768 resolution is not available by default in Ubuntu Trusty when
connecting to Cisco KVM. It works fine with RHEL 6.5 (xorg-xserver
x1.13.0) and SLES 11.4 (xorg-xserver v1.6.5).
The workaround to enable display in Ubuntu Trusty is:
1. Stop lightdm (service lightdm stop)
Please test the -proposed package, it blocks the next SRU that is
waiting in the queue. Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1566487
Title:
Container apps should use sam
@saurav1: Only tested the script on freshly installed Xubuntu 16.04. The
screen doesn't get relocked on my computer.
Maybe it's a race condition and setting "Delay after locking screen
saver for" in "XFCE Power Manager" under the "Security" tab to a higher
value helps.
--
You received this bug n
46 matches
Mail list logo
