[Ubuntu-x-swat] [Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics
Still broken despite upgrading kernel to 4.15.0-46.49 grub to 2.02-2ubuntu8.12 mesa to 18.2.8-0ubuntu0~18.04.2 The recent mesa changelog gave hope:- "i965-revert-enabling-softpin.diff: Don't enable softpin, causes issues on 32bit installs. (LP: #1815172)" but no improvement noted and GPU still hanging at the login screen. Perhaps installing i386 was a mistake? -- 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/1767993 Title: Lubuntu: X11 freezing/low resolution on N3150 intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+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 1784488] Re: libwacom touch strip mappings are reversed for cintiq 21ux
you should file this upstream https://github.com/linuxwacom/libwacom/issues -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1784488 Title: libwacom touch strip mappings are reversed for cintiq 21ux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1784488/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Thanks Daniel and MarcAndre for chiming in here. Atfer thinking more about it I agree to Daniel that actually mesa should honor and stick with its affinity assignment. For documentation purpose: the solution proposed on the ML is at https://lists.freedesktop.org/archives/mesa-dev/2019-February/215926.html I also added a bug tracker to the fredesktop bug as task. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=109695 Importance: Unknown Status: Unknown -- 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
@Ubuntu-Desktop Team (now subscribed) - is there a chance we can revert [1] in mesa before it will be released with Disco for now. That would be needed until an accepted solution throughout the stack of libvirt/qemu/mesa is found? Otherwise using GL backed qemu graphics will fail as outlined in the bug. Once such a cross-package solution to the problem is found we can (if needed at all) SRU back the set of changes to all components required. [1]: https://github.com/mesa3d/mesa/commit/d877451b48a59ab0f9a4210fc736f51da5851c9a -- 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Adding Timo who maintainers mesa. -- 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
Launchpad has imported 9 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=109695.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2019-02-20T20:12:32+00:00 Ahzo wrote:
Since upgrading Mesa from 18.2 to 18.3, launching a QEMU virtual machine
with Spice OpenGL enabled (for virgl), causes QEMU to crash with SIGSYS
inside the radeonsi driver. The reason for this is that the QEMU sandbox
option 'resourcecontrol=deny' disables the sched_setaffinity syscall
called in pthread_setaffinity_np, which is now used by the radeonsi
driver.
A simple way to reproduce this problem is:
$ gdb --batch --ex run --ex bt --args qemu-system-x86_64 -spice gl=on -sandbox
on,resourcecontrol=deny
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x745aa700 (LWP 23432)]
[New Thread 0x708e5700 (LWP 23433)]
[New Thread 0x7fffe3fff700 (LWP 23434)]
[New Thread 0x7fffe37fe700 (LWP 23435)]
Thread 4 "qemu-system-x86" received signal SIGSYS, Bad system call.
[Switching to Thread 0x7fffe3fff700 (LWP 23434)]
0x768cc9cf in __pthread_setaffinity_new (th=,
cpusetsize=cpusetsize@entry=128, cpuset=cpuset@entry=0x7fffe3ffe680) at
../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
34 ../sysdeps/unix/sysv/linux/pthread_setaffinity.c: No such file or
directory.
#0 0x768cc9cf in __pthread_setaffinity_new (th=,
cpusetsize=cpusetsize@entry=128, cpuset=cpuset@entry=0x7fffe3ffe680) at
../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
#1 0x712ba2b3 in util_queue_thread_func
(input=input@entry=0x5640b1f0) at ../src/util/u_queue.c:252
#2 0x712b9c17 in impl_thrd_routine (p=) at
../src/../include/c11/threads_posix.h:87
#3 0x768c1fa3 in start_thread (arg=) at
pthread_create.c:486
#4 0x767f280f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
The problematic code at src/util/u_queue.c:252 was added in the following
commit:
commit d877451b48a59ab0f9a4210fc736f51da5851c9a
Author: Marek Olšák
Date: Mon Oct 1 15:51:06 2018 -0400
util/u_queue: add UTIL_QUEUE_INIT_SET_FULL_THREAD_AFFINITY
Initial version discussed with Rob Clark under a different patch name.
This approach leaves his driver unaffected.
Since setting the thread affinity seems non-essential here, the failing syscall
should be handled gracefully, for example by setting a signal handler to ignore
the SIGSYS signal.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/12
On 2019-02-20T21:30:42+00:00 Marek Olšák wrote:
Mesa needs a way to query that it can't set thread affinity.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/13
On 2019-02-21T17:15:56+00:00 Ahzo wrote:
To check for the availability of the syscall, one can try it in a child
process and see if the child is terminated by a signal, e.g. like this:
#include
#include
#include
#include
#include
static bool
can_set_affinity()
{
pid_t pid = fork();
int status = 0;
if (!pid) {
/* Disable coredumps, because a SIGSYS crash is expected. */
struct rlimit limit = { 0 };
limit.rlim_cur = 1;
limit.rlim_max = 1;
setrlimit(RLIMIT_CORE, &limit);
/* Test the syscall in the child process. */
syscall(SYS_sched_setaffinity, 0, 0, 0);
_exit(0);
} else if (pid < 0) {
return false;
}
if (waitpid(pid, &status, 0) < 0) {
return false;
}
if (WIFSIGNALED(status)) {
/* The child process was terminated by a signal,
* thus the syscall cannot be used.
*/
return false;
}
return true;
}
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/14
On 2019-02-27T14:42:21+00:00 Dan-freedesktop wrote:
(In reply to Ahzo from comment #2)
> To check for the availability of the syscall, one can try it in a child
> process and see if the child is terminated by a signal, e.g. like this:
Afraid not, QEMU's seccomp filter blocks use of fork() too :-)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815889/comments/27
On 2019-02-27T14:45:24+00:00 Dan-freedesktop wrote:
(In reply to Ahzo from comment #0)
> The problematic code at src/util/u_queue.c:252 was added in the following
> commit:
> commit d877451b48a59ab0f9a4210fc736f51da5851c9a
> Author: Marek Olšák
> Date: Mon Oct 1 15:51:06 2018 -0400
>
>
[Ubuntu-x-swat] [Bug 1818100] [NEW] sistema roto
Public bug reported: cuando quiero actualizar, me dice que el sistema esta roto. cada vez que abro office, primero tiene que restaurar. esto es nuevo, hasta hace 2 dias no hacia nada de esto. gracias ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 28 12:53:00 2019 DistUpgraded: 2018-10-26 19:46:47,556 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: ath9k-msi, 1.1: added radeon-si, 1a, 4.4.0-38-generic, x86_64: built GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0789] InstallationDate: Installed on 2017-07-14 (594 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 14-3467 ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=4da0aff2-5e0c-4124-950f-922794c92879 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2018-10-26 (124 days ago) dmi.bios.date: 04/07/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.07.00 dmi.board.name: 0PCXP1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.07.00:bd04/07/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0PCXP1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 14-3467 dmi.product.sku: 0789 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 xserver.bootTime: Sun Mar 25 21:08:16 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1319 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1818100 Title: sistema roto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1818100/+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 1818101] Re: nvidia dkms modules fail to build with linux 4.4.0-143.169
** Also affects: nvidia-graphics-drivers-304 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-304 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-340 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-384 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-304 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-340 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Trusty) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-384 (Ubuntu Xenial) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1818101 Title: nvidia dkms modules fail to build with linux 4.4.0-143.169 To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1818101/+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 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)
I tried the v5.0-rc7 and rc8 kernels. the problem is not solved ** Tags added: kernel-bug-exists-upstream -- 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/1813701 Title: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813701/+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
I also have just experienced this bug on: Lenovo Ideapad Yoga 13 Ubuntu 18.04.02 Syslog looks the same: Feb 28 21:20:21 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 214.802472] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:21 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 214.802479] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.961924] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.961933] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.968062] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:22 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 215.968068] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.052276] atkbd serio0: Unknown key pressed (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.052282] atkbd serio0: Use 'setkeycodes e03e ' to make it known. Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.057285] atkbd serio0: Unknown key released (translated set 2, code 0xbe on isa0060/serio0). Feb 28 21:20:23 masha-Lenovo-IdeaPad-Yoga-13 kernel: [ 217.057291] 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 1308105] Re: Xfce resets TV mode to NULL when power cycled
Is there any hope of this being backported to 16.04? This is a big problem for our customers running our digital signage players running 16.04. This is a pretty critical bug to leave unaddressed in an LTS that still has two years of support left. -- 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/1308105 Title: Xfce resets TV mode to NULL when power cycled To manage notifications about this bug go to: https://bugs.launchpad.net/mythbuntu/+bug/1308105/+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 1818100] Re: sistema roto
Can you please provide a screenshot or photo of the problem? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1818100 Title: sistema roto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1818100/+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 1818101] Re: nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’]
*** This bug is a duplicate of bug 1573508 *** https://bugs.launchpad.net/bugs/1573508 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1573508, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - nvidia dkms modules fail to build with linux 4.4.0-143.169 + nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] ** This bug has been marked a duplicate of bug 1573508 nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’] -- 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/1818101 Title: nvidia dkms modules fail to build with linux 4.4.0-143.169 [error: too many arguments to function ‘get_user_pages’] To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1818101/+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
