@sbeattie I tested the package you built for 22.04 and it fixes the
problem for me.
--
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/2060354
Title:
Segfaults and assertion failures in
@sbeattie It's broken in mantic too. In xwayland, the window dies. in
xorg, the session crashes, badly.
--
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/2060354
Title:
Segfaults and
Yeah, for me it crashed 100% of the time with no changes, and removing a
configuration file (which among other things removed my non-default
preference for grayscale antialias) completely stopped the crashing.
This is in a kvm/qemu VM. So from my perspective, and from a few others
users, it looks
for what it's worth, JetBrains bug reports find that the problem is
triggered by requesting grayscale anti-aliasing.
https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I've tested the proposed mesa + hwe kernel and as far as I can tell it's
working well. I believe my Z16 is navi 2nd generation and it has an iGPU
and dGPU both AMD (600M series and RX 6500 respectively). What I tested:
- firefox you tube videos (with both DRI_PRIME=0 and 1)
- steam deb running
** Tags removed: rls-mm-incoming
** Tags added: rls-mm-notfixing
--
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/2037497
Title:
gnome-shell crashed with SIGSEGV at NULL from end_query() from
Public bug reported:
As discussed in this thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/8601#note_2092811
On my laptop, HP Zbook Power 15 G9 (i7-12800H), HDMI is not detected.
According to the discussion a fix has been implemented in kernel
v6.6-rc1.
If it's possible for Ubuntu to
That would be the commit to include in the backport, yes.
I am happy to help with the work. Please give me details about how to
involve said kernel team, thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
Hi Daniel,
I am not a Ubuntu bug supervisor so I do not have a "nominate for
series" link (found this out via
https://answers.launchpad.net/launchpad/+question/140509). If you are,
could you please help out, or rope in someone who can?
About intel-media-va-driver-non-free: This is the workaround
Hello Ubuntu maintainers,
Are there any pending items I can help with to move this along?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2019831
Title:
intel-media-va-driver VPP
Additionally I see intel-media-driver on
https://tracker.debian.org/pkg/intel-media-driver has a 23.1.1 stable
backport for Debian Bullseye. [https://packages.debian.org/bullseye-
backports/intel-media-va-driver]
Could we update to this version?
--
You received this bug notification because
Public bug reported:
See https://github.com/intel/media-driver/issues/1662 for bug filed
against upstream Intel media-driver project.
The version of intel-media-va-driver on Jammy has broken functionality in the
VPP path.
This can be worked around by replacing with
Public bug reported:
Xephyr window appears but then does not accept any input from keyboard
or mouse.
This seems related:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1289
Output is:
unrecognised device identifier: /dev/input/event3
unrecognised device identifier: /dev/input/event0
Ubuntu 22.04.
I still have this problem
intel-media-va-driver 22.3.0
tigerlake laptop
$ apt-cache show intel-media-va-driver
Package: intel-media-va-driver
Architecture: amd64
Version: 22.3.0+dfsg1-1
tim@ochre:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib
This issue should be resolved with 1.20.12 on Focal? Do the expected
release date will be? Thank you
--
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/1875015
Title:
Ubuntu 20.04 and
I believe I am experiencing this on 20.04
> (EE) open /dev/dri/card0: No such file or directory
The problem seems to be that gdm-wait-for-drm doesn't work for (muxless)
dual GPU laptops when using the dGPU.
GDM will start when only card1 is available, *both* card0 and card1 need
to be available
No data available from (1) or (2) and the problem has not reoccurred.
I have commented line 23 of crashdb.conf
--
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/1927767
Title:
All apps
For lswh read lshw - sorry!
This problem is pretty bad on my system - it becomes unusable after a
while. I will have to avoid any kernel upgrades.
Given that the problem seems to happen after a while, and then gets
worse and worse, I wonder whether it is some sort of corruption issue
that gets
The lswh information on graphics says:
Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
--
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/1923632
Title:
Screen
I have the same problem on that kernel (ubuntu 20.10), and on the update
to 5.8.0-50.55. I have gone back to 5.8.0-48.54 and it has stabilised.
I get all sorts of different effects. Blocks of text being partially
blank, whole menu boxes being blank, and so on. This usually happened
after the
Another wrinkle since this week's kernel update in 20.04.1 (from
5.4.0.54.57 to 5.4.0.56.59: on every second or third startup in the
UltraDock and with the external HDMI display as primary (which is where
this suspend on login password problem occurs), the system now goes into
never-never land
This bug remains, and exhibits with every startup in the T570's
UltraDock. Likewise, this bug has exhibited on every system here (all
ThinkPads) when in their respective UltraDocks. This includes a T480,
which is a current machine based on the i7-8xxx chipset.
--
You received this bug
Update: this is still acting up, even after the kernel update and Intel
microcode updates of Nov 11 and Nov 12 respectively. Given those
updates, I tested to see whether this bug is still there. Unfortunately,
it is.
This is a ThinkPad T570, docked, using external HDMI display (via the
dock) as
Daniel, of course. My point was that I've now seen multiple occurrences
where this suspend on login bug, as it continues to occur on a given
system, causes Ubuntu to become less and less stable over time.
Unfortunately that impact has become predictable at least on the
machines here. So to me,
Error while sending AddMatch () message: The connection is closed
Stopping Tracker file system data miner...
OK
systemd-hotnamed.service: Succeeded.
Delay lock is active (UID 1000/tim, PID 1690/gnome-shell) but inhibitor timeout
is reached.
Starting Suspend...
Suspending system...
PM: suspend entry
This may also help:
I'm testing the fix for bug 1872159 (spinning logo hang on startup). It seems
to be working.
So, since the rendering of the nVidia driver is superior to the x.org driver, I
switched for the generic x.org back to nVidia's latest 450 version for the
T570's GeForce 940MX. Well:
Another system failed under 20.04.1: A T480 that hadn't been used for a
while, set up dual boot Ubuntu 20.04 and Win 10. Ubuntu had updates
waiting including the 20.04.1 updates from several weeks ago. As soon as
that installed and the system was restarted, malfunctions began. The
system was
Daniel, this seems consistent: so long as I don't load the Dropbox app,
I haven't seen the suspend. I don't know if this is the cause but
regardless the Dropbox app may help in reproducing this issue? Thanks...
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Daniel, thanks; looks like there IS something with the Dropbox app going on as
one triggers of this. I changed the Dropbox properties so that Dropbox does not
automatically start; turned off Dropbox sync; and turned off the Dropbox app.
Shut down the system. When I started the system, it did
Looking through the logs...
Seeing "Suspending" from systemd-logind this morning.
The line immediately before (below) that is
dropbox: load fq extention
'/home/tim/.dropbox-dist/dropbox-lnx.x86_64-108.4.453/psutil._psutil_posi
The lines immediately after (above) the suspe
Posted this detail upstream at Plymouth in hopes it may help:
So I did 3 things yesterday: I applied all Ubuntu Updates; turned the splash
screen back on; and reverted from the third-party nVidia drivers back to the
open source driver. Then rebooted. This was the first time in a month that I
Daniel, you're right: it just happened again. Suspended as soon as I put
in the login password. Uh- oh!
--
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/1897185
Title:
Laptop docked with
NOTE that I'm not seeing this since today's fix for 1872159 (the spinning logo
splash hang on startup). Are these related? Something has changed; but I'm not
sure whether it's truly fixed?
Thanks...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Daniel, please see also bug #1897185. Quite similar. And when I searched
for information on the suspend on login password problem, I also found
#1481442, 1589593, and 1626689 which *may* be related. I see this on
Thinkpad T570 in a mechanical dock with external HDMI display and
external USB
This happens to me too. Note: when X is NOT running, the kernel still
locks up. This appears to be a kernel driver issue and not an X issue.
--
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/1746638
Buy a cheap Radeon card. This fight is not worth having.
On Mon, Jul 27, 2020 at 3:15 PM Adrian Nida <1875...@bugs.launchpad.net> wrote:
>
> Hi, Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
> display issue. I also have the same graphics card:
>
> >From lspci:
> 03:00.0 VGA
Ah, that makes much sense. If you are having problems you could help
yourself. ;)
--
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/1882102
Title:
[vmwgfx] Gnome Desktop only starting with
Public bug reported:
When booting on a VPS connected via VNC at first the text messages via
boot are displayed. Then the resolution changes several times (VNC size
changes) and after a lot of resolution changes it gets stuck in a
corrupd graphic design. The cursor is still blinking but alt+Fx
You are using multi user target because you like to or also having some
kind of problems?
If I use (which means removing the if else)
exec /usr/libexec/gnome-session-binary --systemd "$@"
the result is the same. Still the same message for missing permission.
And with
exec
To be clear - I have not found an edit option:
-stop service gdm3
-start service gdm3
+sudo service gdm3 stop
+sudo service gdm3 start
This will not result in something visible in the VNC. sudo startx does.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Can you log in normally from the login screen? Is it only an issue with
'startx'?
No, if I try to boot directly to GUI the resolution changes several
times (I can see that via VNC which is available at boot time for the
VPS because the VNC size is changing several times) and then get's
stuck.
Public bug reported:
All files in home folder are owned by the user. startx is only working
with root rights.
xinit: connection to X server lost/usr/bin/gnome-session: 29: exec:
/usr/libexec/gnome-session-binary: Permission denied
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg
idia card after switching from the
> digital video output to the on-card VGA output, but over a period of a
> couple of weeks or so, the video degraded again.
>
> The new card is a VisionTek Radeon 5450.
>
>
> On 4/28/20 1:42 PM, Tim Hockin wrote:
> > I just filed https://b
I just filed https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712
which feels like it might be similar?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1860483
Title:
** Attachment added: "photo of screens"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362776/+files/IMG_20200428_105019.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "photo of screens"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362777/+files/IMG_20200428_104633.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "photo of screens"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362778/+files/IMG_20200428_104657.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "photo of screens"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362775/+files/IMG_20200428_111516.jpg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Note: the corruption is not changing unless I move windows around.
Moving the mouse alone draws the pointer corrctly.
** Attachment added: "photo of screens"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+attachment/5362774/+files/IMG_20200428_084746.jpg
--
You received this
Public bug reported:
This is an older card, but it worked well on ubuntu 12.x :)
Booting "Try Ubuntu" on 20.04 get the correct resolution and 2 displays,
but the video glitches and shows all sorts of noise. It is largely
unusable (which makes filing this bug very hard).
Safe Graphics works in
Public bug reported:
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO
underrun
I have screen flashing and some tearing on HP Elitebook Folio G1. Had
the same problem on 16.04 and 18.04. Previously was able to use
"i915.enable_rc6=0" on 16.04 and then
I have been investigating other bug reports. I can't find anything that
helps my very much, but I did note references to timing. It is very
puzzling why I don't have problems when booting from the installation to
an external drive. That drive is actually a USB stick (ext4 formatted).
My internal
I have been trying to work out how to log a failed session with plymouth debug
messages. I finally succeeded, it is attached.
Note that at the end of log file, it goes into suspend. That was me trying to
power off the machine, and not holding the button long enough. It actually
suspends and
I installed 20.04 beta on a usb drive on the same machine, and reinstalled
packages to resemble my main install as closely as possible. The bug does not
occur when booting from the usb drive.
The most significant difference I can think of is that the main install is on
an lvm partition
** Attachment added: "boot messages with plymouth debugging messages"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Summary changed:
- booting with splash hangs when external monitors are connected (pure intel
laptop)
+ booting with splash hangs when external monitors are connected (pure intel
8th gen laptop)
** Description changed:
+ I think this is a problem with the splash boot loader. This problem
** Summary changed:
- booting with splash hangs when external monitors are connected
+ booting with splash hangs when external monitors are connected (pure intel
laptop)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "journalctl -b-1 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Attachment added: "journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
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/1872159
Title:
booting with splash hangs when external monitors are
@Alberto, couldn't prime-select do this when going into hybrid or
Optimus mode? Only users with nvidia hybrid graphics would go down this
logic path, and they are only ones who need the fix (but only if they
are using gdm3, sddm and lightdm continue to be unaffected by this)
The set of users who
This bug persists in 20.04 daily.
The one-line Pop!OS solution
(https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26)
works, just logout and login.
Pop!OS has used this for several releases now, just saying.
** Summary changed:
- nvidia-drm.modeset=1, gdm3 and optimus
On bios 1.10.0 that was released yesterday with kernel 5.4(fedora) I no
longer have this issue. The keyboard and mouse work on boot for me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
#46 Still working for me, have not had the issue since I made that
change. I'm on Fedora 31 as well, fully up to date. Maybe I have just
been lucky so far.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
@Peter_Lustig
Yes unfortunately that is correct. It makes the laptop more then
usable, but does not fix the later bios issues.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1822394
Title:
I just installed popOS 19.10 an an Optimus laptop, nvidia option. Out of
the box you get gdm3 and tear-free prime-sync; it uses Jeremy Soller's
solution (root rights granted in Xwrapper)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I have a workaround on linux(its not ideal).
On linux if i disable "disable while typing" and then disable "tap to
click" it works. It would seem that the act of disabling and enabling
the touchpad over and over causes it to not enable once and awhile. Its
not ideal to not be able to tap to
And PS: workaround continues to be: use lightdm, a five minute fix at
worst.
https://askubuntu.com/questions/139491/how-to-change-from-gdm-to-lightdm
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
19.10 beta and nvidia drivers 430 and 435 have the same problem. I have
made the bug title correctly specific.
** Summary changed:
- nvidia-drm.modeset=1 results in no monitors detected by Xorg
+ nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors
detected by Xorg
--
A very similar thing just happened to me, with the 435 drivers via ppa.
Reverting to 430 solved it. Ubuntu 19.04, P50. USB mouse works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
bug could have been received by email on yahoo on another linked
computer
--
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/1823698
Title:
dont know
To manage notifications about this bug go to:
Public bug reported:
could be via email ?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
Last ones are from no-display -38 kernel
--
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/174
Title:
Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36
To manage
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205585/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205592/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205584/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205591/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205590/+files/XorgLog.txt
--
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/174
apport information
** Attachment added: "XorgConf.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205589/+files/XorgConf.txt
--
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/174
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205588/+files/UdevDb.txt
--
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/174
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205587/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205586/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205583/+files/Lsusb.txt
--
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/174
Title:
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205581/+files/DpkgLog.txt
--
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/174
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205582/+files/Lspci.txt
--
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/174
Title:
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205577/+files/BootLog.txt
--
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/174
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205578/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205579/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DkmsStatus.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205580/+files/DkmsStatus.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Description changed:
Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
running on VGA, DVI and display port all connected to the dock. BIOS
mode set to run external displays ONLY with nvidia chipset. prime-select
nvidia run.
When running under
apport-collect -p xorg wants to run some tests an other users? under
ssh session, this asks for passwords, but still is writing s to the
display. I'm not sure it took my authentication. Should I run as root?
then it won't have my cached credentials. Trying again under -39
--
You
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205573/+files/XorgLog.txt
--
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/174
apport information
** Attachment added: "XorgConf.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205572/+files/XorgConf.txt
--
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/174
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205574/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205575/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205571/+files/UdevDb.txt
--
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/174
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205565/+files/Lspci.txt
--
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/174
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205566/+files/Lsusb.txt
--
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/174
Title:
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205569/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/174/+attachment/5205567/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
1 - 100 of 618 matches
Mail list logo
