[Bug 146411] Re: gnect crashed with SIGSEGV
A user of another distro also hit this with gnometris. We debugged the
problem, here is the result.
static void games_sound_init (void)
{
GError *err = NULL;
g_assert (g_thread_supported ());
pipeline = gst_element_factory_make ("playbin", "playbin");
threads = g_thread_pool_new ((GFunc) games_sound_thread_run, NULL, 10,
FALSE, &err);
sound_init = TRUE;
}
The code doesn't check the return value of gst_element_factory_make(),
and that's the real bug. It returns NULL if there are no sound output
plugins installed.
I.e., in order for sound in GNOME games to be functional, the users must
install at least base and good plugins, and also ogg and vorbis plugins.
Note: I am not a user of Ubuntu, and will not help with this bug
further.
--
gnect crashed with SIGSEGV
https://bugs.launchpad.net/bugs/146411
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589099] [NEW] does not work on amd64 without -no-kvm
Public bug reported: Binary package hint: qemu-kvm Ubuntu release: Lucid Lynx architecture: amd64 failing package version: 0.12.3+noroms-0ubuntu9 working package version: 0.11.0-0ubuntu6.3 (from karmic-updates) When I run "qemu" with any valid arguments, I expect it to work. E.g., when no arguments are given, it should attempt booting from all possible devices and then fail, with non-black screen. However, the version in Lucid just shows black screen, unless the -no-kvm argument is given. ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- does not work on amd64 without -no-kvm https://bugs.launchpad.net/bugs/589099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589099] Re: does not work on amd64 without -no-kvm
I think I have already provided enough words: the SDL window is entirely black for all my attempts to run new qemu-kvm, unless I pass -no-kvm. I expect it to contain something visible, e.g. the following lines when there is nothing to boot from: Booting from Hard Disk... Boot failed: could not read the boot disk Booting from Floppy... Boot failed: could not read the boot disk Booting from CD-Rom... Boot failed: Could not read from CDROM (code 0003) No bootable device. (and they do appear when starting with -no-kvm, or with old version of qemu-kvm) Does qemu work for you on amd64 (as I suspect that the bug is specific to that architecture)? As for the 'apport-collect 589099' command, I will run this tomorrow, because now I am at home (with a different distro where qemu-kvm works). Should I run it with the failing version installed, with the working version, or it doesn't matter? -- does not work on amd64 without -no-kvm https://bugs.launchpad.net/bugs/589099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 589099] Re: does not work on amd64 without -no-kvm
apport-collect 589099 says that the additional information could not be collected. -- does not work on amd64 without -no-kvm https://bugs.launchpad.net/bugs/589099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1792771] [NEW] Force-renewal of a certificate fails
Public bug reported: Running "dehydrated -c -x" on Ubuntu 18.04 fails with "invalid challenge" error, as it tries to access the challenge file on the server with the POST request, instead of sending this POST to Let's Encrypt servers. This is the same as https://github.com/lukas2511/dehydrated/issues/515 , and that github issue contains a fix (also attached). Could you please update the package in Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dehydrated 0.6.1-2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 Date: Sun Sep 16 07:10:08 2018 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 TERM=xterm SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, no user) SourcePackage: dehydrated UpgradeStatus: Upgraded to bionic on 2018-04-29 (139 days ago) modified.conffile..etc.dehydrated.config: [modified] mtime.conffile..etc.dehydrated.config: 2018-09-15T15:47:27.197404 ** Affects: dehydrated (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Patch added: "Upstream fix" https://bugs.launchpad.net/bugs/1792771/+attachment/5189383/+files/ff18d39aa8175b9d9e7b6db53a7e1aed6051984a.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1792771 Title: Force-renewal of a certificate fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dehydrated/+bug/1792771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
David, how long did you have to wait? For me, it's still not started, even though the uptime is 7 minutes. And I don't see how it is supposed to be started, given that nothing pulls it in (i.e. it is not WantedBy anything). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
I will test it later today, but - why are you using default.target instead of multi-user.target? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1448924] Re: watchdogd doesn't start on boot
The proposed modification of the service file works. It works both with default.target and with multi-user.target. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1448924 Title: watchdogd doesn't start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/watchdog/+bug/1448924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
As far as I remember, the switch to a new firmware uploading mechanism was due to the fact that newer firmware disabled TSX instructions completely on Haswell, thus causing segfaults of applications linked against libpthread. I.e. patching firmware later than "very early on boot" was too late at least for Haswell. This consideration does not apply directly to Trusty, as Trusty's glibc never used hardware lock elision. However, this might be the case for containers and chroots (including non-Ubuntu ones) running on Trusty. As far as I understand, Ubuntu glibc was later rebuilt to never use hardware lock elision, because it exposed too many double-unlocking bugs in third-party software. My conclusion is that it is 100% unsafe to update firmware blobs in Trusty if there is a possibility that any non-Ubuntu container gets started before the firmware is uploaded to the CPU. If such situation is impossible, then please treat this comment as a no-op. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1700373] Re: Please update microcode to version 20170511 on all supported platforms
Uqbar: if your servers are running Trusty, then thanks for the confirmation that too-late update is not an issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1700373 Title: Please update microcode to version 20170511 on all supported platforms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1700373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758619] [NEW] lxc-update-config incorrectly converts network settings
Public bug reported: Before the update, on LXC 2.0.8, I had: lxc.network.type = veth lxc.network.flags = up lxc.network.link = lxcbr0 lxc.network.ipv4 = 10.0.3.205/24 lxc.network.ipv4.gateway = 10.0.3.1 lxc.network.hwaddr = 00:16:3e:ae:79:d7 After the update to LXC 3.0.0beta3, I have: lxc.net.0.type = veth lxc.net.0.flags = up lxc.net.0.link = lxcbr0 lxc.net.0.ipv4 = 10.0.3.205/24 lxc.net.0.ipv4.gateway = 10.0.3.1 lxc.net.0.hwaddr = 00:16:3e:ae:79:d7 The conversion is wrong. lxc.network.ipv4 (which was the correct spelling, according to the man page in the old package) should have been converted to lxc.net.0.ipv4.address, not to lxc.net.0.ipv4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc-utils 3.0.0~beta3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 25 14:24:16 2018 InstallationDate: Installed on 2018-01-25 (58 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic ** Attachment removed: "lxcsyslog.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089681/+files/lxcsyslog.txt ** Attachment removed: "KernLog.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089675/+files/KernLog.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089674/+files/JournalErrors.txt ** Attachment removed: "dnsmasq.conf.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+attachment/5089678/+files/dnsmasq.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758619 Title: lxc-update-config incorrectly converts network settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1758619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759247] Re: lxc-copy forgets to change /etc/hostname and /etc/hosts
Unfortunately I had to delete all logs from this bug report because they contained possibly-confidential information. If you need, I can try to reproduce this on a non-company machine with nothing confidential, and reattach the logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759247 Title: lxc-copy forgets to change /etc/hostname and /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1759247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759247] [NEW] lxc-copy forgets to change /etc/hostname and /etc/hosts
Public bug reported: LXC 2.x behaved like this when cloning containers: it wrote the new hostname into /etc/hostname of the new container, and changed /etc/hosts accordingly. LXC 3.0.0.beta3 no longer does it. root@zh1cn:/var/lib/lxc# lxc-create -t download -n ubuntu-1604-new -- -d ubuntu -a amd64 -r xenial Setting up the GPG keyring Downloading the image index Downloading the rootfs Downloading the metadata The image cache is now ready Unpacking the rootfs --- You just created an Ubuntu container (release=xenial, arch=amd64, variant=default) To enable sshd, run: apt-get install openssh-server For security reason, container images ship without user accounts and without a root password. Use lxc-attach or chroot directly into the rootfs to set a root password or create user accounts. root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new/config # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: -d ubuntu -a amd64 -r xenial # Template script checksum (SHA-1): 5f6cea9c51537459a7ab5f81e2c1eac6a94b5e08 # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.arch = x86_64 # Container specific configuration lxc.rootfs.path = dir:/var/lib/lxc/ubuntu-1604-new/rootfs lxc.uts.name = ubuntu-1604-new # Network configuration lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:65:85:6b root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new/rootfs/etc/hostname ubuntu-1604-new root@zh1cn:/var/lib/lxc# lxc-copy -n ubuntu-1604-new -N ubuntu-1604-new1 root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new1/config # Template used to create this container: /usr/share/lxc/templates/lxc-download # Parameters passed to the template: -d ubuntu -a amd64 -r xenial # Template script checksum (SHA-1): 5f6cea9c51537459a7ab5f81e2c1eac6a94b5e08 # For additional config options, please look at lxc.container.conf(5) # Uncomment the following line to support nesting containers: #lxc.include = /usr/share/lxc/config/nesting.conf # (Be aware this has security implications) # Distribution configuration lxc.include = /usr/share/lxc/config/common.conf lxc.arch = x86_64 # Container specific configuration # Network configuration lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:ec:9a:54 lxc.rootfs.path = dir:/var/lib/lxc/ubuntu-1604-new1/rootfs lxc.uts.name = ubuntu-1604-new1 root@zh1cn:/var/lib/lxc# cat ubuntu-1604-new1/rootfs/etc/hostname ubuntu-1604-new I would expect ubuntu-1604-new1 here, or maybe no such file at all (so that lxc.uts.name applies from the config). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc 3.0.0~beta3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.9-0ubuntu1 Architecture: amd64 Date: Tue Mar 27 19:21:21 2018 InstallationDate: Installed on 2018-01-25 (61 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180120) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 TERM=xterm SHELL=/bin/bash PATH=(custom, no user) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.net.0.type = veth lxc.net.0.link = lxcbr0 lxc.net.0.flags = up lxc.net.0.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1759247/+attachment/5092115/+files/JournalErrors.txt ** Attachment removed: "KernLog.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1759247/+attachment/5092116/+files/KernLog.txt ** Attachment removed: "dnsmasq.conf.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1759247/+attachment/5092119/+files/dnsmasq.conf.txt ** Attachment removed: "lxcsyslog.txt" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1759247/+attachment/5092122/+files/lxcsyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759247 Title: lxc-copy forgets to change /etc/hostname and /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1759247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839527] [NEW] mysqld eats more than 16 GB of memory on startup
Public bug reported: (this bug has been reproduced in an LXC container running on Arch Linux, that's why the strange kernel version) On Ubuntu 18.04, systemd runs mysqld in two steps. First: ExecStartPre=/usr/share/mysql/mysql-systemd-start pre In this script, one of the steps is: mysqld --verbose --help --innodb- read-only Then: ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysqld/mysqld.pid It's the first mysqld (with --help) which is a problem. The problem happens because, due to PermissionsStartOnly=true, systemd runs ExecStartPre commands with insane limits. In particular: Aug 08 18:19:23 mysql57 bash[13131]: core file size (blocks, -c) unlimited Aug 08 18:19:23 mysql57 bash[13131]: data seg size (kbytes, -d) unlimited Aug 08 18:19:23 mysql57 bash[13131]: scheduling priority (-e) 0 Aug 08 18:19:23 mysql57 bash[13131]: file size (blocks, -f) unlimited Aug 08 18:19:23 mysql57 bash[13131]: pending signals (-i) 63701 Aug 08 18:19:23 mysql57 bash[13131]: max locked memory (kbytes, -l) 16384 Aug 08 18:19:23 mysql57 bash[13131]: max memory size (kbytes, -m) unlimited Aug 08 18:19:23 mysql57 bash[13131]: open files (-n) 1073741816 <--- see this? Aug 08 18:19:23 mysql57 bash[13131]: pipe size(512 bytes, -p) 8 Aug 08 18:19:23 mysql57 bash[13131]: POSIX message queues (bytes, -q) 819200 Aug 08 18:19:23 mysql57 bash[13131]: real-time priority (-r) 0 Aug 08 18:19:23 mysql57 bash[13131]: stack size (kbytes, -s) 8192 Aug 08 18:19:23 mysql57 bash[13131]: cpu time (seconds, -t) unlimited Aug 08 18:19:23 mysql57 bash[13131]: max user processes (-u) 63701 Aug 08 18:19:23 mysql57 bash[13131]: virtual memory (kbytes, -v) unlimited Aug 08 18:19:23 mysql57 bash[13131]: file locks (-x) unlimited When running with such a high "ulimit -n" (again, this is something which systemd does by default for ExecStartPre), "mysqld --help" consumes unimaginable amounts of memory and even causes swapping and page allocation failures on my PC with 16 GB of RAM. Workaround in /etc/systemd/system/mysql.service.d/override.conf: [Service] ExecStartPre= ExecStartPre=/bin/sh -c 'ulimit -n 1024 ; /usr/share/mysql/mysql-systemd-start pre' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mysql-server-5.7 5.7.27-0ubuntu0.18.04.1 Uname: Linux 5.2.5-arch1-1-ARCH x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Aug 8 18:29:38 2019 Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: False ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: mysql-5.7 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: [modified] mtime.conffile..etc.mysql.mysql.conf.d.mysqld.cnf: 2019-08-08T17:51:27.927907 ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839527 Title: mysqld eats more than 16 GB of memory on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1839527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839527] Re: mysqld eats more than 16 GB of memory on startup
Well, it is not just "Arch Linux default". What happens here is that recent systemd upstream (and therefore Arch Linux, too) sets fs.nr_open=1073741816 by default. The commit that introduces this is https://github.com/systemd/systemd/commit/a8b627aaed409a15260c25988970c795bf963812. LXC just inherits it. See also the discussion here: https://github.com/systemd/systemd/issues/11510 ** Bug watch added: github.com/systemd/systemd/issues #11510 https://github.com/systemd/systemd/issues/11510 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839527 Title: mysqld eats more than 16 GB of memory on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1839527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1836772] [NEW] Xorg crash on 3d-enabled virgl (Haswell host)
Public bug reported:
I am running a KVM virtual machine with 3D acceleration (virgl). The
host is Arch Linux, the guest is Ubuntu 18.04. However, recently, the
session started crashing just after the login. In xorg logs, I see this:
[15.338] (WW) modeset(0): Page flip failed: Invalid argument
[15.338] (EE) modeset(0): present flip failed
[15.397] (WW) modeset(0): Page flip failed: Invalid argument
[15.397] (EE) modeset(0): present flip failed
[15.418] (WW) modeset(0): Page flip failed: Invalid argument
[15.419] (EE) modeset(0): present flip failed
[15.440] (WW) modeset(0): Page flip failed: Invalid argument
[15.440] (EE) modeset(0): present flip failed
[15.460] (WW) modeset(0): Page flip failed: Invalid argument
[15.460] (EE) modeset(0): present flip failed
[15.975] (WW) modeset(0): Page flip failed: Invalid argument
[15.976] (EE) modeset(0): present flip failed
[16.039] (WW) modeset(0): Page flip failed: Invalid argument
[16.040] (EE) modeset(0): present flip failed
[16.064] (WW) modeset(0): Page flip failed: Invalid argument
[16.064] (EE) modeset(0): present flip failed
[16.096] Failed to compile FS: 0:11(2): error: `color0' undeclared
0:11(2): error: value of type vec4 cannot be assigned to variable of type error
0:12(2): error: `color1' undeclared
0:12(2): error: value of type vec4 cannot be assigned to variable of type error
[16.096] Program source:
#ifdef GL_ES
precision mediump float;
#endif
#define ATLAS_DIM_INV 0.0009765625
varying vec2 glyph_pos;
uniform vec4 fg;
uniform sampler2D atlas;
void main() {
vec4 mask = texture2D(atlas, glyph_pos);
vec4 source = fg;
color0 = source * mask;
color1 = source.a * mask;
}
[16.096] (EE)
Fatal server error:
[16.096] (EE) GLSL compile failure
Downgrading libgl1-mesa-dri from 19.0.2-1ubuntu1.1~18.04.1 to
18.0.0~rc5-1ubuntu1 helps.
Arch on Arch does not fail this way. Mesa version is 19.1.1-1 there.
On the host, the GPU is Intel Haswell:
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200
v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412]
(rev 06)
The CPU is Intel(R) Core(TM) i7-4770S CPU.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jul 16 20:52:03 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100]
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no username)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic
root=UUID=4fa5252e-51d1-476f-8903-e4d8b7266af0 ro splash quiet vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.12.0-20181126_142135-anatol
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-q35-4.0
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.0:cvnQEMU:ct1:cvrpc-q35-4.0:
dmi.product.name: Standard PC (Q35 + ICH9, 2009)
dmi.product.version: pc-q35-4.0
dmi.sys.vendor: QEMU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic crash ubuntu
** Attachment added: "Xorg.0.log.old"
https://bugs.launchpad.net/bugs/1836772/+attachment/5277429/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1836772
Title:
Xorg crash on 3d-enabled virgl (Haswell host)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1836772/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
[Bug 1836772] Re: Xorg crash on 3d-enabled virgl (Haswell host)
It works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836772 Title: Xorg crash on 3d-enabled virgl (Haswell host) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837081] [NEW] xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
Public bug reported: I have recently files this bug: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836772 and decided to test if it affects Ubuntu 19.04. Just to remind you, this was about xorg crashing in a virtual machine that uses virtio VGA with virgl enabled. The host is Arch Linux, the CPU is Intel Core i7 4770S (Haswell). Well, xorg crashes on 19.04, too, but with a different backtrace, and adding ppa:ubuntu-x-swat/updates does not help. So I believe this is a separate bug. Disabling virgl on qemu command line helps, but I would rather have it enabled. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Thu Jul 18 21:09:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=UUID=0617cd90-66d8-4848-8ef8-fdf7fc919a93 ro splash quiet vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-20181126_142135-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-20181126_142135-anatol:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1837081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
https://bugzilla.redhat.com/show_bug.cgi?id=1652274 is a duplicate ** Bug watch added: Red Hat Bugzilla #1652274 https://bugzilla.redhat.com/show_bug.cgi?id=1652274 ** Also affects: xorg (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1652274 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1837081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
I have tried to follow the instructions, but not sure if I did it correctly. Does this link help? https://errors.ubuntu.com/oops/d2e06dde- a9d9-11e9-a2e9-fa163e6cac46 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837081] Re: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc
Ping - did I follow the instructions correctly? ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837081 Title: xorg crashes on virgl with 3d enabled (Haswell on the host), ms_dri2_schedule_wait_msc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1837081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
No news, the bug is still reproducible, and it is not clear what information is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
No news, the bug is still reproducible, and it is not clear what information is needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740027] [NEW] Wrong license information for NVidia proprietary driver
Public bug reported: When I attempted to download NVidia drivers (specifically, version 384.98) from the official website for a non-Ubuntu system, I got this license: http://www.nvidia.com/content/DriverDownload- March2009/licence.php?lang=us&type=GeForce Note specifically: """ No Datacenter Deployment. The SOFTWARE is not licensed for datacenter deployment, except that blockchain processing in a datacenter is permitted. """ This clause is not present in a license for Tesla GPUs, but I don't have a Tesla. And my application is not related to blockchain, either. And then I remembered that I have an Ubuntu server in Hetzner with a GeForce GTX 1080 GPU. The copyright file in the package does not have this "No Datacenter Deployment" clause. Is it because Ubuntu has somehow negotiated the exception, because the file in the package is incomplete, or because there was no such restriction yet in version 384.90? But the same license shows up on NVidia site even if I attempt to manually download the older version - did they change it retroactively? In other words - should I shut down the server because my use violates the NVidia license? If possible, please package separately the last version of the NVidia driver that does not have any restrictions on its use in datacenters, because many of them still only provide (now-illegal) GeForce GPUs. # apt-cache policy nvidia-384 nvidia-384: Installed: 384.90-0ubuntu0.16.04.2 Candidate: 384.90-0ubuntu0.16.04.2 Version table: *** 384.90-0ubuntu0.16.04.2 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 384.90-0ubuntu0.16.04.1 500 500 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-384 384.90-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Mon Dec 25 14:28:11 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-384 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-384 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1740027/+attachment/5026960/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740027 Title: Wrong license information for NVidia proprietary driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1740027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299499]
*** Bug 77391 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299499 Title: kwin crashes on desktop startup with wobbly windows enabled To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1299499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1271358] Re: Update to 3.18 (remove controls needed for Unity and other desktops)
Note that Vino 3.8.1 bundles a very old libvncserver, with significant image quality problems. One example is attached to https://github.com/novnc/noVNC/issues/737 I do not object to forking 3.8.1, as long as the fork is updated to use the latest libvncserver. ** Bug watch added: github.com/novnc/noVNC/issues #737 https://github.com/novnc/noVNC/issues/737 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271358 Title: Update to 3.18 (remove controls needed for Unity and other desktops) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/1271358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605953] Re: skylake Modesetting Driver on X failure
Please describe what desktop environment and window manager you use, and whether compositing is enabled in the window manager settings. I am asking because the same bug exists on Haswell in Arch Linux with Marco window manager (in MATE), and is fixable by installing and running compiz. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1605953 Title: skylake Modesetting Driver on X failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1409100]
*** This bug has been marked as a duplicate of bug 64017 *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1409100 Title: Simultaneous audio-out has a slight delay [per-card interface]. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-lowlatency/+bug/1409100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514690] Re: rebooting container with systemd >= 226 fails to create /lxc/adt-xenial/init.scope control group
This bug still affects lxcfs 0.11-0ubuntu3~ubuntu14.04.1, which is available in trusty-backports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514690 Title: rebooting container with systemd >= 226 fails to create /lxc/adt- xenial/init.scope control group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxcfs/+bug/1514690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585539] [NEW] x11vnc crashes on Skylake CPUs when display resolution is changed
Public bug reported: When I change the display resolution, x11vnc crashes. This crash is reproducible only on Skylake CPUs. The crash has been traced to a double-unlock of the X lock (non-TSX implementation of mutexes in glibc ignores this bug, while the TSX one crashes). The bug is already fixed upstream, please backport this patch to Ubuntu package: https://github.com/LibVNC/x11vnc/commit/011177796d2ce26ad3656d3c07031b81f43db796 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: x11vnc 0.9.13-1.2build1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Wed May 25 10:52:53 2016 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: x11vnc UpgradeStatus: Upgraded to xenial on 2016-04-20 (34 days ago) ** Affects: x11vnc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug patch xenial ** Patch added: "Patch that fixes the bug" https://bugs.launchpad.net/bugs/1585539/+attachment/4669991/+files/20_fix-double-unlock.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585539 Title: x11vnc crashes on Skylake CPUs when display resolution is changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1585539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585539] Re: x11vnc crashes on Skylake CPUs when display resolution is changed
Note: the patch by itself is not sufficient - it has some dependencies that I have not tracked down yet. Merely applying this patch yields: *** stack smashing detected ***: x11vnc terminated ** Patch removed: "Patch that fixes the bug" https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1585539/+attachment/4669991/+files/20_fix-double-unlock.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585539 Title: x11vnc crashes on Skylake CPUs when display resolution is changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1585539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585539] Re: x11vnc crashes on Skylake CPUs when display resolution is changed
It's not "dependencies". Stack smashing is detected even if x11vnc is rebuilt without changes! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585539 Title: x11vnc crashes on Skylake CPUs when display resolution is changed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1585539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588508] [NEW] nslcd does not survive "service nslcd restart"
Public bug reported: On fast machines, if I change the configuration of nslcd and restart it via "service nslcd restart", the result is: * LDAP name resolution does not work * nslcd is running but the init script thinks that it isn't * In the Journal, there are such lines: Jun 02 18:53:54 munin-de systemd[1]: Stopping LSB: LDAP connection daemon... Jun 02 18:53:54 munin-de nslcd[2354]: * Stopping LDAP connection daemon nslcd Jun 02 18:53:54 munin-de nslcd[2354]:...done. Jun 02 18:53:54 munin-de systemd[1]: Stopped LSB: LDAP connection daemon. Jun 02 18:53:54 munin-de systemd[1]: Starting LSB: LDAP connection daemon... Jun 02 18:53:54 munin-de nslcd[613]: caught signal SIGTERM (15), shutting down Jun 02 18:53:54 munin-de nslcd[2382]: * Starting LDAP connection daemon nslcd Jun 02 18:53:54 munin-de nslcd[2398]: version 0.9.6 starting Jun 02 18:53:54 munin-de nslcd[2398]: accepting connections Jun 02 18:53:54 munin-de nslcd[2382]:...done. Jun 02 18:53:54 munin-de systemd[1]: Started LSB: LDAP connection daemon. Jun 02 18:53:54 munin-de nslcd[613]: version 0.9.6 bailing out There is a Debian bug with exactly the same manifestation, maybe the fix needs to be backported to Ubuntu? https://bugs.debian.org/814881 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nslcd 0.9.6-3 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: overlayfs xt_multiport ebtable_broute ebtable_nat ebt_ip6 ebtable_filter ebtables pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv xt_nat xt_comment xt_conntrack xt_addrtype aufs veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm eeepc_wmi asus_wmi sparse_keymap shpchp lpc_ich crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel wmi aes_x86_64 lrw serio_raw gf128mul glue_helper video mac_hid ablk_helper cryptd lp parport btrfs libcrc32c raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 r8169 raid0 ahci libahci mii multipath linear ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Jun 2 18:57:56 2016 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nss-pam-ldapd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nss-pam-ldapd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588508 Title: nslcd does not survive "service nslcd restart" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1588508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588508] Re: nslcd does not survive "service nslcd restart"
Applying this patch (same as used by Debian) to the init script helps: https://arthurdejong.org/viewvc/nss-pam-ldapd/debian/nss-pam- ldapd/trunk/debian/nslcd.init?view=patch&r1=2136&r2=2148&sortby=file ** Tags added: patch-accepted-debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588508 Title: nslcd does not survive "service nslcd restart" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1588508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568799] [NEW] httping: built without SSL support
Public bug reported:
Httping mentions SSL-related options in its manpage and has libssl-dev
as a build-dependency, but the SSL support is not actually there.
ubuntu $ lsb_release -rd
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
ubuntu $ apt-cache policy httping
httping:
Installed: 2.4-1
Candidate: 2.4-1
Version table:
*** 2.4-1 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
100 /var/lib/dpkg/status
ubuntu $ httping --version
HTTPing v2.4, (C) 2003-2013 folk...@vanheusden.com
ubuntu $ ldd /usr/bin/httping
linux-vdso.so.1 => (0x7ffd063d7000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fc57b2f)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fc57af26000)
/lib64/ld-linux-x86-64.so.2 (0x7fc57b601000)
ubuntu $ httping -c 1 -S -M https://launchpad.net/
Auto enabling SSL due to https-URL[
Segmentation fault (core dumped)
For comparison, here is what I get on an Arch Linux system:
arch $ httping --version
HTTPing v2.4, (C) 2003-2013 folk...@vanheusden.com
* SSL support included (-l)
* ncurses interface with FFT included (-K)
arch $ ldd /usr/bin/httping
linux-vdso.so.1 (0x7ffc18785000)
libm.so.6 => /usr/lib/libm.so.6 (0x7feff1a74000)
libssl.so.1.0.0 => /usr/lib/libssl.so.1.0.0 (0x7feff1803000)
libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x7feff138c000)
libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x7feff111f000)
libfftw3.so.3 => /usr/lib/libfftw3.so.3 (0x7feff0d1e000)
libc.so.6 => /usr/lib/libc.so.6 (0x7feff097d000)
/lib64/ld-linux-x86-64.so.2 (0x7feff1d79000)
libdl.so.2 => /usr/lib/libdl.so.2 (0x7feff0779000)
arch $ httping -c 1 -S -M https://launchpad.net/
Auto enabling SSL due to https-URL[
{ "status" : "1", "seq" : "1", "start_ts" : "1460371981,551323", "resolve_ms" :
"1,090491e+02", "connect_ms" : "3,707514e+02", "request_ms" : "4,601479e-02",
"total_ms" : "6,026330e+02", "http_code" : "200", "msg" : "200 OK",
"header_size" : "576", "data_size" : "0", "bps" : "0,00", "host" :
"91.189.89.222", "ssl_fingerprint" :
"6b:2d:72:36:55:ea:db:7b:37:57:72:2d:91:a7:74:5d", "time_offset" :
"-18340092,664480", "tfo_success" : "false", "ssl_ms" : "2,495561e-01",
"tfo_succes" : "false", "ssl_ms" : "2,495561e-01", "write" : "1,225369e+02",
"close" : "5,960464e-03", "cookies" : "0", "to" : "-1,834009e+07",
"tcp_rtt_stats" : "1,216250e+02", "re_tx" : "0", "pmtu" : "1500", "tos" : "00" }
]
** Affects: httping (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568799
Title:
httping: built without SSL support
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httping/+bug/1568799/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568799] Re: httping: built without SSL support
Fixed this bug and other misdetections locally by the attached patch. ** Patch added: "Fixed the configure script" https://bugs.launchpad.net/ubuntu/+source/httping/+bug/1568799/+attachment/4632543/+files/bug1568799.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568799 Title: httping: built without SSL support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/httping/+bug/1568799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 638749] [NEW] enters infinite loop on entering certain date formats
Public bug reported: Binary package hint: gedit To reproduce: Start gedit in the ru_RU.utf8 locale (this is important! in this locale %p yields an empty string, in the C or en_US.utf8 locale it doesn't and thus the bug is not reproducible). Choose Правка > Вставить дату и время... (Edit > Insert Date and Time...) from the menu. Choose the Использовать другой формат (Use custom format) option. Try to enter %p in the provided box. Once you do so, gedit starts consuming 100% CPU and compiz dims its window. At this point, you don't have any other option except to kill gedit. Instead, gedit should process the provided date format and yield nothing. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gedit 2.30.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Wed Sep 15 14:22:40 2010 ProcEnviron: PATH=(custom, user) LANG=ru_RU.utf8 SHELL=/bin/bash SourcePackage: gedit ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- enters infinite loop on entering certain date formats https://bugs.launchpad.net/bugs/638749 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 638749] Re: enters infinite loop on entering certain date formats
** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/638749/+attachment/1587180/+files/Dependencies.txt -- enters infinite loop on entering certain date formats https://bugs.launchpad.net/bugs/638749 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504175]
Maybe he has some other USB audio device? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504175 Title: Starting pavucontrol creates sound drop-out [related to C270/C910 Logitech webcam] To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1504175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1504175]
For me, disconnecting the webcam helps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1504175 Title: Starting pavucontrol creates sound drop-out [related to C270/C910 Logitech webcam] To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1504175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Today I talked about this bug with Keith Packard. As a result of our testing, I have to state that, with the patch, the pointer is not constrained properly on the right side if one applies keystone correction. That's with xorg-server 1.16.1, will now retest with the latest git. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Today I talked about this bug with Keith Packard. As a result of our testing, I have to state that, with the patch, the pointer is not constrained properly on the right side if one applies keystone correction. That's with xorg-server 1.16.1, will now retest with the latest git. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Retested with the latest git. The patch indeed breaks constraining the mouse on the right side when keystone correction is active. However, the whole "keystone correction" feature is already so horribly broken that I'd just propose to drop it. The breakage is that, if you click something, the click will not go into a point that you intended to click. I.e. you can't even undo the damage using the xkeystone GUI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Retested with the latest git. The patch indeed breaks constraining the mouse on the right side when keystone correction is active. However, the whole "keystone correction" feature is already so horribly broken that I'd just propose to drop it. The breakage is that, if you click something, the click will not go into a point that you intended to click. I.e. you can't even undo the damage using the xkeystone GUI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 421621]
Should be fixed in git with a different patch: http://cgit.freedesktop.org/pulseaudio/pavucontrol/commit/?id=35e844d2b2cf35f5a4cb29b1e32f4f1fa95dda7b Could you please build from git and retest? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/421621 Title: pavucontrol's window width depends on stream names, may get very wide To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/421621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
The bug is also relevant to scaling. You can test it (assuming a 1920x1200 monitor) with the following example commands: xrandr --fb 3840x2400 xrandr --output DVI-I-1 --scale 2x2 The example has no purpose as written, except to illustrate the bug, but similar "xrandr --scale" commands are useful if one wants to mirror a 1366x768 laptop screen and a 1920x1080 projector for a presentation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
Why is this bug still in the NEEDINFO state? I.e. what info is needed before someone reviews the patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
Why is this bug still in the NEEDINFO state? I.e. what info is needed before someone reviews the patch? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
The bug is also relevant to scaling. You can test it (assuming a 1920x1200 monitor) with the following example commands: xrandr --fb 3840x2400 xrandr --output DVI-I-1 --scale 2x2 The example has no purpose as written, except to illustrate the bug, but similar "xrandr --scale" commands are useful if one wants to mirror a 1366x768 laptop screen and a 1920x1080 projector for a presentation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1299499]
That new bug is probably https://bugs.gentoo.org/show_bug.cgi?id=513500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1299499 Title: kwin crashes on desktop startup with wobbly windows enabled To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1299499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 638749] Re: enters infinite loop on entering certain date formats
I am not a user of Ubuntu anymore, thus cannot test the version in Ubuntu. However, the bug is so simple that you should really test it yourself. And it does exist in version 2.30.4 in Gentoo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/638749 Title: enters infinite loop on entering certain date formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/638749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 638749] Re: enters infinite loop on entering certain date formats
The same bug also exists in gedit 3.0.6 in Gentoo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/638749 Title: enters infinite loop on entering certain date formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/638749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608201] [NEW] endless stream of uevents related to Intel onboard graphics
Public bug reported: On my Ubuntu system, udev, init and upstart-udev-bridge each eat around ~8% CPU. On my Gentoo system at home (that also has Intel graphics), udev eats nothing. Here is the "udevadm monitor" output: patra...@patrakov-desktop:~$ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1279711636.543757] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.545723] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.550036] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.556736] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.560277] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.562998] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.573643] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.575592] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.629531] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.631481] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.659774] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.661881] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.673441] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.675395] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.713191] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.715157] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.746274] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.748273] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.749674] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.753128] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.764809] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.766845] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.772156] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.774026] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.788969] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.792166] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.822973] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.824931] change /devices/pci:00/:00:02.0/drm/card0 (drm) KERNEL[1279711636.828249] change /devices/pci:00/:00:02.0/drm/card0 (drm) UDEV [1279711636.830143] change /devices/pci:00/:00:02.0/drm/card0 (drm) ...and so on So it looks like the graphics driver emits a useless uevent up to 200 times a second. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-23-generic 2.6.32-23.37 Regression: No Reproducible: Yes ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: patrakov 4856 F pulseaudio CRDA: Error: [Errno 2] Нет такого файла или каталога Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfdff8000 irq 16' Mixer name : 'Realtek ALC888' Components : 'HDA:80862803,80860101,0010 HDA:10ec0888,1458a002,0011' Controls : 44 Simple ctrls : 23 Date: Wed Jul 21 17:27:49 2010 IwConfig: lono wireless extensions. eth0 no wireless extensions. tap0 no wireless extensions. Lsusb: Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. EG41MFT-US2H ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-23-generic root=UUID=e154a633-7199-47fb-b225-fbfcaf458ace ro quiet splash ProcEnviron: PATH=(custom, user) LANG=ru_RU.utf8 SHELL=/bin/bash RelatedPackageVersions: linux-firmware 1.34.1 RfKill: SourcePackage: linux dmi.bios.date: 09/30/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: EG41MFT-US2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd09/30/2009:svnGigabyteTechnologyCo.,Ltd.:pnEG41MFT-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEG41MFT-US
[Bug 608201] Re: endless stream of uevents related to Intel onboard graphics
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/52257280/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/52257281/AplayDevices.txt ** Attachment added: "ArecordDevices.txt" http://launchpadlibrarian.net/52257282/ArecordDevices.txt ** Attachment added: "BootDmesg.txt" http://launchpadlibrarian.net/52257283/BootDmesg.txt ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/52257284/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/52257285/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.2.txt" http://launchpadlibrarian.net/52257286/Card0.Codecs.codec.2.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/52257287/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/52257288/Dependencies.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/52257289/Lspci.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/52257290/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/52257291/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/52257292/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/52257293/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/52257294/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/52257295/UdevLog.txt ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/52257296/WifiSyslog.txt -- endless stream of uevents related to Intel onboard graphics https://bugs.launchpad.net/bugs/608201 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608201] Re: endless stream of uevents related to Intel onboard graphics
In 2.6.35-9-generic from kernel-ppa, the bug does not exist. So it needs to be fixed in lucid kernel only. -- endless stream of uevents related to Intel onboard graphics https://bugs.launchpad.net/bugs/608201 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 608201] Re: endless stream of uevents related to Intel onboard graphics
Jeremy, as I already wrote, the bug is already fixed in later Ubuntu kernels from the kernel PPA. Are you sure, given this fact, that you still want me to test the latest self-compiled kernel? What would such testing achieve? -- endless stream of uevents related to Intel onboard graphics https://bugs.launchpad.net/bugs/608201 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
