For PRIME users: as a workaround you can make you X session work with
Intel driver with this minimal xorg.conf
Section "ServerLayout"
Identifier "layout"
Screen 0 "Screen0" 0 0
Option "Xinerama" "0"
EndSection
Section "Monitor"
Identifier "Monitor0"
Be sure to purge the previous used nvidia driver before testing a new one
(settings removal).
Do you get the same issue if 'nouveau' driver is used ? (nvidia purged, and
reboot)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Same symptoms with a brand new GTX 1070 ti :(
** Changed in: xorg (Ubuntu)
Status: Incomplete => 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/1768906
Title:
Xorg crash
To manage
Public bug reported:
Monitor resolution is limited to 1024x768 with no option for higher
resolution
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
ApportVersion:
Public bug reported:
I am not able to log to ubuntu 18.04 after the upgrade. When I login I
get setup screen with the word "Welcome" and the system freezes
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname:
Should I set this back to 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/1768906
Title:
Xorg crash
To manage notifications about this bug go to:
Please be more polite. I committed more time to researching this bug
report yesterday than any other. What the motherboard is capable of is
at least relevant and you should be aware of it.
While you are using the kernel parameter "nomodeset", the default X
graphics driver ("modesetting") will be
** Changed in: libinput (Ubuntu)
Status: Incomplete => Triaged
** Changed in: libinput (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
Same problem here with a Dell XPS 15 9560 after Kubuntu 17.10 -> 18.04 upgrade.
Finally solved after lots of retries and reboots. I have now:
Graphics Drivers PPA
(https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
- sudo add-apt-repository ppa:graphics-drivers/ppa
- sudo apt update
-
uname -r
4.15.0-20-generic
bluez 5.48
I have juste upgraded my distro to 18.04 and I am still experiencing
this issue. I'm just about to desolder the motors from this crap lol
this is unbelievable. Why is this not an issue on windows?
--
You received this bug notification because you are a
Trying to install from ppa I get:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required
Public bug reported:
Ubuntu is overheating at my laptop. Opening youtube on firefox is enough
for critical temperature shutdown.
Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C
with only firefox or chrome open and doing nothing.
On my old 16.04 with same using, the
Today I got all working, but although prime-select query showed me
"nvidia", nvidia drivers were not loaded and nvidia-settings did not
start. I regret that I decided to run "sudo prime-select intel". Login
worked but it broke suspend mode and my logout/shutdown times are
horrible: 1,5 minutes.
*
** Summary changed:
- Screen randomly flips 180 degreese twice
+ Screen randomly flips 180 degrees
** Description changed:
- I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen
- will become flipped, go black for a second, and then return to normal.
+ I'm running Ubuntu 18.04
Public bug reported:
I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen
will become flipped, go black for a second, and then return to normal.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Same thing happens with nvidia-346.
--
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/1768906
Title:
Xorg crash
To manage notifications about this bug go to:
I have managed to work nvidia binary drivers version 340.102 with kernel
4.15 with patch https://pastebin.com/raw/fVJVvQy7 , which is mentioned
on https://devtalk.nvidia.com/default/topic/1026911/linux/4-15-rc1
-patches-for-384-98-and-340-104.
My nvidia m720 graphics is working again on Ubuntu
** Changed in: libinput
Status: Incomplete => Fix Released
--
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/1752530
Title:
Logitech touchpad hesitates or stops
To manage notifications
With that card, use nvidia-331 or 346 instead.
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
--
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/1768906
Title:
Xorg crash
To manage
Public bug reported:
When attempting to log in to a newly updated bionic beaver via the
display manager (I think this is the right term), I immediately see a
crash, a return to the user selection/login screen and a no-longer
functioning keyboard and mouse. This happens both with the proprietary
*** This bug is a duplicate of bug 1752938 ***
https://bugs.launchpad.net/bugs/1752938
** This bug has been marked a duplicate of bug 1752938
Upgrading Ubuntu 18.04 disables GPU hardware acceleration
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Forgot to add:
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1"
(see @tim-tim-richardson++'s remark). prime is set to nvidia (as default when
you install the binary drivers). Performance: very good.
--
You received this bug notification because you are a member of
There are two setups where the solution is with my setup (NVIDIA Corporation
GK107M [GeForce GT 750M], laptop with nvidia and intel):
- Use Wayland with nouveau drivers: performance OK.
- Use Xorg with nvidia drivers with kernel parameter "nvidia-drm.modeset=1"
(see @tim-tim-richardson++'s
I've upgraded from ubuntu 17.10 to 18.04 and I got the same issue.
When I boot on my laptop with a gtx 1070, I can see on my laptop screen
and my monitor connected through a USB-C adapter the startup console
starting all the modules. On the other hand I have the login screen
working well on my
** Tags added: bionic
--
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/1768755
Title:
Missing links to libGL.so and libglapi.so
To manage notifications about this bug go to:
also, in `/var/log/Xorg.1.log.old`
I see such error:
[ 16706.342] (EE)
Fatal server error:
[ 16706.342] (EE) Cannot run in framebuffer mode. Please specify busIDs
for all framebuffer devices
[ 16706.342] (EE)
[ 16706.342] (EE)
Please consult the The X.Org Foundation support
I'm running Ubuntu 18 (although I had exactly the same issue on 16 too)
and instalation of Nvidia drivers works fine, until I choose to change
to Intel graphics card. Then, after rebooting I can't open the Nvidia
GUI anymore. This means I can't use my Hdmi port. Seems like I'll have
to get back to
no fix is released, please change the status. Things are definetly not
fine yet
--
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
This is not a new problem, and it affects every gdm3-based distro that I have
used. Long story short; if you want to use modeset=1 with nvidia to get rid of
tearing (which would be every linux Optimus user on the planet), gdm3 doesn't
work. No one seems to know why.
Change your display manager
Are you just here to keep me busy with useless conversation?
As I said:
- that machine with that monitor connected over display port was working well
for more than a year with
ubuntu 16.10, 17.04, 17.10, it just took the nomodeset
- and it works well under 18.04 just for the login screen,
Also here, with a Radeon R7.
--
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/1752938
Title:
Upgrading Ubuntu 18.04 disables GPU hardware acceleration
To manage notifications about this bug go
The issue is affecting me as well, GTX 1050, ASUS laptop.
None of the resolution tactics proposed so far helped in loading the drivers
properly.
The only way to load the system is to add nomodeset and acpi=off in the grub
menu.
--
You received this bug notification because you are a member of
"Wayland" is only a protocol and "wayland (Ubuntu)" is a series of
libraries for that protocol. So please don't log bugs against "wayland".
What you are describing sounds most likely like Gnome Shell, where the
mutter component chooses Wayland or X11.
** Package changed: wayland (Ubuntu) =>
Sorry, I forgot to give my workaround :
* Turn off the monitor (electrically), disconnect the power cord if need...
* Turn back on the monitor.
* There you go.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
Public bug reported:
When my laptop start on a dock with lid closed and with 2 monitors
connected, one DVI and one DisplayPort, sometime, one of the monitors
switch to “economy mode” and turn off, randomly.
* Sometime, it's happen during boot sequence, when text flow is displayed (yes,
I remove
Public bug reported:
In Ubuntu 18.04, the package libgl1-mesa-dev:amd64 does not contain the
symbolic links libGL.so and libglapi.so.
Thus, it is not possible to use the -lGL option to compile a program...
System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit
Package: libgl1-mesa-dev:amd64
Public bug reported:
With wayland can't control screen brightness using nvidia proprietary
drivers. The screen brightness is always at 100%.
Please DON'T enable wayland by default on fresh installations or updates
because it's not 100% compatible with nvidia proprietary drivers.
Nouveau still
Don't mess the system until it's 100% functional.
--
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/1768764
Title:
disable wayland by default - nvidia proprietary drivers backlight
To manage
it seems that the i915 module is missing from the Paquet linux-
modules-4.15.0-20-generic package.
--
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
** Package changed: ubuntu => xorg (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/1768615
Title:
Intel HD3000 Sandy Bridge - Wrong display driver used by X.org
To manage notifications
You have been subscribed to a public bug:
Hello,
in Ubuntu 18.04, after upgrade from 17.10, when I login to Ubuntu desktop via
X.org, a wrong display driver is used (llvmpipe). It will cause a horribly poor
performance due to software acceleration.
When I switch to Wayland, the correct driver
41 matches
Mail list logo
