[Ubuntu-x-swat] [Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics
Resolution limits are almost always imposed by the motherboard/system manufacturer. Not the software or CPU/GPU manufacturer. In the case of your system there are some interesting notes: --- "*This DisplayPort only supports DP to D-Sub dongles. DP to HDMI dongles and DP to DVI dongles are not supported. To power up three monitors, please connect your monitors to 2 x HDMI and 1 x DP ports or 2 x HDMI and 1 x D-Sub ports via a DP to D-Sub dongle. HDMI 1 (4K/2K@30Hz) / HDMI 2 (4K/2K@30Hz) Supports DisplayPort 1.1a with max. resolution up to 4K x 2K (4096x2304) @ 30Hz" --- [https://www.asrock.com/nettop/Intel/Beebox%20Series/index.asp#Specification] So it appears the machine has some hardware limits that are relevant here: "DP to HDMI dongles and DP to DVI dongles are not supported." so make sure you're not using converters or converter cables. "HDMI 1 (4K/2K@30Hz) / HDMI 2 (4K/2K@30Hz)" so 2560x1440x60Hz is not supported over HDMI. 1920x1080x60Hz is the highest resolution those HDMI ports can do at full frame rate (presumably 60Hz). Although if you're OK with stuttering then you might be able to select 2560x1440x30Hz. "Supports DisplayPort 1.1a with max. resolution up to 4K x 2K (4096x2304) @ 30Hz" Sounds like it should support 2560x1440x60Hz but only if you're using a cable that is DisplayPort at both ends, because "DP to HDMI dongles and DP to DVI dongles are not supported". This is a problem I'm familiar with... A lot of low-power (but modern CPU) systems are made with graphics connectors that don't allow you to use the full resolution the GPU is capable of. Your best bet sounds like trying more cables that are DisplayPort at both ends. See also: https://en.wikipedia.org/wiki/HDMI#Refresh_frequency_limits_for_standard_video https://en.wikipedia.org/wiki/DisplayPort#Resolution_and_refresh_frequency_limits_for_DisplayPort -- 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/1767993 Title: Lubuntu: X11 freezing/low resolution on N3150 intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+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 1752053] Re: nvidia-390 fails to boot graphical display
Reiterating the above experiences regarding the Dell XPS 9560. Black screen with nvidia drivers. Cannot workaround this issue unless I remove the drivers. -- 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/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1752053] Re: nvidia-390 fails to boot graphical display
Hi. I am new to this forum. I have recently bought Dell XPS 15 9560 with GTX 1050 graphic card. I am trying Ubuntu 18.04, but I can't find any working nvidia driver. From ppa I tried 384, 390 as well as 396, each installation results in black screen. If I uninstall nvidia driver, laptop boots normally. I also tried the proprietary driver from Nvidia website, which didn't work as well. I also tried to switch using nvidia- prime after installation, which broke Ubuntu and I had to reinstall the system. So... are there any fixes coming? I don't have xorg.conf file so deleting it is not an option. I did not imagine this hardware has so bad support on Linux. Did anybody have good experience with older Ubuntu and GTX 1050? I don't want to give up and agree this issue is NOT FIXED. -- 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/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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
[Ubuntu-x-swat] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes
This bug has been affecting me since around 2012 or so, when I was using Arch linux (still installed btw). Same graphics chip as OP's. Upgraded ubuntu MATE to 18.04 a week ago, and today the freeze happened again. This time, I intentionally wanted to test if it was fixed, and found out that it still was not. It is random as OP said, but easily reproducible by launching any application involving accelerated 3D. So today I wanted to turn on the 3D spectrum in VLC, and the screen became garbage like on the pic below : https://i.stack.imgur.com/FEaIj.jpg And since it was VLC, I also heard the looping short bit of my music that was playing when my system froze. So no screenshot possible, the only way out is the reset button. I can confirm this never happened when I used the proprietary driver. This is not a production machine, so I'm willing to test possible fixes if needed. Will post my lspci output tomorrow, +whatever else is needed. Thanks. -- 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
[Ubuntu-x-swat] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Upgraded 17.10 -> 18.04, Thinkpad X460p with GeForce 940MX. No issues before (even both prime AND bumblebee worked). Exhaustively tried combinations of blacklisting modules, nvidia.modeset kernel lines and reinstalls of both default and ppa 390/396 drivers. The system will not boot past the filesystem check with nvidia drivers (and prime/bumblebee can't load them either), which renders the GPU unusable. -- 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/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768661] [NEW] can't make WIFI work
Public bug reported: I can't make the WIfFI operate Compact Presario V2000 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12 Uname: Linux 4.2.0-42-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 2 17:05:59 2018 DistUpgraded: 2018-05-01 16:52:36,093 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: ndiswrapper, 1.59: added ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] [1002:5955] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3091] InstallationDate: Installed on 2018-05-01 (1 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) Lsusb: Bus 001 Device 011: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless Network Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard Presario V2000 (EP377UA#ABA) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic root=UUID=3698752e-32a7-443e-959d-c4578e3e85a3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2018-05-01 (1 days ago) dmi.bios.date: 01/02/2006 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 3097 dmi.board.vendor: Quanta dmi.board.version: 47.0F dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd01/02/2006:svnHewlett-Packard:pnPresarioV2000(EP377UA#ABA):pvrRev1:rvnQuanta:rn3097:rvr47.0F:cvnQuanta:ct10:cvrN/A: dmi.product.name: Presario V2000 (EP377UA#ABA) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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 xserver.bootTime: Wed May 2 12:26:46 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1~trusty1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty 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/1768661 Title: can't make WIFI work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768661/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
Deceivingly similar issue, and one that I also encountered, in Fedora here: https://ask.fedoraproject.org/en/question/120258/macbook-touchpad- becomes-unresponsive/ And a fix here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-abb147f32e It would be nice to have this resolved as it pretty much renders Ubuntu unusable in affected Macbooks. The issue is reproducible on the 18.04 “LiveCD”. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1764097 Title: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+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 1768634] [NEW] /usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected
Public bug reported: Hello, I noticed the following error messages in my journal after an upgrade to 18.04 LTS from 16.04 LTS: The failsafeXServer lines show errors -- the rest is for context: May 02 12:06:35 hunt systemd[1]: Reached target Multi-User System. May 02 12:06:35 hunt systemd[1]: Starting Update UTMP about System Runlevel Changes... May 02 12:06:35 hunt systemd[1]: Reached target Graphical failsafe fallback. May 02 12:06:35 hunt audit[1656]: SYSTEM_RUNLEVEL pid=1656 uid=0 auid=4294967295 ses=4294967295 msg='old-level=N new-level=3 comm="systemd-update-utmp" exe="/lib/systemd/systemd-update-utmp" hostname=? addr=? terminal=? res=success' May 02 12:06:35 hunt systemd[1]: Started Update UTMP about System Runlevel Changes. May 02 12:06:35 hunt set-cpufreq[796]: Setting powersave scheduler for all CPUs May 02 12:06:35 hunt systemd[1]: Startup finished in 4.007s (kernel) + 6.827s (userspace) = 10.834s. May 02 12:06:35 hunt audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:35 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-update-utmp-runlevel comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:35 hunt audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ondemand comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 02 12:06:35 hunt systemd[1]: Reloading OpenBSD Secure Shell server. May 02 12:06:35 hunt failsafeXServer[1103]: expr: non-integer argument May 02 12:06:35 hunt failsafeXServer[1103]: /usr/share/xdiagnose/failsafeXServer: line 87: [: -lt: unary operator expected May 02 12:06:35 hunt failsafeXServer[1103]: xinit /usr/share/xdiagnose/failsafeXinit /etc/X11/xorg.conf.failsafe -- /usr/bin/X -br -once -config /etc/X11/xorg.conf.failsafe -logfile /var/log/Xorg.failsafe.log May 02 12:06:35 hunt systemd[1]: Reloaded OpenBSD Secure Shell server. May 02 12:06:35 hunt sshd[1528]: Received SIGHUP; restarting. May 02 12:06:35 hunt sshd[1528]: Server listening on 0.0.0.0 port 22. May 02 12:06:35 hunt sshd[1528]: Server listening on :: port 22. May 02 12:06:35 hunt nm-dispatcher[1042]: req:6 'connectivity-change': start running ordered scripts... May 02 12:06:35 hunt failsafeXServer[1103]: X.Org X Server 1.19.6 May 02 12:06:35 hunt failsafeXServer[1103]: Release Date: 2017-12-20 May 02 12:06:35 hunt failsafeXServer[1103]: X Protocol Version 11, Revision 0 May 02 12:06:35 hunt failsafeXServer[1103]: Build Operating System: Linux 4.4.0-119-generic x86_64 Ubuntu May 02 12:06:35 hunt failsafeXServer[1103]: Current Operating System: Linux hunt 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 May 02 12:06:35 hunt failsafeXServer[1103]: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash crashkernel=384M-2G:128M,2G-:256M crashkernel=384M-2G:128M,2G-:256 May 02 12:06:35 hunt failsafeXServer[1103]: Build Date: 13 April 2018 08:07:36PM May 02 12:06:35 hunt failsafeXServer[1103]: xorg-server 2:1.19.6-1ubuntu4 (For technical support please see http://www.ubuntu.com/support) May 02 12:06:35 hunt failsafeXServer[1103]: Current version of pixman: 0.34.0 May 02 12:06:35 hunt failsafeXServer[1103]: Before reporting problems, check http://wiki.x.org May 02 12:06:35 hunt failsafeXServer[1103]: to make sure that you have the latest version. May 02 12:06:35 hunt failsafeXServer[1103]: Markers: (--) probed, (**) from config file, (==) default setting, May 02 12:06:35 hunt failsafeXServer[1103]: (++) from command line, (!!) notice, (II) informational, May 02 12:06:35 hunt failsafeXServer[1103]: (WW) warning, (EE) error, (NI) not implemented, (??) unknown. May 02 12:06:35 hunt failsafeXServer[1103]: (++) Log file: "/var/log/Xorg.failsafe.log", Time: Wed May 2 12:06:35 2018 May 02 12:06:35 hunt failsafeXServer[1103]: (++) Using config file: "/etc/X11/xorg.conf.failsafe" May 02 12:06:35 hunt failsafeXServer[1103]: (==) Using system config directory "/usr/share/X11/xorg.conf.d" May 02 12:06:36 hunt avahi-daemon[854]: Service "Squid deb proxy on hunt" (/services/squid-deb-proxy.service) successfully established. May 02 12:06:36 hunt dbus-daemon[1716]: [session uid=0 pid=1714] AppArmor D-Bus mediation is enabled May 02 12:06:36 hunt dbus-daemon[1716]: [session uid=0 pid=1714] Activating service name='org.a11y.Bus' requested by ':1.0' (uid=0 pid=1706 comm="zenity --warning --text The system is runn" label="unconfined") May 02 12:06:36 hunt dbus-daemon[1716]: [session uid=0 pid=1714] Successfully activated service 'org.a11y.Bus' May 02 12:06:36 hunt org.a11y.Bus[1716]: dbus-daemon[1723]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=0 pid=1706
[Ubuntu-x-swat] [Bug 1768633] [NEW] desktop or window fallen over after standby
Public bug reported: after wake up from standby the screen was flickering and a window was fallen over ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 NonfreeKernelModules: openafs nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 387.34 Tue Nov 21 03:09:00 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 2 21:04:50 2018 DistUpgraded: 2017-08-25 15:00:28,865 DEBUG /openCache(), new cache size 89089 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5] NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5] MachineType: LENOVO 2441CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=d69762cf-74da-49ec-97d9-c040c9e21557 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2017-08-25 (250 days ago) dmi.bios.date: 09/26/2017 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA9WW (2.69 ) dmi.board.asset.tag: Not Available dmi.board.name: 2441CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA9WW(2.69):bd09/26/2017:svnLENOVO:pn2441CTO:pvrThinkPadW530:rvnLENOVO:rn2441CTO:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2441CTO dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to load info from any available system ERROR: Unable to load info from any available system version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed May 2 20:59:06 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) [drm] Failed to open DRM device for (null): -2 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4589 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial ** Attachment added: "window fallen over" https://bugs.launchpad.net/bugs/1768633/+attachment/5132367/+files/Bildschirmfoto%20vom%202018-05-02%2012-36-57.png -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1768633 Title: desktop or window fallen over after standby To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768633/+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 883319] Re: xrandr --scale restricts area in which mouse moves
** Changed in: xorg-server Status: Confirmed => Fix Released -- 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/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+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 881046] Re: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10
** Changed in: xorg-server Status: Confirmed => Fix Released -- 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/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+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 1768599] [NEW] .
Public bug reported: . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed May 2 18:53:03 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:0862] InstallationDate: Installed on 2017-03-28 (400 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) MachineType: ASUSTeK COMPUTER INC. M32CD_A_F_K20CD_K31CD ProcEnviron: LANGUAGE=hu PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic root=UUID=e1f42172-878a-46d2-94ee-30e4c533ab2e ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0901 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M32CD_A_F_K20CD_K31CD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr0901:bd01/28/2016:svnASUSTeKCOMPUTERINC.:pnM32CD_A_F_K20CD_K31CD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM32CD_A_F_K20CD_K31CD:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: Desktop dmi.product.name: M32CD_A_F_K20CD_K31CD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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 xserver.bootTime: Wed May 2 18:18:24 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu xenial -- 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/1768599 Title: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768599/+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 1768581] [NEW] Crashes when unlock the screen after a long time
Public bug reported: The screen freezes when I log in after I put my PC to sleep for a long time. It is usually when Google Chrome is open. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 2 21:06:15 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:3824] Subsystem: Lenovo Radeon R9 M375 [17aa:3824] InstallationDate: Installed on 2017-01-29 (457 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 80K6 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=acce47d1-0094-4b71-9644-604188760968 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: C2CN17WW(V1.03) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Z51-70 dmi.board.vendor: LENOVO dmi.board.version: 31900059 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z51-70 dmi.modalias: dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvr31900059WIN:cvnLENOVO:ct10:cvrLenovoZ51-70: dmi.product.family: IDEAPAD dmi.product.name: 80K6 dmi.product.version: Lenovo Z51-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 May 1 13:24:43 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5572 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 ** 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/1768581 Title: Crashes when unlock the screen after a long time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768581/+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 1767096] Re: Random Xorg crashes
** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed -- 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/1767096 Title: Random Xorg crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1767096/+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 1768556] Re: Tilde/macron is no longer a dead key on German keyboard
Thanks for your report. It seems to be an intentional upstream change of the basic German layout: https://cgit.freedesktop.org/xkeyboard- config/commit/symbols/de?id=49129c63 So it's not a bug. The good news is that the "German (dead tilde)" layout variant provides the behavior you prefer. ** Changed in: xkeyboard-config (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1768556 Title: Tilde/macron is no longer a dead key on German keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1768556/+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 1768558] [NEW] At start-up displays only root terminal
Public bug reported: SORRY I thought I had a duplicate "adwaita-icon-theme" and removed the small. Now no regular start-up only root. Tried to reinstall thru package manager while using usb as start-up drive, but still only root at start-up. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CasperVersion: 1.376 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed May 2 14:29:14 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (primary) [1028:01fe] Subsystem: Dell Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1028:01fe] LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: Dell Inc. Latitude D830 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0HN341 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd06/07/2007:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubuntu xenial -- 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/1768558 Title: At start-up displays only root terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768558/+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 1768556] [NEW] Tilde/macron is no longer a dead key on German keyboard
Public bug reported: Steps to reproduce: 1. Enable the German keyboard layout. 2. Open a text editor of your choice. 3. Press AltGr and + (second key after P), then press a. 4. Press AltGr + Shift and +, then press a. Expected behavior: Key acts as a dead key, the key sequences produce ã and ā, respectively. Actual behavior: Key acts as a regular key, the key sequences produce ~a and ¯a, respectively. This breaks the ability to easily input diacritics for several languages (including Portuguese, Spanish, Estonian, Latvian, Lithuanian). Additional information: Both keystrokes acted as dead keys in Ubuntu 16.04. I doubt removing the dead key functionality was intentional: While I do understand that some people might need the tilde key frequently but hardly ever need a tilde accent, I cannot think of many situations in which one would require a bare macron. Plus, for situations in which dead keys are undesirable, there is also a “nodeadkeys” variant of the German layout, which has been around for some time. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xkb-data 2.23.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Wed May 2 16:16:00 2018 Dependencies: DistUpgraded: 2018-05-01 00:48:55,072 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-29 (824 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=a1cb66fa-2942-48a4-b7d8-13881405227a ro quiet splash SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to bionic on 2018-04-30 (1 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 ** Affects: xkeyboard-config (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 xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1768556 Title: Tilde/macron is no longer a dead key on German keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1768556/+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 1752053] Re: nvidia-390 fails to boot graphical display
Same problem here with 4 1050TI cards. Installed 18.04, installed 390 driver, system doesn't boot anymore -- 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/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768232] Re: i915 driver issue in Ubuntu 18.04
I had to use a 4.16 kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline to have a working machine! -- 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/1768232 Title: i915 driver issue in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics
I've found the problem (or at least got some closer): It's the display port. I'm using a monitor with 2560x1440 pixels, connected with display port. The computer has, although tiny, 2xhdmi and 1xdisplay port outputs. when (without nomodeset) lightdm starts Xorg, it works on the display port with full resolution, but as soon as the session starts, the screen remains black. When I use a HDMI Monitor together with the display port, only console and mouse pointer work, not even a visible login screen. but when I use a FullHD HDMI Monitor only, everything works. Now, when I use my 2560x1440 monitor over HDMI, the session works, but does have FullHD 1920x1080 only and thus is somewhat blurred. Furthermore, there's trouble with the mouse, it behaves crazy as soon as entering an thin area on the left side of the screen. So now I have a slightly blurred 1920x1080 desktop, a troubled mouse, and a display-port-monitor connected with an HDMI cable. -- 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/1767993 Title: Lubuntu: X11 freezing/low resolution on N3150 intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+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 1767096] Re: Random Xorg crashes
** Attachment added: "Stacktrace" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1767096/+attachment/5131915/+files/Stacktrace -- 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/1767096 Title: Random Xorg crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1767096/+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 1768232] Re: i915 driver issue in Ubuntu 18.04
Same thing here with a Dell Latitude E6540 (i5-4210M CPU) `lspci -v` returns : 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller Flags: bus master, fast devsel, latency 0, IRQ 11 Memory at f580 (64-bit, non-prefetchable) [size=4M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at f000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: [90] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [a4] PCI Advanced Features and sudo lshw -c display ~ *-display UNCLAIMED description: VGA compatible controller product: 4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list configuration: latency=0 resources: memory:f580-f5bf memory:e000-efff ioport:f000(size=64) memory:c-d The xorg intel package is installed: Package: xserver-xorg-video-intel Version: 2:2.99.917+git20171229-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/1768232 Title: i915 driver issue in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics
** Summary changed: - X11 freezing/low resolution on N3150 intel graphics + Lubuntu: X11 freezing/low resolution on N3150 intel graphics -- 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/1767993 Title: Lubuntu: X11 freezing/low resolution on N3150 intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+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 1767993] Re: X11 freezing/low resolution on N3150 intel graphics
This is definitely not correct. a) the problem is not that I can't login. The problem is, the the screen remains black and freezes after login when nomodeset is not given. b) I had the same problem with the same machine under 17.04 and 17.10, but giving nomodeset solved the problem, the x server then came up with high resolution. So it is wrong to claim that nomodeset causes the Xserver to remain in vesa mode. c) logging in via ssh will take some time because I don't have a second machine here on my desk, I have to get a second computer first. Although I'm more than willing to blame systemd for any sort of problem, I'm not sure whether systemd would explain resolution problems. d) Would be easier if the ubuntu team fixed the recovery mode that's not working under 18.04. e) Once upon a time (10-20 years ago) X servers used to have a -probeonly option to analyze and solve that sort of problem. -- 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/1767993 Title: X11 freezing/low resolution on N3150 intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+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 1768232] Re: i915 driver issue in Ubuntu 18.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1768232 Title: i915 driver issue in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768232/+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 1752053] Re: nvidia-390 fails to boot graphical display
I am still facing the same issue with Nvidia 820m , it's not fixed -- 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/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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
