Public bug reported:
When using 'gsettings set org.gnome.desktop.interface text-scaling-
factor' command to set the scaling factor to something greater than 1,
the text gets misaligned in the search bar, which seems to be too small
(shown in an attachment here).
ProblemType: Bug
DistroRelease:
Public bug reported:
When I use a desktop interface text scaling factor of 1.5, the alignment
text in the applications menu search bar is not set properly
I have attached a screenshot showing the issue.
1)
Description:Ubuntu 22.04.1 LTS
Release:22.04
2) xorg:
Installed:
One more note: While booting, my external (USB) monitor was
disconnected.
--
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/1981849
Title:
Xorg freeze
To manage notifications about this bug go
Public bug reported:
Although I filed this against X11, this might be a kernel issue.
I upgraded packages on 7/13/22 & rebooted today (7/15/22 -- I hadn't
noted the "reboot required pop-up).
After reboot, the screen was blank/black and unresponsive. Looking at
indicator lights, I believe that
** Description changed:
When running Xorg+xwayland+wayland+sway, the ImageMagick "import"
command was executed on the commandline. The pointer was then dragged
across an Ungoogled Chromium window. I should have drawn a rectangle to
show the area being snapshot'd, but no box appeared.
Public bug reported:
When running Xorg+xwayland+wayland+sway, the ImageMagick "import"
command was executed on the commandline. The pointer was then dragged
across an Ungoogled Chromium window. I should have drawn a rectangle to
show the area being snapshot'd, but no box appeared. When the
Public bug reported:
With x11 not running, this was executed: "Xorg -configure". It should
simply build a configuration file. The output below appears in the
terminal with an error. It manages to create a config file anyway, but
what it creates causes "startx" to fall over. So I am forced to
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
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/1925973
Title:
Nvidia driver 450.119 crashes lxpanel on Ubuntu 18.04
To manage
Public bug reported:
Running Ubuntu 18.04 with the LXDE desktop.
After installing the Nvidia driver version 450.119 and rebooting, the
LXDE desktop crashes, specifically lxpanel.
Reloaded clonezilla clone of / with Nvidia driver 450.102, all is well
again.
ProblemType: Bug
DistroRelease:
Some follow-up with users from the Ubuntu MATE Community forums show
that this is occurring on Focal and Groovy; with 5.4, 5.8, and 5.10
kernels.
Following is a list of hardware and graphics information from affected users:
System:
Host: huppyryzen Kernel: 5.4.0-54-generic x86_64 bits: 64
*** This bug is a duplicate of bug 1873895 ***
https://bugs.launchpad.net/bugs/1873895
** This bug has been marked a duplicate of bug 1873895
Regression: block staircase display with side-by-side monitors of different
pixel widths
--
You received this bug notification because you are a
Public bug reported:
My laptop (Lenovo ThinkPad P51) has 2 display interfaces. One mini-dp
and one HDMI. But none of them is shown in xrandr, and my external
display connected through mini-dp is not detected also.
When I used LiveCD, the external monitor works normally. The above
situation
Ubuntu MATE 20.04 2020315
QEMU: crash
VirtualBox VBoxVGA crash
VirtualBox VMSVGA: no crash
In this case VirtualBox 6.1.4 (version shipping in 20.04)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
This continues to be an issue with Virt-Manager/QEMU with the 20200306
ISO of Ubuntu MATE and the 20200305 ISO of Ubuntu Budgie.
With VirtualBox 6.1.4 the following results occur:
1. Using VMSVGA there is no crash
2. Using VBoxSVGA the crash occurs.
--
You received this bug notification
This does occur with 20200216 ISO with Ubuntu MATE using Virt-
manager/QEMU, however this issue does not occur using VirtualBox.
--
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/1745345
@Alberto 390.116
There is more info on a duplicate bug but for brevity this is a T430
using NVIDIA GF108M [NVS 5400M]
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1851162
These are not working on 5.3.0-28
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1851162
Title:
nvidia-drivers-390 fail to build with kernel 5.3
To manage notifications
nVidia driver 340.107 is available, however switching to that in
Software & Updates has resulted in some issues.
After Apply Changes, I am kicked to the Nouveau driver.
And I get an ErrorBrokenCount > 0
Trying to resolve with sudo apt --fix-broken install as recommended by
apt gives me:
The
Public bug reported:
System is Ubuntu MATE 18.04.3 T430 with nVidia
On 27 Jan 2019 nvidia drivers were updated to 390.116 via apt upgrades with no
issues.
On 28 Jan 2919 kernel was updated to 5.3.0-28.30-18 via apt upgrades with no
issues.
System was rebooted today.
Expected outcome:
System
Word to the wise:
If you successfully compiled the driver, don't update your 18.04 system
to the HWE stack. The driver didn't seem to work with the kernel from
18.10
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in
Not an authority, but I don't think it will be fixed. Patch and compile
the driver as explained in the link from comment #13 and then use any
kernel you like.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Patch and compile the driver as explained in the link from comment #13
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
nvidia-graphics-drivers-304
With offline help from @audfray I got this to work. Really appreciate
the help.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
nvidia-graphics-drivers-304
And, the build process failed with Unable to build the NVIDIA kernel
module. Sigh.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
I really appreciate your doing this. I am trying it right now and the
patch process just stops. I looked at the combined patch file and it
seems to end with an unterminated left parenthesis. Does the file end
prematurely?
--
You received this bug notification because you are a member of
It's the only driver that manages the thermal load correctly on the
video card in my old HP laptop :(
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1748000
Title:
I do not understand this at all.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server-hwe-16.04 in Ubuntu.
https://bugs.launchpad.net/bugs/1765218
Title:
package xserver-xorg-core-hwe-16.04 2:1.19.3-1ubuntu1~16.04.4 failed
to
Public bug reported:
The notice popped up unexpectedly
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core-hwe-16.04 2:1.19.3-1ubuntu1~16.04.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-lowlatency 4.10.17
Uname: Linux 4.10.0-28-lowlatency x86_64
ApportVersion:
I'd love to have it too. It controlled the heating on my laptop better
than any other version.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1737750
Title:
*** This bug is a duplicate of bug 1737750 ***
https://bugs.launchpad.net/bugs/1737750
"Thanks."
Since I reported the bug in the first place, I'm well aware of what it
covered.
I was commenting to let affected users know that a different driver,
compatible with the same hardware (at least
** Description changed:
Running fine with nvidia-384 until this kernel update came along. When
booted into the new kernel, got super low resolution and nvidia-settings
was missing most of its functionality - could not change resolution.
Rebooted into 4.4.0-112 kernel and all was well.
My Trusty (14.04) also shows gcc-4.8 version 4.8.4-2ubuntu1~14.04.4
--
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/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04
For Trusty (14.04) I successfully installed the driver with gcc version
4:4.8.2-1ubuntu6
--
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/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks
The -116 kernel contains protections against the Spectre / Meltdown
exploits. So yeah, it's pretty great.
--
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/1750937
Title:
4.4.0-116 Kernel update
As long as you have the updated gcc installed before you install the
kernel, it works fine.
--
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/1750937
Title:
4.4.0-116 Kernel update on 2/21 breaks
Jay Flory, your information was the key! I removed the -116 kernel and
reinstalled it, and the graphics are fine now. It looks like this was
indeed due to a timing problem between when my system got the gcc update
and the kernel update.
It appears that I'll have to reinstall virtualbox as well.
Looking at apt logs, it appears my system got a gcc update the day AFTER
the kernel was pushed out. I'll try reinstalling the kernel and see if
that makes a difference.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Jay Flory, that's important information and sounds like it can lead
those of us affected to a solution. However, my version of gcc is the
default one for 14.04, I do not have a custom version, yet I still have
this problem. Do you know what version of gcc I should install?
--
You received this
*** This bug is a duplicate of bug 1737750 ***
https://bugs.launchpad.net/bugs/1737750
I changed to nvidia-340 and it works.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
I'm glad to know that the problem is fixable, but my knowledge level is
not such that I could apply this patch without detailed instructions.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
Public bug reported:
After updating to the 4.15.0-10-generic kernel today and rebooting,
could log in but not do anything after that (got desktop image and
conky, but no panel). Returning to the prior kernel, everything was OK
except apport popped up with this error.
ProblemType: Package
Mythological, you have to fix the system to the point that you can
install packages. I am not sure you are that point yet from your
description. Once you are there, you can install an old kernel by
following the procedure outlined here
Mythological, instead of waiting for a new kernel, you could install the
-112 instead, it still works fine.
--
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/1750937
Title:
14.04 Kernel update on
In the kernel log when I booted with the -116 kernel, I found this
nvidia: version magic '4.4.0-116-generic SMP mod_unload modversions '
should be '4.4.0-116-generic SMP mod_unload modversions retpoline '
This line doesn't occur in the kernel log for the -112 kernel, the case
when the driver
Public bug reported:
Running fine with nvidia-384 until this kernel update came along. When
booted into the new kernel, got super low resolution and nvidia-settings
was missing most of its functionality - could not change resolution.
Rebooted into 4.4.0-112 kernel and all was well.
Using 17.10
My Elantech mousepad on Gigabyte laptop is nearly unusable.
Over sensitive. Move and it suddenly decides I tapped and start selecting text,
or it clicks when I did not tap.
Trying to find where to configure the sensitivity reveals lots of dead programs
(gpointing-device-settings,
Bug filed to track scaling support:
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1645372
--
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/1196239
Title:
Add support for fake modes on
Just catching up on the comments here..
To answer the question of what is the user requirement, I believe the
answer is "I'd like everything on my screen to look bigger/smaller". The
system settings for Displays will have a Scale slider (which currently
is hidden until the capability exists).
this feature becomes quite critical to use a unity8 desktop, as it's
unusable now on a high res screen unless you have amazing vision :)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
Public bug reported:
sometimes when I boot up, the screen stays black. Only the mouse cursor
works, and control-alt-f1 gives a useable screen. Rebooting from there
usually gives me a clean bootup, but sometimes it takes several efforts.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg
Please disregard my last comment...helps to download the correct package
:)
The Yakkety package is working for me as well in Mate 16.04. This is
the link to find it quickly:
https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel
Pacakge name 64bit: xserver-xorg-video-
I am running 16.04 Mate and would like to install the Yakkety intel
package but I am having trouble with dependencies with the deb package.
Can you please provide some instructions for the install? Thanks!
Bill
--
You received this bug notification because you are a member of Ubuntu-X,
which
looks like the script in #143 works beautifully on the bunch of
Thinkpads I have running Intel graphics...
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1568604
Title:
I can confirm this on a fresh install of Lubuntu 16.04 on a relatively
new laptop. This bug effectively renders the laptop useless.
Libreoffice crashes X regularly (!) and hence is not usable. When I look
at /var/log/syslog the culprit is always something like:
May 9 20:55:54 kermit kernel: [
SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
> Tags: xenial
> Uname: Linux 4.4.0-18-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups:
>
> _MarkForUpload: True
>
> To manage notificatio
Public bug reported:
xserver-xorg-video-nouveau used to work perfectly. Then I attached a 2nd
monitor and adjusted the settings (successfully, as I thought), but the
next boot was to a black screen. I can only boot in recovery mode, and
cannot access high resolution (1600 x 900).
I gave up on
Alberto I never did try the NVIDIA installer. Anthony had done that.
I've been using the ubuntu driver set from the outset, regardless here's
a fresh log out put.
** Attachment added: nvidia-bug-report.log.gz
and gpu-manager log
** Attachment added: gpu-manager.log
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1307236/+attachment/4087262/+files/gpu-manager.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-settings in
Here you go Alberto. let me know if you need anything else. Just FYI
I'm GMT-5 if you need to do some realtime stuff.
** Attachment added: gpu-manager.log
https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1307236/+attachment/4085367/+files/gpu-manager.log
--
You received this
I have a similar issue on an optimus enabled laptop. Dell Latitude
E6520. I'd be happy to help out if you think my report be usefull. I'm
not running prime or the dkms module snce it interfered with the 331.20
train of drivers and my multimonitor set up. I have not ran the
workaround mentioned
I just hope it helps out. I can't code so helping test is all I can do.
--
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/1307236
Title:
NVidia Issues - blurry text after upgrading from
Public bug reported:
bill@WB4ALM-07:~$ lsb_release -rd
Description:Ubuntu 13.10
Release:13.10
bill@WB4ALM-07:~$apt-cache policy pkgname
N: Unable to locate package pkgname
I get frequent system hangs...
...sometime xorg restarts itself, many times it does not.
Usually I have
Hi,
This is no longer an issue as the computer and video card have been
disposed of.
Thanks for your help.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/612799
Title:
This is the terminal output from nvidia 319 install
Hope nit helps to identify the problem
ted@ted-Satellite-C660D:~$ sudo apt-get install nvidia-persistenced
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package nvidia-persistenced is not
Like many others, I have been getting random screen freezes since July
2013.
They are more frequent under 13.10, but I was also getting them under
13.04
I have a quad processor, and it seems that if one cpu approaches 100%, I am
much more likely to see a screen freeze. Some of the freezes
-8001
Switching to the proprietary driver was a good workaround for me.
Bill.
--
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/1247419
Title:
gnome-control-center crashes
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = bill allen (coolbreez66)
--
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/1142733
Title:
Nvidia: unknown chipset
In reply to my own comment 12, that 'rc.local' trick worked!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1168188
Title:
black screen on lenovo g580 and ubuntu 13.04
To
FYI, I noticed that if I use the Fn+F4 key on my laptop (which is the
'lower screen brightness' function key) and drop it to 0% (as reported
by a screen brightness overlay in KDE, if I'm logged in), my backlight
goes completely off, to the point that I cannot see anything on the
screen (similar to
I tried, and as with Ron A. in comment #5 to this bug, I, too can
'blindly' log in to my KDE desktop after entering my password. (So
basically, the screen goes completely off, then KDM comes up). After
logging in, the screen becomes active again.
--
You received this bug notification because you
Public bug reported:
There is 1 error.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: fglrx 2:9.010-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.9.2-0ubuntu8
AptOrdering:
fglrx:
Public bug reported:
There is 1 error.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: fglrx 2:9.010-0ubuntu3
ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.9.2-0ubuntu8
AptOrdering:
fglrx:
I just upgraded from Kubuntu 12.10 to 13.04, and have been struck by
this. Unless I attach my external monitor (via HDMI) during boot, my
laptop's LCD goes blank after showing the Kubuntu logo for a few
seconds. I know it's getting to the KDM login screen, since if I move my
mouse down+right, then
It's works like a charm. The only problem now is that I can't switch to
fglrx(high performance) without causing X to crash(segment fault). But,
at least I can safely shutdown. Thanks.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to the bug
@Nick,
I installed the packages in your ppa.
$ dpkg --list|grep -e video-intel -e fglrx
ii fglrx 2:9.000-0ubuntu3+andrik4
amd64Video driver for the AMD graphics accelerators
ii fglrx-amdcccle
not noticed
the problem since I moved.
Thanks for letting me know.
Bill
--
+--+
| Bill Purvis |
| b...@billp.org |
+--+
--
You received this bug notification because you are a member of Ubuntu-X
Public bug reported:
Error happens when starting Firefox
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.1.901-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
Uname: Linux 3.8.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion:
Public bug reported:
System problem when starting Firfox
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.1.901-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-0.2-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
NonfreeKernelModules: nvidia
Public bug reported:
When I have my screen resolution set to 1920 x 1080 (16:9), and I use my
KVM switch to change to my laptop, if I am 'away' for more than about 10
minutes, when I click back to my Ubuntu workstation, the display is set
to some very low, barely recognizable, resolution. As a
Public bug reported:
For as long as I can remember I've had this system configured to bring a
window into focus as the mouse travels over it. Without overtly
changing any X or mouse driver configuration parameters the
functionality has vanished. Now a mouse click is required to bring a
window
Public bug reported:
A number of applications fail to draw arcs while high-level alerts and similar
windows are present.
For example the pop ups that alert me when Thunderbird has just read a new
message, or when
dropbox is updated. Also, if I have a window tagged with 'always on top' that
** Attachment added: here's a screenshot of the same display but without the
interfering window
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1070830/+attachment/3411677/+files/without_bug.png
--
You received this bug notification because you are a member of Ubuntu-X,
which is
I also confirm that the workaround in #37 works! The correct option is
Option ConstrainCursor no
...and not...
Option ConstrainCursor no
(it also needs a before the Constrain )
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
Public bug reported:
Error while using nvidia-settings. Failed to write
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-2.2-generic 3.5.0-rc4
Uname: Linux 3.5.0-2-generic x86_64
NonfreeKernelModules: nvidia
--
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/1020356
Title:
failed to write xorg.conf unable to write
To manage notifications about this bug go to:
Public bug reported:
Upgrading to 12.04 from 11.10, the dual monitor setup is not working any more.
The two monitors work fine when mirrored.
If unmirrored, the screens become corrupt. When the previous configuration is
restored after a few seconds,
the screens change but are again corrupted.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1000501
Title:
nvidia-current-updates 295.49-0ubuntu1: nvidia-current-updates kernel
module failed to build
To manage
Public bug reported:
Using synaptic to load
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: nvidia-current-updates 295.49-0ubuntu1
ProcVersionSignature: Ubuntu 3.4.0-1.3-generic 3.4.0-rc5
Uname: Linux 3.4.0-1-generic x86_64
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Public bug reported:
Already reported, however this is a clean install of 12.04 and it still
happens
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+12ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/998719
Title:
Xorg fails to start unless change from lightdm to gdm using Nouveau
To manage notifications about this bug go to:
Public bug reported:
Failed while trying to install current driver.
ProblemType: Package
DistroRelease: Ubuntu 12.10
Package: nvidia-current 295.49-0ubuntu1
ProcVersionSignature: Ubuntu 3.4.0-1.3-generic 3.4.0-rc5
Uname: Linux 3.4.0-1-generic x86_64
.tmp.unity.support.test.0:
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/998178
Title:
nvidia-current 295.49-0ubuntu1: nvidia-current kernel module failed to
build
To manage notifications about this
I'm getting this same error message every time I start a Dell GX520 that
I dual-booted this morning. True dual-boot, not wubi. And a clean
install, vs. upgrade. The GX520 came with a Radeon 9250 Pro low-profile
card. The error apparently has something to do with the intel gpu. I
tried pulling
Public bug reported:
Upgraded via update-manager from 11.10,
On restart got from tail /var/log/Xorg.0.log
23.997] (II) NOUVEAU(0): NVEnterVT is called.
[ 24.661] (EE) NOUVEAU(0): failed to set mode: Invalid argument
Fatal server error:
[ 24.661] failed to create screen resources
The monitor
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/993078
Title:
Xorg failed to start on boot after upgrade using Nouveau
To manage notifications about this bug go to:
after logging in in character mode startx was successful,
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/993078
Title:
Xorg failed to start on boot after upgrade using Nouveau
To manage
changed from lightdm to GDM window manager and logs in graphically. So
maybe the problem is with lightdm
** Summary changed:
- Xorg failed to start on boot after upgrade using Nouveau
+ Xorg failed to start on boot after upgrade using Nouveau and LightDM
--
You received this bug notification
I get the (apport) bug only on my Dell computer that was upgraded from
11.10 to 12.04 Beta 2. I do not get the bug on my
eMachine that I installed straight from 12.04 Beta 2 download. It seems
to be just the upgraded one that has the problem.
It leaves my desktop with shadows when I expand the
I also have repeatedly encountered this issue where the cursor gets
stuck rapidly and repeatedly bouncing between my second and third
monitor. I am running Ubuntu Linux 10.04 32-bit with the latest updates
and the latest driver for my two NVidia GeForce GT430 graphics cards. I
am running three
This morning I applied updates that came in via update manager. There
were Unity updates, so I rebooted and tried again to use my two
monitors, but I still have the same behavior as described in #42.
Anyone else having this issue?
--
You received this bug notification because you are a member
1 - 100 of 189 matches
Mail list logo
