[Ubuntu-x-swat] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
@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 Xorg's render/glyph.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2060354/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
@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 assertion failures in Xorg's render/glyph.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2060354/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
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 like the cause and a good workaround. But other people
in the set of JetBrains tickets report intermittent, unpredictable
crashing that doesn't benefit from such a settings change. I think think
upstream is talking about race conditions.


So far in the bug report (the Ubuntu one) I don't understand what the proposed 
course of action is.

I think this is the upstream bug report:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659

** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1659
   https://gitlab.freedesktop.org/xorg/xserver/-/issues/1659

-- 
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 Xorg's render/glyph.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2060354] Re: Segfaults and assertion failures in Xorg's render/glyph.c

2024-04-08 Thread Tim Richardson
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 xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2060354

Title:
  Segfaults and assertion failures in Xorg's render/glyph.c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2060354/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2037604] Re: Backport packages for 22.04.4 HWE stack

2024-01-10 Thread Tim Holmes-Mitra
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 dota and quake2 (with both DRI_PRIME=0 and 1)
- desktop is hardware rendered with the iGPU and working well
- multi-monitor (2 external 4k monitors)

Let me know if there's anything else I should add or test.

-- 
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/2037604

Title:
  Backport packages for 22.04.4 HWE stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2037497] Re: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()

2023-10-05 Thread Tim Holmes-Mitra
** 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
  cogl_gl_create_timestamp_query() from
  cogl_onscreen_egl_swap_buffers_with_damage()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2037497/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2036802] [NEW] HDMI not detected on HP Zbook Power 15 G9

2023-09-20 Thread Tim Lachmann
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 implement some fix in the current LTS
version that would be MUCH helpful and appreciated for me and all other
ubuntu users on the same laptop.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-32-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.104.05  Sat Aug 19 
01:15:15 UTC 2023
 GCC version:  gcc version 11.4.0 (Ubuntu 11.4.0-1ubuntu1~22.04)
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 20 19:25:44 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 evdi/1.14.1, 6.2.0-32-generic, x86_64: installed
 evdi/1.14.1, 6.2.0-33-generic, x86_64: installed
 nvidia/535.104.05, 6.2.0-32-generic, x86_64: installed
 nvidia/535.104.05, 6.2.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:89c0]
   Subsystem: Hewlett-Packard Company Device [103c:89c1]
InstallationDate: Installed on 2023-08-21 (29 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: HP HP ZBook Power 15.6 inch G9 Mobile Workstation PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic 
root=UUID=8a70988e-02bd-462a-b919-7e3ff4500355 ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/26/2023
dmi.bios.release: 8.0
dmi.bios.vendor: HP
dmi.bios.version: U97 Ver. 01.08.00
dmi.board.name: 89C0
dmi.board.vendor: HP
dmi.board.version: KBC Version 11.63.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 17.99
dmi.modalias: 
dmi:bvnHP:bvrU97Ver.01.08.00:bd06/26/2023:br8.0:efr17.99:svnHP:pnHPZBookPower15.6inchG9MobileWorkstationPC:pvr:rvnHP:rn89C0:rvrKBCVersion11.63.00:cvnHP:ct10:cvr:sku6B867EA#UUW:
dmi.product.family: 103C_5336AN HP ZBook
dmi.product.name: HP ZBook Power 15.6 inch G9 Mobile Workstation PC
dmi.product.sku: 6B867EA#UUW
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubuntu

** Summary changed:

- HDMI not detected
+ HDMI not detected on HP Zbook Power 15 G9

-- 
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/2036802

Title:
  HDMI not detected on HP Zbook Power 15 G9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2036802/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2019831] Re: intel-media-va-driver VPP broken until 22.6.5

2023-05-31 Thread Tim Kelsall
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.
https://bugs.launchpad.net/bugs/2019831

Title:
  intel-media-va-driver VPP broken until 22.6.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019831/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2019831] Re: intel-media-va-driver VPP broken until 22.6.5

2023-05-30 Thread Tim Kelsall
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 we
currently recommend. But as you can imagine getting all end-users to
change this on their endpoint is non-trivial.

-- 
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 broken until 22.6.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019831/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2019831] Re: intel-media-va-driver VPP broken until 22.6.5

2023-05-22 Thread Tim Kelsall
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 broken until 22.6.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019831/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2019831] Re: intel-media-va-driver VPP broken until 22.6.5

2023-05-16 Thread Tim Kelsall
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 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 broken until 22.6.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019831/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2019831] [NEW] intel-media-va-driver VPP broken until 22.6.5

2023-05-16 Thread Tim Kelsall
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 intel-media-va-driver-non-free.

