Thanks, Daniel
- I assumed this bug was known -- others online have had it. But I
wanted to still report it in hope that it will not always be an issue.
- Neither setting org.gnome.desktop.peripherals.touchpad
disable-while-typing nor any other solution I have found online for this
Public bug reported:
It makes my laptop much less usable.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Confirmed same issue as recorded here: https://github.com/mate-
desktop/mate-session-manager/issues/297
Please release a fix for Ubuntu MATE as focal 20.04 currently crashes
with Nvidia drivers.
** Bug watch added: github.com/mate-desktop/mate-session-manager/issues #297
Some more details: Using both gnome-wayland & ubuntu-wayland sessions,
the common major errors are the following:
12:22:45 PM gnome-shell: Can't create a GtkStyleContext without a display
connection
12:22:23 PM gdm-session-wor: gkr-pam: unable to locate daemon control file
It happens when the
Public bug reported:
So, this started about a week ago after an update from Ubuntu. I can
initially login with XWayland, but something loading after the desktop
appears, causes the session to exit. The only thing I can find relevant
in the logs at the timestamp this occurred are the following:
nee: (unassigned) => Stephen Allen (stephen-d-allen)
--
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/1866995
Title:
XWayland both Gnome-Session and/or Ubuntu Session No Cursor Ava
Public bug reported:
The cursor is there, just invisible. If one moves the mouse around one
can see that it's there, but not visible. Tested in both Ubuntu XWayland
session and Gnome Vanillia session. It's working OK in Xorg.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xwayland
I'm seeing this issue for the first time in Ubuntu 19.10 (eoan).
Both the screensaver and the power manager have preferences for locking.
I see this issue when both are enabled.
Under: Screensaver Preferences -> Lock Screen, I see:
Enable Lock Screen: Y/N
Lock Screen with Screensaver: Y/N
Lock
The video card in question has died...
The machine wouldn't boot at all with the video card in the machine. So I think
the bug report should be retired, not so much resolved as unresolvable. I can't
collect any more data on the symptoms and I can't swear the problem wasn't an
early indication
If it helps interpreting the logs: when the log file snapshot was taken,
I was of course running the Nouveau drivers, 'cause that's the only way
the system works. But the boot attempt immediately preceeding that was
with the NVidia 390 drivers installed.
--
You received this bug notification
Public bug reported:
The video card is a GeForce GT 730, which worked well with Ubuntu 16.04.
After changing to Xubuntu 18.04, I can only run the Nouveau driver and the lack
of acceleration is quite noticeable. When I try to enable the "tested" NVidia
driver (390), the system never presents a
Hi Dan
I did not report this bug
Steve
On August 28, 2019 3:26:09 AM Daniel van Vugt
wrote:
> Returned in bug 1841718?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1821552).
> https://bugs.launchpad.net/bugs/1822075
>
> Title:
> tooltips
Public bug reported:
I was trying unsuccessfully to load gpsim at the time the bug came to my
attention
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
I reinstalled 18.10 last evening (taking all the updates) and the issue
appears to be resolved.
--
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/1799875
Title:
Kernel Crash -
Public bug reported:
This bug is fixed in version 0.28.1, which is shipped with Cosmic. I am
requesting this be backported to Bionic. I know this was fixed
relatively recently, so I'm not sure if it's "in the queue" or not.
Here is the libinput bug report:
I didn't want the possibility of corrupting a HD from trying to shutdown
my system had have the kernel crash every time. I therefore reverted
to 18.04LTS.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
Last evening I posted the tail end of the currentDmesg.txt (attached to
this ticket) to the linux kernel mailing list.
I received back the following [0]
The newer kernels (like 4.18) have checks regarding copies to userspace for
unwanted kernel memory exposure.
The check fails here. This
I updated to the latest ASUS BIOS and tried again... on the next Ubuntu
shutdown the kernel crashed as before.
--
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/1799875
Title:
I installed the upstream kernel[0] as requested in comment #3, ran
update-grub, booted into kernel 4.19 and then tried to shutdown the
system. Again, the system crashed.
Side note: installing linux-image-
unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb, and
> Did this issue start happening after an update/upgrade?
This did not happen with 18.04LTS. I started seeing this after the update to
18.10.
The first time I tried to shut down the system since moving to 18.10 was
two nights ago (and therefore the first time I saw the issue).
> Would it
I found that in my situation it was the upgrade not working good with some
config settings in my ~/home. When I was beta testing, I don't think the
Ubuntu developers considered that many problems are associated with
upgrades. Once I did a clean install, this situation was gone.
On Wed, Sep 12,
Well it's fixed, that's the important thing.
On Sat, Jun 2, 2018 at 9:30 PM Trish1274 <1758...@bugs.launchpad.net>
wrote:
> Make that 4.13 kernel. Can't type today.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
Trish, run this in a terminal as one line:
gsettings get org.gnome.desktop.peripherals.mouse left-handed
What does it return? True or false?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
It was fixed some time ago before 18.04 was released. Do you have all
repos activated, including /contrib & /universe?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1758306
If I recall correctly it might have been a libinput update? I'm sure the
developer will answer soon. Trish I assume you've rebooted?
On Thu, May 31, 2018 at 7:01 PM Trish1274 <1758...@bugs.launchpad.net>
wrote:
> Actually, I just tried plugging in my office wireless mouse into the
> personal
Confirm that as of Saturday April 14/18 update: the issue is resolved
for me.
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in
Note the missing apply button is also mentioned in #1745440
--
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/1751892
Title:
Unable to set different Scale on different Monitors
To manage
Public bug reported:
My laptop screen is 3840x2160 while my external monitor is only
1680x1050. In order for the laptop monitor to be usable I have the
scaling set at 200 (this works wonderful). However, when I plug in my
external monitor it is scaled up to 200% as well making it unusable.
@Jouni Mettala
Your suggestion worked!
After enabling 'WaylandEnable=false'. Thanks for figuring this out,
didn't think of looking there myself.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
If you mean is Wayland installed and an option in GDM? Yes, correct. I'll
try your suggestion and report back. Thanks!
On Sun, Feb 18, 2018 at 10:45 AM Jouni Mettala
wrote:
> But your GDM is still using Wayland, Right?
>
> I had to edit /etc/gdm3/custom.conf and uncomment
That's interesting @JouniMettala - I'm getting it on Gnome-Vanilla on
Xorg.
On Sun, Feb 18, 2018 at 4:35 AM Jouni Mettala
wrote:
> I noticed this bug in Gnome with Wayland. Selected Gnome with Xorg and
> mouse buttons work. GDM session selector was affected so I had to
@Daniel van Vugt:
OK Installed the downgrade. The only difference is that the mouse cursor
isn't visible at all. Prior, using the up-to-date version, the cursor
was shown, would move but wouldn't respond to clicks. HTH
** Attachment added: "Screengrab"
Oops sorry, didn't completely answer number 1/ Yes, regular mouse not a
trackpad.
--
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/1749878
Title:
GDM doesn't accept mouse clicks
To manage
Hi Daniel, thanks for the response.
1. No, not a touchpad. This is a workstation with regular MSFT type
keyboard.
2. Sure, will downgrade libinput and report back.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
I am experiencing this same but on 18.04 Bionic Beaver. Could this patch
be applied there as well?
--
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/1743018
Title:
Unable to install
*** This bug is a duplicate of bug 1672955 ***
https://bugs.launchpad.net/bugs/1672955
** This bug has been marked a duplicate of bug 1672955
unity-system-compositor crashed with SIGSEGV in
libinput_device_config_accel_is_available() from
libinput_device_config_accel_set_speed() from
*** This bug is a duplicate of bug 1675448 ***
https://bugs.launchpad.net/bugs/1675448
** Changed in: gtk+3.0 (Ubuntu)
Assignee: William Hua (attente) => (unassigned)
** Changed in: gtk+3.0 (Ubuntu)
Status: Confirmed => Invalid
** This bug has been marked a duplicate of bug
@dinamic I think you're seeing a different problem with similar
symptoms, probably related to libSDL2 probing order.
--
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/1675364
Title:
** Summary changed:
- [regression] GTK apps fail to start under Unity8 (without gnome-session
running)
+ [regression] GTK and KDE apps fail to start under Unity8 (without
gnome-session running)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Changed in: unity8 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: ubuntu-app-launch (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
** Summary changed:
- [Regression] xmir applications fail to render
+ [Regression] applications linked to GTK fail to start without gnome-session
running
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
** Changed in: qtmir (Ubuntu)
Status: Incomplete => Invalid
**
I get the same behaviour from gedit. It seems any application relying
on gnome-session running is going to hang. I would point at some Gnome
library as being the casue of this.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
It seems the difference between my two test machines is that one one I
had logged in to Unity 7 previously, and that left gnome-session-binary
running. After a reboot to kill all systemd --user units, konsole now
hangs on both test machines.
It looks like this problem is in konsole, which
More information: the system on which this occurring shows konsole is
stuck waiting for a child bash process.
12414 ?Ss 0:00 \_ /usr/bin/python3 /usr/bin/libertine-launch
konsole
12415 ?Sl 0:00 | \_ Xmir -rootless -displayfd 3 -mir
org.kde.konsole
12420 ?Sl
OK, I can repro this on one machine but not another (not sure what the
difference is yet). For the record, journalctl is spammed with error
like the following when it does happen.
Mar 23 09:00:01 xt2-17 konsole[12421]: g_application_get_application_id:
assertion 'G_IS_APPLICATION (application)'
Does the problem persist after a reboot?
--
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/1675364
Title:
[Regression] xmir applications fail to render
To manage notifications about this
Public bug reported:
dependency failed for swap
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus..01.00.0:
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
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/1671731
Title:
[xmir] closing an app while a child window is
This is simple to reproduce. The application has disappeared from the
screen but continues to run.
It looks like qtmir is closing the window (as requested) but no word
gets out to the actual process (ie. there is no session management).
I'm suspecting the Unity 8 lifecycle for desktops is not in
Public bug reported:
Log out does not work either.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: xorg 1:7.7+13ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Stephen M. Webb (bregma)
** Changed in: canonical-devices-system-image
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-
The log shows Firefox is being run natively under Unity 8 (no Xmir).
Firefox is known to not be built natively for Mir, so it's not a
surprise that it it not start.
Assuming that an Xmir instance should be launched just in case for any
and all applications run under Unity 8 was purposefully
Public bug reported:
After the most recent upgrade (It is now January 15, 2017 at 2:45 EST),
I right-click on the desktop. Then I select the "Create New Folder"
value. When I select the "Rename..." value and then click on the text
box, the monitor display disappears from view, although the
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xmir
--
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/1635047
Title:
A touch event
Trackpad works flawlessly on my ASUS Zenbook UX32VD except for this one
issue. It makes it incredibly frustrating to use the laptop. Tested on
Ubuntu 16.04.1 LTS.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-synaptics in
Updated debdiff after adding new changelog and backporting to Mir 0.21.
** Attachment removed: "debdiff for Xenial SRU"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1613708/+attachment/4739347/+files/debdiff
** Attachment added: "debdiff for Xenial SRU"
Debdiff for Xenial SRU
** Attachment added: "debdiff for Xenial SRU"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1613708/+attachment/4739347/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in
** Description changed:
+ [Impact]
+
+ XMir clients do not have their input transform matrix modified properly
+ when the screen dimensions and orientation change (ie. rotation).
+
+ This shows up primarily on Bq M10 tablets which rotate on startup.
+
+ [Test Case]
+
+ Install XMir on a
** Attachment added: "screenshot showing the conflicting XRandR and window
extents"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1613708/+attachment/4722803/+files/screenshot20160817_140306627.png
--
You received this bug notification because you are a member of Ubuntu-X,
** Changed in: xorg-server (Ubuntu)
Importance: Undecided => Medium
** Changed in: xorg-server (Ubuntu)
Status: New => Triaged
** Changed in: libertine (Ubuntu)
Importance: Undecided => Medium
** Changed in: libertine (Ubuntu)
Status: New => Triaged
** Also affects:
For the record, I can reproduce this on Intel drivers. It appears to be
a crash in x.org possibly related to cursor handling or maybe XSHM.
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Tags added: xmir
--
You received this bug notification because you
Also using Ubuntu MATE 16.04
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated
Graphics Controller
Display Server: X.Org 1.17.2 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1680x1050@59.95hz
GLX Renderer: Mesa DRI Intel Haswell Desktop
** Changed in: libertine
Status: New => Triaged
** Changed in: libertine
Importance: Undecided => Medium
--
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/1543351
Title:
Add
** Summary changed:
- Add on-screen-keyboard support for Xmir/Puritine apps
+ Add on-screen-keyboard support for Xmir/Libertine apps
** Also affects: libertine
Importance: Undecided
Status: New
** Changed in: libertine
Assignee: (unassigned) => Brandon Schaefer (brandontschaefer)
Public bug reported:
When the Xmir server is run on a device or desktop under Unity 8 it
fails to start with the following error messages.
[xkb] Can't rename /run/user/32011/confined/com.ubuntu.sdk/fileSgDXpU to
/tmp/server-B20D7FC79C7F597315E3E501AEF10E0D866E8E92.xkm, error: Invalid
Changing the resolution with xrandr has not been successful in bringing
the cursor back recently, but attempting to switch to another user (and
then returning to the original session) DOES cause the cursor to
reappear. This at least gives me a workaround (and hopefully hints at a
fix).
--
You
Could you share a little technical background on how the BIOS could
affect what seems to be a problem manifested either in X or the Intel
display driver? I'm not saying it couldn't play a role, but it seems
extremely likely that the problem lies in one of those places.
I've been unsuccessful so
I added fglrx-installer and fglrx-installer-updates. It would be nice to
get this fixed as it's a longstanding bug in the driver that I believe
the official AMD Windows driver fixed a while ago.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Same thing happens to me on Ubuntu GNOME 15.10 x64 with fglrx
2:15.201-0ubuntu2~15.10.2. Anyway we can bump this report to fglrx
instead of linuxmint directly?
** Also affects: fglrx-installer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fglrx-installer-updates (Ubuntu)
** Description changed:
(This report is incomplete; I need some guidance regarding steps I can
take the next time this happens so I can gather better information to
report.)
What happens:
1. I'll be working
2. The mouse cursor will become invisible for no apparent reason,
Public bug reported:
(This report is incomplete; I need some guidance regarding steps I can
take the next time this happens so I can gather better information to
report.)
What happens:
1. I'll be working
2. The mouse cursor will become invisible for no apparent reason, typically on
just one of
Public bug reported:
1) Release information:
$ lsb_release -rd
Description:Ubuntu 15.10
Release:15.10
2) Package version information
15:26:38-stephen~$ apt-cache policy xserver-xorg
xserver-xorg:
Installed: 1:7.7+7ubuntu4
Candidate: 1:7.7+7ubuntu4
Version table:
*** 1:7.7
The first crash in my description corresponds to the attachment above
named "Log from the first crash described in the description"
(https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1516822/+attachment/4520297/+files/XorgPstormCrash.log).
The second crash corresponds to "XorgLogOld.txt" which
Yes, both are installed. Looking at the segmentation fault hotspot log
from my java application, it says libwayland and mesa-egl are being
loaded. I don't have gnome-session-wayland even installed and mesa
shouldn't be loaded if fglrx is being used. I've attached the java log
as well.
**
wily-proposed boots fine but the following errors are in the xorg log
[48.168] (EE) open /dev/dri/card0: No such file or directory
[48.602] (EE) AIGLX error: failed to open
/usr/X11R6/lib64/modules/dri/fglrx_dri.so,
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared
# jerrylamos (jerrylamos) wrote on 2015-10-29: #26
# How do I tell if this Lenovo M58p has Intel GMA4500 ?
google m85p gma4500 --> cnet review stating that it does.
or
glxinfo | grep OpenGL
and see something about G45
--
You received this bug notification because you are a member of
Under Ubuntu-Mate 15.04 only my wallpaper, scroll-sliders, and right window
edges were garbled.
After do-release-upgrade to 15.10 all of the things are hashed garbled tearing
whatever, even the text, even inside terminal windows.
Cory Davis (corzneffect) is correct;
Downgrading the video
*** This bug is a duplicate of bug 1507255 ***
https://bugs.launchpad.net/bugs/1507255
** This bug has been marked a duplicate of bug 1507255
Garbled graphics in Wily with Intel GMA4500 chip
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
This affects me and my card as well. I have an ATI R9 200x and cannot
use fglrx with kernel 4.2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1493888
Title:
FGLRX incompatible with
Public bug reported:
Booting from usb install. BTW creating usb install boot only worked with
Windows running unetbootin.
startup disk creator failed grub install with ubuntu. unbootin on ubuntu
failed as well.
This error shows up booting usb ubuntu
ProblemType: Package
DistroRelease: Ubuntu
** Also affects: canonical-pocket-desktop
Importance: Undecided
Status: New
--
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/1501039
Title:
Xmir from overlay PPA no longer tells
Exactly the same experience as Franck971 - touchpad/mouse does not
function
Hi. Same problem 100% time with fresh Ubuntu 15.04 EFI on Acer Aspire E15 E51
Very annoying with Nautilus (almost unusable)
Synaptics touchpad is very unstable with this laptop (also not detected at boot
50% time)
I'm
I tested The 15.7 drivers from AMD today under the desktop drivers and
they worked (though gnome is a bit sluggish). Also, I saw that fglrx
2:15.200-0ubuntu4-2 was released and that seems to have worked for me
better than the AMD driver.
--
You received this bug notification because you are a
I have the same problem after upgraded from Ubuntu 14.10 to 15.04. My
graphic card is AMD R7 260X using fglrx-amdcccle-updates
2:15.200-0ubuntu4 driver. This driver seems working fine except I got
blank screen when I tried to switch to virtual consoles with ctl+alt+fx
keys.
The open source driver
Any news on this bug?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
https://bugs.launchpad.net/bugs/1450089
Title:
fglrx causes ubuntu to hang before login
To manage notifications about this bug go to:
setting update software updater to install pre-released updates fixed
the graphics issues
although it killed my trackpad
this was fixed using
sudo apt-get install xserver-xorg-input-synaptics
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
I have updated the BIOS to A05 and will let you know if the problem
happens again.
** Tags removed: bios-outdated-a05
--
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/1463864
Title:
Black Screen
Xorg.0.log for my system (W8100)
** Attachment added: Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1450089/+attachment/4413187/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
dmesg
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1450089/+attachment/4413188/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
I have installed Trusty Tahr and switched from using displayPort only to
using displayPort and DVI. That seems to have resolved the issue.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-ati in Ubuntu.
Public bug reported:
Occasionally, when I recover from power save mode I get a black screen
with just a cursor. I can't see the desktop or any applications but,
according to ps, they are still running. I have to kill X to recover
from this bug.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
** Description changed:
Occasionally, when I recover from power save mode I get a black screen
with just a cursor. I can't see the desktop or any applications but,
according to ps, they are still running. I have to kill X to recover
from this bug.
+
+ Currently, I am running KDE using
Public bug reported:
I was running Utopic and when I came in this morning my monitors
wouldn't come out of power-save mode. I logged in remotely and rebooted
the system. The monitors now work but they are both displaying the same
content (mirroring) while they were spanning before. I have now
Any news on if/when this package can be updated?
** Package changed: fglrx-installer (Ubuntu) = fglrx-installer-updates
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer-updates in Ubuntu.
I believe I am also seeing the same thing. A live image present me with
a choice to try or install and 'try' results in a blank screen (hard
crash?) with no ttys available.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Public bug reported:
After updating Ubuntu GNOME 14.10 to 15.04, uninstalling old AMD 14.12
binary (downloaded from their site) and installing fglrx-updates or
fglrx fails to boot correctly into gdm. Not sure exactly what files to
post; I'll supply anything that's requested.
The only errors I
demesg contains several dups of the following error.
[ 637.133657] traps: compiz[5430] trap invalid opcode ip:7fe2bd6f05f5
sp:7fff0b63f0b8 error:0
[ 868.799930] traps: compiz[6021] trap invalid opcode ip:7f0fab07c5f5
sp:7fff64019268 error:0
It would be helpful if a stacktrace of compiz could
Hi Peter,
Thanks for reporting this. I'm not sure I understand why you think this
concerns libevdev though...
Regards,
Stephen
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libevdev in Ubuntu.
https://bugs.launchpad.net/bugs/1447313
Title
We're closing this bug since it is has been some time with no response
from the original bug reporter. However, if the issue still exists in
the latest development version of Ubuntu and you are the original
reporter please feel free to reopen with the requested information. If
you are not the
1 - 100 of 316 matches
Mail list logo