[Touch-packages] [Bug 1969856] [NEW] bash --version does not correspond to package name
Public bug reported: While investigating a potentially compromised system, I ran `bash --version` and got the following: `GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)` Disquieting, given that I had just installed a package named `bash_4.4.18-2ubuntu1.3_amd64.deb`. I downloaded the `.deb` archive and, upon extracting it, checked its hash (SHA256) against the instance on my path. They were the same (`15d4469eb3da716fefcc0c395a5b1d1657ad0555ec3ae623e727bb0dfcee19cf`)--indicating, presumably, that I was running whatever version was in the `.deb` I'd just downloaded. Why is the version reported by the binary different from the version used to denote the package? ** Affects: bash (Ubuntu) Importance: Undecided Status: New ** Description changed: While investigating a potentially compromised system, I ran `bash --version` and got the following: `GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)` Disquieting, given that I had just installed a package named `bash_4.4.18-2ubuntu1.3_amd64.deb`. I downloaded the `.deb` archive and, upon extracting it, checked its hash (SHA256) against the instance on my path. They were the same - (`15d4469eb3da716fefcc0c395a5b1d1657ad0555ec3ae623e727bb0dfcee19cf`). + (`15d4469eb3da716fefcc0c395a5b1d1657ad0555ec3ae623e727bb0dfcee19cf`)--indicating, + presumably, that I was running whatever version was in the `.deb` I'd + just downloaded. Why is the version reported by the binary different from the version used to denote the package? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1969856 Title: bash --version does not correspond to package name Status in bash package in Ubuntu: New Bug description: While investigating a potentially compromised system, I ran `bash --version` and got the following: `GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)` Disquieting, given that I had just installed a package named `bash_4.4.18-2ubuntu1.3_amd64.deb`. I downloaded the `.deb` archive and, upon extracting it, checked its hash (SHA256) against the instance on my path. They were the same (`15d4469eb3da716fefcc0c395a5b1d1657ad0555ec3ae623e727bb0dfcee19cf`)--indicating, presumably, that I was running whatever version was in the `.deb` I'd just downloaded. Why is the version reported by the binary different from the version used to denote the package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1969856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915091] Re: Nautilus shows LXD storage pool in sidebar
Could it be relevant that /var/snap is a bind-mount? To clarify, I have a relatively small root partition and a large data partition, and bind- mount various directories that require a lot of space -- like /var/snap, /var/lib/snapd, /home -- from the data partition. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1915091 Title: Nautilus shows LXD storage pool in sidebar Status in lxc package in Ubuntu: New Bug description: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1915091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1915091] Re: Nautilus shows LXD storage pool in sidebar
Thanks for following up. Here it is. ** Attachment added: "mountinfo" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1915091/+attachment/5462047/+files/mountinfo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1915091 Title: Nautilus shows LXD storage pool in sidebar Status in lxc package in Ubuntu: New Bug description: I recently set up LXD 4.11 on Ubuntu 20.04 with a file-backed btrfs storage pool called "default". Now Nautilus shows a "default" device in the sidebar despite the loop device not being intended for users to directly interact with. System: Ubuntu 20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1915091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 962082] Re: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6236 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/962082 Title: Profiles that require duplex audio like Head Set (HSP) and Hands Free (HFP) do not work on machines with Broadcom BCM20702A0 Bluetooth chips Status in HWE Next: Fix Released Status in bluez package in Ubuntu: Fix Released Bug description: This problem seems to occur on every device that uses the BCM20702A0 Bluetooth hardware. How to reproduce: (1) Pair a bluetooth headset with a machine equipped with a BCM20702A0. (2) Activate the device. Usually there is a button on the headset you should press to notify the bluetooth stack that you're ready to use the device. This creates SCO link and the plumbs the audio components. (3) Open the sound settings tool and select the bluetooth device under the "Input" and "Output" tabs. Under each tab you should see a table with an entry that has a headset icon on the left with the bluetooth device name to the right. This is the item to select. Now, everything should be configured so that you can use your bluetooth device to hear and record audio. Test this by: Testing Input: (1) In the sound settings tool, select the "Input" tab. (2) Make sure the "Input Volume" is not muted and the scale widget is not set to zero. (3) Make sounds into the headset mic -- you should see the "Input Level" bar raise. Testing Output: In the same program: (1) Select the "Hardware" tab. (2) In the box labeled "Choose a device to configure", select your bluetooth device. (3) A combobox should appear at the bottom of the window labeled "Settings for the selected device". Choose "Telephony Duplex (HSP/HFP)". (4) Now click on the "Test Speakers" button to the right. (5) Run speaker test. You should hear a sound. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/962082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860620] [NEW] ubuntu-desktop-minimal should not depend on mysql libs
Public bug reported: After upgrading to 20.04 I decided to remove packages that I don't need or use. I was surprised to find that mysql client, server and common packages were installed, as I could not remember having installed mysql -- I don't use it or develop for it... When I removed them, ubuntu-desktop-minimal went along for the ride: c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common mysql-server-core-5.7 Reading package lists... Done Building dependency tree Reading state information... Done Package 'mysql-client-core-5.7' is not installed, so not removed Package 'mysql-server-core-5.7' is not installed, so not removed The following package was automatically installed and is no longer required: libgsound0 Use 'sudo apt autoremove' to remove it. The following packages will be REMOVED: colord* gnome-control-center* libmysqlclient21* libsane* libsnmp30* mysql-common* ubuntu-desktop-minimal* 0 upgraded, 0 newly installed, 7 to remove and 0 not upgraded. After this operation, 28.4 MB disk space will be freed. (Reading database ... 381127 files and directories currently installed.) Removing ubuntu-desktop-minimal (1.443) ... Removing gnome-control-center (1:3.34.1-1ubuntu3) ... Removing colord (1.4.4-1ubuntu1) ... Removing libsane:amd64 (1.0.27-3.2ubuntu3) ... Removing libsnmp30:amd64 (5.7.3+dfsg-5ubuntu6) ... Removing libmysqlclient21:amd64 (8.0.18-0ubuntu5) ... Removing mysql-common (5.8+1.0.5ubuntu2) ... Processing triggers for mime-support (3.64ubuntu1) ... Processing triggers for gnome-menus (3.32.0-1ubuntu1) ... Processing triggers for libglib2.0-0:amd64 (2.63.3-1) ... Processing triggers for libc-bin (2.30-0ubuntu3) ... Processing triggers for man-db (2.9.0-2) ... Processing triggers for dbus (1.12.16-2ubuntu2) ... Processing triggers for udev (244-3ubuntu1) ... Processing triggers for desktop-file-utils (0.24-1ubuntu1) ... (Reading database ... 380812 files and directories currently installed.) Purging configuration files for mysql-common (5.8+1.0.5ubuntu2) ... Purging configuration files for colord (1.4.4-1ubuntu1) ... And, reinstalling ubuntu-desktop-minimal wants to brings them back, even with recommends and suggests turned off: c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install- --no-install-recommends --no-install-suggests c@slate:~$ sudo apt install ubuntu-desktop-minimal --no-install-recommends --no-install-suggests Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common Suggested packages: colord-sensor-argyll gnome-user-share realmd libcanberra-gtk-module hplip Recommended packages: gnome-online-accounts gnome-control-center-faces rygel | rygel-tracker sane-utils firefox hplip The following NEW packages will be installed: colord gnome-control-center libmysqlclient21 libsane libsnmp30 mysql-common ubuntu-desktop-minimal 0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/6,114 kB of archives. After this operation, 28.4 MB of additional disk space will be used. Do you want to continue? [Y/n] This seems really wrong... and looks like a transitive dependency, as I don't see it in apt-get showpkg ubuntu-desktop-minimal. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-desktop-minimal 1.443 ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 Uname: Linux 4.15.0-74-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair binder_linux ashmem_linux ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 22 19:26:53 2020 InstallationDate: Installed on 2018-08-26 (514 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to focal on 2020-01-23 (0 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1860620 Title: ubuntu-desktop-minimal should not depend on mysql libs Status in ubuntu-meta package in Ubuntu: New Bug description: After upgrading to 20.04 I decided to remove packages that I don't need or use. I was surprised to find that mysql client, server and common packages were installed, as I could not remember having installed mysql -- I don't use it or develop for it... When I removed them, ubuntu-desktop-minimal went along for the ride: c@slate:~$ sudo apt-get purge -y mysql-client-core-5.7 mysql-common mysql-server-core-5.7 Reading package lists... Done
[Touch-packages] [Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /
nicely researched and documented bug. Why not fixed three years later? I
hit this (or seeminly this same bug) doing an install of server 18.04.2
yesterday. I needed to enable ssh for remote install and lowered debconf
priority. This gave me some good clues I'll now try some work-arounds.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1582899
Title:
in-target: mkinitramfs: failed to determine device for /
Status in base-installer package in Ubuntu:
Invalid
Status in initramfs-tools package in Ubuntu:
Invalid
Status in live-installer package in Ubuntu:
Confirmed
Bug description:
Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
server ISO installer failed due to being unable to configure linux-
image-4.4.0-21-generic.
Lots of diagnostics and one SSH remote session later we seem to have
narrowed it down to the installer.
At the installer's boot menu the F6 option "Expert mode" is chosen.
During initial ram file-system creation (after the kernel image is installed)
the /dev/ file-system is not mounted in /target/ and therefore
the initramfs-tools/hook-functions::dep_add_modules_mount() cannot match
the mount device of "/" (in this case /dev/sda3) with any node under /dev/
which only contains static entries.
Cause appears to be that live-installer.postinst has the crucial step
calling library.sh:setup_dev() commented out:
#waypoint 1 setup_dev
OS=linux
setup_dev() calls setup_dev_${OS}
setup_dev_linux() mounts procfs and devtmpfs into /target/
Originally the cause of the error message appeared to be that the
symlink names in /dev/disk/by-uuid/ haven't been updated after the
partitioning stage if there were pre-existing partitions and file-
systems on the install device, *and* the sysadmin chose to format the
existing partitions when selecting mountpoints.
In this case a hardware RAID device presents:
/dev/sda1 (/boot/)
/dev/sda2 (swap)
/dev/sda3 (/)
From the shell I noticed:
root@tmpstorage:/# ll /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 May 17 19:39 130e4419-4bfd-46d2-87f9-62e5379bf591
-> ../../sda1
lrwxrwxrwx 1 root root 10 May 17 19:39 127d3fa1-c07c-48e4-9e26-1b926d37625c
-> ../../sda3
lrwxrwxrwx 1 root root 10 May 17 19:39 78b88456-2b0b-4265-9ed2-5db61522d887
-> ../../sda2
lrwxrwxrwx 1 root root 9 May 17 19:39 2016-04-20-22-45-29-00 -> ../../sr1
drwxr-xr-x 6 root root 120 May 17 19:39 ..
drwxr-xr-x 2 root root 120 May 17 19:39 .
root@tmpstorage:/# blkid /dev/sda*
/dev/sda: PTUUID="a84e60fd" PTTYPE="dos"
/dev/sda1: UUID="61365714-8ff7-47a2-8035-8aed9e3191a6" TYPE="ext4"
PARTUUID="a84e60fd-01"
/dev/sda2: UUID="78b88456-2b0b-4265-9ed2-5db61522d887" TYPE="swap"
PARTUUID="a84e60fd-02"
/dev/sda3: UUID="75f68451-9472-47c7-9efc-ed032bfa9987" TYPE="ext4"
PARTUUID="a84e60fd-03"
More details to follow.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 387957] Re: Improve Save As Dialog Box (focus issues)
I would like to note that this is still/again a problem in 2019 on Ubuntu 19.04. (I didn't notice it on 18.10, but maybe I just missed it.) I agree with pretty much everything that gdi2k wrote above, particularly that the following seemingly simple change would remove a significant annoyance for anyone who occasionally uses the mouse without at all detracting from keyboard-only functionality: "Reverting focus to the Name field if a folder is double-clicked using the mouse (familiar Windows behaviour, which does not impact keyboard- using advanced users in any way)." -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/387957 Title: Improve Save As Dialog Box (focus issues) Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: The save dialog box has the irritating habit of not focusing on the file name area once I have browsed to the location where I would like to save my document. This is done better in Windows. There are two main scenarios when saving a document where this behaviour annoys: Scanario 1 - Browsing to save location by double-clicking: 1. File -> Save As (to bring up the "Save" dialog box). 2. Double click on the folder in which you would like to save the document. 3. Notice that the focus is now in the folder list area, not on the file name area. 4. I now have to click in the file name area to be able to name my document. In Windows, the focus is returned immediately to the file name box once a folder is double clicked, so the name can be typed and the document saved in one step. Scenario 2 - Browsing save location using the keyboard (find as you type): 1. File -> Save As (to bring up the "Save" dialog box). 2. Click on the folder area so that folder names can be typed to find them. Hit enter to enter desired folder. 3. Within the folder, step 2 can be repeated for subfolders indefinitely. 4. Once the desired location has been reached, the user must use the mouse click in the file name area to name the file before saving. In Windows, when using find as you type, although focus is retained by the folder area when entering a lower folder level (so that you can browse to another level using the keyboard if desired), jumping to the file name box is simply a matter of pressing tab ONCE. In Ubuntu, I have to reverse tab (shift-tab) around 10 times to get back to the file name box at the top of the screen, or use the mouse - most annoying. Solutions (copy the Windows behaviour): 1. If a folder is double clicked with the mouse, the focus should jump back to the file name box. 2. If a folder is entered into by pressing enter (on the keyboard), focus should remain in the folder area, but the file name box should only be a single tab away. I understand that solution 2 is problematic in that tabbing would ordinarily jump to the next element (usually the "file type" dropdown), not back to the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/387957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()
I am getting the same issue, same error. Crashes once I reach the
progress screen of 18.04 installation.
Syslog report:
..
Apr 28 20:26:54 ubuntu localechooser: info: Set debian-installer/locale =
'en_CA.UTF-8'
Apr 28 20:26:54 ubuntu localechooser: info: System locale
(debian-installer/locale) = 'en_CA.UTF-8'
Apr 28 20:26:54 ubuntu ubiquity: /usr/lib/ubiquity/localechooser/localechooser:
910: [: C.UTF-8: unexpected operator
Apr 28 20:26:54 ubuntu ubiquity[3103]: debconffilter_done: ubi-timezone
(current: ubi-timezone)
Apr 28 20:26:54 ubuntu ubiquity[3103]: Step_before = stepLocation
Apr 28 20:26:54 ubuntu partman: mke2fs 1.44.1 (24-Mar-2018)
Apr 28 20:26:54 ubuntu ubiquity[3103]: switched to page usersetup
Apr 28 20:26:54 ubuntu clear_partitions: Considering /home,/dev/nvme0n1p6.
Apr 28 20:26:54 ubuntu kernel: [ 100.161039] EXT4-fs (nvme0n1p6): mounted
filesystem with ordered data mode. Opts: (null)
Apr 28 20:26:54 ubuntu kernel: [ 100.278116] EXT4-fs (nvme0n1p7): mounted
filesystem with ordered data mode. Opts: errors=remount-ro
Apr 28 20:26:54 ubuntu kernel: [ 100.296127] EXT4-fs (nvme0n1p6): mounted
filesystem with ordered data mode. Opts: (null)
Apr 28 20:26:55 ubuntu ubiquity: File descriptor 3 (pipe:[67210]) leaked on pvs
invocation. Parent PID 18458: /bin/sh
Apr 28 20:26:55 ubuntu ubiquity[3103]: debconffilter_done:
ubiquity.components.partman_commit (current: ubi-usersetup)
Apr 28 20:26:55 ubuntu /install.py: keeping packages due to preseeding:
icedtea6-plugin openoffice.org
Apr 28 20:26:55 ubuntu /install.py: keeping language packs for: en_US.UTF-8
Apr 28 20:26:56 ubuntu ubiquity: W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/bionic/InRelease Could not resolve
'archive.ubuntu.com'
Apr 28 20:26:56 ubuntu ubiquity: W: Failed to fetch
http://security.ubuntu.com/ubuntu/dists/bionic-security/InRelease Could not
resolve 'security.ubuntu.com'
Apr 28 20:26:56 ubuntu ubiquity: W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease Could not
resolve 'archive.ubuntu.com'
Apr 28 20:26:56 ubuntu ubiquity: W: Some index files failed to download. They
have been ignored, or old ones used instead.
Apr 28 20:26:56 ubuntu ubiquity: W: --force-yes is deprecated, use one of the
options starting with --allow instead.
Apr 28 20:27:13 ubuntu ubiquity[3103]: debconffilter_done: ubi-usersetup
(current: ubi-usersetup)
Apr 28 20:27:13 ubuntu ubiquity[3103]: Step_before = stepUserInfo
Apr 28 20:27:14 ubuntu kernel: [ 119.884166] do_trap: 26 callbacks suppressed
Apr 28 20:27:14 ubuntu kernel: [ 119.884168] traps: ubiquity[3103] trap int3
ip:7ff0a1502c41 sp:7ffe0681d810 error:0 in
libglib-2.0.so.0.5600.1[7ff0a14b1000+113000]
Apr 28 20:27:25 ubuntu /install.py: Exception during installation:
Apr 28 20:27:25 ubuntu /install.py: Traceback (most recent call last):
Apr 28 20:27:25 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 765, in
Apr 28 20:27:25 ubuntu /install.py: install.run()
Apr 28 20:27:25 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 135, in run
Apr 28 20:27:25 ubuntu /install.py: self.copy_all()
Apr 28 20:27:25 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 513, in copy_all
Apr 28 20:27:25 ubuntu /install.py: self.db.progress('SET', 10 +
copy_progress)
Apr 28 20:27:25 ubuntu /install.py: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Apr 28 20:27:25 ubuntu /install.py: lambda *args, **kw:
self.command(command, *args, **kw))
Apr 28 20:27:25 ubuntu /install.py: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Apr 28 20:27:25 ubuntu /install.py: status = int(status)
Apr 28 20:27:25 ubuntu /install.py: ValueError: invalid literal for int() with
base 10: ''
Apr 28 20:27:25 ubuntu /install.py:
Apr 28 20:27:25 ubuntu nautilus-autostart.desktop[2103]: Trace/breakpoint trap
(core dumped)
Apr 28 20:27:31 ubuntu dbus-daemon[1666]: [session uid=999 pid=1666] Activating
via systemd: service name='org.gnome.Terminal'
unit='gnome-terminal-server.service' requested by ':1.81' (uid=999 pid=18835
comm="/usr/bin/gnome-terminal.real " label="unconfined")
Apr 28 20:27:31 ubuntu systemd[1622]: Starting GNOME Terminal Server...
Apr 28 20:27:31 ubuntu dbus-daemon[1666]: [session uid=999 pid=1666]
Successfully activated service 'org.gnome.Terminal'
Apr 28 20:27:31 ubuntu systemd[1622]: Started GNOME Terminal Server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
ubiquity crashed with signal 5 in _XEventsQueued()
Status in glib2.0 package in Ubuntu:
Incomplete
Status in ubiquity package in Ubuntu:
Triaged
Status in glib2.0 source package in Bionic:
Incomplete
Status in ubiquity source package in Bionic:
Triaged
Bug description:
Crashed in a VM in the middle of installation. The host is
[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
For any poor soul who wanders here, here is the best known workaround for this issue I've seen to date: 22-09-2016 15:23:18 < stgraber!~stgraber@ubuntu/member/stgraber: cmars: if you mask (systemctl mask) the systemd units related to binfmt (systemctl -a | grep binfmt) and reboot, then the problem is gone for good. This is related to systemd's use of automount and not to binfmt- misc (which just ships a bunch of binfmt hooks) FYI, I think this will disable binfmt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630884] [NEW] Xorg freeze; mouse moves, but no mouse click or keyboard response
Public bug reported: I've encountered this issue on several fresh installations of Ubuntu 16.04.1 on different machines. Typically, the machine becomes unresponsive to the keyboard presses or to mouse clicks; however, it does respond to mouse movement. I am unable to open a text console to manipulate processes, and I am forced to hard restart the machine. During the most recent instance, I noticed that the mouse cursor would change in response to its location on the screen while The issue most often occurs about 3-5 minutes after Chromium has been opened, but it has also occurred without Chromium being installed. Moreover, it as occurred while using Xfce and GNOME 3 and while using open source and proprietary video drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Oct 6 00:04:47 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GF119M [NVS 4200M] [10de:1056] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF119M [NVS 4200M] [1028:0493] InstallationDate: Installed on 2016-10-06 (0 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=3c7f4e14-5817-44b1-adbb-1666f8c29348 ro SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/04/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A23 dmi.board.asset.tag: TSI3251 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.asset.tag: TSI3251 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA23:bd01/04/2016:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1630884 Title: Xorg freeze; mouse moves, but no mouse click or keyboard response Status in xorg package in Ubuntu: New Bug description: I've encountered this issue on several fresh installations of Ubuntu 16.04.1 on different machines. Typically, the machine becomes unresponsive to the keyboard presses or to mouse clicks; however, it does respond to mouse movement. I am unable to open a text console to manipulate processes, and I am forced to hard restart the machine. During the most recent instance, I noticed that the mouse cursor would change in response to its location on the screen while The issue most often occurs about 3-5 minutes after Chromium has been opened, but it has also occurred without Chromium being installed. Moreover, it as occurred while using Xfce and GNOME 3 and while using open source and proprietary video drivers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Thu Oct 6 00:04:47 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu
[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
I apt purge'ed binfmt-support from my system and I'm still able to comment here :) We'll see if this fixes the issue. If it does, why was it even installed on my system by default to begin with? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
Still seeing this on xenial enough that I've written a script to perform the umounting when LXD gets stuck. Do I even need binfmt_misc on my system? Can I just remove it or would that break something? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1572679] Re: screen flickering and tearing kwin nouveau kubuntu 16.04
I am dealing with the same flickering issue as described above, and am using the same hardware. If there is any information I can provide, please let me know. Casey -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1572679 Title: screen flickering and tearing kwin nouveau kubuntu 16.04 Status in xorg package in Ubuntu: New Bug description: The bug I see on my Dell D830 (8GB RAM, Nvidia G86M [Quadro NVS 140M] (rev a1)) with nouveau driver using Kubuntu 16.04. After login everything seems to work fine for roughly 2 minutes. After that flickering and tearing starts (when moving windows around with the mouse) and gets more intense until the screen is full of "color- blobs" (which means: one cannot see anything anymore). Starting a flash movie in Firefox provokes immediate tearing and flickering. Restarting the kwin compositor helps - for another 2 minutes, then the whole problem starts to catch on momentum again. I tried everything mentioned here: http://askubuntu.com/questions/672007/flickering-in-kde-plasma-5-4 the only thing that helps for a longer period of time is turning off compositing completely. I am unsure where to further look for the problem: Is it kwin? xorg? nouveau? All of them? Whatever? The logs I checked (xorg, syslog, dmesg etc.) contain nothing that I can make sense of. I'd appreciate any hint to where (and: what) to look (for) and which more specific information to collect ... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 20 19:22:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-22 (28 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160320) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CurrentDesktop: KDE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: kubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed bcmwl, 6.30.223.248+bdcom, 4.4.0-24-generic, x86_64: installed vboxhost, 5.0.22, 4.4.0-22-generic, x86_64: installed vboxhost, 5.0.22, 4.4.0-24-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation G86M [Quadro NVS 140M] [10de:0429] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G86M [Quadro NVS 140M] [1028:01fe] InstallationDate: Installed on 2016-05-02 (46 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. Latitude D830 NonfreeKernelModules: wl Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic root=UUID=5f4a29b4-76d7-473a-948b-6e916e79e20f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Tags: xenial kubuntu Uname: Linux 4.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark _MarkForUpload: True dmi.bios.date: 07/21/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0UY141 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd07/21/2008:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1572679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://laun
[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
When is this going to be fixed upstream? I'm having to remount on the host and restart containers quite often. I can't imagine this will be a good user experience for new LXD users on xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555760] Re: Too many levels of symbolic links /proc/sys/fs/binfmt_misc
I'm not seeing the symbolic links error, but I am seeing this when trying to start a trusty container on xenial: https://github.com/lxc/lxd/issues/1836 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1555760 Title: Too many levels of symbolic links /proc/sys/fs/binfmt_misc Status in binfmt-support package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Bug description: At first I thought this was an LXD issue, but it turns out the issue is in systemd https://github.com/lxc/lxd/issues/1727#issuecomment-194416558 ls -l /proc/sys/fs/binfmt_misc fails with error: Too many levels of symbolic links I restarted binfmt manually by running: sudo /usr/sbin/update-binfmts --disable sudo /usr/sbin/update-binfmts --enable I think using systemd to do this would have also worked: sudo service binfmt-support restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/1555760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
I can work around this with my custom build of pcscd with udev disabled, but it seems that this issue will still affect Debian and Ubuntu users who install the package. Can we mark this bug as Confirmed, since my symptoms are so similar to the descriptions in the Debian bug[1] you've linked above? Anything else I can do to help? Thanks, Casey [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812087 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
Recompiling with --disable-libudev gets rid of the 100% CPU problem and I can still use my smartcard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
Here's a core dump with the corresponding pcscd binary I built from source, which was taken in the above-mentioned gdb session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
** Attachment added: "pcscd binary and core dump" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4588521/+files/pcscd-core-bin.tar.bz2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
Ran it with gdb, reproduced, and then interrupted when it started consuming 100% CPU: Thread 1 "pcscd" received signal SIGINT, Interrupt. 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00411cfd in ProcessEventsServer (pdwClientID=pdwClientID@entry=0x7fffe49c) at winscard_msg_srv.c:223 #2 0x004037f9 in SVCServiceRunLoop () at pcscdaemon.c:128 #3 main (argc=, argv=) at pcscdaemon.c:685 (gdb) info threads Id Target Id Frame * 1Thread 0x77fb9740 (LWP 18298) "pcscd" 0x774e2853 in select () from /lib/x86_64-linux-gnu/libc.so.6 2Thread 0x76fb0700 (LWP 18302) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 3Thread 0x767af700 (LWP 18303) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 4Thread 0x75fae700 (LWP 18304) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 5Thread 0x757ad700 (LWP 18305) "pcscd" 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 2 [Switching to thread 2 (Thread 0x76fb0700 (LWP 18302))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x76fc064c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 3 [Switching to thread 3 (Thread 0x767af700 (LWP 18303))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x76fc064c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #3 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 4 [Switching to thread 4 (Thread 0x75fae700 (LWP 18304))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x76fb9bc5 in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #2 0x76fbab53 in libusb_handle_events_timeout_completed () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #3 0x76fbac3f in libusb_handle_events () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 #4 0x771d64bc in ?? () from /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so #5 0x771d0b83 in ?? () from /usr/lib/pcsc/drivers/ifd-ccid.bundle/Contents/Linux/libccid.so #6 0x004064db in EHStatusHandlerThread (rContext=0x61f010) at eventhandler.c:464 #7 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #8 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) thread 5 [Switching to thread 5 (Thread 0x757ad700 (LWP 18305))] #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x774e09ed in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x0040eeaa in poll (__timeout=-1, __nfds=1, __fds=0x757aced0) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46 #2 HPEstablishUSBNotifications (arg=0x649910) at hotplug_libudev.c:624 #3 0x777b666a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x774ec01d in clone () from /lib/x86_64-linux-gnu/libc.so.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
Oh, here's /var/log/syslog from unplugging and replugging in my camera. I Ctrl-C killed pcscd after it went to 100% each time. pcscd segfaulted. Mar 4 12:04:11 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug level=debug Mar 4 12:04:13 mawhrin-skel kernel: [14604.513268] usb 3-1: USB disconnect, device number 6 Mar 4 12:04:13 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:04:13 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. Mar 4 12:04:13 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:04:13 mawhrin-skel laptop_mode[17937]: Laptop mode Mar 4 12:04:13 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:04:13 mawhrin-skel laptop_mode[17937]: enabled, not active [unchanged] Mar 4 12:04:53 mawhrin-skel systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... Mar 4 12:04:53 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:04:53 mawhrin-skel systemd[1]: Started Laptop Mode Tools - Battery Polling Service. Mar 4 12:04:53 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:04:53 mawhrin-skel laptop_mode[17997]: Laptop mode Mar 4 12:04:53 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:04:53 mawhrin-skel laptop_mode[17997]: enabled, not active [unchanged] Mar 4 12:04:53 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. Mar 4 12:05:01 mawhrin-skel CRON[18049]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Mar 4 12:05:17 mawhrin-skel kernel: [14668.018203] pcscd[17921]: segfault at 7f447696064c ip 7f447696064c sp 7f447694fed0 error 14 in libc-2.21.so[7f4476d85000+1c] Mar 4 12:05:20 mawhrin-skel pcscd: debuglog.c:289:DebugLogSetLevel() debug level=debug Mar 4 12:05:30 mawhrin-skel kernel: [14681.443071] usb 3-1: new high-speed USB device number 7 using xhci_hcd Mar 4 12:05:31 mawhrin-skel kernel: [14681.844167] usb 3-1: New USB device found, idVendor=046d, idProduct=0825 Mar 4 12:05:31 mawhrin-skel kernel: [14681.844175] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=2 Mar 4 12:05:31 mawhrin-skel kernel: [14681.844179] usb 3-1: SerialNumber: DD923C60 Mar 4 12:05:31 mawhrin-skel kernel: [14681.845342] uvcvideo: Found UVC 1.00 device (046d:0825) Mar 4 12:05:31 mawhrin-skel kernel: [14681.937806] input: UVC Camera (046d:0825) as /devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/input/input19 Mar 4 12:05:32 mawhrin-skel kernel: [14683.279489] usb 3-1: set resolution quirk: cval->res = 384 Mar 4 12:05:32 mawhrin-skel mtp-probe: checking bus 3, device 7: "/sys/devices/pci:00/:00:14.0/usb3/3-1" Mar 4 12:05:32 mawhrin-skel mtp-probe: bus: 3, device: 7 was not an MTP device Mar 4 12:05:32 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:05:32 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. Mar 4 12:05:32 mawhrin-skel systemd[1]: message repeated 3 times: [ Reloaded Laptop Mode Tools.] Mar 4 12:05:32 mawhrin-skel systemd-udevd[18064]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99. Mar 4 12:05:32 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:05:32 mawhrin-skel laptop_mode[18067]: Laptop mode Mar 4 12:05:32 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:05:32 mawhrin-skel laptop_mode[18067]: enabled, not active [unchanged] Mar 4 12:05:32 mawhrin-skel pulseaudio[6720]: [pulseaudio] source.c: Default and alternate sample rates are the same. Mar 4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Supervising 3 threads of 1 processes of 1 users. Mar 4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Successfully made thread 18136 of process 6720 (n/a) owned by '1000' RT at priority 5. Mar 4 12:05:32 mawhrin-skel rtkit-daemon[6721]: Supervising 4 threads of 1 processes of 1 users. Mar 4 12:07:09 mawhrin-skel kernel: [14780.487379] pcscd[18060]: segfault at 7f74fedfa64c ip 7f74fedfa64c sp 7f74fede9ed0 error 14 in libc-2.21.so[7f74ff21f000+1c] Mar 4 12:07:43 mawhrin-skel systemd[1]: Starting Laptop Mode Tools - Battery Polling Service... Mar 4 12:07:43 mawhrin-skel systemd[1]: Reloading Laptop Mode Tools. Mar 4 12:07:43 mawhrin-skel systemd[1]: Started Laptop Mode Tools - Battery Polling Service. Mar 4 12:07:43 mawhrin-skel laptop-mode: Laptop mode Mar 4 12:07:43 mawhrin-skel laptop_mode[18161]: Laptop mode Mar 4 12:07:43 mawhrin-skel laptop-mode: enabled, not active [unchanged] Mar 4 12:07:43 mawhrin-skel laptop_mode[18161]: enabled, not active [unchanged] Mar 4 12:07:43 mawhrin-skel systemd[1]: Reloaded Laptop Mode Tools. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
It starts consuming 100% CPU after this: 02341452 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed 0217 hotplug_libudev.c:619:HPEstablishUSBNotifications() 0068 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed 0149 hotplug_libudev.c:619:HPEstablishUSBNotifications() 2713 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed 0152 hotplug_libudev.c:619:HPEstablishUSBNotifications() 00020583 hotplug_libudev.c:642:HPEstablishUSBNotifications() USB Device removed 0143 hotplug_libudev.c:619:HPEstablishUSBNotifications() 02634822 ifdhandler.c:1143:IFDHPowerICC() action: PowerDown, usb:1050/0115:libudev:1:/dev/bus/usb/003/002 (lun: 0) 0091 eventhandler.c:479:EHStatusHandlerThread() powerState: POWER_STATE_UNPOWERED or this: 05000574 ifdhandler.c:1143:IFDHPowerICC() action: PowerDown, usb:1050/0115:libudev:1:/dev/bus/usb/003/002 (lun: 0) 0261 eventhandler.c:479:EHStatusHandlerThread() powerState: POWER_STATE_UNPOWERED 06904552 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add 0242 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x046D, PID: 0x0825, path: /dev/bus/usb/003/007 0015 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a supported smart card reader 0017 hotplug_libudev.c:619:HPEstablishUSBNotifications() 00022668 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add 0214 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x046D, PID: 0x0825, path: /dev/bus/usb/003/007 0013 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a supported smart card reader 0017 hotplug_libudev.c:619:HPEstablishUSBNotifications() 6048 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add 0207 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x046D, PID: 0x0825, path: /dev/bus/usb/003/007 0014 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a supported smart card reader 0015 hotplug_libudev.c:619:HPEstablishUSBNotifications() 00014614 hotplug_libudev.c:648:HPEstablishUSBNotifications() USB Device add 0200 hotplug_libudev.c:294:get_driver() Looking for a driver for VID: 0x046D, PID: 0x0825, path: /dev/bus/usb/003/007 0016 hotplug_libudev.c:414:HPAddDevice() /dev/bus/usb/003/007 is not a supported smart card reader 0014 hotplug_libudev.c:619:HPEstablishUSBNotifications() Basically, if I plug or unplug a USB device, pcscd immediately starting using 100% CPU. Let me know if there is anything else I can send you to help you debug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
I ran pcscd as you suggested, capturing output. Made sure the smart card was working by using my SSH key. I was then able to reproduce the 100% cpu condition by plugging in my Logitech USB webcam. Attached the output, but I redacted the hex dumps before posting here because I'm not sure if they contain sensitive information. Let me know if you need the original. ** Attachment added: "pcscd debug output (redacted)" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+attachment/4587143/+files/pcscd.log.redacted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] Re: Excessive CPU utilization
This is what I've got installed ^^ c@mawhrin-skel:~/omnibus-layers$ dpkg -l | grep pcscd ii pcscd 1.8.14-1ubuntu1 amd64Middleware to access a smart card using PC/SC (daemon side) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551897] [NEW] Excessive CPU utilization
Public bug reported: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1551897 Title: Excessive CPU utilization Status in pcsc-lite package in Ubuntu: New Bug description: In xenial, pcscd CPU utilization occasionally goes haywire: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 27404 root 20 0 384264 4992 2228 S 100.3 0.0 75:39.03 /usr/sbin/pcscd --foreground --auto-exit I get this about once a day since installing xenial. I can't quite connect it to any specific event on the system, it just seems to happen sporadically -- fan turns on, I run top, and there it is again. Never had this issue on same hardware incl. smartcard with trusty. I wonder if it might be this? https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=718473 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1551897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491243] [NEW] padding needs slight adjustment
Public bug reported: As demonstrated in the attached screenshot (taken in Ubuntu 15.04), there appears to be too little space between the day and the time. The "1" looks at first glance to be part of the time. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot.png" https://bugs.launchpad.net/bugs/1491243/+attachment/4455968/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1491243 Title: padding needs slight adjustment Status in indicator-datetime package in Ubuntu: New Bug description: As demonstrated in the attached screenshot (taken in Ubuntu 15.04), there appears to be too little space between the day and the time. The "1" looks at first glance to be part of the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1491243/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460838] [NEW] headphones won't work unless pavucontrol is installed and the internal microphone is unmuted from there
Public bug reported: The issue is as described in the summary. My device is now working fine, however this fix is clearly some sort of bug, so I figured it would be helpful to report. If someone feels like working on it and wants any log files just let me know! Not sure what would actually be helpful.I had this issue in both 14.10 and 15.04 with the most recent releases of pulseaudio and alsamixer. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Description changed: The issue is as described in the summary. My device is now working fine, however this fix is clearly some sort of bug, so I figured it would be helpful to report. If someone feels like working on it and wants any log - files just let me know! Not sure what would actually be helpful. + files just let me know! Not sure what would actually be helpful.I had + this issue in both 14.10 and 15.04 with the most recent releases of + pulseaudio and alsamixer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1460838 Title: headphones won't work unless pavucontrol is installed and the internal microphone is unmuted from there Status in alsa-driver package in Ubuntu: New Bug description: The issue is as described in the summary. My device is now working fine, however this fix is clearly some sort of bug, so I figured it would be helpful to report. If someone feels like working on it and wants any log files just let me know! Not sure what would actually be helpful.I had this issue in both 14.10 and 15.04 with the most recent releases of pulseaudio and alsamixer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1460838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1295445] Re: Cursor size is not updated on HiDPI at intermediate UI scale levels
I also get this same issue (I have the Dell XPS 15 too, as David White above - it's the 9530 model). UI Scaling is set to 2x and looks fine everywhere except the cursor. Cursor is correct size in Google Chrome however as reported above. The workaround of restarting unity works, but is not ideal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1295445 Title: Cursor size is not updated on HiDPI at intermediate UI scale levels Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: When UI scale factor is at intermediate values from 1.0-2.0 and from 2.0-3.0 the cursor size is not updated to match current settings. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368864] Re: old motd is displayed on login
Hello: This affects my server(s), 14.04.2 LTS. In fact I just logged in and got information that was 11 days old. I rely on the welcome message especially to tell me when I need to REBOOT for some automatically- installed (perhaps security) updates to be fully applied. Perhaps a wiser sysadmin would have a better way to be notified about that! Anyway, could this bug perhaps be assigned to someone and solved soon please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1368864 Title: old motd is displayed on login Status in shadow package in Ubuntu: Triaged Bug description: On Trusty, during login, the motd displayed is from the cache file /run/motd.dynamic. After being displayed, the scripts from /etc /update-motd.d are run to refresh /run/motd.dynamic. This behavior of displaying the cache first is not very convenient and didn't happen on Precise. This is also does not match the documentation (man 5 update- motd) nor the users' expectations. Steps to reproduce: $ cat EOF | sudo tee /etc/update-motd.d/60-test #!/bin/sh printf motd from: $(date +%T)\n EOF $ sudo chmod +x /etc/update-motd.d/60-test $ echo 'echo real time: $(date +%T);exit' | ssh -T localhost Welcome to Ubuntu 14.04.1 LTS (GNU/Linux 3.13.0-35-generic x86_64) * Documentation: https://help.ubuntu.com/ motd from: 6:05:43 real time: 12:36:14 The above is just an example of how old/stale the output can be. More details: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 $ apt-cache policy libpam-modules libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libpam-modules 1.1.8-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 12 12:22:09 2014 InstallationDate: Installed on 2014-01-26 (228 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1368864/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