The root cause is that free EU kernel shaders were not updated before
22.6.5, causing the vaCreateContext call to fail with the
VAEntrypointVideoProc entry point.

Please could Jammy's (and Kinetic's ?) intel-media-va-driver be updated
to 22.6.5 to allow users to do VPP in the free package. Thanks.

Extra information:
1. Ubuntu 22.04.1 LTS 
2. intel-media-va-driver 22.3.1+dfsg1-1: amd64
3. Expected the call sequence to succeed, as with the 
intel-media-va-driver-non-free package's libraries.
4. The VAAPI vaCreateContext call failed, instead.

** Affects: intel-media-driver (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 broken until 22.6.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2019831/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1988275] [NEW] Xephyr does not recognize keyboard or mouse

2022-08-31 Thread Tim Hawes
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
unrecognised device identifier: /dev/input/event2
unrecognised device identifier: /dev/input/event1
Kbd option key (_source) of value (server/udev) not assigned!
Kbd option key (major) of value (13) not assigned!
Kbd option key (minor) of value (70) not assigned!
Kbd option key (config_info) of value 
(udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:258A:003A.0001/input/input13/event6)
 not assigned!
couldn't find driver for keyboard device "HID 258a:003a" (/dev/input/event6)
unrecognised device identifier: /dev/input/event7
unrecognised device identifier: /dev/input/event8
unrecognised device identifier: /dev/input/event9
Pointer option key (_source) of value (server/udev) not assigned!
Pointer option key (major) of value (13) not assigned!
Pointer option key (minor) of value (74) not assigned!
Pointer option key (config_info) of value 
(udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:093A:2510.0003/input/input17/event10)
 not assigned!
couldn't find driver for pointer device "HID 093a:2510" (/dev/input/event10)
Pointer option key (_source) of value (server/udev) not assigned!
Pointer option key (major) of value (13) not assigned!
Pointer option key (minor) of value (33) not assigned!
Pointer option key (config_info) of value 
(udev:/sys/devices/pci:00/:00:14.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:093A:2510.0003/input/input17/mouse1)
 not assigned!
couldn't find driver for pointer device "HID 093a:2510" (/dev/input/mouse1)
unrecognised device identifier: /dev/input/event12
unrecognised device identifier: /dev/input/event13
unrecognised device identifier: /dev/input/event14
unrecognised device identifier: /dev/input/event15
unrecognised device identifier: /dev/input/event16
unrecognised device identifier: /dev/input/event17
unrecognised device identifier: /dev/input/event18
unrecognised device identifier: /dev/input/event19
unrecognised device identifier: /dev/input/event11
Kbd option key (_source) of value (server/udev) not assigned!
Kbd option key (major) of value (13) not assigned!
Kbd option key (minor) of value (68) not assigned!
Kbd option key (config_info) of value 
(udev:/sys/devices/platform/i8042/serio0/input/input4/event4) not assigned!
couldn't find driver for keyboard device "AT Translated Set 2 keyboard" 
(/dev/input/event4)
unrecognised device identifier: /dev/input/event5
unrecognised device identifier: /dev/input/mouse0

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xserver-xephyr 2:21.1.3-2ubuntu2.1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Aug 31 03:59:02 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 
00 [VGA controller])
   Subsystem: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:2212]
InstallationDate: Installed on 2022-07-28 (33 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System76 Galago Pro
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_el3sdk@/vmlinuz-5.15.0-46-generic 
root=ZFS=rpool/ROOT/ubuntu_el3sdk ro quiet splash vt.handoff=1
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/13/2020
dmi.bios.release: 4.11
dmi.bios.vendor: coreboot
dmi.bios.version: 2020-05-20_de5eab8
dmi.board.name: Galago Pro
dmi.board.vendor: System76
dmi.board.version: galp4
dmi.chassis.type: 9
dmi.chassis.vendor: System76
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvncoreboot:bvr2020-05-20_de5eab8:bd05/13/2020:br4.11:efr0.0:svnSystem76:pnGalagoPro:pvrgalp4:rvnSystem76:rnGalagoPro:rvrgalp4:cvnSystem76:ct9:cvr:sku:
dmi.product.name: Galago Pro
dmi.product.version: galp4
dmi.sys.vendor: System76
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: 

[Ubuntu-x-swat] [Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed

2022-04-01 Thread Tim Richardson
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/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit
tim@ochre:~$

-- 
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/1966571

Title:
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init
  failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow

2021-08-20 Thread tim O
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 Displaylink is extremely slow

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1875015/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth

2021-05-20 Thread Tim Crawford
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 before starting X.

(As a quick hack, I am using `ExecStartPre=/bin/sleep 1` to give drm
enough time before starting GDM.)

-- 
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/1925344

Title:
  [nvidia] Session not started after reboot (black screen) - requires
  switching tty back and forth

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1925344/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1927767] Re: All apps crashed in my X11 session, then terminal console crashed, reboot failed

2021-05-16 Thread Tim Richardson
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 crashed in my X11 session, then terminal console crashed,
  reboot failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1927767/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1923632] Re: Screen flickering

