[Bug 1860390] Re: Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram)
Same problem on Dell 5540 clean install Ubuntu 24.04 I also can't change /sys/power/mem_sleep, also not with the method suggested by leezu. The systemd-tmpfiles method also doesn't change the file. The method of the OP of replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" doesn't help either. Still gives koenr@koenr-Latitude-5540:~$ sudo journalctl | grep "PM: suspend" | tail -2 jul 10 20:06:16 koenr-Latitude-5540 kernel: PM: suspend entry (s2idle) jul 10 20:06:25 koenr-Latitude-5540 kernel: PM: suspend exit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860390 Title: Dell XPS 13 (9360) defaults to s2idle sleep/suspend instead of deep (suspend to ram) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
From cloud-init point of view the solution now implemented make sense: to run it before the apt-daily-upgrade. However, I wanted to add that there are other use cases as well such as SSM documents being executed on instances. These can be executed in batch at any time and may also require installation of packages and thus interfere with these unattended upgrades. The execution of documents is not linked directly to cloud-init and may be ran after the instances has been booted, so this falls in the other category of having some kind queuing system or at least a centralized way to obtain a lock to be able to use apt. At the moment there are dozens of different possibilities how to get a mutex to be able to execute apt, but somehow we couldn't find a bullet proof way that works *every time*. So maybe this does not really fit into this ticket, but to address that this is only a partial fix to a bigger problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Just tested the proposed gssproxy fix, and can confirm that it solved the issue Tested on Ubuntu Focal (20.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938096] Re: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend
I can confirm this exact bug. I have the same machine (Thinkpad X1 Carbon 9th gen). However, I am running an up-to-date Fedora 34 system. For me, changing the sleep mode to what the BIOS calls "Linux and Windows" (apparently software suspend?) also fixes the problem. I have not had a chance yet to compare the impact on battery life during suspend. Would it be an idea to report this to Fedora as well? I might be able to help test things out if needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938096 Title: [Lenovo X1 Carbon 9th] [SYNA8009:00 06CB:CE57] touchpad lagging after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
I can confirm that manual build and install of gssproxy 0.8.4 works on my ubuntu 20.04 server. (that version has the patch mentioned above) gssproxy solves my original issue of rpc-svcgssd hanging on large kerberos tickets https://bugs.launchpad.net/ubuntu/+source/nfs- utils/+bug/1466654 Hopefully this patch find its way fast through the official ubuntu release channel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466654] Re: kernel soft lockup on nfs server when using a kerberos mount
The workaround as suggested it to use gssproxy Unfortunately that also has a bug https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466654 Title: kernel soft lockup on nfs server when using a kerberos mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1466654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466654] Re: kernel soft lockup on nfs server when using a kerberos mount
Manually compiling and installing the latest version of gssproxy did solve the issue for me -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466654 Title: kernel soft lockup on nfs server when using a kerberos mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1466654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
gssproxy/focal,now 0.8.2-2 amd64 [installed] libselinux1/focal,now 3.0-1build2 amd64 [installed,automatic] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
I couldn't get it to generate a coredump. But I ran it with valgrind Hope this helps valgrind -v /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock ==29249== Memcheck, a memory error detector ==29249== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==29249== Using Valgrind-3.15.0-608cb11914-20190413 and LibVEX; rerun with -h for copyright info ==29249== Command: /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock ==29249== --29249-- Valgrind options: --29249---v --29249-- Contents of /proc/version: --29249-- Linux version 5.4.0-74-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 --29249-- --29249-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-rdrand --29249-- Page sizes: currently 4096, max supported 4096 --29249-- Valgrind library directory: /usr/lib/x86_64-linux-gnu/valgrind --29249-- Reading syms from /usr/sbin/gssproxy --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/ld-2.31.so --29249-- Considering /usr/lib/x86_64-linux-gnu/ld-2.31.so .. --29249-- .. CRC mismatch (computed 975d0390 wanted 30bd717f) --29249-- Considering /lib/x86_64-linux-gnu/ld-2.31.so .. --29249-- .. CRC mismatch (computed 975d0390 wanted 30bd717f) --29249-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.31.so .. --29249-- .. CRC is valid --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/valgrind/memcheck-amd64-linux --29249--object doesn't have a symbol table --29249--object doesn't have a dynamic symbol table --29249-- Scheduler: using generic scheduler lock implementation. --29249-- Reading suppressions file: /usr/lib/x86_64-linux-gnu/valgrind/default.supp ==29249== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-29249-by-root-on-??? ==29249== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-29249-by-root-on-??? ==29249== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-29249-by-root-on-??? ==29249== ==29249== TO CONTROL THIS PROCESS USING vgdb (which you probably ==29249== don't want to do, unless you know exactly what you're doing, ==29249== or are doing some strange experiment): ==29249== /usr/lib/x86_64-linux-gnu/valgrind/../../bin/vgdb --pid=29249 ...command... ==29249== ==29249== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==29249== /path/to/gdb /usr/sbin/gssproxy ==29249== and then give GDB the following command ==29249== target remote | /usr/lib/x86_64-linux-gnu/valgrind/../../bin/vgdb --pid=29249 ==29249== --pid is optional if only one valgrind process is running ==29249== --29249-- REDIR: 0x4022e10 (ld-linux-x86-64.so.2:strlen) redirected to 0x580c9ce2 (???) --29249-- REDIR: 0x4022be0 (ld-linux-x86-64.so.2:index) redirected to 0x580c9cfc (???) --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_core-amd64-linux.so --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so --29249--object doesn't have a symbol table ==29249== WARNING: new redirection conflicts with existing -- ignoring it --29249-- old: 0x04022e10 (strlen ) R-> (.0) 0x580c9ce2 ??? --29249-- new: 0x04022e10 (strlen ) R-> (2007.0) 0x0483f060 strlen --29249-- REDIR: 0x401f5f0 (ld-linux-x86-64.so.2:strcmp) redirected to 0x483ffd0 (strcmp) --29249-- REDIR: 0x4023370 (ld-linux-x86-64.so.2:mempcpy) redirected to 0x4843a20 (mempcpy) --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libpopt.so.0.0.0 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libkrb5.so.3.3 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libverto.so.1.0.0 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libini_config.so.5.2.1 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libref_array.so.1.2.1 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libselinux.so.1 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libgssrpc.so.4.2 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 --29249--object doesn't have a symbol table --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libpthread-2.31.so --29249-- Considering /usr/lib/debug/.build-id/e5/4761f7b554d0fcc1562959665d93dffbebdaf0.debug .. --29249-- .. build-id is valid --29249-- Reading syms from /usr/lib/x86_64-linux-gnu/libc-
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
** Attachment added: "/var/crash/_usr_sbin_gssproxy.0.crash" https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+attachment/5507903/+files/_usr_sbin_gssproxy.0.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
The reason we want gssproxy, and not the default rpc-gssd and rpc- svcgssd services is that we are using active directory, and most of our accounts are members of many groups, causing gssd to fail. This is a known issue and is one of the things that gssproxy solves. >>The reason we did this was to allow the kernel NFS server to handle big tickets like those containing a MS-PAC payload that may be received by a Microsoft client. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788459] Re: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd
Trying to get gssproxy working with NFS (rpc-gssd and rpc-svcgssd) on Ubuntu 20.04 Following https://github.com/gssapi/gssproxy/blob/main/docs/NFS.md /etc/gssproxy/gssproxy.conf [gssproxy] debug = true debug_level = 3 /etc/gssproxy/25-nfs-server.conf [service/nfs-server] mechs = krb5 socket = /run/gssproxy.sock cred_store = keytab:/etc/krb5.keytab trusted = yes kernel_nfsd = yes euid = 0 When I start the gssproxy service, either through systemd or manually with: /usr/sbin/gssproxy --interactive --debug --debug-level=3 --socket=/run/gssproxy.sock I get this result: [2021/06/28 14:49:19]: Debug Enabled (level: 3) [2021/06/28 14:49:19]: Service: nfs-client, Keytab: /etc/krb5.keytab, Enctype: 23 [2021/06/28 14:49:19]: Service: nfs-server, Keytab: /etc/krb5.keytab, Enctype: 23 [2021/06/28 14:49:19]: Client [2021/06/28 14:49:19]: (/usr/sbin/gssproxy) [2021/06/28 14:49:19]: connected (fd = 13)[2021/06/28 14:49:19]: (pid = 7821) (uid = 0) (gid = 0)Segmentation fault (core dumped) It is the kernel_nfsd = yes config part that causes the segfault What it does (from the docs linked above) ... The gssproxy client registers to the kernel by performing 2 actions in the following order: * creates a unix socket for kernel communication in /var/run/gssproxy.sock (this path is hardcoded in the kernel and cannot be changed at this time) * writes 1 byte in the proc file /proc/net/rpc/use-gss-proxy (the client must be ready to accept a connection from the kernel when this is done, as the kernel we check that the socket is available) ... It enables the kernel extensions to the protocol (the context is exported as a lucid context for example, and a list of resolved credentials is returned if authentication succeeds) The proc files seems ok (it was -1 before) cat /proc/net/rpc/use-gss-proxy 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788459 Title: gssproxy crashes in libselinux.so.1 on Ubuntu 18.04 when called by rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssproxy/+bug/1788459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729433]
I think this bug describes the behaviour on https://askubuntu.com/questions/1274365/windows-of-an-application-have- minimum-size-and-i-cant-find-the-window-anymore We have noticed that with several of our students on Ubuntu 20.04 with LO 7.0.4.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729433 Title: LibreOffice doesn't remember window size when running under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@robin Windey I had no luck with kernel 5.10.2, try 5.9.16 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Touchpad works without workaround on Ubuntu 20.04 with Kernel 5.9.16 Same goes for ubuntu 20.10. Easiest way is to use the workaround, install mainline(alternative for ukuu) install kernel 5.9.16 Reboot and relax -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Ubuntu 20.10 with kernel : Linux legion5 5.9.16-050916-generic #202012211331 SMP Mon Dec 21 14:11:13 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Touchpad works without any work around -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Installed ubuntu 20.10 on ARH05, the gpio workaround makes the mouse work. Left click and right click button works -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] Re: mysql timeoutsec results in killing mysql process
** Description changed: MySQL on 20.04 has TimeoutSec set to 600 (IIRC) in the systemd script. This has the effect of killing the MySQL process if this timeout is reached. IMHO this is a Very Bad Idea. A database server process should only be force killed by a user action. I would prefer that the server had unlimited time to cleanly shutdown and startup (eg if recovering). Our DB is about 500GB with some very large tables (for us at least) eg. 250GB and we've had more than a few unfortunate delays as a result of delayed startup caused by recoveries because MySQL was killed prematurely. Because MySQL 8.0 has reduced the default logging level, it was not clear to me that the process was being force killed. I believe the MySQL team are of the same view as me per https://bugs.mysql.com/bug.php?id=91423: ``` [12 Jul 2019 15:57] Paul Dubois Posted by developer: - + Fixed in 8.0.18. On Debian, long InnoDB recovery times at startup could cause systemd service startup failure. The default systemd service timeout is now disabled (consistent with RHEL) to prevent this from happening. ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] Re: mysql timeoutsec results in killing mysql process
I'm unassigning myself as I'm not sure what the next steps are but I believe it should be corrected by ubuntu taking the latest debian version of the package (i.e. mysql-8.0 (8.0.22-1)) -> no ubuntu-patch needed ** Changed in: mysql-8.0 (Ubuntu) Assignee: Koen (koen-beek) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] Re: mysql timeoutsec results in killing mysql process
hmm when doing a git clone https://salsa.debian.org/mariadb-team/mysql.git -b mysql-8.0/debian/master it seems it has been fixed by putting infinity to TimeoutSec (I suppose that's the same as 0) in Debian mysql/debian/mysql-server-8.0.mysql.service:TimeoutSec=infinity -> seems to have been fixed in Debian in mysql-8.0.0.22 and https://metadata.ftp- master.debian.org/changelogs//main/m/mysql-8.0/mysql-8.0_8.0.22-1_changelog shows : mysql-8.0 (8.0.22-1) unstable; urgency=medium ... * d/systemd: Disable service timeout For large databases, the service could timeout on stop, possibly leading to data corruption during a system shutdown. (LP: #1882527) --> it's in debian in the next patch release Ubuntu is currently on 8.0.22-0(ubuntu0.20.10.2) -> ubuntu just needs to align with debian 8.0.22-1 instead of 8.0.22-0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] Re: mysql timeoutsec results in killing mysql process
There does not seem to be an equivalent debian bug about this issue yet will make a patch in ubuntu and forward it to debian : https://wiki.ubuntu.com/Debian/Bugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882527] Re: mysql timeoutsec results in killing mysql process
The mysql bug ticket (https://bugs.mysql.com/bug.php?id=91423) mentions [12 Jul 2019 15:57] Paul Dubois Posted by developer: Fixed in 8.0.18. On Debian, long InnoDB recovery times at startup could cause systemd service startup failure. The default systemd service timeout is now disabled (consistent with RHEL) to prevent this from happening. -- the latest ubuntu code (based on 8.0.22) contains following mentions of TimeoutSec koen@hpubuntu:~/Dev/personal/ubuntu/mysql$ grep -rR TimeoutSec * mysql-8.0-8.0.22/packaging/deb-in/mysql-packagesource-server.mysql.service.in:TimeoutSec=0 mysql-8.0-8.0.22/packaging/deb-in/mysql-packagesource-server.my...@.service.in:TimeoutSec=0 mysql-8.0-8.0.22/scripts/systemd/mys...@.service.in:TimeoutSec=0 mysql-8.0-8.0.22/scripts/systemd/mysqld.service.in:TimeoutSec=0 mysql-8.0-8.0.22/debian/mysql-server-8.0.mysql.service:TimeoutSec=600 --> it seems there's still 1 mention of 600 seconds in the Debian/ubuntu package I can take on this issue but it might take a few weeks forme to complete - ETA mid Jan 2021 as I'm pretty new at ubuntu bugfixing/packaging and I'll have some questions for some more expert people - correct patch description - how to involve Debian upstream - how to make patches for several releases (I'll start with hirsute) if it's more urgent don't hesitate to assign someone else ** Bug watch added: MySQL Bug System #91423 http://bugs.mysql.com/bug.php?id=91423 ** Changed in: mysql-8.0 (Ubuntu) Assignee: (unassigned) => Koen (koen-beek) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882527 Title: mysql timeoutsec results in killing mysql process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1882527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900318] Re: compliments/complements typo in package description
subscribed ubuntu sponsors team following this process https://wiki.ubuntu.com/SponsorshipProcess -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900318 Title: compliments/complements typo in package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1900318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900318] Re: compliments/complements typo in package description
** Changed in: update-motd (Ubuntu) Assignee: Koen (koen-beek) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900318 Title: compliments/complements typo in package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1900318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900318] Re: compliments/complements typo in package description
Fix type in debian/control file for package description : compliments -> complements My first patch in a long time - beware I followed this workflow : https://packaging.ubuntu.com/html/fixing-a-bug.html i.e. - pull-lp-source update-motd hirsute - cd update-motd-3.6/ - change control text file in debian folder (vi) - debuild -S -d -us -uc (OK) - pbuilder-dist hirsute build ../update-motd_3.6-0ubuntu8.dsc - debuild -S -d - debdiff update-motd_3.6-0ubuntu7.dsc update-motd_3.6-0ubuntu8.dsc > 1-3.6-0ubuntu8.debdiff ** Patch added: "fix typo in debian/control file (package description)" https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1900318/+attachment/5444001/+files/1-3.6-0ubuntu8.debdiff ** Changed in: update-motd (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900318 Title: compliments/complements typo in package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1900318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900318] Re: compliments/complements typo in package description
I can't find "compliments" in the source package koen@hpubuntu:~/Dev/personal/ubuntu/update-motd-3.6$ grep -irR compli * COPYING:for enforcing compliance by third parties with this License. I can only find the text on this page : https://launchpad.net/ubuntu/+source/update-motd No idea how that can be changed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900318 Title: compliments/complements typo in package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1900318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900318] Re: compliments/complements typo in package description
Ok, found it it's in the ubuntu diff : https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/update- motd/3.6-0ubuntu7/update-motd_3.6-0ubuntu7.diff.gz quote : +Package: update-motd +Architecture: all +Depends: ${misc:Depends}, libpam-modules (>= 1.0.1-9ubuntu3) +Description: compliments pam_motd in libpam-modules I can take it as my first packaging try ** Changed in: update-motd (Ubuntu) Assignee: (unassigned) => Koen (koen-beek) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900318 Title: compliments/complements typo in package description To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1900318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903298] Re: aide segfaults on Ubuntu 20.10
also crashes in development release 21.10 root@koen-VirtualBox:/var/crash# ls -lrt total 416 -rw-r- 1 root whoopsie 425471 Dez 15 18:08 _usr_bin_aide.0.crash root@koen-VirtualBox:/var/crash# sudo dmesg | tail -n5 [ 90.657264] rfkill: input handler disabled [ 1493.234716] aide[21779]: segfault at e5 ip 7f10e9a02ee4 sp 7ffe42f012e0 error 4 in libc-2.32.so[7f10e98e8000+16d000] [ 1493.234721] Code: ff 48 85 c0 0f 84 99 00 00 00 41 80 3c 24 ff 0f 85 b4 00 00 00 48 8b 05 fa 0e 0a 00 49 0f be 16 4c 89 f5 64 48 8b 08 48 89 d0 44 51 01 20 74 18 0f 1f 44 00 00 48 0f be 55 01 48 83 c5 01 48 [ 1688.321670] aide[24107]: segfault at e5 ip 7f3e5e79aee4 sp 7ffdcfb899a0 error 4 in libc-2.32.so[7f3e5e68+16d000] [ 1688.321680] Code: ff 48 85 c0 0f 84 99 00 00 00 41 80 3c 24 ff 0f 85 b4 00 00 00 48 8b 05 fa 0e 0a 00 49 0f be 16 4c 89 f5 64 48 8b 08 48 89 d0 44 51 01 20 74 18 0f 1f 44 00 00 48 0f be 55 01 48 83 c5 01 48 root@koen-VirtualBox:/var/crash# lsb_release -rd; uname -r Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 5.8.0-25-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903298 Title: aide segfaults on Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1903298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789850] Re: Advertising in the MOTD
doesn't seem like a bug to me - it works as expected ** Changed in: update-motd (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789850 Title: Advertising in the MOTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1789850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903298] Re: aide segfaults on Ubuntu 20.10
error confirmed by other user : https://askubuntu.com/questions/1296526 /segmentation-fault-core-dumped-aide-init-return-code-139 ** Changed in: aide (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903298 Title: aide segfaults on Ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1903298/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907914] Re: default locale when selecting english(US) and belgian timezone is incorrect
** Description changed: When installing ubuntu (20.04 and later (earlier also probably))selecting - english (US) language - Brussels-Belgian timezone ubuntu selects de_BE as locale which is teh Belgian German-language locale in Belgium about 60% are dutch-speaking (nl_BE) and 40% are french speaking (fr_BE) and less than 1% are german speaking (de_BE)--> choosing de_BE seems to be a bad default value + related ubiquity code is here : + https://git.launchpad.net/ubiquity/tree/scripts/localechooser-apply - related ubiquity code is here : https://git.launchpad.net/ubiquity/tree/scripts/localechooser-apply - - - it seems when a language (en) is selected for Belgium which is not available as a locale (i.e. en-BE) the locale de_BE is chosen using this code + it seems when a language (en) is selected for Belgium which is not + available as a locale (i.e. en-BE) the locale de_BE is chosen using this + code -- code -- - combined="$(grep ' UTF-8' /usr/share/i18n/SUPPORTED | \ - grep "${deflang}_$COUNTRY[.@ ]" | head -n1 | \ - cut -d' ' -f1)" + combined="$(grep ' UTF-8' /usr/share/i18n/SUPPORTED | \ + grep "${deflang}_$COUNTRY[.@ ]" | head -n1 | \ + cut -d' ' -f1)" -- code -- - de_BE is chosen as I suppose it is alphabetically before fr_BE and nl_BE - I'm not sure what the best solution is I'd propose the following changes in order of my preference 1. add a en_BE locale (https://www.localeplanet.com/icu/en-BE/index.html) and make that default for non wa, nl, fr and de languages 2. allow user to select nl_BE or fr_BE locale when installing ubuntu (and maybe also de_BE or wa_BE which have much smaller % of people in Belgium) - may require a change of ubuntu install process - but I guess Belgium is not the only country with several languages with similar issues : Switzerland, ... 3. set default language nl for Belgium (might be politically problematic for 40% of Belgian people) but makes more sense than de - - related AskUbuntu question : https://askubuntu.com/questions/1299522/belgian-formats-when-choosing-us-language-regional-language-settings-issue + related AskUbuntu question : https://askubuntu.com/questions/1299522 + /belgian-formats-when-choosing-us-language-regional-language-settings- + issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907914 Title: default locale when selecting english(US) and belgian timezone is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1907914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907914] [NEW] default locale when selecting english(US) and belgian timezone is incorrect
Public bug reported: When installing ubuntu (20.04 and later (earlier also probably))selecting - english (US) language - Brussels-Belgian timezone ubuntu selects de_BE as locale which is teh Belgian German-language locale in Belgium about 60% are dutch-speaking (nl_BE) and 40% are french speaking (fr_BE) and less than 1% are german speaking (de_BE)--> choosing de_BE seems to be a bad default value related ubiquity code is here : https://git.launchpad.net/ubiquity/tree/scripts/localechooser-apply it seems when a language (en) is selected for Belgium which is not available as a locale (i.e. en-BE) the locale de_BE is chosen using this code -- code -- combined="$(grep ' UTF-8' /usr/share/i18n/SUPPORTED | \ grep "${deflang}_$COUNTRY[.@ ]" | head -n1 | \ cut -d' ' -f1)" -- code -- de_BE is chosen as I suppose it is alphabetically before fr_BE and nl_BE I'm not sure what the best solution is I'd propose the following changes in order of my preference 1. add a en_BE locale (https://www.localeplanet.com/icu/en-BE/index.html) and make that default for non wa, nl, fr and de languages 2. allow user to select nl_BE or fr_BE locale when installing ubuntu (and maybe also de_BE or wa_BE which have much smaller % of people in Belgium) - may require a change of ubuntu install process - but I guess Belgium is not the only country with several languages with similar issues : Switzerland, ... 3. set default language nl for Belgium (might be politically problematic for 40% of Belgian people) but makes more sense than de related AskUbuntu question : https://askubuntu.com/questions/1299522 /belgian-formats-when-choosing-us-language-regional-language-settings- issue ** Affects: ubiquity (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/1907914 Title: default locale when selecting english(US) and belgian timezone is incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1907914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889253] [NEW] error
Public bug reported: ww ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 28 16:19:48 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889253 Title: error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1889253/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883108] [NEW] kile missing icons in interface and launcher
Public bug reported: I found kile missing nearly all icons in the interface (open, save, undo, redo, ...). Also the application Icon was corrupt in the launcher. Solutions: apt install qt5-gtk-platformtheme:amd64 fixed the missing icons in the interface echo 'StartupWMClass=kile' >> /usr/share/applications/org.kde.kile.desktop solved the corrupt icon in the launcher apt-cache policy kile kile: Geïnstalleerd: 4:2.9.91-4 Kandidaat: 4:2.9.91-4 Versietabel: *** 4:2.9.91-4 500 500 http://be.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 ** Affects: kile (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/1883108 Title: kile missing icons in interface and launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kile/+bug/1883108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1557215] Re: "The update information is outdated" warning won't go away. No information given about how to fix
I see this same behaviour regularly on systems running 18.04 as well. Running sudo apt update makes the update process resume - no errors shown. Without doing that the system reports that it is up to date and it isn't, making it unsafe. Non techy users freak out on using a command line command. I think this could and should be self healing, eg by running an apt update on resume after network up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1557215 Title: "The update information is outdated" warning won't go away. No information given about how to fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1557215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830771] [NEW] Installation on ZenBook pro 14 (GRUB install failed)
Public bug reported: Stopped at installation. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 19:07:52 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash acpi=off --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830771 Title: Installation on ZenBook pro 14 (GRUB install failed) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1830771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
Tried it, no change drwxr-xr-x 74 root root 0 Jan 31 19:00 .. lrwxrwxrwx 1 root root 0 Jan 31 19:00 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar lrwxrwxrwx 1 root root 0 Jan 31 19:03 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane lrwxrwxrwx 1 root root 0 Jan 31 19:03 input4::capslock -> ../../devices/platform/i8042/serio0/input/input4/input4::capslock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input4::numlock -> ../../devices/platform/i8042/serio0/input/input4/input4::numlock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input4::scrolllock -> ../../devices/platform/i8042/serio0/input/input4/input4::scrolllock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input7::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::capslock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input7::compose -> ../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::compose lrwxrwxrwx 1 root root 0 Jan 31 19:03 input7::kana -> ../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::kana lrwxrwxrwx 1 root root 0 Jan 31 19:03 input7::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::numlock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input7::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:1050:0407.0001/input/input7/input7::scrolllock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input8::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::capslock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input8::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::compose lrwxrwxrwx 1 root root 0 Jan 31 19:03 input8::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::kana lrwxrwxrwx 1 root root 0 Jan 31 19:03 input8::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::numlock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input8::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0003/input/input8/input8::scrolllock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input9::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::capslock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input9::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::compose lrwxrwxrwx 1 root root 0 Jan 31 19:03 input9::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::kana lrwxrwxrwx 1 root root 0 Jan 31 19:03 input9::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::numlock lrwxrwxrwx 1 root root 0 Jan 31 19:03 input9::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0004/input/input9/input9::scrolllock lrwxrwxrwx 1 root root 0 Jan 31 19:03 phy0-led -> ../../devices/pci:00/:00:14.3/leds/phy0-led asus_wireless 20480 0 asus_nb_wmi28672 0 asus_wmi 28672 1 asus_nb_wmi sparse_keymap 16384 1 asus_wmi wmi28672 4 intel_wmi_thunderbolt,asus_wmi,wmi_bmof,mxm_wmi video 49152 2 asus_wmi,i915 Was it on the same hardware @david? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
It is a fresh install never tried an older version. I have tried the new kernel, same issue. The asus-nb-wmi module is loaded but seems not to support this keyboard. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
Fedora 29, same thing. Doesn't start in graphic mode. The only version that seems to work is Linux Mint 19 at the moment. I've added an output of inxi: System:Host: GM501GM Kernel: 4.15.0-20-generic x86_64 bits: 64 Desktop: Cinnamon 3.8.9 Distro: Linux Mint 19 Tara Machine: Device: laptop System: ASUSTeK product: Zephyrus M GM501GM v: 1.0 serial: N/A Mobo: ASUSTeK model: GM501GM v: 1.0 serial: N/A UEFI: American Megatrends v: GM501GM.306 date: 07/31/2018 BatteryBAT0: charge: 54.4 Wh 100.1% condition: 54.4/55.0 Wh (99%) CPU: 6 core Intel Core i7-8750H (-MT-MCP-) cache: 9216 KB clock speeds: max: 4100 MHz 1: 1558 MHz 2: 2000 MHz 3: 1933 MHz 4: 2003 MHz 5: 1683 MHz 6: 1383 MHz 7: 2001 MHz 8: 2000 MHz 9: 1955 MHz 10: 1340 MHz 11: 2000 MHz 12: 1249 MHz Graphics: Card-1: Intel Device 3e9b Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia (unloaded: fbdev,vesa,nouveau) Resolution: 1920x1080@144.03hz OpenGL: renderer: GeForce GTX 1060/PCIe/SSE2 version: 4.6.0 NVIDIA 390.87 Audio: Card Intel Device a348 driver: snd_hda_intel Sound: ALSA v: k4.15.0-20-generic Network: Card: Intel Device a370 driver: iwlwifi IF: wlo1 state: up speed: N/A duplex: N/A mac: Drives:HDD Total Size: 756.2GB (27.2% used) ID-1: /dev/nvme0n1 model: SAMSUNG_MZVPW256HEGL size: 256.1GB ID-2: /dev/sda model: Samsung_SSD_860 size: 500.1GB Partition: ID-1: / size: 210G used: 8.1G (5%) fs: ext4 dev: /dev/nvme0n1p2 ID-2: swap-1 size: 25.52GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p3 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 41.0C mobo: N/A gpu: 41C Fan Speeds (in rpm): cpu: N/A Info: Processes: 304 Uptime: 0 min Memory: 754.7/15890.6MB Client: Shell (bash) inxi: 2.3.56 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
Ubuntu 18.10 does not work on this laptop, at least not the live version. It blocks on the GPU. In linux mint it works smooth, apart from the keyboard backlight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
Ubuntu 18.10 does not work on this laptop, at least not the live version. It blocks on the GPU. In linux mint it works smooth, apart from the keyboard backlight. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] Re: keyboard backlight not working on Asus GM501
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802652] [NEW] keyboard backlight not working on Asus GM501
Public bug reported: The keyboard lights and most of the F keys aren't working. Kernel = 4.15.0-20-generic System linux mint 19 ls -hal /sys/class/leds/ total 0 drwxr-xr-x 2 root root 0 Nov 10 15:47 . drwxr-xr-x 72 root root 0 Nov 10 15:43 .. lrwxrwxrwx 1 root root 0 Nov 10 15:43 asus::lightbar -> ../../devices/platform/asus-nb-wmi/leds/asus::lightbar lrwxrwxrwx 1 root root 0 Nov 10 15:47 asus-wireless::airplane -> ../../devices/LNXSYSTM:00/LNXSYBUS:00/ATK4002:00/leds/asus-wireless::airplane lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::capslock -> ../../devices/platform/i8042/serio0/input/input4/input4::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::numlock -> ../../devices/platform/i8042/serio0/input/input4/input4::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input4::scrolllock -> ../../devices/platform/i8042/serio0/input/input4/input4::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::compose lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::kana lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input7::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.0/0003:0B05:1866.0001/input/input7/input7::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::capslock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::capslock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::compose -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::compose lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::kana -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::kana lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::numlock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::numlock lrwxrwxrwx 1 root root 0 Nov 10 15:47 input8::scrolllock -> ../../devices/pci:00/:00:14.0/usb1/1-10/1-10:1.1/0003:0B05:1866.0002/input/input8/input8::scrolllock lrwxrwxrwx 1 root root 0 Nov 10 15:47 phy0-led -> ../../devices/pci:00/:00:14.3/leds/phy0-led ** Affects: linux (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/1802652 Title: keyboard backlight not working on Asus GM501 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174650] Re: xorg very slow when rotated on external monitor (i965)
lspci | grep -i VGA 00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04) 01:00.0 VGA compatible controller: NVIDIA Corporation Device 1c8d (rev a1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/174650 Title: xorg very slow when rotated on external monitor (i965) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/174650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174650] Re: xorg very slow when rotated on external monitor (i965)
I'm having this issue on ubuntu conntecting my externel display using displaylink (only when rotated) No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.4 LTS Release:16.04 Codename: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/174650 Title: xorg very slow when rotated on external monitor (i965) To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/174650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730343] Re: firmware update breaks Ubuntu
For me the update was also successful. Went from bios version 1.7.5 to 1.8.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730343] Re: firmware update breaks Ubuntu
Hello all, I just tried the proposed package on 16.04 and it failed. I took this picture with my phone: https://www.dropbox.com/s/6r6zeadqakbtjg5/2018-01-04%2023.35.59-1.jpg?dl=0 After that screen it just continued with a regular boot. ** Tags removed: verification-needed-xenial ** Tags added: verification-failed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733311] Re: pip crashes at startup importing from OpenSSL
I discovered the root cause of the issue by comparing the output of `pip freeze` on both servers. Apparently on the upgraded server cryptography-1.9 was installed in `/usr/local/python2.7/dist-packages`, while overriding python- cryptography package. Running `sudo pip uninstall cryptography` resolves the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733311 Title: pip crashes at startup importing from OpenSSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyopenssl/+bug/1733311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733311] Re: pip crashes at startup importing from OpenSSL
I experience the same issue after upgrading from 14.04.5 to 16.04.3. Other server where 16.04.3 has been installed from fresh doesn't have the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733311 Title: pip crashes at startup importing from OpenSSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyopenssl/+bug/1733311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730343] Re: firmware update breaks Ubuntu
Hello, it was requested I also leave a comment here. Yesterday I experienced this issue on Ubuntu 16.04 LTS. I then found this github ticket: https://github.com/rhboot/fwupdate/issues/86 Which had a workaround that got my machine working again. I was told that "The Ubuntu archive admin needs to release the uploaded package for 16.04." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730343 Title: firmware update breaks Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1730343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1653324] Re: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet
Same on a Dell latitude 5580 with Intel Corporation Device 24fd (rev 78) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1653324 Title: No wireless networks visible on resume from suspend. Erroneous Wired connection icon in nm-applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1653324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694022] Re: Dell Latitude 5580 trackpoint not working after suspend
This seemed to be solved by some kernel upgrade. 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux runs fine. ** Changed in: linux-hwe (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694022 Title: Dell Latitude 5580 trackpoint not working after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1694022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
I see the same behavior as mikewiz38: via a webtest 104 Mbps download and in the graphical interface it lists as 6Mbps. So speed is not bad - it just looks bad (on 16.04.1 with hwe kernel 4.8.0-53) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575655] Re: the network indicator shows the wrong status
same here: koenr@koenr-Latitude-5580:~$ lspci |grep -i network 02:00.0 Network controller: Intel Corporation Device 24fd (rev 78) koenr@koenr-Latitude-5580:~$ nmcli --version nmcli tool, versie 1.2.6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575655 Title: the network indicator shows the wrong status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-applet/+bug/1575655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694022] Re: Dell Latitude 5580 trackpoint not working after suspend
Upgraded bios to Version: 1.4.3 without improvement -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694022 Title: Dell Latitude 5580 trackpoint not working after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1694022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694022] Re: Dell Latitude 5580 trackpoint not working after suspend
koenr@koenr-Latitude-5580:~$ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ DLL07A8:01 044E:120B id=11 [slave pointer (2)] ⎜ ↳ DualPoint Stick id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ Integrated Webcam_HD id=10 [slave keyboard (3)] ↳ Intel HID events id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Dell WMI hotkeys id=15 [slave keyboard (3)] koenr@koenr-Latitude-5580:~$ xinput list-props 12 Device 'DualPoint Stick': Device Enabled (140): 1 Coordinate Transformation Matrix (142): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (267): 0 Device Accel Constant Deceleration (268): 1.00 Device Accel Adaptive Deceleration (269): 1.00 Device Accel Velocity Scaling (270):10.00 Device Product ID (261):1102, 4619 Device Node (262): "/dev/input/event13" Evdev Axis Inversion (306): 0, 0 Evdev Axes Swap (308): 0 Axis Labels (309): "Rel X" (150), "Rel Y" (151) Button Labels (310):"Button Left" (143), "Button Middle" (144), "Button Right" (145), "Button Wheel Up" (146), "Button Wheel Down" (147), "Button Horiz Wheel Left" (148), "Button Horiz Wheel Right" (149) Evdev Scrolling Distance (311): 0, 0, 0 Evdev Middle Button Emulation (312):1 Evdev Middle Button Timeout (313): 50 Evdev Third Button Emulation (314): 0 Evdev Third Button Emulation Timeout (315): 1000 Evdev Third Button Emulation Button (316): 3 Evdev Third Button Emulation Threshold (317): 20 Evdev Wheel Emulation (318):1 Evdev Wheel Emulation Axes (319): 6, 7, 4, 5 Evdev Wheel Emulation Inertia (320):10 Evdev Wheel Emulation Timeout (321):200 Evdev Wheel Emulation Button (322): 2 Evdev Drag Lock Buttons (323): 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694022 Title: Dell Latitude 5580 trackpoint not working after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1694022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694022] Re: Dell Latitude 5580 trackpoint not working after suspend
xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ DualPoint Stick id=11 [slave pointer (2)] ⎜ ↳ DLL07A8:01 044E:120B id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Sleep Button id=9[slave keyboard (3)] ↳ Integrated Webcam_HD id=10 [slave keyboard (3)] ↳ Intel HID events id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Dell WMI hotkeys id=15 [slave keyboard (3)] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694022 Title: Dell Latitude 5580 trackpoint not working after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1694022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694022] [NEW] Dell Latitude 5580 trackpoint not working after suspend
Public bug reported: After a fresh boot, the track point or dual point stick is working and so does the left, right and middle button for it. After suspend and resume, none of the above work anymore. The touchpad and accompanied left and right button are not affected and work always perfectly. I noticed bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630857 which reports the same problem for a different type of Dell laptop. My kernel version is a lot newer then the one where it is fixed in. Ubuntu version is 16.04..02 LTS This Dell Latitude 5580 is listed as Ubuntu certified. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-52-generic 4.8.0-52.55~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 27 15:07:05 2017 InstallationDate: Installed on 2017-05-24 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (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/1694022 Title: Dell Latitude 5580 trackpoint not working after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1694022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515308] Re: Buttons on control bar/panel are not visible
Same on Xenial after upgrade from Trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515308 Title: Buttons on control bar/panel are not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ardesia/+bug/1515308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1515308] Re: Buttons on control bar/panel are not visible
Purged and reinstalled: no improvement ardesia -V Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. Enabled Device in screen 2. 0x1ea3ab0: "Virtual core pointer" (Type: 0) DEBUG: Annotation window get screen-changed event DEBUG: Annotation window get configure event (1366,768) Clear screen The save point /tmp/ardesia/ardesia_project_2016-4-9_11:43:50/images/ardesia_1_vellum.png has been stored in file Acquire grab DEBUG: Annotation window get configure event (1366,768) DEBUG: Annotation window get configure event (1366,768) DEBUG: Annotation window get configure event (1366,768) DEBUG: Annotation window get configure event (1366,768) The pen with colour FFFF has been selected The pen with colour FFFF has been selected The pen with colour FFFF has been selected The pen with colour FFFF has been selected The pen with colour FFFF has been selected The pen with colour FFFF has been selected DEBUG: Annotation window get expose event Restore surface The save-point /tmp/ardesia/ardesia_project_2016-4-9_11:43:50/images/ardesia_1_vellum.png has been loaded from file The pen with colour FFFF has been selected The pen with colour FFFF has been selected The pen with colour FFFF has been selected Release grab The pen with colour FFFF has been selected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1515308 Title: Buttons on control bar/panel are not visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ardesia/+bug/1515308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1583612] Re: touch-devices stops working after insert/remove other USB device
Maybe I should have specified 'stops working' some more; in order to get touch scroll functionality we added the touch-devices flag. This works fine, but is this expected behavior? (Is this flag usually required for touch scroll?) When any USB device is then (un-)plugged the flag will stop working (touch scroll is no longer available). I will get back to you on those xinput lists, currently on mobile. Op 19 mei 2016 5:10 p.m. schreef "Chad Miller" : > Whoa, it's more weird that you have to specify touch-devices at all. > Please plug in your device, run "xinput list --long" and attach the > results with a good comment. > > Then, plug in your other device, run it again, attach with a good > comment. > > Then, remove your other device, run it again, and attach that. > > ** Changed in: chromium-browser (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1583612 > > Title: > touch-devices stops working after insert/remove other USB device > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > When using the --touch-devices= flag to enable touch > support in Chromium (or Chrome) the removal or insertion of a USB > device (which does not cause the ID of the touch device to change) > causes the functionality (finger-scrolling) to stop working until the > browser/app is restarted. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1583612/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583612 Title: touch-devices stops working after insert/remove other USB device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1583612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583612] [NEW] touch-devices stops working after insert/remove other USB device
Public bug reported: When using the --touch-devices= flag to enable touch support in Chromium (or Chrome) the removal or insertion of a USB device (which does not cause the ID of the touch device to change) causes the functionality (finger-scrolling) to stop working until the browser/app is restarted. ** Affects: chromium-browser (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/1583612 Title: touch-devices stops working after insert/remove other USB device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1583612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559308] Re: Plugging HDMI screen in causes system hang
In comment #8 it's mentioned that it is not fixed in 4.4.0-22. I hope that's a typo :-( I have a crashing 4.4.0-21 (Thinkpad 13 with an Intel N3150 processor / HD 510 Graphics) My workaround is installing kernel 4.6RC6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559308 Title: Plugging HDMI screen in causes system hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1559308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572494] Re: (xenial) installation of kde-l10n-nl ruins plasma
Importance: Undecided?! Assigned to: Unassigned?! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572494 Title: (xenial) installation of kde-l10n-nl ruins plasma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-l10n-nl/+bug/1572494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558489] Re: touchpad stopped working
I can confirm Zanna's solution for the Acer B115 apt-get install linux-image-generic-lts-xenial linux-headers-generic-lts-xenial, resulting in kernel 4.4.0-15-generic solved the problem. So the 4.4.0.-13.7 and 3.19.0-56 are not ok, the 4.4.0-15-generic #31~14.04.1 is ok -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558489 Title: touchpad stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/1558489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466034] Re: PCSC_scan doesn't find Vasco 870
The bug was reported for 1.4.18. I upgraded to Ubuntu 14.04 which ships with 1.4.22 and that version works. Thank you for your reply. I suppose version 1.4.18 is not relevant anymore, but I can't find a button how to close 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/1466034 Title: PCSC_scan doesn't find Vasco 870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-tools/+bug/1466034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558489] [NEW] touchpad stopped working
Public bug reported: with a dist-upgrade 14.04 upgraded from kernel 3.19.56 over 4.2.36 to 4.4.0 Both in 4.2 and in 4.4 the touchpad is not working. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-generic-lts-xenial 4.4.0.13.7 ProcVersionSignature: Ubuntu 4.4.0-13.29~14.04.1-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 17 11:54:18 2016 InstallationDate: Installed on 2016-03-16 (1 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: linux-meta-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-lts-xenial (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558489 Title: touchpad stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1558489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558489] Re: touchpad stopped working
We have seen the problem now with 3 of our students , all using Acer Travelmate B115. 2 running Ubuntu 14.04, one running Elementary OS. ** Also affects: linux-meta-lts-trusty (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/1558489 Title: touchpad stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-trusty/+bug/1558489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558489] Re: touchpad stopped working
I'm wrong. 3.19.0-51 is the last version I found where the touchpad works. All higher versions (including 3.19.0-56) are not ok Touchpad is SYN1B7D:01 06CB:2991 and SYN1B7D:01 06CB:74D9 I don't know where the second type number comes from. The devices are Acer B115. Acer has upgraded the firmware of the touchpads due to erratic cursor behaviour. Next time I looked, the 2991 seemed to have changed to 74D9. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558489 Title: touchpad stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lts-xenial/+bug/1558489/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477720] Re: Unity8 won't install properly
Just tested it & works for me now! Thanks! I ran: ``` sudo unity8-lxc-setup --destroy sudo unity8-lxc-setup ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1477720 Title: Unity8 won't install properly To manage notifications about this bug go to: https://bugs.launchpad.net/unity8-preview-lxc/+bug/1477720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440012] Re: The cursor disappears on the top of the screen
I am affected as well. I'm on Xubuntu 14.04LTS and I use the nvidia346.82 proprietary driver. I had tearing issues with my new NVIDIA card. To resolve it I added the following line to /etc/X11/xorg.conf : Option "metamodes" "nvidia-auto-select +0 +0 { ForceFullCompositionPipeline = On }" The tearing problems are now gone, but now my cursor disappears when I move it to the top of my screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440012 Title: The cursor disappears on the top of the screen To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1440012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482314] [NEW] The # symbol can't be used (as part of a password) in the /etc/ppp/chap-secrets file
Public bug reported: Title says it all. Sample file below would be perfectly valid: # Secrets for authentication using CHAP # clientserver secret IP addresses koen* Jekeke543 * However, in my daily password, I use a #. So the chap-secret below gives me errors: # Secrets for authentication using CHAP # clientserver secret IP addresses koen* Jekeke543# * This generates the following error lines in syslog: Aug 6 19:12:49 SERVER pppd[12738]: Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded. Aug 6 19:12:49 SERVER pppd[12738]: pptpd-logwtmp: $Version$ Aug 6 19:12:49 SERVER pppd[12738]: The remote system is required to authenticate itself Aug 6 19:12:49 SERVER pppd[12738]: but I couldn't find any suitable secret (password) for it to use to do so. Aug 6 19:12:49 SERVER pppd[12738]: (None of the available passwords would let it use an IP address.) Aug 6 19:12:49 SERVER pptpd[12737]: GRE: read(fd=6,buffer=7f2a008454a0,len=8196) from PTY failed: status = -1 error = Input/output error, usually caused by unex$ Aug 6 19:12:49 SERVER pptpd[12737]: CTRL: PTY read or GRE write failed (pty,gre)=(6,7) Aug 6 19:12:49 SERVER pptpd[12737]: CTRL: Reaping child PPP[12738] Aug 6 19:12:49 SERVER pptpd[12737]: CTRL: Client x.x.x.x control connection finished ** Affects: pptpd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482314 Title: The # symbol can't be used (as part of a password) in the /etc/ppp /chap-secrets file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pptpd/+bug/1482314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466034] Re: PCSC_scan doesn't find Vasco 870
apport information ** Tags added: apport-collected precise running-unity ** Description changed: A vasco 870 reader is not recognised. It is supposed to work: http://pcsclite.alioth.debian.org/ccid/shouldwork.html#0x1A440x0870 It is recognised on the USB-bus. I purged and reïnstalled pcsc-tools. I got another reader working (cherry) lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 1a44:0870 VASCO Data Security International Bus 001 Device 003: ID 8087:07da Intel Corp. pcsc_scan PC/SC device scanner V 1.4.18 (c) 2001-2011, Ludovic Rousseau Compiled with PC/SC lite version: 1.7.4 Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader... lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 apt-cache policy pcsc-tools pcsc-tools: Geïnstalleerd: 1.4.18-1 Kandidaat: 1.4.18-1 Versietabel: *** 1.4.18-1 0 500 http://be.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status + --- + ApportVersion: 2.0.1-0ubuntu17.9 + Architecture: amd64 + DistroRelease: Ubuntu 12.04 + InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) + MarkForUpload: True + Package: pcsc-tools 1.4.18-1 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=nl_BE:nl + TERM=xterm + PATH=(custom, no user) + LANG=nl_BE.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.13.0-54.91~precise1-generic 3.13.11-ckt20 + Tags: precise running-unity + Uname: Linux 3.13.0-54-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip fuse lpadmin plugdev sambashare sudo ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1466034/+attachment/4416252/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466034 Title: PCSC_scan doesn't find Vasco 870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-tools/+bug/1466034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466034] [NEW] PCSC_scan doesn't find Vasco 870
Public bug reported: A vasco 870 reader is not recognised. It is supposed to work: http://pcsclite.alioth.debian.org/ccid/shouldwork.html#0x1A440x0870 It is recognised on the USB-bus. I purged and reïnstalled pcsc-tools. I got another reader working (cherry) lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 1a44:0870 VASCO Data Security International Bus 001 Device 003: ID 8087:07da Intel Corp. pcsc_scan PC/SC device scanner V 1.4.18 (c) 2001-2011, Ludovic Rousseau Compiled with PC/SC lite version: 1.7.4 Using reader plug'n play mechanism Scanning present readers... Waiting for the first reader... lsb_release -rd Description:Ubuntu 12.04.5 LTS Release:12.04 apt-cache policy pcsc-tools pcsc-tools: Geïnstalleerd: 1.4.18-1 Kandidaat: 1.4.18-1 Versietabel: *** 1.4.18-1 0 500 http://be.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: pcsc-tools (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/1466034 Title: PCSC_scan doesn't find Vasco 870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-tools/+bug/1466034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1385937] Re: [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in kernel 3.16 after upgrade to Ubuntu 14.10
I added xinput --set-prop "SYN1B7D:01 06CB:2991 UNKNOWN" "Synaptics ClickPad" 1 xinput --set-prop "SYN1B7D:01 06CB:2991 UNKNOWN" "Synaptics Middle Button Timeout" 0 xinput --set-prop "SYN1B7D:01 06CB:2991 UNKNOWN" "Synaptics Soft Button Areas" 734 0 561 0 0 0 0 0 to /etc/X11/Xsession.d/95synaptic (see http://ubuntuforums.org/showthread.php?t=2274385) using kernel 3.16-36 generic on an ubuntu 14.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1385937 Title: [Acer Travelmate B115-M] Synaptic touchpad not correctly detected in kernel 3.16 after upgrade to Ubuntu 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1385937/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 373680] Re: network-manager fails periodically , on backgound networks scan?
This is still not fixed in 14.04! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/373680 Title: network-manager fails periodically , on backgound networks scan? To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/373680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
I didn't hear anything from Tim Gardner. What a shame - the fix is here and hundreds of users get a bad user experience using Ubuntu, with a constantly locking laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1094278] Re: cu doesn't connect properly to a serial console
neat confirmation - it's 2015, and this bug is from 1995. Seemingly no- one has had a need for a serial line in the last two decades :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1094278 Title: cu doesn't connect properly to a serial console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/1094278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
No, I don't know the ways to get it upstream. Suppose I could send a message to Tim Gardner. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
I can confirm that this driver solves the problem. The problem is reduced to the problem that exists in the Windows driver (being locking for 2 seconds in stead of locking for very long or forever when touching the touch pad with more then one finger) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
Thanks a lot for this! I don't have a device with me to test, so I'll test it next week. I did a diff with the current elantech file for 3.13 and there are so many differences. It's for me not possible to tell which one solves the problem. I think it is based on an older version of the file. I took the liberty to include Hans de Goede in this bug. He did all 2014 changes to the elantech driver in Ubuntu this year - I hope you don't mind Hans. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
Hi ftoledo, did you make any progress with the elantech driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1374705] Re: package grub-pc 2.02~beta2-9ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I ran do-release-upgrade -s on a server with software raid ; it failed and when I agreed to send in an error report, I was pointed to this bug as "we already know about this problem". Just came here to confirm it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1374705 Title: package grub-pc 2.02~beta2-9ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1374705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
I can confirm the behavior in Windows. The pointer works fine, but if you touch it with two fingers, it somewhat hangs for 1 or 2 seconds and then moves on. It's not really disturbing. No multitouch working, but Anyway, it's not relevant what it does in Windows. The complete locking of the pointer in Linux is really annoying. I'm happy to help testing - I'm sorry I can't help coding. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
For our machines, there is no bios update published by the manufacturer yet (don't know where else to look). I would assume that if a device loads different firmware, it is a different device, no?. comparing bios versions: our bios version MPBYT10A.90A.0029.2014.0421.1908 with dmi.bios.date: 04/21/2014 your bios version MPBYT10A.86A.0023.2014.0317.1155 with Release Date: 03/17/2014 It seems like our bios is more recent than yours. Interesting to note that they don't run trouble free on Windows either. Would there be more problems then the driver? I'll give that a try next week. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211550/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211548/+files/PciNetwork.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211549/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211545/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211547/+files/NetworkManager.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/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211541/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] [NEW] Can't select 5Ghz in infrastructure mode
Public bug reported: 5Ghz is possible in ad-hoc mode, not in infrastructure mode (option to select band is not offered) tested with kernel 3.13.0-34 - firmware 22.24.8.0 3.13.0-35 - firmware 22.24.8.0 3.17.0-999 (8 september 2014) - firmware 23.214.9.0 Very occacionally there is made a connection at 5 Ghz N (visible at network controller of access points) Hardware: Network controller: Intel Corporation Wireless 3160 (rev 83) Intel Classmate MGED101A9BE001 --- ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 DistroRelease: Ubuntu 14.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-09-15 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 10.0.0.27 dev wlan0 proto static 10.0.0.0/16 dev wlan0 proto kernel scope link src 10.0.3.80 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true Package: network-manager 0.9.8.8-0ubuntu7 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Tags: trusty Uname: Linux 3.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1e178776c-5695-4300-bea9-015fe3aff4ef 802-3-ethernet1411394595 ma 22 sep 2014 16:03:15 CEST yes no /org/freedesktop/NetworkManager/Settings/2 KC100/3 70d04365-c062-4e87-9703-dd9145221650 802-11-wireless 1410843696 di 16 sep 2014 07:01:36 CEST yes no /org/freedesktop/NetworkManager/Settings/1 ritalln beaa6895-7a45-4e0a-a215-234bccecb10e 802-11-wireless 1411396392 ma 22 sep 2014 16:33:12 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected trusty ** Tags added: apport-collected trusty ** Description changed: 5Ghz is possible in ad-hoc mode, not in infrastructure mode (option to select band is not offered) tested with kernel 3.13.0-34 - firmware 22.24.8.0 3.13.0-35 - firmware 22.24.8.0 3.17.0-999 (8 september 2014) - firmware 23.214.9.0 Very occacionally there is made a connection at 5 Ghz N (visible at network controller of access points) Hardware: Network controller: Intel Corporation Wireless 3160 (rev 83) Intel Classmate MGED101A9BE001 + --- + ApportVersion: 2.14.1-0ubuntu3.4 + Architecture: amd64 + DistroRelease: Ubuntu 14.04 + IfupdownConfig: + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback + InstallationDate: Installed on 2014-09-15 (7 days ago) + InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) + IpRoute: + default via 10.0.0.27 dev wlan0 proto static + 10.0.0.0/16 dev wlan0 proto kernel scope link src 10.0.3.80 metric 9 + NetworkManager.state: + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true + Package: network-manager 0.9.8.8-0ubuntu7 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=nl_BE:nl + TERM=xterm + PATH=(custom, no user) + LANG=nl_BE.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 + Tags: trusty + Uname: Linux 3.13.0-35-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + nmcli-con: + NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + Wired connection 1e178776c-5695-4300-bea9-015fe3aff4ef 802-3-ethernet1411394595 ma 22 sep 2014 16:03:15 CEST yes no /org/freedesktop/NetworkManager/Settings/2 + KC100/3 70d04365-c062-4e87-9703-dd9145221650 802-11-wireless 1410843696 di 16 sep 2014 07:01:36 CEST yes no
[Bug 1372496] NetDevice.wlan0.txt
apport information ** Attachment added: "NetDevice.wlan0.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211546/+files/NetDevice.wlan0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211543/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] NetDevice.eth0.txt
apport information ** Attachment added: "NetDevice.eth0.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211544/+files/NetDevice.eth0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211542/+files/IpAddr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1372496] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1372496/+attachment/4211540/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372496 Title: Can't select 5Ghz in infrastructure mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1372496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] Re: Elantech touchpad locks cursor when touching with 2 or more fingers
The problem is exactly the same with the mainline kernel (3.17-rc5) ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1369684] [NEW] Elantech touchpad locks cursor when touching with 2 or more fingers
Public bug reported: Running Ubuntu 14.04.1, Unity desktop, kernel 3.13.0-35 generic on Intel Classmate, MG Pupil 109 The touchpad is identified in dmesg as [1.539535] mousedev: PS/2 mouse device common for all mice [2.528608] psmouse serio4: elantech: assuming hardware version 3 (with firmware version 0x354f01) [2.541184] psmouse serio4: elantech: Synaptics capabilities query result 0x39, 0x16, 0x09. The cursor locks when you touch the touchpad with 2 or more fingers. The only way I found to get it loose is reboot or suspend and resume. modprobe -r psmouse modprobe psmouse doesn' t work, also not with proto=auto In systemsettings I disabled 2 finger scrolling without result In dmesg I see messages like "psmouse serio4: Touchpad at isa0060/serio4/input0 lost synchronization, throwing 5 bytes away during normal operation". The number of bytes can be 4 too. When the cursor locks up, I don't see such a message. Nothing is reported in dmesg. Doing some research, I've learned that the touchpad should support multi touch. Off course that doesn't work, since touching the pad with more fingers makes it lock. Any help much appreciated. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-35-generic 3.13.0-35.62 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: test 1474 F pulseaudio Date: Mon Sep 15 20:00:38 2014 HibernationDevice: RESUME=UUID=6f2e0704-c6a4-4f89-b357-c8e46ff9d0ec InstallationDate: Installed on 2014-09-15 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Intel Corporation Intel powered classmate PC ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic.efi.signed root=UUID=40917190-7ade-42d5-a5d2-91f8c497278e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-35-generic N/A linux-backports-modules-3.13.0-35-generic N/A linux-firmware 1.127.5 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: MPBYT10A.90A.0029.2014.0421.1908 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Intel powered classmate PC dmi.board.vendor: Intel Corporation dmi.board.version: Clamshell dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 11 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrMPBYT10A.90A.0029.2014.0421.1908:bd04/21/2014:svnIntelCorporation:pnIntelpoweredclassmatePC:pvrClamshell:rvnIntelCorporation:rnIntelpoweredclassmatePC:rvrClamshell:cvnIntelCorporation:ct11:cvr0.1: dmi.product.name: Intel powered classmate PC dmi.product.version: Clamshell dmi.sys.vendor: Intel Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug staging trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1369684 Title: Elantech touchpad locks cursor when touching with 2 or more fingers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1369684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1343972] Re: otrs 2 upgrade from Ubuntu 12.04 to 14.04 fails - otrs database upgrade incomplete ?
extra info this is the initial error during release upgrade ⤠Configuring otrs2 â â â â An error occurred while upgrading the database: â â /usr/share/dbconfig-common/scripts/otrs2/upgrade/mysql/3.2.1 exited with â non-zero status and ending with A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Please report this bug in a browser at http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug and attach the files in /var/log/dist-upgrade/ to the bug report. installArchives() failed ** Attachment added: "main.log" https://bugs.launchpad.net/ubuntu/+source/otrs2/+bug/1343972/+attachment/4155585/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1343972 Title: otrs 2 upgrade from Ubuntu 12.04 to 14.04 fails - otrs database upgrade incomplete ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/otrs2/+bug/1343972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs