Hi Paul, since my post, I migrated to Ubuntu 22.04.
You can close this report.
--
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/1682133
Title:
Dual screen is broken
To manage notification
Hi Coiby
To answer your question in message #359
> In hybrid mode, does external monitor work for you?
The answer is yes, it works. I tested the hotplug of an HDMI external
monitor, it was detected by Ubuntu 20.04 and worked by default as an
extended desktop (both internal & external display used
Following the bot's message, I do not see a new kernel in -proposed ?
(with 5.8.0-41-generic rightg now). Is this a bot bug, or is there a
newer 5.8 kernel with all patches applied ?
Regarding brightness control, as mentioned early in the thread by
Helmut, we also had the issue on this model. No v
Thanks a lot @Coiby Xu (coiby), amazing work. Let's hope the third patch
will be backported and 20.04.x LTS will work our the box after this.
--
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.laun
Thanks Helmut and Francesco
I have a (bold ?) question.
As previously reported, it works (at least, moves and clicks as
expected, not talking gestures here) in the UEFI BIOS prior to the
loading of any operating system.
Does this mean there is a kind of working driver in code of the UEFI
BIOS ?
I have the same issue on Thinkpad X250 on 20.04 with the following config:
```
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
Option "AccelMethod" "uxa"
Option "TearFree" "true"
EndSection
```
resulting in being unable to use plasma wayland sessions, random
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legi
Thanks Helmut and Ben. These are very precise information and better than any
post elsewhere.
I got no reply from the email contacts provided by Kai-Heng yet...
Anyone with a Lenovo connection ?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xs
It's a good question.
In my understanding, the Legion R7000 is the name for China of the
Legion-5 15ARH05. In the Lenovo forum, the Lenovo employee has no access
to the equipment and indicates it's a kernel issue, suggesting it used
to work prior to 5.4 kernel. That looks strange.
https://forums.
Hello Didi,
The issue we face could be different : on the Lenovo Legion-5 15ARH05
(which is the object of this bug report) there is no working trick to
boot on Windows then Ubuntu : it just never worked under Linux on the
two BIOS tested (factory I think EUCN16WW and June update EUCN19WW), in
UEFI
done today
got an error from vger.kernel.org (policy analysis reported: your
address is not liked source for email) but not from other recipients, so
if any of the other affected users has an approved email address with
this server, I will be glad to provide the initial email for forwarding
--
Y
** Attachment added: "Capture d’écran de 2020-07-15 13-46-14.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392809/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-07-15%2013-46-14.png
--
You received this bug notification because you are a member of Ubuntu-X,
AMDI0010:03 and pinctrl_amd are present but the count does not move when
I move finger or click on the touchpad.
Please note I tried to remove my USB Mouse which is responsible for the
high counts on one of xhci_hcd. For this mouse it's moving rapidly.
Two screen captures enclosed.
** Attachment
Here you go
Nicolas
** Attachment added: "dmesg 5.4.42 kernel.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5392768/+files/dmesg%205.4.42%20kernel.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Hello,
The kernel 5.4.0-42-generic from
https://people.canonical.com/~khfeng/lp1887190/ does not work either.
Thanks
Nicolas
--
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
I can confirm this is still an issue. The odd part is, however, that I
did not have this issue on 19.10 with the nvidia drivers from the ppa.
Upgrading to 20.04 introduced this issue to me.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-g
I am still experiencing the issue after updating the BIOS firmware to
version 1.10.0, on Ubuntu 19.10 (kernel 5.3.0-26).
Firmware info and download page:
https://www.dell.com/support/Home/us/en/frdhs1/Drivers/DriversDetails?driverId=0KJ0
--
You received this bug notification because you are a me
Dell released yesterday BIOS version 1.9.1 for the affected XPS 9575:
https://www.dell.com/support/Home/us/en/19/Drivers/DriversDetails?driverId=MDP34&lwp=rt
There is nothing clear in the release notes on the issue, but affected
users may want to try the update.
--
You received this bug notific
Public bug reported:
Hi,
Since the installation of Ubuntu 18.10, I get the login screen but once
logged in I get a black screen. It happens only with the proprietary
nvidia driver 390. If I remove the nvidia driver to use nouveau, it
works.
My graphic card is: NVIDIA Corporation GP104 [GeForce G
Public bug reported:
I have a dual monitor setup. Sometimes, when I log back in from the lock screen
(I mean the session is already running), one of the screens does something
quite strange. When I try maximise a window, it only uses a small part of the
screen's width, as you can see here https
Public bug reported:
I guess it happens because I made and update of my nvidia drivers using
apt-get dist-upgrade while gnome was up and running. Because during the
update gnome freezes and restarts itself after a while.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
P
** Summary changed:
- UI login invisible / UI hanging when Dual 4K monitor via Displayport MST is
connected (Lenovo Ultra Dock)
+ Login screen invisible / UI hanging when both 4K monitors connected via
Displayport MST (docking station)
--
You received this bug notification because you are a me
Update:
I did a full 17.10 reinstall as last attempt.
I can confirm the following symptoms:
- When both 4k displays are connected to the docking (displayport MST), UI
login screen is already hanging (see earlier screenshot)
- When 1 x 4K display is connected it works. When connecting 2nd display
** Tags added: displayport multimonitor
--
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/1725455
Title:
Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock)
To manage notifications
Public bug reported:
I have a Nvidia GTX 670. I tried the nouveau driver. At boot, it takes a
unusual long time then finally shows me gdm3 and everything is working
after. But echo $XDG_SESSION_TYPE is set to "x11". Reading the logs, I
can see that after multiple failures to launch wayland, it fal
Public bug reported:
I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming
from 17.04 with Gnome, kernel 4.13).
I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock
(containing 2 x Displayport via MST), where the Lenovo T550 is
connected onto it. Both monito
On 18/04/17 11:36, James Cameron wrote:
> Bug also affects me. I've isolated it to a specific kernel patch and
> updated the upstream bug.
>
thanks ! To be frank, the mac being useless for my use is now resold :-)
N.
--
You received this bug notification because you are a member of Ubuntu-X,
w
No update were made, and my screen is back... oO
** Changed in: xorg (Ubuntu)
Status: New => Incomplete
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Nicolas (nicolastracktik)
** Changed in: xorg (Ubuntu)
Status: Incomplete => Opinion
** Changed in: xor
Public bug reported:
with de Graphics Controller
VGA compatible controller : Intel Corporation 3rd Gen Core
processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.11.0-041100rc5-generic
Public bug reported:
Hi,
After an update of Ubuntu 14.04 and a reboot, my second screen was not
recognized by the laptop.
This is the second time I get this. Last time I had to re-install all my
stuffs...
Laptop: Samsung NP900X3G
System: Ubuntu 14.04.5 LTS
Graphic card: Intel (00:02.0 VGA comp
Hi
Working for 2 days now on Ubuntu 17.04, updated to your proposed kernel
4.11.0-994
Amazing... working dual 4K now via 2x displayport 1.2 without a glitch on both
monitors for the first time.
Fantastic! And indeed, I hope too, that these fixes will be included a.s.a.p.
I was almost desperate
After a long search for many many weeks/months, I have found this post.
I own a Lenovo T550 and tried different versions of Ubuntu's, to connect
to my 2 external Asus PB279Q (4K) via Displayport (1.2). Tried as well
via the docking-station and the DP in the laptop itself (connecting both
gives me
iMac11,1 (RV770/M98L [Mobility Radeon HD 4850]) needs nomodeset to boot
https://bugs.freedesktop.org/show_bug.cgi?id=98046
** Bug watch added: freedesktop.org Bugzilla #98046
https://bugs.freedesktop.org/show_bug.cgi?id=98046
--
You received this bug notification because you are a member of
** Attachment added: "Xorg.0.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+attachment/4752435/+files/Xorg.0.log
--
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/1406810
Title
yes, and there is nothing in it that looks suspicious from my level of
knowledge.
--
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/1406810
Title:
[iMac11,1] Unable to boot
To manage notifications
Christopher Penalver, here is the dmsg of the boot. My video capture is
too blury to be usable. Do you need it?
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+attachment/4751600/+files/dmesg.log
--
You received this bug notification because you
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4751582/+files/ProcEnviron.txt
--
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/1406
apport information
** Description changed:
I'm unable to boot.
WORKAROUND: Use kernel parameter:
nomodeset
The causes a sluggish display and an inability to wake up the screen
after going to sleep.
---
.tmp.unity.support.test.0:
ApportVersion: 2.14.1-0ubuntu3.19
Arch
Christopher Penalver, I did test several versions.
12.04 with nomodeset -> stop at the console with an Xorg error (no screen found)
12.04 without nomodeset -> black screen
12.10 with nomodeset -> hang in console mode
12.10 without nomodeset -> black screen
13.04 with nomodeset -> hang in console
Christopher Penalver, I understand that the bug that affect me is of low
interest, so I don't expect that upstream shall fix it except by chance,
nor that you may have lot of time to spend on it.
The negatives for me are a sluggish display and an inability to wake up
the screen after going to slee
Christopher Penalver, I've now tested the 4.8-rc5. Unsurprisingly the
result is the same than for 4.8-rc4.
Do you think that testing each new kernel version one after the other is
a path to a solution? It feels more like a path to madness to me.
To recap, 14.04 with kernel 3.13 *was* working and
No, not 4.8-rc5, but 4.8-rc4 yes.
--
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/1406810
Title:
screen is garbled with 14.10 (was fine with 14.04)
To manage notifications about this bug go to:
Christopher Penalver, with nomodeset, all the kernels are "working".
So to resume, you want me to bisect between 3.13 and 4.4 to seek what?
--
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/1406810
Christopher Penalver, I'm not sure that we understand each other. Since
the bios upgrade there is *no* good kernel version for 14.04.
I don't mind the chore of a kernel bisect, but I haven't a starting
point.
--
You received this bug notification because you are a member of Ubuntu-X,
which is su
Yes, with nomodeset it works with 14.04.1. Do you want me to install the
12.04?
To recap, it was working with 14.04 and not with 14.10/15.04/15.10/16.04
before the bios upgrade. After it, it wasn't working anymore on 14.04
but still didn't work on 15.10 and 16.04. I haven't tried 14.10 and
15.04 b
I did reinstall 14.04.1 (kernel 3.13.0-32). I got a black screen. I
remember that 14.04.4 failed *after* the bios upgrade.
--
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/1406810
Title:
screen is
I suppose 3.13, but I don't know for sure. I suppose I can install a
14.04 again to see?
--
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/1406810
Title:
screen is garbled with 14.10 (was fine with
The stock kernel for 14.04 at the time (around march 2016).
--
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/1406810
Title:
screen is garbled with 14.10 (was fine with 14.04)
To manage notificati
As I said in msg #35, after the bios upgrade there was no display in
14.04 anymore. Since then I wiped the 14.04 install. I can reinstall it
if it may be useful.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchp
** Tags added: apport-collected bot-comment compiz-0.9 kernel-bug-
exists-upstream-4.8-rc4 latest-bios regression-release ubuntu utopic
vivid wily 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/b
** Tags removed: apport-collected bot-comment compiz-0.9 latest-bios
regression-release ubuntu utopic vivid wily xenial
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launch
Yes, indeed it works. 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/1406810
Title:
screen is garbled with 14.10 (was fine with 14.04)
To manage notifications about this bug go to:
http
Hello,
I updated my 16.04 server install yesterday and it boots to a black
screen unless I boot in rescue mode where I get a login prompt. Any idea
of what I could do?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.
I burned the iso from http://cdimage.ubuntu.com/daily-live/current
/xenial-desktop-amd64.iso downloaded yesterday. The image was from the
8th of April.
The boot gives a black screen as usual now that stay till the DVD become
quiet.
When editing the grub line and removing the "quiet splash" argume
I've some new info. I installed 15.10 in server mode, installed lubuntu-desktop
and ubuntu-desktop and started X without problem.
startx unity or startx both works.
But nor lightdm nor gdm start. lightdm crash and gdm gives a black
screen.
systemctl status lightdm.service
● lightdm.service - Li
I just tried with 12.04 and I also get a black screen. So I got a black
screen with 12.04, 14.04, 14.10 and 15.10 - Desktop install DVD.
FWIW, to upgrade the bios I had to install OS X 11 (El Capitan), that worked
flawlessly.
--
You received this bug notification because you are a member of Ub
here you are
1) nicolas@i27:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
[sudo] password for nicolas:
IM111.88Z.0034.B04.1509231906
09/23/15
2) there is no display any more in 14.04, still no display in 14.10
** Changed in: xorg (Ubuntu)
Status:
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601382/+files/XorgLogOld.txt
--
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/140681
apport information
** Tags added: apport-collected compiz-0.9 trusty ubuntu
** Description changed:
On a iMac Alu 2010, when
1) upgrading from 14.04 desktop to 14.10 desktop
OR
2) installing 10.10 server (SSH package only)
the screen shows thin horizontal lines moving on a black backgr
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601377/+files/ProcModules.txt
--
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/1406
here is the apport file for the 15.04 install
** Attachment added: "apport_xorg_1406810"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1406810/+attachment/4601453/+files/apport_xorg_1406810
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
I've a install of 15.04 running in console mode. I'll add the run of
apport xorg from this one. I've not tried to install a console mode
15.10. I may find the time to do that this WE if needed.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg
apport information
** Attachment added: "xserver.outputs.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601386/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601376/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601383/+files/Xrandr.txt
--
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/1406810
Title:
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601368/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601373/+files/Lsusb.txt
--
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/1406810
Title:
apport information
** Attachment added: "UnitySupportTest.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601380/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "GconfCompiz.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601367/+files/GconfCompiz.txt
--
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/1406
apport information
** Attachment added: "LightdmGreeterLogOld.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601370/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launc
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601365/+files/Dependencies.txt
--
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/14
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601374/+files/ProcCpuinfo.txt
--
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/1406
apport information
** Attachment added: "BootLog.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601363/+files/BootLog.txt
--
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/1406810
Tit
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601378/+files/UdevDb.txt
--
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/1406810
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601364/+files/CurrentDmesg.txt
--
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/14
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601381/+files/XorgLog.txt
--
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/1406810
Tit
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601369/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "xserver.devices.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601385/+files/xserver.devices.txt
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601375/+files/ProcEnviron.txt
--
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/1406
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601384/+files/xdpyinfo.txt
--
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/1406810
T
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601371/+files/LightdmLog.txt
--
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/140681
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601366/+files/DpkgLog.txt
--
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/1406810
Tit
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601379/+files/UdevLog.txt
--
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/1406810
Tit
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1406810/+attachment/4601372/+files/Lspci.txt
--
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/1406810
Title:
I had the occasion to try again with 15.04, 15.10 and 16.04 (downloaded
Sunday 13 March 2016). In each case the screen is dark with fine lines
going up.
I've no network and no console. The hardware is the one described.
--
You received this bug notification because you are a member of Ubuntu-X,
I agree with you all and don't wanted to be mean with Alberto or whoever
else.
I really don't care of who is guilty (if there is ever such a "who"),
but what concerns me is that from the outside there have been no sign
from Canonical, the kernel team or whatever to at least acknowledge that
what h
I don't understand why everyone thanks Canonical here.
I mean, they messed up the SRU kernel process and broke a big number of stable
desktops in the wild (including some LTS users).
An now everyone is saying everything is great &all now that an update was
pushed?
But did you think of those casu
Well, the new FGLRX is only in proposed, so most users are still affected. The
only sane option in my point of view would be to release a new kernel without
the patch that broke things originally.
Don't forget that the fix here does nothing for people that installed FGLRX
directly from the AMD w
Kernel 3.19.0-26.28 was pushed as a security update to all Ubuntu users today
(it is no longer in the, disabled by default, "proposed" repository).
This means all FGLRX users on Vivid (and those that installed 14.04.2) will
lose their graphical environment as soon as they reboot.
The only worka
I wont say it's not xorg, but the symptoms are the same with a base
server install.
--
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/1406810
Title:
screen is garbled with 14.10 (was fine with 14.0
Thanks a lot Digulla-hepe!
The workaround in one command:
sudo sed -i -e 's/XKit/xkit/g' /usr/lib/python2.7/dist-packages/Quirks/*
--
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/
Public bug reported:
On ubuntu version 14.10
after a screen rotation when we come back to normal rotation our mouse pointer
is doubled: the old
rotated one and the actual one.
This bug was already reported in:
https://bugs.freedesktop.org/show_bug.cgi?id=81886
with a complete solution.
I checked
Public bug reported:
during apt-upgrade dpkg return an error on upgrading fglrx :
update-alternatives reports bad gl conf
(fresh ubuntu-gnome 14.10 beta 1 install)
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: fglrx-core (not installed)
ProcVersionSignature: Ubuntu 3.16.0-14.20-gene
I am also affected by this bug. Note that this behaviour is inconsistent with
the manual description of the AreaBottomEdge Option which states :
" Ignore movements, scrolling and tapping which take place below this edge.
The option is disabled by default and can be enabled by setting the
AreaBo
(In reply to comment #75)
> Nicolas,
>
> Where does the need to *have* a key for nbsp come from?
Because unlike in English most French punctuation symbols require a
space (sometimes a short space) before. And if it's not a non-breakable
space apps will perform line breaks at the
(In reply to comment #75)
> Nicolas,
>
> Where does the need to *have* a key for nbsp come from?
Because unlike in English most French punctuation symbols require a
space (sometimes a short space) before. And if it's not a non-breakable
space apps will perform line breaks at the
(In reply to comment #71)
> And even if we wanted to please those apps, we mayb be able to without
> adding a new modifier (Level5) and a key for it -- again, see (comment #46).
I'm pretty sure some of the other spacebar configurations available as
xkb options do not require level5. They are not
(In reply to comment #70)
> If no agreement can be reached, would it be possible to have the old layout
> accessible, even under another name?
The old layout was never removed and kept its historical name (fr
latin9)
--
You received this bug notification because you are a member of Ubuntu-X,
wh
(In reply to comment #70)
> If no agreement can be reached, would it be possible to have the old layout
> accessible, even under another name?
The old layout was never removed and kept its historical name (fr
latin9)
--
You received this bug notification because you are a member of Ubuntu-X,
wh
(In reply to comment #71)
> And even if we wanted to please those apps, we mayb be able to without
> adding a new modifier (Level5) and a key for it -- again, see (comment #46).
I'm pretty sure some of the other spacebar configurations available as
xkb options do not require level5. They are not
1 - 100 of 254 matches
Mail list logo