2021-04-17 Thread Tim Passingham
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 worse as the corruption grows.  It doesn't seem to be a
fundamental graphics issue that happens every time a certain set of
actions takes place.  That probably means it will be difficult to track
down, and may vary a lot between systems.

I'm willing to try and help analyse the issue, but I have no idea what
data I could provide to help.

-- 
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 flickering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923632/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1923632] Re: Screen flickering

2021-04-16 Thread Tim Passingham
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 flickering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923632/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1923632] Re: Screen flickering

2021-04-16 Thread Tim Passingham
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 system has been on for a few hours, so I initially suspected
hardware, but reverting to 5.8.0-48 fixed it.

The worst effected are browsers (Firefox, Chrome and Brave) possibly
only when not full screen, but parts of the application icon toolbar and
others parts flicker on and off as well.

I tried wayland, but it was no better, so an x.org update may not help
(I can't see one available at present)

I'm using "Intel® HD Graphics 4600 (HSW GT2) graphics", on "Intel® Core™
i7-4770T CPU @ 2.50GHz × 8".  No special drivers.  Monitor connected via
HDMI.

-- 
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 flickering

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923632/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-12-05 Thread Tim Wetzel
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 instead of suspending. The external display stays
active (doesn't go into power standby) but remains black; if I open the
lid of the docked laptop it also usually remains black; the soft reboot
(Alt+Prtscrn followed by REISUB) does nothing; so the only option is a
hard power down.

Wait 10-15 seconds and restart, and it's back to the usual suspend on
entry of the login password.

Please fix again, this bug affects every Ubuntu system here. All
20.04 and ThinkPads from T440 through T480 series; so older to
practically new.

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/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-11-30 Thread Tim Wetzel
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 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 lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-11-14 Thread Tim Wetzel
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 primary. Also external Lenovo keyboard and mouse, obviously. By
simply re-selecting the proprietary nVidia driver for the discrete
graphics, the system goes into suspend as soon as the login password is
entered. These drivers worked just fine until the Ubuntu update issues
in September.

I tried 2 different versions of the nVidia driver; both continue to
cause this bug as has been the case since I opened this bug report.

I have also seen this bug triggered by automatic loading of the Dropbox
app (which I am keeping turned off until this is fixed); by a Logitech
USB wireless mouse (on a T480 configuration); and after a few
occurrences even by just the loading of the gnome shell.

-- 
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 lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-11-10 Thread Tim Wetzel
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, this particular bug is of increasing concern
and urgency.

I'm new to Ubuntu and appreciate your pointers. If I can see consistency
and gather enough information to report a new bug, I will. So far, what
I see is that this suspend on login bug can follow various events on a
docked laptop: loading the Dropbox app, loading the Logitech module for
a USB wireless mouse, loading third party nVidia drivers... and then
with continued occurrences it goes deeper into the gnome shell. The
affected systems have submitted automated crash reports already. But at
this point my concern is this suspend on login bug.

I certainly didn't intend to shift attention from the bug at hand! Quite
the opposite. 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/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-11-09 Thread Tim Wetzel
This bug is destabilizing the main Ubuntu system here again. Gnome shell has 
begun to crash. Latest cold start once again went into suspend as soon as the 
login password was entered. Lines immediately before suspending were:
Stopped target Main User Target
A connection to the bus can't be made
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 (deep)

Please get on this. 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/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-11-04 Thread Tim Wetzel
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: on startup, the system exhibited this bug and went 
into suspend as soon as I put in the password. Immediately before suspending, 
the logs showed:
NVidia: access.
Using input driver 'libinput' for 'Video Bus'
and then suspended.
I then tried nVidia's 435 driver; same result (system suspended at login).
So I've gone back to the generic x.org driver for the discrete graphics again.
This is the same system where loading the Dropbox app on startup will also 
cause suspend.
Hope this helps.
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/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-10-31 Thread Tim Wetzel
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 docked (UltraDock) running lid closed with an external HDMI
display as primary and a Lenovo USB external keyboard. The dock also had
a Logitech USB dongle for the wireless Logitech mouse.

Immediately upon restarting, the system suspended as soon as the login
password was entered. In looking at the logs, it appears that the action
immediately preceeding the suspend was loading the Logitech module. This
now happens every startup unless the Logitech mouse is turned OFF during
startup.

The splash screen is turned off to prevent the spinning logo hang (done
on the first restart after the updates -- after resuming from suspend --
to prevent the hang); the initramfs error messages are on full display
with every start.

This system includes discrete nVidia graphics on an 8th gen Intel
chipset with Sierra Wireless. Ubuntu is using the proprietary nVidia
drivers, which were loaded prior to the 20.04.1 updates; those updates
did install the most recent nVidia driver. This system does NOT have
Dropbox loaded.

Posting this to provide another data point that I hope will help to pin
down this problem. FYI, this is now 3 of 3 Ubuntu LTS 20.04 systems here
that have been afflicted with the Ubuntu 20.04.1 bugs.

-- 
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 lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-10-27 Thread Tim Wetzel
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 subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-10-23 Thread Tim Wetzel
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 not suspend? Perhaps 
this will help to reproduce this issue? Again, as best I could see in the logs, 
the event immediately before the suspend event was loading a dropbox extension 
(comment 14 above).
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/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-10-22 Thread Tim Wetzel
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 suspending line are (going upward)
NetworkManager-dispatcher.service: Succeeded.
 [1603373101.8743] manager: NetworkManager state is now ASLEEP

Is this where it suspended after I put in the login password?

If you can point me to the particular log and what to look for, I'll be
glad to see if I can find it or I can upload a log if you tell me what
file?

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/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-10-22 Thread Tim Wetzel
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 
was able to get past these problems. Today, with no further changes, the 
suspend on login is back. As with the spinning logo, it occurs when laptops are 
docked and running lid down with external HDMI display as primary along with 
external keyboard and mouse. I hope that this may help in pinning these down? 
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/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-10-22 Thread Tim Wetzel
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 lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login

2020-10-21 Thread Tim Wetzel
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 to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1897185

Title:
  Laptop docked with lid closed, goes to sleep immediately on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1900057] Re: ThinkPad T400 sleeps immediately after login in Xorg sessions, but not Wayland

2020-10-19 Thread Tim Wetzel
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 keyboard and mouse; laptop is running lid closed. I also
see it intermittently on a T440s, same configuration. On startup in that
mode, as soon as I enter the password at the login, the machine
suspends.

-- 
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/1900057

Title:
  ThinkPad T400 sleeps immediately after login in Xorg sessions, but not
  Wayland

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1900057/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

2020-09-16 Thread Tim Riker
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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


Re: [Ubuntu-x-swat] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

2020-07-27 Thread Tim Hockin
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 compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT] 
> (rev a1)
>
> Is there any workaround I can perform to make this desktop usable? Other
> than blowing away the install and going back to 19.10?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1875712
>
> Title:
>   Unusable graphics, nouveau + G73 (GEForce 7600)
>
> Status in mesa package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   New
>
> Bug description:
>   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 low-res.
>
>   The nvidia proprietary driver seems to not support this device any
>   more.  I like this card because it has no fan (and I don't do a lot of
>   graphics-intense stuff).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: xorg 1:7.7+19ubuntu14
>   ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
>   Uname: Linux 5.4.0-26-generic x86_64
>   NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu27
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CasperVersion: 1.445
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Apr 28 18:13:48 2020
>   DistUpgraded: Fresh install
>   DistroCodename: focal
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 
> [VGA controller])
>  Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
>   LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
>   MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  
> ---  priority=low
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/30/2010
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: P1.40
>   dmi.board.name: X58 Extreme6
>   dmi.board.vendor: ASRock
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: To Be Filled By O.E.M.
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.family: To Be Filled By O.E.M.
>   dmi.product.name: To Be Filled By O.E.M.
>   dmi.product.sku: To Be Filled By O.E.M.
>   dmi.product.version: To Be Filled By O.E.M.
>   dmi.sys.vendor: To Be Filled By O.E.M.
>   version.compiz: compiz N/A
>   version.libdrm2: libdrm2 2.4.101-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20200226-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+subscriptions

