[Ubuntu-x-swat] [Bug 1641275] [NEW] apitrace:i386 not installable, depending on missing package python-imaging:i386
Public bug reported: Cannot install package apitrace:i386. There is a missing dependency on python-imaging:i386 (see: https://bugs.launchpad.net/ubuntu/+source /python-imaging/+bug/1641274) --- The following packages have unmet dependencies: apitrace:i386 : Depends: python-imaging:i386 but it is not installable When trying to install python-imaging:i386 I get: Package python-imaging:i386 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: python-pil python-pil:i386 E: Package 'python-imaging:i386' has no installation candidate --- Description:Ubuntu 16.10 Release:16.10 ** Affects: apitrace (Ubuntu) Importance: Undecided Status: New ** Also affects: apitrace (Ubuntu) Importance: Undecided Status: New ** No longer affects: python-imaging (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to apitrace in Ubuntu. https://bugs.launchpad.net/bugs/1641275 Title: apitrace:i386 not installable, depending on missing package python- imaging:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apitrace/+bug/1641275/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
Improvements and bug fixes for your graphics card should eventually filter down from the latest kernels into the stable kernel series, and from then into Ubuntu. If you want to make sure of that, you can file an upstream bug report at bugzilla.kernel.org -- 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/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1570653/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1570653/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1579596] Re: [amdgpu] [TOPAZ 1002:6900] System failed to resume from suspend with amdgpu loaded.
** Changed in: hwe-next Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Invalid => Won't Fix ** Changed in: hwe-next Status: Invalid => Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1579596 Title: [amdgpu] [TOPAZ 1002:6900] System failed to resume from suspend with amdgpu loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1579596/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1619033] Re: System is freezing
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1619033 Title: System is freezing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1619033/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1508407] Re: libre office impress display broken gradient in slide show
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1508407 Title: libre office impress display broken gradient in slide show To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1508407/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1639180] Re: no login possible after update to nvidia 304.132
I also cannot log on since the update to 304.132. Ubuntu 14.04 Geforce 9100 Right now I am using the nouveau driver but it is not a satisfactory solution. I have two monitors and with the nouveau driver one runs at a much lower resolution that the other. With the 304.131 driver this was not the case. Having struggled to get a system that works I am hesitant to try the workaround in comment #20 -- 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/1639180 Title: no login possible after update to nvidia 304.132 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639180/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build
Lubuntu noticed that I had 304.131-0ubuntu3, and Software Updates offered to install the (non-fixed) 304.132-0ubuntu1. In the changelog displayed, I noted that there was a 304.131-0ubuntu4 and 304.131-0ubuntu5. but the latest I found at the above website was 304.131-0ubuntu3. I see from the changelog: "Version 304.131-0ubuntu5: * debian/templates/control.in: - Add transitional packages to deprecate the -updates flavour. Version 304.131-0ubuntu4: * debian/templates/dkms.conf.in, debian/dkms/patches/buildfix_kernel_4.6.patch: - Add support for Linux 4.6." Since Lubuntu 16.04 used Linux 4.4.xxx, I am guessing that whatever changed in 4.6 that made 304.131-0ubuntu4 necessary is still present in 4.8, and thus possibly that is why 304.131-0ubuntu3 did not work. Why is there no version higher than 304.131-0ubuntu3 in the official (?) nvidia-graphics-drivers-304 site above? Where can I find 304.131-0ubuntu5 (at least 304.131-0ubuntu4, but I assume what bug(s) 304.131-0ubuntu5 fixed might somehow be important...)? -- 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/1641233 Title: nvidia-304 (not installed): nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1641233/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: New => Confirmed -- 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/1641233 Title: nvidia-304 (not installed): nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1641233/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641233] [NEW] nvidia-304 (not installed): nvidia-304 kernel module failed to build
Public bug reported:
I had used nvidia-304 successfully in Lubuntu 16.04.
With Lubuntu 16.10, it would not load into the kernel.
I just recently downloaded a fixed 304.132 version, which loaded into the
kernel, and was
usable, but a program (Hugin) which had started up fine under nouveau (but
during the use of which nouveau had screen-crashed, forcing hard-shutdown),
failed to start, with the following terminal output:
"
The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 541 error_code 2 request_code 154 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
"
Since Hugin had worked fine in Lubuntu 16.04 with nvidia-304 - 304.131,
I found a version of that for Xenial Xerus (304.131-0ubuntu3) at
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304, and tried to
install that.
It failed to install, however...
"Building initial module for 4.8.0-27-generic
Error! Bad return status for module build on kernel: 4.8.0-27-generic (x86_64)
Consult /var/lib/dkms/nvidia-304/304.131/build/make.log for more information."
I will (try to) attach the log file for the install
("/var/lib/dkms/nvidia-304/304.131/build/make.log"), but here are the lines
containing the word "error":
"echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix
it."; \
...
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:52:11: error: too many
arguments to function ‘get_user_pages’
ret = get_user_pages(current, mm, (unsigned long)address,
^~
In file included from /var/lib/dkms/nvidia-304/304.131/build/nv-linux.h:82:0,
from /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:15:
./include/linux/mm.h:1315:6: note: declared here
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:65:13: error: implicit
declaration of function ‘page_cache_release’
[-Werror=implicit-function-declaration]
page_cache_release(user_pages[i]);
^~
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target
'/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o' failed
make[3]: *** [/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o] Error 1
Makefile:1489: recipe for target
'_module_/var/lib/dkms/nvidia-304/304.131/build' failed
make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.131/build] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
Makefile:255: recipe for target 'module' failed
make[1]: *** [module] Error 1
makefile:59: recipe for target 'module' failed
make: *** [module] Error 2
"
I am hoping that there is some simple way to get this older version to
load/work,
as I am running out of options for being able to run Hugin:
1: nouveau screen-crashes in Hugin (which starts up fine) when I try to open
the images from which to make the panorama
2: the fixed nvidia-304.132 loads in the kernal, but Hugin crashes upon
starting up
3: the older nvidia-304.131 fails to install
4: I would consider going back to 16.04 (which is in one of 5 partitions which
I reserve for different Lubuntu versions as they come along), but grub, in
installing 16.10, somehow made booting 16.04 impossible (some sort of Emergency
terminal starts up, and I don't know enough of what's happening to know what to
do... The partition is fine - I can traverse the directory tree and look at
files, etc. but I cannot boot it...)
If anyone knows what is going on when I attempt to install 304.131 here in
Lubuntu 16.10,
and can advise me what to do. I would be very grateful.
--
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20
21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc
Ubuntu 16.10
yakkety
scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
Lubuntu
nvidia-graphics-drivers-304 (304.131-0ubuntu3) xenial;
--
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: nvidia-304 304.131-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 4.8.0-27-generic
Date: Fri Nov 11 15:48:41 2016
DuplicateSignature:
[Ubuntu-x-swat] [Bug 1641215] [NEW] nvidia driver 304 fails to load libGLU, GLX errors
Public bug reported: resulting setup is useless for openGL and SDL rendering is very slow kernels 4.4.0-47 -45 xubuntu 16.04 64bit ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.132 Fri Sep 16 11:02:09 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 11 16:05:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.132, 4.4.0-45-generic, x86_64: installed nvidia-304, 304.132, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0370] InstallationDate: Installed on 2016-11-05 (6 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=9b509dd9-28f8-42d9-bd9f-c2fa7eb33811 ro vebose SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A8R-MVP dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/09/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8R-MVP:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Nov 10 16:07:53 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1641215 Title: nvidia driver 304 fails to load libGLU, GLX errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1641215/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641055] Re: startx, lightdm fail to start
After deleting the .Xauthority file, I can now successfully log into a Unity session. The problem seems to be gone (rebooting worked fine after this). Maybe somebody can figure out how I got into this situation, but otherwise the bug can be closed as far as I'm concerned. -- 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/1641055 Title: startx, lightdm fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641055] Re: startx, lightdm fail to start
If I *remove* xserver-xorg-video-intel, lightdm is able to show me the login screen. However, there is corruption on the screen and trying to log into a Unity or Gnome session just shows a blank screen and then puts me back into the login screen after 1 second. -- 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/1641055 Title: startx, lightdm fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1570653] Re: LG 31MU97-B Black 31" 4K Monitor not detected properly
following the instructions on http://penguindreams.org/blog/running-a-lg31mu97-on-linux-at-4096x2160 -at-60hz/ the monitor is now able to display at 4096x2160_60. my current kernel is - Linux music 4.4.0-45-lowlatency #66-Ubuntu SMP PREEMPT Wed Oct 19 14:57:51 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux and yes, I had to go through the tutorial to make it 4096x2160_60 as it was not detected after booting. what is the next appropriate step to have persist? please let me know what to further test. 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/1570653 Title: LG 31MU97-B Black 31" 4K Monitor not detected properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1570653/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1196239] Re: Add support for fake modes on laptop screens which only have one
I was just including my example as another plus point for fake modes ("scale"
in this case didn't mean "output scaling".
If we had the fake modes then output scaling wouldn't really be required in
this case, as we would have a set of mutually inclusive modes to chose from.
--
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 laptop screens which only have one
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1196239/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1575000] Re: font glyph corruption on dialog box
** No longer affects: xorg-server -- 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/1575000 Title: font glyph corruption on dialog box To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1575000/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1575000] Re: font glyph corruption on dialog box
tumbleweed.. tested or not, the bug should be closed with latest updates ** Changed in: xorg-server (Ubuntu Xenial) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1575000 Title: font glyph corruption on dialog box To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1575000/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13
This issue is *very* likely to have smth to do with the other issue mentioned in Description above, i was not seeing this for a long time already and it appeared again similarly to sticky arrow keys: Nov 11 10:26:19 yogi kernel: [37507.484136] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Nov 11 10:26:19 yogi kernel: [37507.484144] atkbd serio0: Use 'setkeycodes e03e ' to make it known. -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1238914] Re: Random stuck keys on Lenovo Yoga 13
The bug went away after some package update for several months (wow!) in 16.04 -- therefore I refused to run updates all this time to get a bit of "normal life" during typing ;) A few days ago I did an update and the damn bug returned... several years of suffering from this Bug. BTW, guys, what keyboard layout are you using when experiencing this bug? I'm experiencing it only when using Neo2 layout. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1238914 Title: Random stuck keys on Lenovo Yoga 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1238914/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13
trying to re-open ** Changed in: xorg (Ubuntu) Status: Expired => 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1585094] Re: Random stuck keys on Lenovo Yoga 13
not really expired. The bug went away after some package update for several months (wow!) in 16.04 -- therefore I refused to run updates all this time to get a bit of "normal life" during typing ;) A few days ago I did an update and the damn bug returned... several years of suffering from this Bug. BTW, guys, what keyboard layout are you using when experiencing this bug? I'm experiencing it only when using Neo2 layout. It is not possible for me to find out the package causing it because of "bulk" updating -- too many packages are on list and it is rather impossible to update/upgrade them one-by-one and then test for the bug -- 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/1585094 Title: Random stuck keys on Lenovo Yoga 13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1585094/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641055] [NEW] startx, lightdm fail to start
Public bug reported: After updating from 16.04 to 16.10, lightdm doesn't start. Adding 'nomodeset' for booting allows it to start, but apparently lacks all acceleration. Trying different kernels doesn't help, including the one from 16.04. Sorry for brevity, I'm writing this on my phone... ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.4-1ubuntu6 Uname: Linux 4.8.7-040807-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 BootLog: /dev/sda1: clean, 2557730/15417344 files, 54003285/61639424 blocks CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Nov 11 09:07:35 2016 DistUpgraded: 2016-11-10 20:42:28,744 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: acpi_call, 1.0, 3.2.0-21-generic, x86_64: built tp_smapi, 0.42, 4.4.0-47-generic, x86_64: installed tp_smapi, 0.42, 4.8.0-27-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-generic, x86_64: installed tp_smapi, 0.42, 4.8.7-040807-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2011-03-11 (2071 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MachineType: LENOVO 20BWS02D00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.7-040807-lowlatency root=UUID=45e540a8-fe2a-49e7-9c27-99725af4a6bd ro quiet splash i915.i915_enable_rc6=1 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to yakkety on 2016-11-10 (0 days ago) dmi.bios.date: 12/09/2014 dmi.bios.vendor: LENOVO dmi.bios.version: JBET39WW (1.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET39WW(1.04):bd12/09/2014:svnLENOVO:pn20BWS02D00:pvrThinkPadT450s:rvnLENOVO:rn20BWS02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BWS02D00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.71+git1611081830.670f1e~gd~y version.libgl1-mesa-dri: libgl1-mesa-dri 13.1~git1611101930.f500c3~gd~y version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 13.1~git1611101930.f500c3~gd~y version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Fri Nov 11 09:06:56 2016 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu6 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubuntu yakkety -- 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/1641055 Title: startx, lightdm fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1641055/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
