[Ubuntu-x-swat] [Bug 1816269] [NEW] No image on KVM switch
Public bug reported: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to a dual DisplayPort adapter, to an Avocent SV340D KVM. If I have the KVM on the switch for the NUC, everything works great. If I switch the KVM to another channel, and then switch back to the NUC, I only get black screens. The only solution is to hard reboot the NUC. Any help would be appreciated. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi all, I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04 (uname -r = 4.18.0-15-generic). I have the NUC connected via USB-C to a dual DisplayPort adapter, to an Avocent SV340D KVM. If I have the KVM on the switch for the NUC, everything works great. If I switch the KVM to another channel, and then switch back to the NUC, I only get black screens. The only solution is to hard reboot the NUC. - Any help would be aprpeciated. + Any help would be appreciated. -- 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/1816269 Title: No image on KVM switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1816269/+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 1763975] Re: DP1.2 daisy-chain flickering
Just wondering if there is any update on this? -- 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/1763975 Title: DP1.2 daisy-chain flickering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763975/+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 1816265] [NEW] Disco Dingo Wayland Fractional Scale
Public bug reported: Installed live session on a Dell XPS 13. Runs really well but after enabling wayland and turning on the experimental bits gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" I still don't get fractional scaling on the single laptop screen (100, 200 etc only). When an external monitor is plugged in I do then get fractional scaling and it works well. This needs to be available on a single monitor as well. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1816265 Title: Disco Dingo Wayland Fractional Scale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1816265/+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 1816202] Re: Mesa version is old
that radeon thing should be able to do full 4.5, but the driver is probably missing something which probably is in mesa 18.3 or 19.0, neither of which will be pushed to ubuntu 18.10 -- 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/1816202 Title: Mesa version is old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1816202/+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 1816202] Re: Mesa version is old
your hardware is old, and probably won't ever support any newer opengl version ** Changed in: mesa (Ubuntu) Status: New => Invalid -- 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/1816202 Title: Mesa version is old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1816202/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Had this with nvidia graphics drivers after installing and then removing proprietary drivers downloaded from nvidia website. I could not log in at all at first boot. If you see nvidia modules loaded, make sure that you select an xorg session on the login screen (not wayland) if you this control presented to you. lsmod| grep nvidia nvidia_uvm794624 0 nvidia_drm 40960 13 nvidia_modeset 1040384 1 nvidia_drm nvidia 17285120 653 nvidia_uvm,nvidia_modeset ipmi_msghandler 102400 2 ipmi_devintf,nvidia drm_kms_helper172032 2 nvidia_drm,i915 drm 458752 13 drm_kms_helper,nvidia_drm,i915 Alternatively, just set WaylandEnable to false (and restart gdm). cat /etc/gdm3/custom.conf # ... [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false # ... I also suspect that /etc/X11/xorg.conf generated by nvidia-xconfig (which I ran during driver installation from the website) was causing issues. Steps I performed from a VT session: 1) sudo apt purge 'nvidia*' 2) reboot 3) sudo rm /etc/X11/xorg.conf 4) sudo apt install nvidia-driver- nvidia-dkms- nvidia-settings nvidia-prime 5) reboot I also have 11-nvidia-prime.conf file at /usr/share/X11/xorg.conf.d which is generated by ubuntu-drivers-common: cat /usr/share/X11/xorg.conf.d/11-nvidia-prime.conf # DO NOT EDIT. AUTOMATICALLY GENERATED BY gpu-manager Section "OutputClass" Identifier "Nvidia Prime" MatchDriver "nvidia-drm" Driver "nvidia" Option "AllowEmptyInitialConfiguration" Option "IgnoreDisplayDevices" "CRT" Option "PrimaryGPU" "Yes" ModulePath "/x86_64-linux-gnu/nvidia/xorg" EndSection dpkg -l | grep ubuntu-drivers-common ii ubuntu-drivers-common 1:0.5.2.2 https://github.com/tseliot/ubuntu-drivers- common/blob/bionic/share/hybrid/gpu-manager.c#L1359-L1375 ** Attachment added: "nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5239177/+files/nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+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 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
nvidia-xconfig -generated xorg.conf looked like this https://paste.ubuntu.com/p/4hRVzHmbJV/ -- 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/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
According to this stackexchange thread https://unix.stackexchange.com/questions/36450/how-can-i-find-a-memory-leak-of-a-running-process/282944 Here is almost guarantee steps to find who is leaking the memory the dumps just posted should have enough information to be able to find the leaking code sections in Xorg. -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
-- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
** Attachment added: "The corresponding Xorg process core dump (Note: 3.2 GB when expanded)" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+attachment/5239134/+files/xorg.dump.7z -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
** Attachment added: "cat /procs/{pid}/smaps right after reboot"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+attachment/5239130/+files/xorg_smaps_%40reboot.zip
--
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/1815693
Title:
Kubuntu 18.10 Xorg severe memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+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 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
** Attachment added: "cat /procs/{pid}/smaps right after running for 2.5 hours"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+attachment/5239133/+files/xorg_smaps_%402hours.zip
--
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/1815693
Title:
Kubuntu 18.10 Xorg severe memory leak
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1815693/+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 1816231] [NEW] There is a constant screen flickereing.
Public bug reported: I have installed the 18.04.2 lts version. I have a basic intel graphics card It says unable to locate package pkgname when I type apt-cache policy pkgname. I think it's a problem with the xorg file. not sure. When the mouse tracker is moving there does'nt seem to be a problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 16 18:06:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:19ad] InstallationDate: Installed on 2019-02-16 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. X555LAB ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=ef09309f-b8f6-4d98-9c90-7b08ac5e2392 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LAB.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.303:bd12/19/2014:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1816231 Title: There is a constant screen flickereing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1816231/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
I observed the same behaviour as Adrian S.. Selecting Intel keeps the Nvidia card powered and the fan spinning. Installing and using bbswitch manually works. I can't make it working powering off the card at boot time :( Therefore I have to do it manually every time I boot my notebook. MX150, Ubuntu 18.04.2 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1778011/+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
