When booting into Arch, you will just boot into the terminal, but here
the resolution seems to be bigger than the screen.
** Also affects: xserver-xorg-video-nouveau (Ubuntu)
Importance: Undecided
Status: New
** Also affects: archlinux
Importance: Undecided
Status: New
--
Yo
Public bug reported:
When booting the installation of 24.04 (LTS) I will be presented with a
nice screen. However the resolution is wrong. My screen is actually
1920x1080. However the installation uses a resolution of 2048x1536. It's
a wrong aspect ratio as well, 16:9 vs 4:3.
The weird thing is t
Public bug reported:
Hi,
Randomly the display turns off and then on again. Happens sometimes many
times and others times not at all, randomly.
Related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-495/+bug/1956252
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xor
** Changed in: xorg (Ubuntu)
Status: New => Fix Released
** Changed in: xorg (Ubuntu)
Status: Fix Released => Invalid
--
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/1923840
Title:
Public bug reported:
After booting there is only a black screen showing a blinking _ in the
top left corner. Nothing happens anymore. It only happens with Linux
version 5.8.0-49-generic. Linux version 5.8.0-48-generic boots fine.
Description:Ubuntu 20.04.2 LTS
ProblemType: Bug
DistroRelease:
I'm running Xubuntu 18.0.03, which hasn't reached end-of-life, and this
bug is still present. It was introduced when I upgraded to kernel 5.0
with xorg 1.20.4-1ubuntu3~18.04.1. It can be circumvented using either
of 2 methods:
1. Uninstalling light-locker and installing xscreensaver
or
2. As sugge
Ops, apologies for the typo, I'm running Xubuntu 18.04.03
--
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/1801609
Title:
Fails to deactivate dpms off mode after user initiated wake-up
ev
done
** Description changed:
Linux Version: 4.15.0-36-generic
- After login or during login the screen freezes. Mouse does not move any
longer.
+ on resume from suspend, this could be a login or a minute after the screen
freezes. Mouse does not move any longer.
Total crash/hang this is new
My main issue is "on resume from suspend" which I never had with 16.04. I
probably had 30-50 resumes before I rebooted after a kernel update.
In the mean time I am on 4.15.0-38.
I assume I removed the gnome-shell, also I switched from nouveau to
nvidia-driver-390
I had several (5) resumes after
** Summary changed:
- System freezes after suspend
+ System freezes on resume from suspend
--
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/1797518
Title:
System freezes on resume from sus
Public bug reported:
Linux Version: 4.15.0-36-generic
After login or during login the screen freezes. Mouse does not move any longer.
Total crash/hang this is new since about 3 weeks or so.
All updates are installed.
I attached kern.log, about 9:14 this morning I had to reboot again.
ProblemType:
A hypothesis was discussed in bug #1753012 that the root cause of this
bug was in the kernel, specifically in blk-core.c. The patch was finally
merged in kernel version 4.15.0-31-generic. I'm running on
4.15.0-32-generic but the bug is still happening:
1. Xorg starts to become unresponsive: it fre
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012
@Alan, oh, you're description of the bug is far more accurate than mine:
it's precisely what I experienced.
I'm running vanilla kernel 4.15.0-23-generic, without your fix, so I
wonder why forcing the intel
This bug is still present in Xubuntu 18.04.
Workaround https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1298578/comments/7 does restore maximum brightness, but not
the actual brightness level before suspending.
--
You received this bug notification because you are a membe
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012
As I started to suspect of the kernel i915 modesetting driver, yesterday
I put a workaround in place, not sure if it will have any effect. I
created /etc/X11/xorg.conf.d/10-intel.conf:
Section "Device"
*** This bug is a duplicate of bug 1753012 ***
https://bugs.launchpad.net/bugs/1753012
I've just got an automated email saying that my bug #1775790 is a
duplicate of bug #1753012, but if I try to open it, I get a not found
page, I suppose because these reports are private to the subscribers.
Dummy me, forgive me: I still had the crash file around, it was just a
question of giving read permission to everyone (since it was only
readable by root and group whoopsie), and running ubuntu-bug over it.
So, after changing problem_types in /etc/apport/crashdb.conf to:
'problem_types': ['Bu
Thanks for the swift feedback. I had tried to run:
ubuntu-bug /var/crash/FILE.crash
but it complained of lack of permission. I wasn't aware of the
workaround of bug #994921. As soon as I get another crash, I'll follow
your instructions.
--
You received this bug notification because you are a me
Public bug reported:
Every night I suspend my laptop and resume it in the morning. At least
once a week, the X server crashes with SIGBUS when resuming from
suspend.
I scoured systemd journals and all logs under /var/log, and this was the
only suspicious message I found:
[ 59358.134] (EE) /dev/d
I can confirm that problem on a MacBook Pro 8,1. Combined with the
pointer still moving when attempting to "right-click" with two fingers
this is the single most annoying problem. It's distracting enough that I
simply cannot use Ubuntu on my MacBook Pro outside of a virtual machine.
A pity, since I
same error on Precise x86
AMD kernel module generator version 2.1
.
Active kernel:
uname -a = 3.8.0-32-generic #47~precise1-Ubuntu SMP Wed Oct 2 16:22:28 UTC 2013
i686 athlon i386 GNU/Linux
uname -s = Linux
uname -m = i686
uname -r = 3.8.0-32-generic
uname -v = #47~precise1-Ubuntu SMP Wed Oct 2 1
I found a Workaround: simplay set the screens to the same resolution and
it should work.
Another bug is: if you flip your monitors, so that your left screen is right
and the
right one is on the left side, then the mouse will appear much more on the
right side (should be in my case at 1680-(192
For me this happens too, but in Version 12.04 and on a Nvidia 460 GTX Graphics
Card.
The right screen is 1680 x 1050 and the left screen is 1920 x 1080
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in Ubuntu.
https://b
Ok D'oh... for me it was the "Secure Attention Key" feature of Trinity (KDE3)
KDM.. somehow the "tsak" background process was b0rked with the last upgrade to
kdebase-trinity-bin-3.5.13-2debian0~pre49+9 .. thankfully it can be disabled.
...Sorry for the noise C-;
--
You received this bug notific
and he linux virtual consle is not affteby this stuid
problem...eems to e conneced to ecent package updatesi
pulled in
sh
--
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
Sine
yesterday, i too
havvve this and it is a reeal issu as i use
thekeyoar
So it is safe now to upgrade to 12.10? I did upgrade but ended up going
back to 12.04
El 27/01/2013 09:24, "madbiologist" <1058...@bugs.launchpad.net> escribió:
> This news may be relevant:
>
> http://www.phoronix.com/scan.php?page=news_item&px=MTI4MDE
>
> --
> You received this bug notification b
No to be a downer, but my experience with the open source is so poor
that it is close to unusable for me. I work with eclipse and I keep on
loosing the window, at first I tought eclipse was crashing but all
processes were there, is just the windows that were gone from the
desktop.
Unity is really
@montblanc Exactly the same behaviour here with an Hp Dv6 with ATI RS880M
[Mobility Radeon HD 4200 Series]
I tried both with that ppa and building the packages off the 12.6 legacy driver
zip from amd.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribe
** Branch linked: lp:ubuntu/precise/mesa
--
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/708516
Title:
Mesa alternative on libGL not set in natty
To manage notifications about this bug go to:
ht
** Tags added: precise
--
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/708516
Title:
Mesa alternative on libGL not set in natty
To manage notifications about this bug go to:
https://bugs.launchp
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
As you already mentioned, the logs are not that useful... Anyway, this
seems to be more an issue of warzone messing up the xorg configuration
and not an issue of xorg itself? Is there any specific reason that you
c
Had the same problem. Installed it manually and all is fine again.
(ctrl+alt+1, /etc/init.d/gdm stop, sh nvidia (...).run, reboot
-> on my machine. some elements may differ from your setup, -> check wikis.
driver will be installed correctly if done by hand)
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error caused by a corrupted
archive. I'm closing this issue since it seems that the problem with the
package installation disappeared -- feel free to file new bugs for any
other issue you
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error caused by a corrupted
archive. Please execute the following commands, as it will clear your
package cache, in a terminal ( Applications -> Accessories -> Terminal )
:
sudo apt-get c
VPCC22S8E working fine with newest nvidia drivers (260.19.26) with GT 320M
graphic card.
VGA out works - HDMI not tested
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in ubuntu.
https://bugs.launchpad.net/bugs/657634
T
This is the DSDT for the Acer TravelMate8472TG
00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor
Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA
controller])
01:00.0 VGA compatible controller [0300]: nVidia Corporation GT216 [GeForce GT
330M] [10de:
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/642511/+attachment/1606212/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/642511/+attachment/1606213/+files/CurrentDmesg.txt
** Attachment added: "DKMSBuildLog.txt"
http
Public bug reported:
??
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: fglrx 2:8.723.1-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
Uname: Linux 2.6.32-25-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Sat Sep 18 08:38:33 2010
Error
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/627011/+attachment/1530306/+files/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/627011/+attachment/1530307/+files/CurrentDmesg.txt
** Attachment added: "DRM.card0.SVIDEO.1.txt"
Public bug reported:
Binary package hint: xserver-xorg-video-intel
Apport informs me about this crash on startup, graphics (X11/Compiz)
still work though.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-19.28-
** Tags added: maverick
** Tags removed: lucid
--
quadrapassel doesn't start: Failed to initialise clutter: Unable to select the
newly created GLX context
https://bugs.launchpad.net/bugs/561734
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-s
This bug reappears in Maverick, maybe the newer xserver package is
missing the patch?
This is using virtualbox:
$ quadrapassel --clutter-debug=all
ClutterX11-Message: [BACKEND] ./clutter-backend-x11.c:143: XOpenDisplay on
':0.0'
ClutterX11-Message: [BACKEND] ./clutter-backend-x11.c:170: Getting t
** Tags removed: regression-potential
--
quadrapassel doesn't start: Failed to initialise clutter: Unable to select the
newly created GLX context
https://bugs.launchpad.net/bugs/561734
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
** Tags added: regression-potential
--
quadrapassel doesn't start: Failed to initialise clutter: Unable to select the
newly created GLX context
https://bugs.launchpad.net/bugs/561734
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ub
Thanks for confirming. Yes "fix released" would be fine, as it was
likely fixed by an update. "Invalid" might also be appropriate (because
no one really confirmed the bug when you reported it). I set the status
to "Fix released".
** Changed in: xkeyboard-config (Ubuntu)
Status: Incomplete =
Hi. It's been a while since you reported this issue -- is this still a
problem with Ubuntu Lucid (10.04)? Thanks.
** Changed in: xkeyboard-config (Ubuntu)
Status: New => Incomplete
--
~ key does not appear directly after pressing AltGr-4 on Spanish Keyboard
https://bugs.launchpad.net/bugs
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/34828834/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/34828836/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/34828837/Dependencies.txt
** A
Public bug reported:
Binary package hint: x11-xserver-utils
Since I upgraded from Ubuntu 9.04 to 9.10, I lost my default screen
resolution of 1600x1200. I can use both higher and lower resolution
however. My video hardware is Intel 965G and my screen is a Iiyama
Vision Master Pro 451 (19" CRT).
With BIOS and MICOM version 04CA, the brightness was not working on my Samsung
NC 10 as well, a BIOS update indeed fixed the problem. That said, even without
the BIOS update, the backlight (and modesetting) worked using nc10-backlight
from this PPA: https://launchpad.net/~voria/+archive/ppa
So,
** Tags added: xorg-needs-kernel-fix
--
brightness no more working on karmic (KMS)
https://bugs.launchpad.net/bugs/397617
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
___
Mailing
** Tags added: regression-potential
--
brightness no more working on karmic (KMS)
https://bugs.launchpad.net/bugs/397617
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xf86-video-intel.
___
Mailing
I'm sorry. I assumed it was using the ati driver. Should have done a bit
more research. Stupid me. But I think it can be closed since I'm back to
windows for the moment. So I can't gather more information for the
moment.
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
You rec
There seems to be nothing wrong in Xorg.0.log after reproducing. All I
have to do is restart the Xorg session. Either by logging out or a
reboot.
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
You received this bug notification because you are a member of Ubuntu-X,
which is
** Attachment added: "Xorg.0.log"
http://launchpadlibrarian.net/29299615/Xorg.0.log
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
_
** Attachment added: "output_lspci.txt"
http://launchpadlibrarian.net/29299613/output_lspci.txt
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
You received this bug notification because you are a member of Ubuntu-X,
which is the registrant for xserver-xorg-driver-ati.
_
I've made a (crappy) photo. You should see it, try the top half of the
screen.
** Attachment added: "Photo of corruption / garble"
http://launchpadlibrarian.net/29184599/IMAG0003.jpg
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
You received this bug notification becaus
** Bug watch added: ATi Linux Platform Bugs #59
http://ati.cchtml.com/show_bug.cgi?id=59
** Also affects: xserver-xorg-driver-ati via
http://ati.cchtml.com/show_bug.cgi?id=59
Importance: Unknown
Status: Unknown
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
I'm sorry, didn't realize that there's nothing wrong on the screenshot.
Guess it has to do with the video output then, I'll assume that it's
still a driver problem (?).
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
You received this bug notification because you are a member
** Attachment added: "Screenshot..."
http://launchpadlibrarian.net/29181869/Screenshot.png
--
Xorg loses color depth (?)
https://bugs.launchpad.net/bugs/400590
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in ubuntu.
__
Public bug reported:
Binary package hint: xserver-xorg-video-ati
When I change to the console with ctrl+alt+F1 and go back to the Xorg
session (crtl+alt+f7), xorg seems to lose it's color depth information
or something a like. My VGA card is a ATI 4890 and I'm using the default
open-source ati dr
62 matches
Mail list logo