-- 
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/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
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 root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1882216] [NEW] Xorg freeze

2020-06-05 Thread Tim Mueller
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 does
also not work.

Using sudo service gdm3 stop and sudo startx is working. Due to the fact
that the VNC console is completely frozen and this is hosted at a
provider I have to use a separate putty session to stop gdm and starting
a new gui session which is then displayed in the VNC.

This problem does not exist with Ubuntu 18.04 LTS. It does not matter if
I use a fresh installed Ubuntu 20.04 or an upgraged 18.04 LTS to 20.04
LTS. On a second VPS the problem is similar but not the same. The second
one does not get totally frozen. There is still no GUI when booting but
it ends up in a purple uniform screen even the text mode is purple (the
first VPS ends up a blueish screen with blue vertical lines).

On the second VPS it is possible to switch to shell (purple style) and
executing the abovementioned commands directly without a second putty
session. But the behavior is basically similar for both VPS.

When using sudo reboot the second VPS displays text again and the first
only some graphic trash. So basically they have both the same behavior
but on the first the graphics are totally destroyed even text is not
working anymore. The Funny thing is that startx is still working but
after clothng the startx session the graphic trash is shown again.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Jun  5 10:39:59 2020
DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
 rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Device [1234:] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Red Hat, Inc. Device [1af4:1100]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=4bffe67b-531d-4b96-b192-538defc6d4a0 ro nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-26 (39 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.1
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug false-gpu-hang focal freeze third-party-packages 
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/1882216

Title:
  Xorg freeze

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882216/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
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 /usr/libexec/gnome-session-binary --builtin "$@"
the result is identical.

I thought maybe it's good to sort out this error first and if there are
no problems without starting GUI without root rights than maybe a second
bug report for boot to gui. But I can also open another bug report now.
I'm not sure if this bugs / problems are connected in any way or not.

With 18.04 I did not have this kind of errors on both machines. The
funny thing is: On my Raspberry Pi 4b it is working from start (ok, this
is a special distribution for special hardware so it should run).

-- 
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 root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
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 subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1882102

Title:
  [vmwgfx] Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1882102] Re: [vmwgfx] Gnome Desktop only starting with root rights

2020-06-05 Thread Tim Mueller
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. This happens on two different VPS. I have upgraded from 18.04
LTS. But this error is not connected to the update. I also tried to use
a fresh install and the result was the same. Which means there is no
login screen on both machines.

If it get's stuck the beavior is different on both VPS even if I copy
everything except /sys /run /proc (which means the same installation is
used) one VPS gets stuck in a purple screen and it is possible to change
to command line via Alt+F. The other one ends up in a blueish screen
with lines and a blinking cursor but this one is totally stuck. I added
two screenshots of that.

Sometimes I see the desktop for a part of a socond between the
resolution changes. I also tried to set a fixed resolution but was not
sucessfull because the switching is still happening. If I stop the gdm
serrvice startx with root is possible afterwards. IT took me a while to
realize this because at first I thought I should focus on the GUI boot
problem.

I now switched both VPS to multi user target insted of graphical boot.
If I use stop service gdm3 and start service gdm3 the result is the same
like described above. XRDP combined with remote desktop is also only
working via root login.

Also please run:
  ls -l /usr/libexec/gnome-session-binary
ls -l /usr/libexec/gnome-session-binary
-rwxr-xr-x 1 root root 334664 Mar 26 13:22 /usr/libexec/gnome-session-binary

On tests with xrdp I also saw some other errors in syslog which are more 
detailed as the gnome session permission error which does not seem to be the 
root cause:
May 27 18:34:59 systemd[587724]: at-spi-dbus-bus.service: Failed to execute 
command: Permission denied
May 27 18:34:59 systemd[587724]: at-spi-dbus-bus.service: Failed at step EXEC 
spawning /usr/libexec/at-spi-bus-launcher: Permission denied
May 27 18:34:59 systemd[1678]: at-spi-dbus-bus.service: Main process exited, 
code=exited, status=203/EXEC

I have seen some oher useers with this kind of problem which switched
off at-spi-dbus-bus.service. I tried that and ended up with. That's
where I stopped trying and switched at-spi-dbus-bus.service to start
agein like before. Which means I'm now on standard settings after
upgrade again:

dbus-daemon[642845]: [session uid=0 pid=642843] Activating service 
name='org.freedesktop.systemd1' requested by ':1.20' (uid=0 pid=642800 
comm="/usr/libexec/gnome-session-binary --builtin " label="unconfined")
May 27 19:49:30 dbus-daemon[642845]: [session uid=0 pid=642843] Activated 
service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 
exited with status 1
May 27 19:49:30 org.gtk.vfs.Daemon[642897]: A connection to the bus can't be 
made
May 27 19:49:30 gnome-control-c[646635]: gnome-control-center-search-provider: 
Fatal IO error 11 (Die Ressource ist zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 seahorse[643522]: seahorse: Fatal IO error 11 (Die Ressource 
ist zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 org.gnome.Chara[646649]: 
org.gnome.Characters.BackgroundService: Fatal IO error 11 (Die Ressource ist 
zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 gnome-calendar[643523]: gnome-calendar: Fatal IO error 11 (Die 
Ressource ist zur Zeit nicht verfügbar) on X server :0.
May 27 19:49:30 systemd[1]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 systemd[225333]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 org.gnome.Shell.CalendarServer[643029]: 
gnome-shell-calendar-server[643029]: Lost (or failed to acquire) the name 
org.gnome.Shell.CalendarServer - exiting
May 27 19:49:30 systemd[1678]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 systemd[1679]: root-.cache-gvfs.mount: Succeeded.
May 27 19:49:30 org.gtk.vfs.Daemon[643591]: A connection to the bus can't be 
made
May 27 19:49:30 org.gtk.vfs.Daemon[643694]: A connection to the bus can't be 
made

-- 
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 root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1882102/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1882102] [NEW] Gnome Desktop only starting with root rights

2020-06-04 Thread Tim Mueller
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 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu Jun  4 16:25:19 2020
DistUpgraded: 2020-04-26 18:18:02,277 ERROR Cache can not be locked (E:Konnte 
keinen exklusiven Zugang zur Sperrdatei /var/lib/dpkg/lock erhalten. Diese wird 
vom Prozess 21979 (dpkg) gehalten., W:Beachten Sie, dass das Entfernen der 
Sperrdatei keine Lösung ist und Ihr System zerstören kann., E:Sperren des 
Administrationsverzeichnisses (/var/lib/dpkg/) nicht möglich, wird es von einem 
anderen Prozess verwendet?)
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 rapiddisk, 5.2, 5.4.0-31-generic, x86_64: installed
 rapiddisk, 5.2, 5.4.0-33-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t: /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic 
root=UUID=f8fcb1ae-51b1-4ab2-b79d-66cf34ad77d9 ro nomodeset 
rootflags=subvol=ROOT
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-04-26 (38 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.1
dmi.modalias: 
dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.1
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages 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/1882102

Title:
  Gnome Desktop only starting with root rights

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1882102/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


Re: [Ubuntu-x-swat] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

2020-04-29 Thread Tim Hockin
How is the Radeon 5450 - any problems with it?  I may have to go the
same route.

On Tue, Apr 28, 2020 at 10:20 PM Paul Collinsworth
 wrote:
>
> I replaced the Nvidia video card in my system and the problem seems to
> have gone with it.
>
> I had seen an improvement with the Nvidia 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://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712
> > which feels like it might be similar?
> >
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1875712).
> https://bugs.launchpad.net/bugs/1860483
>
> Title:
>   [nouveau, GeForce 7300 LE] screen background overlaid with scan type
>   artifact in red
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in mesa package in Ubuntu:
>   Confirmed
> Status in mutter package in Ubuntu:
>   Confirmed
> Status in xserver-xorg-video-nouveau package in Ubuntu:
>   Confirmed
>
> Bug description:
>   My desktop has both it's usual items in place; toolbar on left and
>   desktop icons distributed around the screen. Then there's what appears
>   to be a bunch of scan line, raster line artifacts, in red, laid over
>   my normal background, which is a star field photo on what is
>   ordinarily a black field.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18
>   Uname: Linux 4.15.0-74-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7.9
>   Architecture: amd64
>   CompositorRunning: None
>   CurrentDesktop: ubuntu:GNOME
>   Date: Tue Jan 21 13:04:20 2020
>   DistUpgraded: 2018-10-03 14:38:19,863 DEBUG icon theme changed, re-reading
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>NVIDIA Corporation G72 [GeForce 7300 LE] [10de:01d1] (rev a1) (prog-if 00 
> [VGA controller])
>  Subsystem: Dell G72 [GeForce 7300 LE] [1028:0405]
>   InstallationDate: Installed on 2016-08-19 (1249 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
> (20160719)
>   MachineType: Dell Inc. Inspiron 531
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-74-generic 
> root=UUID=08d8f7c1-e351-4abe-8ebe-443d6a751497 ro plymouth:debug=1 quiet 
> splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: Upgraded to bionic on 2018-10-03 (474 days ago)
>   dmi.bios.date: 11/09/2007
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.0.7
>   dmi.board.name: 0RY206
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: ���
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Dell Inc.
>   dmi.chassis.version: Chassis Version
>   dmi.modalias: 
> dmi:bvnDellInc.:bvr1.0.7:bd11/09/2007:svnDellInc.:pnInspiron531:pvr00:rvnDellInc.:rn0RY206:rvr:cvnDellInc.:ct3:cvrChassisVersion:
>   dmi.product.name: Inspiron 531
>   dmi.product.version: 00
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>   version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20171229-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
>   xserver.bootTime: Wed Oct  3 10:41:28 2018
>   xserver.configfile: default
>   xserver.devices:
>inputPower Button KEYBOARD, id 6
>inputPower Button KEYBOARD, id 7
>inputDell Dell USB Keyboard KEYBOARD, id 8
>inputLogitech USB Trackball MOUSE, id 9
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-0ubuntu0.8
>   xserver.video_driver: nouveau
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https:

[Ubuntu-x-swat] [Bug 1860483] Re: [nouveau, GeForce 7300 LE] screen background overlaid with scan type artifact in red

2020-04-28 Thread Tim Hockin
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:
  [nouveau, GeForce 7300 LE] screen background overlaid with scan type
  artifact in red

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860483/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

2020-04-28 Thread Tim Hockin
** 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.
https://bugs.launchpad.net/bugs/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

2020-04-28 Thread Tim Hockin
** 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.
https://bugs.launchpad.net/bugs/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

2020-04-28 Thread Tim Hockin
** 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.
https://bugs.launchpad.net/bugs/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

2020-04-28 Thread Tim Hockin
** 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.
https://bugs.launchpad.net/bugs/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

2020-04-28 Thread Tim Hockin
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 bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1875712] [NEW] Unusable graphics, nouveau + G73 (GEForce 7600)

2020-04-28 Thread Tim Hockin
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 low-res.

The nvidia proprietary driver seems to not support this device any more.
I like this card because it has no fan (and I don't do a lot of
graphics-intense stuff).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 28 18:13:48 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd G73 [GeForce 7600 GT] [1458:3417]
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd  --- 
 priority=low
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: X58 Extreme6
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd12/30/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug corruption focal third-party-packages 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/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875712/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1874821] [NEW] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

2020-04-24 Thread Tim Dollowitch
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 "intel_idle.max_cstate=4" on 18.04
as workarounds. I'd like to help get to the bottom of this rather than a
work-around, but will need guidance to participate.

Description:Ubuntu 20.04 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 10:16:32 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 515 [8086:191e] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 515 [103c:8170]
InstallationDate: Installed on 2020-04-24 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f2:b58e Chicony Electronics Co., Ltd HP IR Camera
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 04f2:b58f Chicony Electronics Co., Ltd HP HD Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP EliteBook Folio G1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=3ef2b246-80ee-47da-ba11-fdfc1eef2362 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2020
dmi.bios.vendor: HP
dmi.bios.version: N91 Ver. 01.45
dmi.board.name: 8170
dmi.board.vendor: HP
dmi.board.version: KBC Version 29.73
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN91Ver.01.45:bd01/05/2020:svnHP:pnHPEliteBookFolioG1:pvr:rvnHP:rn8170:rvrKBCVersion29.73:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook Folio G1
dmi.product.sku: P2C88AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal 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/1874821

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1874821/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-13 Thread Tim Richardson
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 ssd uses lvm, the stick not, but the stick is also much
slower, just in case that is relevant.

-- 
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 connected (pure
  intel 8th gen laptop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-13 Thread Tim Richardson
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 resume right back to the stuck plymouth display, but I don't know 
any way out except to force the machine off.


** Attachment added: "Boot log including plymouth trace messages"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5353608/+files/plymouth_fail.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/1872159

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-12 Thread Tim Richardson
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 (unencrypted).

-- 
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 connected (pure
  intel 8th gen laptop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-11 Thread Tim Richardson
** 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.
https://bugs.launchpad.net/bugs/1872159

Title:
  booting with splash hangs when external monitors are connected (pure
  intel 8th gen laptop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)

2020-04-11 Thread Tim Richardson
** 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 is
+ not reproduced if using nosplash.
  
- I think this is a problem with the splash boot loader.
+ I have installed 20.04 to this laptop. Thinkpad T480, i7, intel
+ graphics.
  
- I have installed 20.04 to this laptop. Clean install, not an upgrade.
+ Clean install of 20.04 beta, not an upgrade.
  When booting from the install, the greeter screen is never reached if 
external monitors are connected at startup.
- I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals.
+ I get the spinning ubuntu logo, and nothing more. I can not change to virtual 
terminals. The fsck step does not commence.
+ 
  In recovery mood, I can log in.
- I am used to having such problems with Nvidia graphics is involved, but this 
is not the case on this laptop. It has been happily running 18.04.
+ 
+ With no external monitors attached, it works.
+ 
+ I am used to having such problems with Nvidia graphics is involved, but
+ this is not the case on this laptop. It has been happily running 18.04.
  
  External displays are recognised if they are connected after login.
  
  Also, when I edit /etc/default/grub so that it reads
  GRUB_CMDLINE_LINUX_DEFAULT=""
  (that is, splash disabled)
  it works fine with two external monitors attached.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 11 13:58:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
-  acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
-  tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
+  acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed
+  tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
-Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
+  Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
+    Subsystem: Lenovo UHD Graphics 620 [17aa:225d]
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: LENOVO 20L5S00F00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/myvg-root ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N24ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20L5S00F00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T480
  dmi.product.name: 20L5S00F00
  dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
  dmi.product.version: ThinkPad T480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

-- 
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 connected (pure
  intel 8th gen laptop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel laptop)

2020-04-11 Thread Tim Richardson
** 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.
https://bugs.launchpad.net/bugs/1872159

Title:
  booting with splash hangs when external monitors are connected (pure
  intel laptop)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected

2020-04-11 Thread Tim Richardson
** 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.
https://bugs.launchpad.net/bugs/1872159

Title:
  booting with splash hangs when external monitors are connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected

2020-04-11 Thread Tim Richardson
** 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.
https://bugs.launchpad.net/bugs/1872159

Title:
  booting with splash hangs when external monitors are connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1872159] Re: booting with splash hangs when external monitors are connected

2020-04-11 Thread Tim Richardson
** 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 connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg, Pop!OS fix works.

2020-03-05 Thread Tim Richardson
@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 "need" this fix are gdm3 users with hybrid Nvidia
graphics (where "need" = want tear-free graphics on their laptop panel
if Optimus, or on all displays if it's something like a T-series
Thinkpad where the nvidia card has no direct access to any display).

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
https://bugs.launchpad.net/bugs/1716857

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg, Pop!OS fix works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2020-02-27 Thread Tim Richardson
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 laptop results in no external monitors 
detected by Xorg
+ nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors 
detected by Xorg, Pop!OS fix works.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-430 in Ubuntu.
https://bugs.launchpad.net/bugs/1716857

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg, Pop!OS fix works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

2020-01-22 Thread Tim Ryder
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.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

2019-11-23 Thread Tim Ryder
#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.
https://bugs.launchpad.net/bugs/1822394

Title:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

2019-11-03 Thread Tim Ryder
@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:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2019-11-02 Thread Tim Richardson
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 nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1716857

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot

2019-10-30 Thread Tim Ryder
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 click, but I no longer have mouse
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:
  [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
  laptop keyboard & touchpad not working at gdm screen after boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2019-09-27 Thread Tim Richardson
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.
https://bugs.launchpad.net/bugs/1716857

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg

2019-09-27 Thread Tim Richardson
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

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1716857

Title:
  nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external
  monitors detected by Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1826597] Re: Synaptic touchpad not responding in ubuntu 19.04 when using nvidia drivers

2019-09-24 Thread Tim Richardson
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.
https://bugs.launchpad.net/bugs/1826597

Title:
  Synaptic touchpad not responding in ubuntu 19.04  when using nvidia
  drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1826597/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1823698] Re: dont know

2019-04-08 Thread tim parker
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:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1823698/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1823698] [NEW] dont know

2019-04-08 Thread tim parker
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
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Apr  8 12:14:53 2019
DistUpgraded: 2018-08-28 23:59:06,593 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics 
Controller [1043:836d]
InstallationDate: Installed on 2012-03-13 (2582 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic 
root=UUID=b5d5d6d6-6240-4254-9586-c18faee66775 ro splash quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-28 (222 days ago)
dmi.bios.date: 11/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0405
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5G41T-M LX2/GB
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0405:bd11/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLX2/GB:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Aug 28 20:10:43 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 8
 inputMicrosoft Natural® Ergonomic Keyboard 4000 KEYBOARD, id 9
 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 10
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1432 
 vendor SAM
xserver.version: 2:1.18.4-0ubuntu0.8

** Affects: xorg (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: apport-bug bionic i386 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/1823698

Title:
  dont know

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1823698/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

2018-10-25 Thread Tim Riker
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] ProcCpuinfoMinimal.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] xserver.devices.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] ProcCpuinfo.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] XorgLogOld.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] XorgLog.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] XorgConf.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] UdevDb.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] ProcModules.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] ProcInterrupts.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] Lsusb.txt

2018-10-25 Thread Tim Riker
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:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] DpkgLog.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] Lspci.txt

2018-10-25 Thread Tim Riker
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:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] BootLog.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] CurrentDmesg.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] Dependencies.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] DkmsStatus.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

2018-10-25 Thread Tim Riker
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 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1
  I boot and all three external displays run fine.
  
  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', 
'/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  

[Ubuntu-x-swat] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

2018-10-25 Thread Tim Riker
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 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] XorgLog.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] XorgConf.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] XorgLogOld.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] xserver.devices.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] UdevDb.txt

2018-10-25 Thread Tim Riker
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

Title:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] Lspci.txt

2018-10-25 Thread Tim Riker
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:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] Lsusb.txt

2018-10-25 Thread Tim Riker
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:
  Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] ProcInterrupts.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1799994] ProcCpuinfo.txt

2018-10-25 Thread Tim Riker
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.
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


  1   2   3   4   5   6   7   >