[Touch-packages] [Bug 1724711] Re: rsyslog fails to start (Lubuntu 17.10)
After reboot it is not running again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1724711 Title: rsyslog fails to start (Lubuntu 17.10) Status in rsyslog package in Ubuntu: New Bug description: 1) Description: Ubuntu 17.10 Release: 17.10 2) 8.16.0-1ubuntu9 3) I'd like to see what happened in the system 4) syslog is empty, messages is obsolete, lastlog shows only pure console logins (it maybe unrelated) root@user:~# systemctl status rsyslog ● rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-10-19 02:24:34 MSK; 1h 15min ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 1858 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE) Main PID: 1858 (code=exited, status=1/FAILURE) окт 19 02:24:33 user systemd[1]: rsyslog.service: Main process exited, code=exited, stat окт 19 02:24:33 user systemd[1]: Failed to start System Logging Service. окт 19 02:24:33 user systemd[1]: rsyslog.service: Unit entered failed state. окт 19 02:24:33 user systemd[1]: rsyslog.service: Failed with result 'exit-code'. окт 19 02:24:34 user systemd[1]: rsyslog.service: Service hold-off time over, scheduling окт 19 02:24:34 user systemd[1]: Stopped System Logging Service. окт 19 02:24:34 user systemd[1]: rsyslog.service: Start request repeated too quickly. окт 19 02:24:34 user systemd[1]: Failed to start System Logging Service. окт 19 02:24:34 user systemd[1]: rsyslog.service: Unit entered failed state. окт 19 02:24:34 user systemd[1]: rsyslog.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: rsyslog 8.16.0-1ubuntu9 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 19 03:59:04 2017 InstallationDate: Installed on 2017-10-06 (12 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1724711/+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 1724711] Re: rsyslog fails to start (Lubuntu 17.10)
How could I gather more info about this issue without rsyslog? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1724711 Title: rsyslog fails to start (Lubuntu 17.10) Status in rsyslog package in Ubuntu: New Bug description: 1) Description: Ubuntu 17.10 Release: 17.10 2) 8.16.0-1ubuntu9 3) I'd like to see what happened in the system 4) syslog is empty, messages is obsolete, lastlog shows only pure console logins (it maybe unrelated) root@user:~# systemctl status rsyslog ● rsyslog.service - System Logging Service Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-10-19 02:24:34 MSK; 1h 15min ago Docs: man:rsyslogd(8) http://www.rsyslog.com/doc/ Process: 1858 ExecStart=/usr/sbin/rsyslogd -n (code=exited, status=1/FAILURE) Main PID: 1858 (code=exited, status=1/FAILURE) окт 19 02:24:33 user systemd[1]: rsyslog.service: Main process exited, code=exited, stat окт 19 02:24:33 user systemd[1]: Failed to start System Logging Service. окт 19 02:24:33 user systemd[1]: rsyslog.service: Unit entered failed state. окт 19 02:24:33 user systemd[1]: rsyslog.service: Failed with result 'exit-code'. окт 19 02:24:34 user systemd[1]: rsyslog.service: Service hold-off time over, scheduling окт 19 02:24:34 user systemd[1]: Stopped System Logging Service. окт 19 02:24:34 user systemd[1]: rsyslog.service: Start request repeated too quickly. окт 19 02:24:34 user systemd[1]: Failed to start System Logging Service. окт 19 02:24:34 user systemd[1]: rsyslog.service: Unit entered failed state. окт 19 02:24:34 user systemd[1]: rsyslog.service: Failed with result 'exit-code'. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: rsyslog 8.16.0-1ubuntu9 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 19 03:59:04 2017 InstallationDate: Installed on 2017-10-06 (12 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1724711/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
@Konrad: thanks for taking the time to explain the situation details. However I have to report that when switching to Windows 10, on the exact same PC (just a drive swap), Bluetooth performs flawlessly with both my speakers (JBL Flip 3 and UE Miniboom). This suggests that it is not a hardware problem but a software one. FYI this problem sits high on the Pulseaudio bug list, but... Best Regards, -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1725847] Re: libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without _GLIBCXX_USE_C99
** Tags added: artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1725847
Title:
libstdc++-4.8-dev:amd64 4.8.5-4ubuntu6 configured without
_GLIBCXX_USE_C99
Status in gcc-4.8 package in Ubuntu:
New
Bug description:
Test program compiled on Artful Aardvark Ubuntu 17.10.
$ which g++-4.8
/usr/bin/g++-4.8
$ /usr/bin/g++-4.8 --version
g++-4.8 (Ubuntu 4.8.5-4ubuntu6) 4.8.5
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ /usr/bin/g++-4.8 -std=c++11 -x c++ - <
#include
int main()
{
std::cout << std::to_string(0) << '\n';
return 0;
}
EOF
Expected result
compile without errors, output 0
Actual result
: In function ‘int main()’:
:5:16: error: ‘to_string’ is not a member of ‘std’
Supposed cause
_GLIBCXX_USE_C99 is not set in
/usr/include/x86_64-linux-gnu/c++/4.8/bits/c++config.h
in package libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu6)
Further information
Test program compiles and runs on Zesty Zapus with package
libstdc++-4.8-dev:amd64 (4.8.5-4ubuntu4).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1725847/+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 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
Sorry for the mistake. ** Attachment added: "upgrade logs" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+attachment/4984300/+files/dist-upgrade.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 Status in resolvconf package in Ubuntu: Incomplete Bug description: After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS lookup on my wireless network connection did not work any more. As it seems, the file /etc/resolv.conf was static and contained wrong data assigned by the NetworkManager. When I changed the file content manually to nameserver 127.0.0.53 DNS lookup worked fine. After reboot, however, I had to repeat this operation since NetworkManager seems to have replaced the file content. Finally, I found a solution. Running sudo dpkg-reconfigure resolvconf the file /etc/resolv.conf was replaced by the link /etc/resolv.conf -> ../run/resolvconf/resolv.conf Now, the wireless network seems to work properly. Hence, there must be some kind of bug during the update process from Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured properly. Best regards, Artur ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 23:17:38 2017 InstallationDate: Installed on 2013-10-18 (1463 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+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 1725680] Re: DNS name resolution doesn't work on Artful
Yes, my wifi provides a DNS nameserver. It's adress is 192.168.44.1, and it is shown when I open System Settings --> WLAN and click on the properties of the connected network. When I manually add this DNS server to resolv.conf, DNS resolution will start working. What I'm currently using is some sort of a "public facility wifi", where anyone can connect freely to without any authentification (and without encryption). Unfortunately, this is the only network I can test ATM, so I don't know if if would be different on e.g. a WPA2-encrypted private wifi. Here is the output of the two commands: $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp7s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.44.1 DNS Domain: lan Link 2 (enp9s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no -- $ sudo NetworkManager --print-config # NetworkManager configuration: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 20-connectivity-ubuntu.conf) (run: 10-globally-managed-devices.conf) (etc: default-wifi-powersave-on.conf) [main] # rc-manager=symlink # auth-polkit=true # dhcp=dhclient dns=systemd-resolved plugins=ifupdown,keyfile [connectivity] uri=http://connectivity-check.ubuntu.com/ [ifupdown] managed=false [logging] # backend=journal # audit=true [device] wifi.scan-rand-mac-address=no [connection] wifi.powersave=3 -- 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/1725680 Title: DNS name resolution doesn't work on Artful Status in systemd package in Ubuntu: New Bug description: If I boot my laptop with a live image or an installation of Ubuntu 17.10, DNS name resolution doesn't work (which means I can't access any website). Steps to reproduce: - Boot laptop with Ubuntu 17.10 live image - Connect to my wireless network - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with the error message "Name or service not known" - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works. As a workaround, I can get a temporarily working DNS resolution by manually editing /etc/resolv.conf (symlink to /run/systemd/resolve /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or some other known DNS server. On Ubuntu 17.04 this bug is not present. The original address in /run/systemd/resolve/stub-resolve.conf is 127.0.0.53 . I get immediate replies if I ping this address, but nevertheless DNS resolution doesn't work. It seems that the service systemd-networkd isn't active by default: $ sudo systemctl status systemd-networkd ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendo Active: inactive (dead) Docs: man:systemd-networkd.service(8) Manually starting it doesn't seem to help for this bug. systemd-resolved is active: $ sudo systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-con https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl Main PID: 1095 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─1095 /lib/systemd/systemd-resolved Okt 21 12:13:1
[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
I confirm that the DNS leakage problem is still present in ubuntu 17.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] Apparently fixed on Ubuntu 17.04, nobody caring about LTS versions. Please see wall of text on comment 50 for a long excuse. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1721948] Re: gvfs-open/xdg-open shows message about 'gio open' which confuses user
Yes, that solved it for me after activating "proposed" on artful, with xdg-utils (1.1.1-1ubuntu3) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1721948 Title: gvfs-open/xdg-open shows message about 'gio open' which confuses user Status in Apport: Fix Released Status in gvfs: Fix Released Status in apport package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Invalid Status in python3.6 package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: Fix Committed Status in xdg-utils source package in Artful: Fix Committed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Try to report bug with Apport by terminal command `apport-bug apport` Expected results: apport-bug reports bug silently Actual results: get output in the terminal $ apport-bug apport This tool has been deprecated, use 'gio open' instead. See 'gio help open' for more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu2 Architecture: i386 CurrentDesktop: MATE Date: Sat Oct 7 13:50:23 2017 InstallationDate: Installed on 2017-08-26 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1721948/+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 1723210] Re: mobile broadband connectie fail (timeout)
I got exactly the same problem since upgraded to artful. My modem is
Huawei E176 (12d1:140c) and my workaround for now is to add file
/etc/udev/rules.d/99-mm-e176.rules with below content to unset
ID_MM_CANDIDATE on /dev/cdc-wdm*.
ACTION!="add|change|move", GOTO="mm_e176_end"
# E176
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="140c", SUBSYSTEM=="usb",
KERNEL=="cdc-wdm*", ENV{ID_MM_CANDIDATE}="0"
ATTRS{idVendor}=="12d1", ATTRS{idProduct}=="140c", SUBSYSTEM=="usbmisc",
KERNEL=="cdc-wdm*", ENV{ID_MM_CANDIDATE}="0"
LABEL="mm_e176_end"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1723210
Title:
mobile broadband connectie fail (timeout)
Status in modemmanager package in Ubuntu:
New
Bug description:
On Ubuntu 17.10 I cannot make a mobile broadband connection.
On my multiboot laptop with a Hewlett-Packard Gobi 2000 Wireless Modem I can
successfully connect to T-Mobile broadband network when I use Ubuntu 17.04
(Gnome), but not with Ubuntu 17.10 (Artful Aardvark) with the latest patches
applied.
The gobi-loader loads the firmware in both instances successfully ( the 3
ttyUSB ports are visible. I get a response on ttyUSB1 with an AT-command)
In the attached syslog you can see the connection times out.
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10
modemmanager:
Installed: 1.6.8-1
Candidate: 1.6.8-1
Version table:
*** 1.6.8-1 500
500 http://nl.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
network-manager:
Installed: 1.8.4-1ubuntu3
Candidate: 1.8.4-1ubuntu3
Version table:
*** 1.8.4-1ubuntu3 500
500 http://nl.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1723210/+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 1725949] [NEW] nouveau drivers fails to start a wayland session and fallback to x11
Public bug reported: I have a Nvidia GTX 670. I tried the nouveau driver. At boot, it takes a unusual long time then finally shows me gdm3 and everything is working after. But echo $XDG_SESSION_TYPE is set to "x11". Reading the logs, I can see that after multiple failures to launch wayland, it falls back to X11. I added an attachement of journalctl -b -1 where it fails with nouveau (I'm filling the bug after reinstalling nvidia proprietary driver). lspci -v 01:00.0 VGA compatible controller: NVIDIA Corporation GK104 [GeForce GTX 670] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] Flags: bus master, fast devsel, latency 0, IRQ 29 Memory at f600 (32-bit, non-prefetchable) [size=16M] Memory at e800 (64-bit, prefetchable) [size=128M] Memory at f000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.90 Tue Sep 19 19:17:35 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: automatic crash report generation. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 11:37:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK104 [GeForce GTX 670] [10de:1189] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK104 [GeForce GTX 670] [3842:2678] InstallationDate: Installed on 2017-09-17 (34 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170915) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=567a9b2b-0864-450e-9cfe-dab7a54b9fce ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd09/28/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Oct 22 11:26:32 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu ** Attachment added: "nouveau-fails-wayland.log" https://bugs.launchpad.net/bugs/1725949/+attachment/4984472/+files/nouveau-fails-wayla
[Touch-packages] [Bug 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)
Bug exists in Ubuntu 17.10 final with GNOME Shell. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1263228 Title: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04) Status in gnome-shell package in Ubuntu: New Status in ido package in Ubuntu: Triaged Status in indicator-power package in Ubuntu: Fix Released Bug description: I have Ubuntu 14.04 with all updates installed. My screen resolution is 1920x1080 (FullHD) at 16.4 inches. Icons from the menu of newest indicator-keyboard and other gnome-panel icons are very small (difficult to read). Please adapt icon sizes to large screen resolutions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 21 00:41:25 2013 InstallationDate: Installed on 2013-10-20 (61 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1263228/+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 1659727] Re: Xorg freeze - blank screen - Enlightenment + nvidia driver
How did you go with the other machine? ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1659727 Title: Xorg freeze - blank screen - Enlightenment + nvidia driver Status in xorg package in Ubuntu: Incomplete Bug description: I helped my friend Roger setup five systems running ubuntu with boinc running in the background for the Einstein@home project. One has a AMD Phenom 9950 CPU, and the others have AMD FX-8320E, FX-8150, FX-8350, and FX-8370 CPUs. All have the X64 version of ubuntu installed. In an effort to speed up processing, we install NVidia GTX 1060 graphics cards in three of them. We added the nvidia-367 kernel driver to two systems that were already upgraded to 16.04 LTS (they use Lightdm and Unity with Xorg). They now use the GPU for one of the processes without problems. This problem system (with the FX-8150 CPU) was originally using Ubuntu Precise Pangolin and running Enlightenment instead of Unity. It was using Trusty when we installed the new graphics card. It still used the Nouveau video driver. I had problems installing the NVidia kernel driver on that, so I gave up and used the 'do-release-upgrade' script to do the upgrade to 16.04.1 LTS (Xenial). Everything seemed OK until I added the NVidia driver to the system. Now, after every reboot the display goes thru the text boot sequence, and flashes briefly when loading X, but then the screen goes blank until rebooting again. Fortunately, I found I could open a ssh session (or use scp to copy files) to the system. The NVidia GPU is being used by one of the BOINC jobs, even with the blank screen on the console! After a lot of horsing around, I moved the file failsafe-x.conf from /etc/init to /root, so I could try various hacks to get the display to work. It took me a long time to find the error message in file /home/roger/.xsession-errors. It says: openConnection: connect: No such file or directory cannot connect to brltty at :0 main init win: 1920x1080 for 1d4 screen region screen 0x6e4140: 0 0 1920x1080 CRI: modules/evas/engines/gl_x11/evas_engine.c:2511 eng_image_native_set() eina_log_print() unknown domain -1, original message format 'GLX Pixmap create fail' action halt 3 action reboot 3 action suspend 3 action hibernate 3 The 5th line (starting with 'CRI') led me to the efl source package associated with enlightenment, (which I installed in /usr/src). It seems to have source for a number of DLLs for e17. I found the line from the message in file: '/usr/src/efl-1.8.6/src/modules/evas/engines/gl_x11/evas_engine.c'. I don't know how to proceed from here. I assume the apport-bug job gave most of the system state information. Is there a way to look at the various X processes that are running? Please advise.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jan 26 22:54:02 2017 DistUpgraded: 2017-01-16 22:52:51,433 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 3.13.0-107-generic, x86_64: installed bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed nvidia-367, 367.57, 4.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-07-09 (1662 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TE
[Touch-packages] [Bug 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default
Users have in the past "accidentally" removed entire desktops ("I
installed this package, now my desktop is gone and I can't use my PC
anymore"). They often just hit enter and don't really read what apt is
going to do.
aptitude does autoremoval by default in any install/remove/upgrade/etc
operation
SuggestsImportant was set to true in 2011 with 0.8.15.3. It's been that
way for 6 years, 3 LTS releases. I feel like it's a bit late to change
that back now.
Also, just setting SuggestsImportant to false will not really help - you
might still get a different result in your example. Any dependency on a
virtual package or an or group will keep _every_ installed package
satisfying that dependency installed. So install A depending on B | C |
D, install packages needing C and D, remove the latter packages and C
and D will still be kept around.
So my personal autoremoval script (which based on pseudo boolean
optimization to mathematically ensure the smallest possible system based
on manually installed + depends + recommends) would currently remove 42
packages, autoremove only 24.
In my opinion, for careful people like us, I do agree that the Suggests
handling is bad (after all, my script also does not treat Suggests as
important). But I don't fully trust normal users with that, given what
we've seen in the past with some not reading what apt is going to do and
then complain afterwards that their entire desktop was gone.
A reasonable compromise here would be to easily give the user the
information that they can remove even more packages:
* Keep autoremove SuggestsImportant
* Add a new option to autoremove and co like --autoremove-more that sets
SuggestsImportant to false
* When running autoremove, show "The following packages could also be removed,
but might enhance other installed packages. Use --autoremove-more to remove
them" and a list of packages that are only kept by Suggests (and preferably
list which package(s) are suggesting them).
Now the enhances might be confusing in the wording, but we eventually
want to also have the autoremover respect Enhances, but Enhances is more
complicated since it's the other way around. But it does explain the
situation.
Finally, I'd like to hear what DonKult has to say, given that he turned
that on in the first place.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1725861
Title:
APT::AutoRemove::SuggestsImportant "false" should be the default
Status in apt package in Ubuntu:
New
Bug description:
After an upgrade to 17.10, I took a look at how much cruft I had
accumulated on my system, and started marking various packages 'auto'
which I know I don't care about keeping installed.
apt autoremove didn't remove nearly as much stuff as I expected, and
as I dug down into some of them I found that a number of them were
being kept because other packages on the system have Suggests:
referencing them.
This is asymmetric and wrong. If Suggested packages are not
automatically installed by default, then a Suggests should also not
prevent a package from being automatically removed.
After a web search led me to 'https://askubuntu.com/questions/351085
/how-to-remove-recommended-and-suggested-dependencies-of-uninstalled-
packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my
apt config; apt autoremove now wants to remove 365MiB of packages from
my system. That is a LOT of cruft that has accumulated over the years
of upgrades, none of which I have ever asked to be installed and all
of which were universe or no-longer-available packages.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1725861/+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 1725861] Re: APT::AutoRemove::SuggestsImportant "false" should be the default
While that sounds reasonable at first in simple situations, if I follow that argument, I can find no reason why we are doing complex metapackage handling, keeping many providers and a lot of other things, so we should get right of all those, too, should we? In reality we have to deal with many many users who only very casually check the output of apt and generally trust it to do the right thing™. And that is kinda reasonable if we don't want to teach every user packaging practices. Most users will just not make the connection between having run autoremove a couple of days ago and suddenly not being able to push audio files from their favorite player&manager directly to their phones causing users (and supporters alike) to be frustrated. Having "too many" packages installed rarely causes that level of frustration in comparison. autoremove is just not an "undo". It is supposed to remove things which are clearly no longer needed by anything. Like old kernels, old libraries and co. In fact, ideally we should end up in a situation in which autoremove can be called automatically so that old kernels are really gone, the system is cleaner after an upgrades and such… (but for various reasons that isn't really possible/advisable at the moment). Perhaps we should implement an "undo" – just named differently as that is too confusing as we can't really perform an undo, but we have the history.log from which we can extract which packages were newly installed in an "apt install A" and offer to remove them as well (maybe with a question ala: those other packages make use of B initially installed with A, should we keep it?). (And, while we are at it also a way for a repository to say: I don't support package A anymore with options among a) you can safely remove it as something else takes care of it now, b) here are potential alternatives [we tend to have a list in RM requests, but nothing a user can look at easily] c) it is dead and nothing compares d) look elsewhere for it e) … – which should deal with a lot of packages which autoremove should be removing, but is too scared ATM as it has not enough information to make a safe call) [No, I haven't implemented either. I haven't even really thought about them. It just sounds for me like those could be potential ways to resolve the situation] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1725861 Title: APT::AutoRemove::SuggestsImportant "false" should be the default Status in apt package in Ubuntu: New Bug description: After an upgrade to 17.10, I took a look at how much cruft I had accumulated on my system, and started marking various packages 'auto' which I know I don't care about keeping installed. apt autoremove didn't remove nearly as much stuff as I expected, and as I dug down into some of them I found that a number of them were being kept because other packages on the system have Suggests: referencing them. This is asymmetric and wrong. If Suggested packages are not automatically installed by default, then a Suggests should also not prevent a package from being automatically removed. After a web search led me to 'https://askubuntu.com/questions/351085 /how-to-remove-recommended-and-suggested-dependencies-of-uninstalled- packages', I set 'APT::AutoRemove::SuggestsImportant "false"' in my apt config; apt autoremove now wants to remove 365MiB of packages from my system. That is a LOT of cruft that has accumulated over the years of upgrades, none of which I have ever asked to be installed and all of which were universe or no-longer-available packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1725861/+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 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
Correction. 0.17+17.10.20170606-0ubuntu1 works ok -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+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 1725980] [NEW] package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinsta
Public bug reported: not updated ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Sun Oct 22 09:37:53 2017 DuplicateSignature: package:libheimntlm0-heimdal:i386:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libheimntlm0-heimdal:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-03-06 (229 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: heimdal Title: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: heimdal (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1725980 Title: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg- 4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in heimdal package in Ubuntu: New Bug description: not updated ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Sun Oct 22 09:37:53 2017 DuplicateSignature: package:libheimntlm0-heimdal:i386:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libheimntlm0-heimdal:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-03-06 (229 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: heimdal Title: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1725980/+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 1725980] Re: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to heimdal in Ubuntu. https://bugs.launchpad.net/bugs/1725980 Title: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg- 4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in heimdal package in Ubuntu: New Bug description: not updated ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Sun Oct 22 09:37:53 2017 DuplicateSignature: package:libheimntlm0-heimdal:i386:1.7~git20150920+dfsg-4ubuntu1.16.04.1 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libheimntlm0-heimdal:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-03-06 (229 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: heimdal Title: package libheimntlm0-heimdal:i386 1.7~git20150920+dfsg-4ubuntu1.16.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1725980/+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 1267235] Re: "System program problem detected" dialog not shown in launcher
Bug exists in Ubuntu 16.04 LTS. Window is not shown on mate-panel. But it exists on screen: $ wmctrl -lx 0x01ab 0 update-notifier.Update-notifier nikolay-UX32A ** Tags removed: amd64 ** Tags added: xenial ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** No longer affects: apport (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1267235 Title: "System program problem detected" dialog not shown in launcher Status in update-notifier package in Ubuntu: Confirmed Bug description: If "system program" crashes displayed dialog for sending report (/usr/lib/update-notifier/system-crash-notification process) doesn't appears in launcher (no window icon) and in Alt+Tab menu, so if I switch to other window that completely overlaps dialog it becomes problematic to get error reporting dialog foreground. To reproduce: 1. Make "system program" crash, e.g. # cat /dev/zero > /dev/null & [1] 8047 # kill -SEGV 8047 2. "System program problem detected" dialog appears. Expected behaviour: dialog window should have icon in launcher and be accessible through Alt+Tab. Observer behaviour: dialog is not shown in launcher and not available in Alt+Tab or Ctrl+Alt+Tab lists. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: update-notifier 0.147.1 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CheckboxSubmission: 3d16077c4fdd6a017d47f6e3dc4f3c54 CheckboxSystem: b633b4f40868d491c2ae5b50030ce6f3 Date: Thu Jan 9 00:27:55 2014 InstallationDate: Installed on 2014-01-01 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: update-notifier UpgradeStatus: No upgrade log present (probably fresh install) upstart.unicast-local-avahi.log: Ср. янв. 8 16:06:33 MSK 2014 avahi disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1267235/+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 1725991] [NEW] GNOME applications are not shown in wmctrl -lx output on Wayland
Public bug reported: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Launch gnome-terminal, gnome-calculator, gnome-calendar etc. 4. Install wmctrl and use it from terminal with `wmctrl -lx` Expected results: wmctrl shows list of windows Actual results: wmctrl do not show list of windows Note: inspired by AskUbuntu question - https://askubuntu.com/q/967565/66509 . ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:21:23 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Affects: wmctrl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: wmctrl (Ubuntu) Importance: Undecided Status: New ** Description changed: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Launch gnome-terminal, gnome-calculator, gnome-calendar etc. 4. Install wmctrl and use it from terminal with `wmctrl -lx` Expected results: wmctrl shows list of windows Actual results: wmctrl do not show list of windows + + Note: + inspired by AskUbuntu question - https://askubuntu.com/q/967565/66509 . ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:21:23 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725991 Title: GNOME applications are not shown in wmctrl -lx output on Wayland Status in gnome-terminal package in Ubuntu: New Status in wayland package in Ubuntu: New Status in wmctrl package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Launch gnome-terminal, gnome-calculator, gnome-calendar etc. 4. Install wmctrl and use it from terminal with `wmctrl -lx` Expected results: wmctrl shows list of windows Actual results: wmctrl do not show list of windows Note: inspired by AskUbuntu question - https://askubuntu.com/q/967565/66509 . ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:21:23 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725991/+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 1723740] Re: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1723740 Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: atualizei da versão 16.04 para 17.04 e agora está apresentando essa mensagem de erro. O que devo fazer para resolver o problema? ProblemType: Package DistroRelease: Ubuntu 17.04 Package: systemd-sysv 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Sat Oct 14 01:40:33 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2017-05-01 (167 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: systemd Title: package systemd-sysv 232-21ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to zesty on 2017-10-14 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1723740/+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 1725991] Re: GNOME applications are not shown in wmctrl -lx output on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725991 Title: GNOME applications are not shown in wmctrl -lx output on Wayland Status in gnome-terminal package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in wmctrl package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Launch gnome-terminal, gnome-calculator, gnome-calendar etc. 4. Install wmctrl and use it from terminal with `wmctrl -lx` Expected results: wmctrl shows list of windows Actual results: wmctrl do not show list of windows Note: inspired by AskUbuntu question - https://askubuntu.com/q/967565/66509 . ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:21:23 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725991/+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 1725991] Re: GNOME applications are not shown in wmctrl -lx output on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725991 Title: GNOME applications are not shown in wmctrl -lx output on Wayland Status in gnome-terminal package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in wmctrl package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Launch gnome-terminal, gnome-calculator, gnome-calendar etc. 4. Install wmctrl and use it from terminal with `wmctrl -lx` Expected results: wmctrl shows list of windows Actual results: wmctrl do not show list of windows Note: inspired by AskUbuntu question - https://askubuntu.com/q/967565/66509 . ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:21:23 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725991/+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 1725991] Re: GNOME applications are not shown in wmctrl -lx output on Wayland
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wmctrl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725991 Title: GNOME applications are not shown in wmctrl -lx output on Wayland Status in gnome-terminal package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Status in wmctrl package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Launch gnome-terminal, gnome-calculator, gnome-calendar etc. 4. Install wmctrl and use it from terminal with `wmctrl -lx` Expected results: wmctrl shows list of windows Actual results: wmctrl do not show list of windows Note: inspired by AskUbuntu question - https://askubuntu.com/q/967565/66509 . ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:21:23 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1725991/+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 1721343] [NEW] VLC does not display video from DVD or streaming video
You have been subscribed to a public bug: VLC was installed originally from the hdhomerun_config_gui package as a dependency. VLC would not display video from HD Homerun Prime network tv tuner with latest firmware (tuner works on different PC). VLC also failed to display video from DVD. Audio worked for both tuner and DVD. Completely removed VLC using Synaptic including configuration files. Installed VLC from Ubuntu Software Center, which installed a SNAP version of VLC. The SNAP version of VLC would not run. Uninstalled VLC using Ubuntu Software Center, installed a different VLC version from Ubuntu Software Center (probably non-SNAP). This version of VLC again will only play audio, not the video from DVD or the hdhomerun_config_gui. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc-nox 2.2.2-5ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 4 12:03:06 2017 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2017-10-02 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- VLC does not display video from DVD or streaming video https://bugs.launchpad.net/bugs/1721343 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. -- 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 1725708] Re: Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click
Be more kindly next time. ** Attachment added: "try this yourself.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725708/+attachment/4985083/+files/try%20this%20yourself.png ** Changed in: gedit (Ubuntu) Status: New => Confirmed ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Changed in: wayland (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725708 Title: Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click Status in gedit package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open Gedit text editor 3. Make right mouse click on its top window bar 4. Window drop-down menu is shown, mouse is over "Minimize" option Expected results: * window drop-down menu is opened, user is able to select option from it (for example move to other workspace or maximize) Actual results: * Gedit window got minimized instantly ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:27:44 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1725708/+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 1726017] [NEW] dnsmasq prematurely returns REFUSED, breaking resolver
Public bug reported: Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update. In my local network, I have two DNS servers; 192.168.1.1 is the local DHCP/DNS server configured to reply to queries inside the local network, and 192.168.1.4 is the forwarder in my DSL Router, responsible to answer queries about the outside world. THe DHCP server returns these in the order 192.168.1.4,192.168.1.1. The internal server replies REFUSED to queries about external domains. This configuration has worked well with Ubuntu 14.04 and other Linux Distros (using Fedora and OpenSUSE internally here), as well as various other OSes. It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance pushes the REFUSED reply from 192.168.1.1 to applications and ignores the successful reply from 2.168.1.4. This causes all DNS queries to external servers to fail. I believe this is fixed in dnsmasq 2.76 and related to http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2016q1/010263.html http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=68f6312d4bae30b78daafcd6f51dc441b8685b1e http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=4ace25c5d6 According to these sources, the bug was introduced with http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=51967f9807665dae403f1497b827165c5fa1084b In my local setup at least, I can work around the problem by using the "strict-order" option to dnsmasq. echo strict-order >/etc/NetworkManager/dnsmasq.d/order.conf But that's not a general solution. If dnsmasq has several forwarders, and some return SERVFAIL or REFUSED and others return SUCCESS, the successful answer should be returned to clients, independent of the strict-order setting. ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1726017 Title: dnsmasq prematurely returns REFUSED, breaking resolver Status in dnsmasq package in Ubuntu: New Bug description: Seen with dnsmasq 2.75-1ubuntu0.16.04.3, after Trusty->Xenial update. In my local network, I have two DNS servers; 192.168.1.1 is the local DHCP/DNS server configured to reply to queries inside the local network, and 192.168.1.4 is the forwarder in my DSL Router, responsible to answer queries about the outside world. THe DHCP server returns these in the order 192.168.1.4,192.168.1.1. The internal server replies REFUSED to queries about external domains. This configuration has worked well with Ubuntu 14.04 and other Linux Distros (using Fedora and OpenSUSE internally here), as well as various other OSes. It does not work with Ubuntu 16.04. NetworkManager's dnsmasq instance pushes the REFUSED reply from 192.168.1.1 to applications and ignores the successful reply from 2.168.1.4. This causes all DNS queries to external servers to fail. I believe this is fixed in dnsmasq 2.76 and related to http://lists.thekelleys.org.uk/pipermail/dnsmasq- discuss/2016q1/010263.html http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=68f6312d4bae30b78daafcd6f51dc441b8685b1e http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=4ace25c5d6 According to these sources, the bug was introduced with http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=object;h=51967f9807665dae403f1497b827165c5fa1084b In my local setup at least, I can work around the problem by using the "strict-order" option to dnsmasq. echo strict-order >/etc/NetworkManager/dnsmasq.d/order.conf But that's not a general solution. If dnsmasq has several forwarders, and some return SERVFAIL or REFUSED and others return SUCCESS, the successful answer should be returned to clients, independent of the strict-order setting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1726017/+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 1721343] Re: VLC does not display video from DVD or streaming video
So, looks like a driver bug. Let's reassign to mesa, which provides the vdpau implementation for nouveau. ** Package changed: vlc (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1721343 Title: VLC does not display video from DVD or streaming video Status in mesa package in Ubuntu: New Bug description: VLC was installed originally from the hdhomerun_config_gui package as a dependency. VLC would not display video from HD Homerun Prime network tv tuner with latest firmware (tuner works on different PC). VLC also failed to display video from DVD. Audio worked for both tuner and DVD. Completely removed VLC using Synaptic including configuration files. Installed VLC from Ubuntu Software Center, which installed a SNAP version of VLC. The SNAP version of VLC would not run. Uninstalled VLC using Ubuntu Software Center, installed a different VLC version from Ubuntu Software Center (probably non-SNAP). This version of VLC again will only play audio, not the video from DVD or the hdhomerun_config_gui. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc-nox 2.2.2-5ubuntu0.16.04.4 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 4 12:03:06 2017 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2017-10-02 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1721343/+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 1726010] Re: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash()
*** This bug is a duplicate of bug 1690935 *** https://bugs.launchpad.net/bugs/1690935 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1690935, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726010/+attachment/4985015/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726010/+attachment/4985018/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726010/+attachment/4985025/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726010/+attachment/4985027/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726010/+attachment/4985028/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726010/+attachment/4985029/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726010/+attachment/4985030/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1690935 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1726010 Title: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash() Status in systemd package in Ubuntu: New Bug description: I was opening a firefox sheet and all was freezed ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sun Oct 22 10:19:55 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=es_AR.UTF-8 LANGUAGE=es_AR:es PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: journal_file_find_data_object_with_hash () from /lib/systemd/libsystemd-shared-234.so ?? () from /lib/systemd/libsystemd-shared-234.so journal_file_append_entry () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in journal_file_find_data_object_with_hash() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/24/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: V7.5 dmi.board.name: MS-7246 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 2.1 dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV7.5:bd05/24/2007:svn:pn:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7246:rvr2.1:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726010/+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 1725976] [NEW] Sometimes need to login 2 times after resume from suspend
You have been subscribed to a public bug: I'm on Xubuntu 17.10 About 50% of resume from suspend requires me to login 2 times instead of just once. I press shift to resume from suspend. The login prompt comes - I login. Sometimes, I get logged in. Other times, the login prompt comes again. login manager : lightdm Been using 17.10 pre-releases (and taking daily updates) since about 20 days. The problem has been around since day one. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Sometimes need to login 2 times after resume from suspend https://bugs.launchpad.net/bugs/1725976 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- 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 1726013] Re: systemd-resolved crashed with SIGABRT in log_assert_failed_realm()
*** This bug is a duplicate of bug 1714792 *** https://bugs.launchpad.net/bugs/1714792 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1714792, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726013/+attachment/4985056/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726013/+attachment/4985059/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726013/+attachment/4985066/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726013/+attachment/4985068/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726013/+attachment/4985069/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726013/+attachment/4985070/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726013/+attachment/4985071/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1714792 ** Information type changed from Private Security to Public Security ** Tags removed: need-amd64-retrace -- 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/1726013 Title: systemd-resolved crashed with SIGABRT in log_assert_failed_realm() Status in systemd package in Ubuntu: New Bug description: Appairs error messge at startup ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Sun Oct 22 09:44:22 2017 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2017-10-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. N552VX ProcCmdline: /lib/systemd/systemd-resolved ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=457b2a84-bb47-47c1-ae79-2e76186547a7 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: log_assert_failed_realm () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-234.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-234.so SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-resolved crashed with SIGABRT in log_assert_failed_realm() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/31/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N552VX.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N552VX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN552VX.300:bd08/31/2016:svnASUSTeKCOMPUTERINC.:pnN552VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN552VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N552VX dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726013/+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 1725976] Re: Sometimes need to login 2 times after resume from suspend
** Package changed: ubuntu => lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1725976 Title: Sometimes need to login 2 times after resume from suspend Status in lightdm package in Ubuntu: New Bug description: I'm on Xubuntu 17.10 About 50% of resume from suspend requires me to login 2 times instead of just once. I press shift to resume from suspend. The login prompt comes - I login. Sometimes, I get logged in. Other times, the login prompt comes again. login manager : lightdm Been using 17.10 pre-releases (and taking daily updates) since about 20 days. The problem has been around since day one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1725976/+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 1726020] [NEW] apport will not process report in /var/crash
Public bug reported: I have an 11K crash report in /var/crash, which Apport refuses to process due to a lack of "free memory to automatically analyze the problem and send a report to the developers". So I am attaching it here in case it is of interest. At least the question of why Apport has so much trouble of it might be interesting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vboxdrv.rules Date: Sun Oct 22 16:11:44 2017 InstallationDate: Installed on 2016-05-31 (509 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-05 (17 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1726020 Title: apport will not process report in /var/crash Status in systemd package in Ubuntu: New Bug description: I have an 11K crash report in /var/crash, which Apport refuses to process due to a lack of "free memory to automatically analyze the problem and send a report to the developers". So I am attaching it here in case it is of interest. At least the question of why Apport has so much trouble of it might be interesting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vboxdrv.rules Date: Sun Oct 22 16:11:44 2017 InstallationDate: Installed on 2016-05-31 (509 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-05 (17 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+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 1725708] Re: Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click
Sorry, forgot that I don't use wayland in practice as it's not close to ready but should when testing. To note: this doesn't occur in a gnome session where the context menu is opened inside the header bar so maybe add ubuntu-session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725708 Title: Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click Status in gedit package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open Gedit text editor 3. Make right mouse click on its top window bar 4. Window drop-down menu is shown, mouse is over "Minimize" option Expected results: * window drop-down menu is opened, user is able to select option from it (for example move to other workspace or maximize) Actual results: * Gedit window got minimized instantly ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:27:44 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1725708/+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 1726020] Re: apport will not process report in /var/crash
** Attachment added: "_lib_systemd_systemd-udevd.0.crash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+attachment/4985136/+files/_lib_systemd_systemd-udevd.0.crash -- 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/1726020 Title: apport will not process report in /var/crash Status in systemd package in Ubuntu: New Bug description: I have an 11K crash report in /var/crash, which Apport refuses to process due to a lack of "free memory to automatically analyze the problem and send a report to the developers". So I am attaching it here in case it is of interest. At least the question of why Apport has so much trouble of it might be interesting. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: udev 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 60-vboxdrv.rules Date: Sun Oct 22 16:11:44 2017 InstallationDate: Installed on 2016-05-31 (509 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-10-05 (17 days ago) dmi.bios.date: 11/14/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A21 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA21:bd11/14/2013:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726020/+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 1726025] [NEW] package dmeventd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139
Public bug reported: After having logged in, I receive the related message ProblemType: Package DistroRelease: Ubuntu 17.04 Package: dmeventd (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu Oct 19 16:14:52 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 139 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: lvm2 Title: package dmeventd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1726025 Title: package dmeventd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 Status in lvm2 package in Ubuntu: New Bug description: After having logged in, I receive the related message ProblemType: Package DistroRelease: Ubuntu 17.04 Package: dmeventd (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu Oct 19 16:14:52 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 139 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: lvm2 Title: package dmeventd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1726025/+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 1726025] Re: package dmeventd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1726025 Title: package dmeventd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 Status in lvm2 package in Ubuntu: New Bug description: After having logged in, I receive the related message ProblemType: Package DistroRelease: Ubuntu 17.04 Package: dmeventd (not installed) ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Thu Oct 19 16:14:52 2017 ErrorMessage: subprocess installed post-removal script returned error exit status 139 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: lvm2 Title: package dmeventd (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1726025/+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 1427600] Re: apport-unpack: ValueError: ['UserGroups'] has no binary content
To my way of thinking, an exception is for something the programmer did not foresee. Since this is now a known failure mode of Apport, I would expect - in an ideal world in which there was enough time to work on all known bugs - a clean exit with a clear error message. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1427600 Title: apport-unpack: ValueError: ['UserGroups'] has no binary content Status in apport package in Ubuntu: Triaged Status in apport source package in Xenial: Triaged Bug description: When running apport-unpack to get at a core dump laney@raleigh> sudo apport-unpack _usr_lib_x86_64-linux-gnu_urfkill_urfkilld.0.crash ~/temp/zozoz [sudo] password for laney: Traceback (most recent call last): File "/usr/bin/apport-unpack", line 73, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 253, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content laney@raleigh> apport-cli --version 2.16.2 It's not terrible, because most files are unpacked (those which sort before UserGroups, I guess). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: apport 2.16.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportLog: ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 10:09:26 2015 InstallationDate: Installed on 2012-10-07 (876 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to vivid on 2013-05-07 (665 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1427600/+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 1713086] Re: systemd fails to generate .device units inside LXD containers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1713086 Title: systemd fails to generate .device units inside LXD containers Status in systemd package in Ubuntu: Confirmed Bug description: See LXD issue here for more context: https://github.com/lxc/lxd/issues/3638 After attaching a block device (in my case /dev/sdc3) to a LXD container, the dev-sdc3.device unit is not generated. However, the dev-sdc3.mount unit is generated correctly. Steps to reproduce (from GitHub issue): stgraber@castiana:~$ truncate -s 10G test.img stgraber@castiana:~$ sudo losetup -f test.img stgraber@castiana:~$ sudo losetup -a /dev/loop1: [0022]:169383 (/var/lib/snapd/snaps/core_2381.snap) /dev/loop2: [0022]:770242 (/var/lib/snapd/snaps/core_2312.snap) /dev/loop0: [0022]:1170310 (/var/lib/snapd/snaps/core_2462.snap) /dev/loop3: [0045]:309158 (/home/stgraber/test.img) stgraber@castiana:~$ lxc launch ubuntu:16.04 issue3638 Creating issue3638 Starting issue3638 stgraber@castiana:~$ lxc config device add issue3638 sda unix-block source=/dev/loop3 path=/dev/sda Device sda added to issue3638 stgraber@castiana:~$ lxc exec issue3638 -- mkfs.ext4 /dev/sda mke2fs 1.42.13 (17-May-2015) Discarding device blocks: done Creating filesystem with 2621440 4k blocks and 655360 inodes Filesystem UUID: 77832ca2-b16d-4b94-8f7d-9ea08c5e6913 Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 Allocating group tables: done Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done stgraber@castiana:~$ echo Y | sudo tee /sys/module/ext4/parameters/userns_mounts Y stgraber@castiana:~$ lxc exec issue3638 -- mount /dev/sda /mnt stgraber@castiana:~$ lxc exec issue3638 bash root@issue3638:~# echo "/dev/sda /mnt ext4 defaults 0 0" >> /etc/fstab root@issue3638:~# cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults0 0 /dev/sda /mnt ext4 defaults 0 0 root@issue3638:~# exit stgraber@castiana:~$ lxc exec issue3638 -- umount /mnt stgraber@castiana:~$ lxc exec issue3638 -- mount /mnt stgraber@castiana:~$ lxc stop issue3638 stgraber@castiana:~$ lxc start issue3638 stgraber@castiana:~$ lxc exec issue3638 -- mount | grep mnt stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep mnt mnt.mount loadedinactive dead start /mnt stgraber@castiana:~$ lxc exec issue3638 -- systemctl -a | grep sda dev-sda.device loadedinactive dead start dev-sda.device dev-sda.mount loadedactive mounted /dev/sda stgraber@castiana:~$ lxc exec issue3638 -- ps aux | grep udev root54 0.0 0.0 41720 1864 ?Ss 16:55 0:00 /lib/systemd/systemd-udevd stgraber@castiana:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713086/+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 1712283] Re: Cannot resolve DNS in artful daily
@vorlon The resolvconf package is installed. I meaned it's not running when I check with 'systemctl status' or 'ps -ef' -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in netcfg package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1724933] Re: I can't adjust display brightness
I found that the brightness controls (via function key or sliders in power management) were changing the values in /sys/class/backlight/acpi_videos0/brightness, but nothing changed in /sys/class/backlight/intel_backlight/brightness. When I edited the value in /sys/class/backlight/intel_backlight/brightness the display backlight brightness did change. I also found that the display brightness could be changed in a unity session, (although not by function key). -- 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/1724933 Title: I can't adjust display brightness Status in xorg package in Ubuntu: Confirmed Bug description: I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I can't adjust display brightness. when I press F2|F3 keys icon brightness appears, the controller moves but the brightness doesn't change. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 22:14:51 2017 DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:3388] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-06-18 (123 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3388 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.25 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124471610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724933/+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 1724233] Re: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner()
i wiped my system and loaded production ubuntu 17.10 and the same error still exists there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1724233 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() Status in python2.7 package in Ubuntu: New Bug description: Booted into stock Ubuntu 17.10 release candidate from October 15, 2017 and this error message simply came up. apt-cache policy python python: Installed: 2.7.14-2ubuntu1 Candidate: 2.7.14-2ubuntu1 Version table: *** 2.7.14-2ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: python2.7-minimal 2.7.14-2ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 06:15:41 2017 ExecutablePath: /usr/bin/python2.7 InstallationDate: Installed on 2017-10-17 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171015) ProcCmdline: python accountable2you.pyc --username ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7f84d920daa9 : movzwl 0xa(%rdi),%r15d PC (0x7f84d920daa9) ok source "0xa(%rdi)" (0x64007d) not located in a known VMA region (needed readable region)! destination "%r15d" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: python2.7 StacktraceTop: ffi_closure_unix64_inner () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_closure_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 IceFlush () from /usr/lib/x86_64-linux-gnu/libICE.so.6 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: python2.7 crashed with SIGSEGV in ffi_closure_unix64_inner() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1724233/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
I believe I encounter this issue with Ubuntu 17.10, which uses "gnome- session 3.26.1-0ubuntu5". The story, I installed Ubuntu 17.04 back in September 2017 and been using Online Accounts for three Gmail accounts. The email client Evolution was working fine. I then upgraded to Ubuntu 17.10 a couple of days ago. After upgrade, Evolution continued to work by using the configured accounts within Online Accounts. So far so good. I then realised that Thunderbird was installed during this OS upgrade too. So I uninstalled Thunderbird with "sudo apt purge thunderbird". After that I had this problem that Online Accounts stopped working. The symptom was that all online accounts showed that the login had expired, despite me having re-logged in a couple of times. I then found this bug report and I followed the instructions provided with https://bugs.launchpad.net/ubuntu/+source/gnome-online- accounts/+bug/1610944/comments/3, which allowed me to get it working again. In the light of this, I believe this problem is still present with "gnome-session 3.26.1-0ubuntu5". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1725455] Re: Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock)
** Tags added: displayport multimonitor -- 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/1725455 Title: Dual 4K monitor via Displayport MST not working (Lenovo Ultra Dock) Status in xorg package in Ubuntu: New Bug description: I am experiencing serious issues after upgrading to Ubuntu 17.10 (coming from 17.04 with Gnome, kernel 4.13). I have 2 x 4K (Asus PB279Q) monitors, connected to a Lenovo Ultra Dock (containing 2 x Displayport via MST), where the Lenovo T550 is connected onto it. Both monitors were working perfectly fine at 30Hz simultaneously in an extended desktop, 4K resolution in my old setup with Gnome for over half a year (since kernel 4.10 blink issues on 4K were solved, i used this setup since then). However after upgrading to 17.10 using the new Gnome interface: When the laptop is connected to the Lenovo Ultra Dock (to work on both monitors), the system is hanging and becoming unresponsive. The mouse pointer is freezing and the only way is to do a hard-reboot. I have checked the monitor settings, it's displayed at 60Hz when active, and it appears I am never able to use both monitors simultaneously. When I get 1 monitor working (disconnecting the 2nd monitor from the MST port), after rebooting it works fine. I tried to put settings of the 4K manually on 30Hz, reconnecting, but the system hangs again. I have tried several combinations. It results in a blank (purple) screen and hanging mouse (see attachment). I tried also with the installation-iso to run a fresh 17.10 and tried the same, the symptoms are similar. I suspect that must be an issue with the Displayport MST on dual 4K setups in the new 17.10. When I connect 1 x 4K monitor to the rear displayport of the Lenovo Ultra Dock (there are 2 for MST on the rear, so I disconnected the other) *and* when I connect the other 4K monitor on the separate displayport of the T550 itself instead, it works 100% fine! Shortly: based on my knowledge that must definitely be some issue with the MST displayport functionality itself, that is unable to recognize/identify both 4K monitors when connected to the dock's both displayport connections? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 Uname: Linux 4.13.4-041304-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 21:10:50 2017 DistUpgraded: 2017-10-19 21:54:53,162 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:2225] Subsystem: Lenovo GM108M [GeForce 940M] [17aa:2225] InstallationDate: Installed on 2017-04-16 (186 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20CKCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.4-041304-generic root=UUID=9fcc7f4c-35c0-4297-9c98-4dac9acee798 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N11ET42W (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CKCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN11ET42W(1.18):bd09/13/2017:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T550 dmi.product.name: 20CKCTO1WW dmi.product.version: ThinkPad T550 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Apr 17 17:36:46 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.lau
[Touch-packages] [Bug 1320020] Re: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all
I have the same problem in Ubuntu 16.04 64b 4.10.0-37-generic, Dell Inspiron 15R chip Realtelk ALC 3223. I have already disabled Windows quick start but the problem persists. In the same way booting in Live cd mode. -- 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/1320020 Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I can get perfect sound through headphones, and the kernel recognizes the internal speaker, but nothing is ever played through it. I have personally tested a pair of earbuds to make sure that sound could play through the headphone port, and that isn't a problem. The sound driver just refuses to recognize the existence of the speaker, even though the kernel does. I wouldn't be surprised if the last upstream update had something to do with it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio CurrentDesktop: GNOME Date: Thu May 15 18:07:52 2014 InstallationDate: Installed on 2014-01-29 (106 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isiah 7361 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 1470, Realtek ALC272, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to trusty on 2014-05-04 (11 days ago) dmi.bios.date: 03/23/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0M7CYJ dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd03/23/2011:svnDellInc.:pnInspiron1470:pvrA05123:rvnDellInc.:rn0M7CYJ:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 1470 dmi.product.version: A05123 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1320020/+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 1726075] [NEW] [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all
Public bug reported: I cannot hear anything without headphone, the speaker don't work at all, even though after i set the speaker volume bar in the alsamixer panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remaincool 1862 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 23 00:57:26 2017 InstallationDate: Installed on 2017-07-06 (108 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: 内置音频 - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remaincool 1862 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.20:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1726075 Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: I cannot hear anything without headphone, the speaker don't work at all, even though after i set the speaker volume bar in the alsamixer panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remaincool 1862 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 23 00:57:26 2017 InstallationDate: Installed on 2017-07-06 (108 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: 内置音频 - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: remaincool 1862 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [HP Pavilion Power Laptop 15-cb0xx, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 836B dmi.board.vendor: HP dmi.board.version: 46.20 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd06/02/2017:svnHP:pnHPPavilionPowerLaptop15-cb0xx:pvrType1ProductConfigId:rvnHP:rn836B:rvr46.20:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Power Laptop 15-cb0xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1726075/+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 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)
Norbert, please open a new bug for your Ubuntu 17.10 issue. I recommend running ubuntu-bug gnome-shell ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1263228 Title: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04) Status in ido package in Ubuntu: Triaged Status in indicator-power package in Ubuntu: Fix Released Bug description: I have Ubuntu 14.04 with all updates installed. My screen resolution is 1920x1080 (FullHD) at 16.4 inches. Icons from the menu of newest indicator-keyboard and other gnome-panel icons are very small (difficult to read). Please adapt icon sizes to large screen resolutions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 21 00:41:25 2013 InstallationDate: Installed on 2013-10-20 (61 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1263228/+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 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Just a heads up, you do understand that this is a feature , not a bug ? https://bugzilla.redhat.com/show_bug.cgi?id=1274451 That bug is 2 years old and marked as "Status: CLOSED WONTFIX" both with Fedora and upstream with Wayland See https://fedoraproject.org/wiki/How_to_debug_Wayland_problems#Graphical_applications_can.27t_be_run_as_root_from_terminal And https://lists.fedoraproject.org/archives/list/devel%40lists.fedoraproject.org/thread/A6VXI4WAGSIIWGOTAVNDBVS4VFYXITHA/#2YU2RBYCXQSCGHGP772W5LRXUMTSINHA XWayland bug report (from 2015) https://bugs.freedesktop.org/show_bug.cgi?id=91071 Bottom line: This is considered a part of wayland security and will not be resolved upstream. The upstream solution is to run graphical apps from the menu, not the command line. Up to Ubuntu how to "resolve" this "problem" but Fedora decided 2 years ago to work on the grahpical tools. xhost is a work around for now and will remain so as long as apps have xwayland support. ** Bug watch added: Red Hat Bugzilla #1274451 https://bugzilla.redhat.com/show_bug.cgi?id=1274451 ** Bug watch added: freedesktop.org Bugzilla #91071 https://bugs.freedesktop.org/show_bug.cgi?id=91071 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: New Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: Posting here what gnome says about porting to wayland, and their tests: GNOME Applications under Wayland GTK+ has a Wayland backend. If it was enabled at compile-time, you can run a GTK+ application under Wayland simply by: GDK_BACKEND=wayland gnome-calculator Applications that use Clutter or clutter-gtk also need the Clutter Wayland backend enabled: GDK_BACKEND=wayland CLUTTER_BACKEND=wayland cheese https://wiki.gnome.org/Initiatives/Wayland/Applications ==> so hope the settings are well set at compile time; maybe a rebuilt to get sure all apps are ok. Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/syste
[Touch-packages] [Bug 1725708] Re: Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click
As a workaround, if you keep the right-click pressed until you move the mouse cursor over another item in the menu, it works. ** No longer affects: wayland (Ubuntu) ** Tags added: wayland -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1725708 Title: Unable to use window menu in default GNOME applications (such as Gedit) - window minimizes on right click Status in gedit package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 17.10 2. Login to the default Ubuntu session 3. Open Gedit text editor 3. Make right mouse click on its top window bar 4. Window drop-down menu is shown, mouse is over "Minimize" option Expected results: * window drop-down menu is opened, user is able to select option from it (for example move to other workspace or maximize) Actual results: * Gedit window got minimized instantly ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 17:27:44 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1725708/+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 1726096] [NEW] "file --extension" not work with PNG files
Public bug reported: $ file l3e9wvdjsvQFD_7R\?24881501 l3e9wvdjsvQFD_7R?24881501: PNG image data, 300 x 169, 8-bit/color RGB, non-interlaced $ file --extension l3e9wvdjsvQFD_7R\?24881501 l3e9wvdjsvQFD_7R?24881501: $ file Q9z_VZVdrhVhQXKb\?24881501 Q9z_VZVdrhVhQXKb?24881501: JPEG image data, JFIF standard 1.01, resolution (DPI), density 96x96, segment length 16, comment: "CREATOR: gd-jpeg v1.0 (using IJG JPEG v80), default quality", baseline, precision 8, 1920x1080, frames 3 $ file --extension Q9z_VZVdrhVhQXKb\?24881501 Q9z_VZVdrhVhQXKb?24881501: jpeg/jpg/jpe/jfif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 22 19:32:35 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 InstallationDate: Installed on 2015-02-02 (993 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: file UpgradeStatus: Upgraded to xenial on 2016-06-02 (506 days ago) ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1726096 Title: "file --extension" not work with PNG files Status in file package in Ubuntu: New Bug description: $ file l3e9wvdjsvQFD_7R\?24881501 l3e9wvdjsvQFD_7R?24881501: PNG image data, 300 x 169, 8-bit/color RGB, non-interlaced $ file --extension l3e9wvdjsvQFD_7R\?24881501 l3e9wvdjsvQFD_7R?24881501: $ file Q9z_VZVdrhVhQXKb\?24881501 Q9z_VZVdrhVhQXKb?24881501: JPEG image data, JFIF standard 1.01, resolution (DPI), density 96x96, segment length 16, comment: "CREATOR: gd-jpeg v1.0 (using IJG JPEG v80), default quality", baseline, precision 8, 1920x1080, frames 3 $ file --extension Q9z_VZVdrhVhQXKb\?24881501 Q9z_VZVdrhVhQXKb?24881501: jpeg/jpg/jpe/jfif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 22 19:32:35 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 InstallationDate: Installed on 2015-02-02 (993 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: file UpgradeStatus: Upgraded to xenial on 2016-06-02 (506 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1726096/+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 1726093] [NEW] ubuntu-desktop: Install gir1.2-gmenu-3.0 by default
Public bug reported: Impact == Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed by several popular GNOME Shell extensions. Test Case = Install the update to Ubuntu 17.10. Open the Ubuntu Software app. Search for Arc Menu Install it. There should be an A menu in the top left of the screen. Other Info == Debian-based distros are somewhat unique in that they split gir files into separate packages. This is normally not a problem since .deb packages should simply depend on the packages they need. It is a bit of a problem for GNOME Shell extensions distributed through extensions.gnome.org since they can't depend on system packages except as a comment in the extension description that may or may be read even if it is mentioned. Specifically, there are several extensions that add a traditional applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0. This wasn't noticed much before because both Debian GNOME and Ubuntu GNOME installed the gnome-shell-extensions package by default which depends on gir1.2-gmenu-3.0. Now though, it just feels to users like Ubuntu is broken. I've read comments that think that Ubuntu is intentionally trying to make it difficult to use these app menu extensions. ** Affects: ubuntu-meta (Ubuntu) Importance: Low Status: Triaged ** Tags: artful gnome-17.10 ** Tags added: gnome-17.10 -- 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/1726093 Title: ubuntu-desktop: Install gir1.2-gmenu-3.0 by default Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Impact == Ubuntu doesn't install particular files ( gir1.2-gmenu-3.0 ) that are needed by several popular GNOME Shell extensions. Test Case = Install the update to Ubuntu 17.10. Open the Ubuntu Software app. Search for Arc Menu Install it. There should be an A menu in the top left of the screen. Other Info == Debian-based distros are somewhat unique in that they split gir files into separate packages. This is normally not a problem since .deb packages should simply depend on the packages they need. It is a bit of a problem for GNOME Shell extensions distributed through extensions.gnome.org since they can't depend on system packages except as a comment in the extension description that may or may be read even if it is mentioned. Specifically, there are several extensions that add a traditional applications menu to GNOME Shell. These usually need gir1.2-gmenu-3.0. This wasn't noticed much before because both Debian GNOME and Ubuntu GNOME installed the gnome-shell-extensions package by default which depends on gir1.2-gmenu-3.0. Now though, it just feels to users like Ubuntu is broken. I've read comments that think that Ubuntu is intentionally trying to make it difficult to use these app menu extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1726093/+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 1263228] Re: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04)
Thanks, Jeremy. The bug on GNOME Shell seems to be already reported - it is bug 1725734 . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1263228 Title: icons in indicators are small (difficult to view on FullHD display and smaller than was on 12.04) Status in ido package in Ubuntu: Triaged Status in indicator-power package in Ubuntu: Fix Released Bug description: I have Ubuntu 14.04 with all updates installed. My screen resolution is 1920x1080 (FullHD) at 16.4 inches. Icons from the menu of newest indicator-keyboard and other gnome-panel icons are very small (difficult to read). Please adapt icon sizes to large screen resolutions. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CurrentDesktop: Unity Date: Sat Dec 21 00:41:25 2013 InstallationDate: Installed on 2013-10-20 (61 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-11-19 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1263228/+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 1726106] [NEW] [P95_HR, Realtek ALC1220, Speaker, Internal] No sound at all
Public bug reported: No sound at all, internal laptop speakers or headphones plugged in. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2209 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 14:16:56 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2209 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [P95_HR, Realtek ALC1220, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd07/14/2017:svnNotebook:pnP95_HR:pvrNotApplicable:rvnNotebook:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_HR dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1726106 Title: [P95_HR, Realtek ALC1220, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all, internal laptop speakers or headphones plugged in. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2209 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 14:16:56 2017 InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2209 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [P95_HR, Realtek ALC1220, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.03 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_HR dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd07/14/2017:svnNotebook:pnP95_HR:pvrNotApplicable:rvnNotebook:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_HR dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1726106/+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 1726122] [NEW] HDA VT2020 missing in pulseaudio sound settings
Public bug reported: Description:Ubuntu 17.10 Release:17.10 pulseaudio 1:10.0-2ubun amd64 Have an analog VT2020 HDA device as primary card and the HDMI digital pitcairn sound card in the system. Bug: The pulseaudio settings in the panel do only list the pitcairn device. @athena:~$ sudo aplay -l [sudo] Passwort für : Liste der Hardware-Geräte (PLAYBACK) Karte 0: SB [HDA ATI SB], Gerät 0: VT2020 Analog [VT2020 Analog] Sub-Geräte: 0/1 Sub-Gerät #0: subdevice #0 Karte 0: SB [HDA ATI SB], Gerät 1: VT2020 Digital [VT2020 Digital] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: SB [HDA ATI SB], Gerät 2: VT2020 Alt Analog [VT2020 Alt Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 8: HDMI 2 [HDMI 2] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 9: HDMI 3 [HDMI 3] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 10: HDMI 4 [HDMI 4] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 11: HDMI 5 [HDMI 5] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Both devices are recognized by alsa, kernel modules are loaded. Temporary bugfix: Installed pavucontrol, it shows the analog VT2020. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: eric 1598 F...m pulseaudio /dev/snd/controlC0: eric 1598 F pulseaudio /dev/snd/controlC1: eric 1598 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sun Oct 22 21:05:19 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-22 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2g dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2g:bd10/07/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1726122 Title: HDA VT2020 missing in pulseaudio sound settings Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu 17.10 Release: 17.10 pulseaudio 1:10.0-2ubun amd64 Have an analog VT2020 HDA device as primary card and the HDMI digital pitcairn sound card in the system. Bug: The pulseaudio settings in the panel do only list the pitcairn device. @athena:~$ sudo aplay -l [sudo] Passwort für : Liste der Hardware-Geräte (PLAYBACK) Karte 0: SB [HDA ATI SB], Gerät 0: VT2020 Analog [VT2020 Analog] Sub-Geräte: 0/1 Sub-Gerät #0: subdevice #0 Karte 0: SB [HDA ATI SB], Gerät 1: VT2020 Digital [VT2020 Digital] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 0: SB [HDA ATI SB], Gerät 2: VT2020 Alt Analog [VT2020 Alt Analog] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 3: HDMI 0 [HDMI 0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 7: HDMI 1 [HDMI 1] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 8: HDMI 2 [HDMI 2] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 9: HDMI 3 [HDMI 3] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 10: HDMI 4 [HDMI 4] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Karte 1: HDMI [HDA ATI HDMI], Gerät 11: HDMI 5 [HDMI 5] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 Both devices are recognized by alsa, kernel modules are loaded. Temporary bugfix: Installed pavucontrol, it shows the analog VT
[Touch-packages] [Bug 1726124] [NEW] DNS domain search paths not updated when VPN started
Public bug reported: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1726124 Title: DNS domain search paths not updated when VPN started Status in systemd package in Ubuntu: New Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few vers
[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
network-manager has resolved integration and it does push search domains to resolved and they are updated in the /etc/resolv.conf. This should continue to work in 17.10. Hence marking this bug affect network-manager and network-manager-openvpn ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- 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/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnA
[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
To be clear, they are NOT updated in /etc/resolv.conf. They ARE updated in /run/NetworkManager/resolv.conf, but that has no effect since we're not using that for resolution: instead we're using systemd-resolve. And as I noted above, it does appear that systemd-resolve is notified about the search domains, because "systemd-resolve --status" does show them associated with the openvpn tun0 device. However, those search domains are never manifested in the /run/systemd/resolve/stub-resolv.conf which is what /etc/resolv.conf is pointing to, so they never take effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asse
[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
Right, so it seems like NM checks the never-default setting, and doesn't push them as resolve domains =/ I will test things out to be sure. Specifically: $ nmcli c show YOUR_VNP_CONNECTION_NAME | grep never-default ipv4.never-default: yes ipv6.never-default: yes And if it is never-default, it doesn't push search domains out, only routing domains. I believe this might be actually correctly intended configuration of the openvpn and network-manager and resolved. Since all traffic is not routed to the VPN connection, its domain names should not be used for resolution. E.g. resolving "foo.company.example.net" should work and should end up being resolved via nameserver on the vpn, and not leak DNS resolution to public DNS server, and one should be able to connect to that host. But resovling "foo" should be failing. I understand this is a change of behaviour, thus does seem like a regression. I will consult on what is correct behaviour and how to best fix it. ** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf
[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
Does everything work, if you route all traffic via VPN? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To m
[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
Thank you for the update. I will check the code, and will try to resolve this as soon as possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version
[Touch-packages] [Bug 1726068] [NEW] package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit statu
You have been subscribed to a public bug: error message on start up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Oct 22 12:33:48 2017 DpkgHistoryLog: Start-Date: 2017-10-22 12:31:01 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Install: linux-image-generic:amd64 (4.4.0.97.102, automatic), libcuda1-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), linux-image-extra-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, automatic), libc6-i386:amd64 (2.23-0ubuntu9, automatic), screen-resolution-extra:amd64 (0.17.1, automatic), ocl-icd-libopencl1:amd64 (2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 (0.8-3ubuntu1, automatic), linux-generic:amd64 (4.4.0.97.102), nvidia-opencl-icd-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), nvidia-387:amd64 (387.12-0ubuntu0~gpu16.04.1), nvidia-settings:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic) EFITables: Oct 22 12:34:32 crs-Ubuntu kernel: efi: EFI v2.40 by American Megatrends Oct 22 12:34:32 crs-Ubuntu kernel: efi: ESRT=0x77e72f98 ACPI=0x77591000 ACPI 2.0=0x77591000 SMBIOS=0x77e71000 SMBIOS 3.0=0x77e7 Oct 22 12:34:32 crs-Ubuntu kernel: esrt: Reserving ESRT space from 0x77e72f98 to 0x77e72fd0. Oct 22 12:34:32 crs-Ubuntu kernel: Secure boot enabled ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-16 (159 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: High Status: Triaged ** Tags: amd64 apport-package xenial -- package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 https://bugs.launchpad.net/bugs/1726068 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. -- 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 1726068] Re: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status
This happens if software-properties is closed on the desktop before the packages have finished installing. You will need to run 'sudo apt-get -f install' from a terminal to complete the configuration of these packages. ** Package changed: shim-signed (Ubuntu) => software-properties (Ubuntu) ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1726068 Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in software-properties package in Ubuntu: Triaged Bug description: error message on start up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Oct 22 12:33:48 2017 DpkgHistoryLog: Start-Date: 2017-10-22 12:31:01 Commandline: aptdaemon role='role-commit-packages' sender=':1.94' Install: linux-image-generic:amd64 (4.4.0.97.102, automatic), libcuda1-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), linux-image-extra-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), nvidia-prime:amd64 (0.8.2, automatic), libxnvctrl0:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic), lib32gcc1:amd64 (1:6.0.1-0ubuntu1, automatic), libc6-i386:amd64 (2.23-0ubuntu9, automatic), screen-resolution-extra:amd64 (0.17.1, automatic), ocl-icd-libopencl1:amd64 (2.2.8-1, automatic), libjansson4:amd64 (2.7-3, automatic), bbswitch-dkms:amd64 (0.8-3ubuntu1, automatic), linux-generic:amd64 (4.4.0.97.102), nvidia-opencl-icd-387:amd64 (387.12-0ubuntu0~gpu16.04.1, automatic), nvidia-387:amd64 (387.12-0ubuntu0~gpu16.04.1), nvidia-settings:amd64 (384.90-0ubuntu0~gpu16.04.1, automatic) EFITables: Oct 22 12:34:32 crs-Ubuntu kernel: efi: EFI v2.40 by American Megatrends Oct 22 12:34:32 crs-Ubuntu kernel: efi: ESRT=0x77e72f98 ACPI=0x77591000 ACPI 2.0=0x77591000 SMBIOS=0x77e71000 SMBIOS 3.0=0x77e7 Oct 22 12:34:32 crs-Ubuntu kernel: esrt: Reserving ESRT space from 0x77e72f98 to 0x77e72fd0. Oct 22 12:34:32 crs-Ubuntu kernel: Secure boot enabled ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-16 (159 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1726068/+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 1712283] Re: Cannot resolve DNS in artful daily
Actually, since you have already used the method from comment #6 to point /etc/resolv.conf directly at resolved instead of at resolvconf, this is also fine. -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in netcfg package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1712283] Re: Cannot resolve DNS in artful daily
@diabloneo resolvconf doesn't leave a process running on the system; it is only triggered when there are changes to the network or to the available local resolvers, and coordinates updates to /etc/resolv.conf. But if /etc/resolv.conf is not a symlink to /run/resolvconf/resolv.conf, this has no effect. And if NetworkManager had written its own contents to /etc/resolv.conf, that means either it was not a symlink to /run/resolvconf/resolv.conf, or you were using a buggy version of NetworkManager. (The Ubuntu package of NetworkManager detects when resolvconf is in use, and avoids overwriting /etc/resolv.conf.) The question is how your system got into that state in 17.04. But this may not be a question we are able to answer after the fact. If you have any further insight into how your system got into this state, we would be interested to know. Otherwise, I recommend you follow Dimitri's guidance from comment #27 to return your system into a supported configuration. -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in netcfg package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1725680] Re: DNS name resolution doesn't work on Artful
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1725680 Title: DNS name resolution doesn't work on Artful Status in systemd package in Ubuntu: Confirmed Bug description: If I boot my laptop with a live image or an installation of Ubuntu 17.10, DNS name resolution doesn't work (which means I can't access any website). Steps to reproduce: - Boot laptop with Ubuntu 17.10 live image - Connect to my wireless network - Try to ping any website, e.g. ping ubuntu.com. This immediately fails with the error message "Name or service not known" - Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works. As a workaround, I can get a temporarily working DNS resolution by manually editing /etc/resolv.conf (symlink to /run/systemd/resolve /stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or some other known DNS server. On Ubuntu 17.04 this bug is not present. The original address in /run/systemd/resolve/stub-resolve.conf is 127.0.0.53 . I get immediate replies if I ping this address, but nevertheless DNS resolution doesn't work. It seems that the service systemd-networkd isn't active by default: $ sudo systemctl status systemd-networkd ● systemd-networkd.service - Network Service Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled; vendo Active: inactive (dead) Docs: man:systemd-networkd.service(8) Manually starting it doesn't seem to help for this bug. systemd-resolved is active: $ sudo systemctl status systemd-resolved ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-con https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl Main PID: 1095 (systemd-resolve) Status: "Processing requests..." Tasks: 1 (limit: 4915) CGroup: /system.slice/systemd-resolved.service └─1095 /lib/systemd/systemd-resolved Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution... Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors: Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2 49aac11d7b6f644 Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2 e06d44b80b8f1d3 Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors: 10.in-add Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'. Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CasperVersion: 1.387 Date: Sat Oct 21 12:26:00 2017 ExecutablePath: /lib/systemd/systemd-resolved LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Acer Extensa 5635Z ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2009 dmi.bios.vendor: Phoenix dmi.bios.version: V0.3305 dmi.board.name: BA50-MV dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV0.3305:bd08/14/2009:svnAcer:pnExtensa5635Z:pvrNotApplicable:rvnAcer:rnBA50-MV:rvrNotApplicable:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5635Z dmi.product.version: Not Applicable dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+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 1726148] Re: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move()
*** This bug is a duplicate of bug 1556439 *** https://bugs.launchpad.net/bugs/1556439 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1556439, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1726148/+attachment/4986285/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1726148/+attachment/4986288/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1726148/+attachment/4986291/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1726148/+attachment/4986292/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1726148/+attachment/4986294/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1726148/+attachment/4986295/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1726148/+attachment/4986296/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1556439 pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1726148 Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() Status in pulseaudio package in Ubuntu: New Bug description: I plugged my headphones Logitech G933 Wireless and selected them in the audio section in the settings and then I changed the volume with my keyboard fn+function ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vinid223 2567 F pulseaudio /dev/snd/controlC0: vinid223 2567 F pulseaudio /dev/snd/controlC1: vinid223 2567 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 22 16:56:46 2017 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/pulse-10.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q501LA.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q501LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ501LA.212:bd12/06/2013:svnASUSTeKCOMPUTERINC.:pnQ501LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ501LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Q dmi.product.name: Q501LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726148/+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 1726124] Re: DNS domain search paths not updated when VPN started
I'm not sure I understand what you mean. In a typical configuration you never send "foo" to the nameservice, there's always a search domain and those lookups are always tried first (because the default value for the ndots is 1). This is handled by the libc resolver linked into every program, it's not handled by a central service. I don't have any idea how systemd-resolve works. But, my understanding of how it used to work with dnsmasq using split tunneling was that the nameservice mapped domains to DNS servers, and the resolver would only forward requests to the DNS server that matched the domain for the host being requested. If you have a VPN interface that adds "mycorp.com" to the search domain that appears in /etc/resolv.conf search, so it contains "mycorp.com localdomain" for example. Then when someone tries to resolve "myhost", the libc resolver sees that there are no dots here and so it starts appending search paths to the hostname, in order, and sending them to the DNS service to look up. So first it will send "myhost.mycorp.com" to the resolver. The resolver sees that the hostname ends in "mycorp.com" and it knows that the VPN DNS servers "own" that domain, so it forwards that request to those servers for lookup. If that doesn't match, then the libc resolver will try to look up "myhost.localdomain". That does NOT match the VPN domain, so it will not try to forward that to the DNS servers for the VPN connection and instead use a different resolver. I don't think there's any information leakage here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardva
[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10
Thanks. This log shows the correct upgrade, but unfortunately it doesn't show any obvious explanation for why /etc/resolv.conf was replaced. I'll set this back to new, but I guess we aren't going to make forward progress on understanding what happened without some further information. ** Changed in: resolvconf (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1725840 Title: resolvconf not correctly configured after update from 17.04 to 17.10 Status in resolvconf package in Ubuntu: New Bug description: After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS lookup on my wireless network connection did not work any more. As it seems, the file /etc/resolv.conf was static and contained wrong data assigned by the NetworkManager. When I changed the file content manually to nameserver 127.0.0.53 DNS lookup worked fine. After reboot, however, I had to repeat this operation since NetworkManager seems to have replaced the file content. Finally, I found a solution. Running sudo dpkg-reconfigure resolvconf the file /etc/resolv.conf was replaced by the link /etc/resolv.conf -> ../run/resolvconf/resolv.conf Now, the wireless network seems to work properly. Hence, there must be some kind of bug during the update process from Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured properly. Best regards, Artur ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 21 23:17:38 2017 InstallationDate: Installed on 2013-10-18 (1463 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+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 1707393] Re: vlc no longer displays certain streams since update vdpau
Hi, I also have the same pb. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1707393 Title: vlc no longer displays certain streams since update vdpau Status in mesa package in Ubuntu: Incomplete Bug description: Display was fine until apdate of vdpau was applied. Vlc codec info from stream: Video MPEG-4 Video (mp4v) Resolution: 640x480 Framerate: 1000 Decode format: planar 4:2:0 YUV Previous recordings of this stream will also do not display anymore, while the standard Videos apllication does play them back fine. New recordings via vlc cannot be played back by both the vlc and Videos application. Console output while starting the stream: VLC media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80) [01589088] core libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface. [7f86a9b8] core input error: ES_OUT_RESET_PCR called [7f86b00092d8] vdpau_avcodec generic error: decoder profile not supported: 12 [7f86b0007ac8] vdpau_avcodec generic error: decoder profile not supported: 12 [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [mpeg4 @ 0x7f869803dfa0] warning: first frame is no keyframe [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. [7f869c001d08] vdpau_display vout display error: output surface creation failure: A catch-all error, used when no other error code applies. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 29 15:02:01 2017 InstallationDate: Installed on 2017-06-17 (42 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707393/+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 1726160] [NEW] On login, display rotates to wrong orientation.
Public bug reported: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 15:15:08 2017 DistUpgraded: 2017-10-22 14:17:00,381 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-37-generic, x86_64: installed bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed nvidia-340, 340.104, 4.10.0-37-generic, x86_64: installed nvidia-340, 340.104, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT216M [GeForce GT 230M] [10de:0a28] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT216M [GeForce GT 230M] [103c:363c] InstallationDate: Installed on 2017-01-11 (284 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) LightdmDisplayLog: (II) Server terminated successfully (0). Closing log file. MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago) dmi.bios.date: 10/05/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 363C dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.25 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1D:bd10/05/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr039D222412102:rvnHewlett-Packard:rn363C:rvr32.25:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.family: 103C_5335KV dmi.product.name: HP Pavilion dv7 Notebook PC dmi.product.version: 039D222412102 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu -- 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/1726160 Title: On login, display rotates to wrong orientation. Status in xorg package in Ubuntu: New Bug description: I'm using a laptop, and on 17.04 the display always showed correctly, but after upgrading to 17.10, when I log in the display rotates to the right (portrait), and I have to open a terminal and run 'xrandr -o 1' to get it back to the correct (landscape) orientation. In previous versions 'xrandr -o 0' was landscape, and '1' was portrait the other way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME
[Touch-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
I dont know what happend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1719004 Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Status in CUPS: Fix Released Status in cups package in Ubuntu: Invalid Status in glibc package in Ubuntu: Confirmed Bug description: 1. Error: Package/cups-daemon2.2.4-7 (mutilated) 2. compiz-core/tmp/apport_core_q_vnqis (corrupted) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Date: Fri Sep 22 22:16:18 2017 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2017-05-27 (118 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: H110M-K D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1719004/+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 1724977] Re: two mouse cursors visible at the same time
It could be related to this bug: See Comment #62 https://bugzilla.gnome.org/show_bug.cgi?id=745079#c62 ** Bug watch added: GNOME Bug Tracker #745079 https://bugzilla.gnome.org/show_bug.cgi?id=745079 -- 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/1724977 Title: two mouse cursors visible at the same time Status in xorg package in Ubuntu: New Bug description: When my 2nd Asus (Ancor) display is in portrait mode and is set to be to the left of my centered landscape display in extended mode, moving the mouse to roughly the left 20% of my landscape display will show a mouse cursor on my landcape display AND portrait display at the same time. Oddly moving a window into this area only shows on the landscape display. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 13:43:30 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:2203] InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=df6662ff-9496-4ff5-8165-82efdbf0b335 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 343522U dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET99WW(2.59):bd05/28/2014:svnLENOVO:pn343522U:pvrThinkPadX230Tablet:rvnLENOVO:rn343522U:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 Tablet dmi.product.name: 343522U dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724977/+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 1583182] Re: error on 01ifupdown script
Same problem. Recently upgraded to ubuntu server 17.10 Networking doesnt't start any interface due to this problem. Wrong arguments while calling fanctl from ubuntu-fan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1583182 Title: error on 01ifupdown script Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: When bring the interface up or down I see this message on the logs May 18 10:03:36 count0 nm-dispatcher[8608]: req:1 'up' [enp2s0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. May 18 10:03:36 count0 NetworkManager[791]: [1463576616.8466] dispatcher: (29) 01ifupdown failed (failed): Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Tracing the problem I see that the call to /usr/sbin/fanctl is done with incorrect parameters. If I execute /etc/NetworkManager/dispatcher.d/01ifupdown enp2s0 down I get this error run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 1 ubuntu-fan is doing the call in following way /usr/sbin/fanctl net "$MODE" "$IFACE" and the parameters passed by ubuntu-fan are $MODE=stop $IFACE=enp2s0 but fanctl expect other parameters as showed on the script's header -- details lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 $ apt-cache policy network-manager network-manager: Installed: 1.1.93-0ubuntu4 Candidate: 1.1.93-0ubuntu4 Version table: *** 1.1.93-0ubuntu4 500 500 http://ar.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 18 10:50:24 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-04-23 (24 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.1.1 dev enp2s0 proto static metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 172.18.0.0/16 dev br-76f79dfb13e0 proto kernel scope link src 172.18.0.1 linkdown 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.8 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH br-76f79dfb13e0 bridgeconnected /org/freedesktop/NetworkManager/Devices/2 br-76f79dfb13e0 0a9f5c9b-cd67-4fb8-a72d-1811ca6fbb68 /org/freedesktop/NetworkManager/ActiveConnection/1 docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 e5f99f7d-532f-4c52-8749-c78afa9271dd /org/freedesktop/NetworkManager/ActiveConnection/2 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 ee3ec6ee-7242-4956-9d19-20ccb19c5fe5 /org/freedesktop/NetworkManager/ActiveConnection/8 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1583182/+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 1726187] [NEW] After 17.04 -> 17.10 upgrade, wifi often freezes
Public bug reported: (might be incorrect package) About once every few hours, my wifi locks up until I use "turn off + turn on" in the network control - upper right corner drop down. This has started happening after the upgrade from 17.04 to 17.10. The wireless signal is very strong, and it remains strong even after lock up. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 20:41:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-13 (192 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.2.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.2.0/24 dev wlp58s0 proto kernel scope link src 192.168.2.131 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 c1be4834-7fc1-4167-8509-90e5d1946c14 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 pups 4bf35394-3e64-4dbe-b1b2-5d1953df7058 /org/freedesktop/NetworkManager/ActiveConnection/14 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726187 Title: After 17.04 -> 17.10 upgrade, wifi often freezes Status in network-manager package in Ubuntu: New Bug description: (might be incorrect package) About once every few hours, my wifi locks up until I use "turn off + turn on" in the network control - upper right corner drop down. This has started happening after the upgrade from 17.04 to 17.10. The wireless signal is very strong, and it remains strong even after lock up. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 20:41:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-13 (192 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.2.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.2.0/24 dev wlp58s0 proto kernel scope link src 192.168.2.131 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 c1be4834-7fc1-4167-8509-90e5d1946c14 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 pups4bf35394-3e64-4dbe-b1b2-5d1953df7058 /org/freedesktop/NetworkManager/ActiveConnection/14 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STAT
[Touch-packages] [Bug 1724933] Re: I can't adjust display brightness
I have the same problem using an ASPIRE 5750G-9463, using Optimus. -- 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/1724933 Title: I can't adjust display brightness Status in xorg package in Ubuntu: Confirmed Bug description: I'm using HP Pavilion DV6. After upgrade to Ubuntu 17.10 from 17.04 I can't adjust display brightness. when I press F2|F3 keys icon brightness appears, the controller moves but the brightness doesn't change. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 22:14:51 2017 DistUpgraded: 2017-10-19 21:15:33,861 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-37-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:3388] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (rev ff) (prog-if ff) InstallationDate: Installed on 2017-06-18 (123 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago) dmi.bios.date: 04/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3388 dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.25 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd04/25/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124471610100:rvnHewlett-Packard:rn3388:rvr10.25:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058F1124471610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1724933/+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 1726197] [NEW] ubuntu-bug complains "This tool has been deprecated, use 'gio open' instead."
Public bug reported: $ ubuntu-bug gnome-shell This tool has been deprecated, use 'gio open' instead. See 'gio help open' for more info. Presumably it's using xdg-open and needs to stop doing that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashReports: 640:0:122:599789:2017-10-20 10:31:03.720189780 -0400:2017-10-20 10:31:03.328187910 -0400:/var/crash/_opt_prod-qlmdm_client_client-cron.py.0.crash CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 21:37:56 2017 InstallationDate: Installed on 2017-05-19 (156 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful regression-release wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1726197 Title: ubuntu-bug complains "This tool has been deprecated, use 'gio open' instead." Status in apport package in Ubuntu: New Bug description: $ ubuntu-bug gnome-shell This tool has been deprecated, use 'gio open' instead. See 'gio help open' for more info. Presumably it's using xdg-open and needs to stop doing that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportLog: ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashReports: 640:0:122:599789:2017-10-20 10:31:03.720189780 -0400:2017-10-20 10:31:03.328187910 -0400:/var/crash/_opt_prod-qlmdm_client_client-cron.py.0.crash CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 21:37:56 2017 InstallationDate: Installed on 2017-05-19 (156 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1726197/+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 1725133] Re: Window buttons don't have paddings
** Also affects: ubuntu-themes Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1725133 Title: Window buttons don't have paddings Status in Ubuntu theme: New Status in ubuntu-themes package in Ubuntu: New Bug description: Window buttons don't have paddings in the Ambiance GNOME theme of Ubuntu 17.10. The Chrome window has such buttons for example. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1725133/+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 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
> FYI this problem sits high on the Pulseaudio bug list, but... For Ubuntu users yes this is the "hottest" bug in the pulseaudio package: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bugs?orderby=-heat&start=0 However, upstream have been mostly silent on this bug since January 2015: https://bugs.freedesktop.org/show_bug.cgi?id=88827 Any solution here will likely come from upstream so if you continue to experience this bug in Ubuntu 17.10 (and soon 18.04) please comment on the above link. -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1702794] Re: Automatically switch audio devices on connection
Yes, I think we'll end up with two (redundant) fixes for this. Both comment #13 and bug 1720519. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1702794 Title: Automatically switch audio devices on connection Status in pulseaudio package in Ubuntu: Fix Released Bug description: This way once a user pairs & connects a bluetooth speaker device pulseaudio will auto switch to it. As it stands now users have to open sound settings & switch manually. It's bad enough that auto discover & connect don't work, (can be scripted thru bluetoothctl), no sense adding to frustration In the ### Automatically load driver modules for Bluetooth hardware section .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doug 1843 F pulseaudio /dev/snd/controlC0: doug 1843 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 6 20:02:15 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-07-04T13:42:27.651527 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1702794/+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 1721278] Re: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later
If it helps anyone, I've got 4.14-rc5 and apparmor working. I've posted a patch at the duplicate bug https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1724450. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1721278 Title: apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/ 4.14-rc2 and later Status in apparmor package in Ubuntu: Confirmed Status in apparmor source package in Xenial: Confirmed Status in apparmor source package in Zesty: Confirmed Status in apparmor source package in Artful: Confirmed Bug description: With Ubuntu 16.04.3 LTS (Xenial Xerus), and apparmor 2.10.95-0ubuntu2.7, in the system log each second the error message below is printed to. ``` […] [Mi Okt 4 16:57:52 2017] audit: type=1400 audit(1507129072.882:554): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:53 2017] audit: type=1400 audit(1507129073.886:555): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:54 2017] audit: type=1400 audit(1507129074.886:556): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" [Mi Okt 4 16:57:55 2017] audit: type=1400 audit(1507129075.886:557): apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" pid=939 comm="cups-browsed" family="unix" sock_type="stream" protocol=0 requested_mask="create" denied_mask="create" […] ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+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 1712283] Re: Cannot resolve DNS in artful daily
@vorlon thank you for your well explaination. My system was upgraded from 16.04 -> 16.10 -> 17.04 -> 17.10, I'm not sure how it became that in 17.04. -- 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/1712283 Title: Cannot resolve DNS in artful daily Status in casper package in Ubuntu: Confirmed Status in livecd-rootfs package in Ubuntu: Fix Released Status in netcfg package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: in the current daily 21 Aug 2017, I can ping 8.8.8.8 from a live session / installed session - running on virtualbox 5.1.26. However I cannot ping google.com - "Name or service not known" Kind of difficult to run ubuntu-bug here without a fully functioning network. Happy to provide more details - please can someone guide me producing a much better bug-report? my zesty VM is working just fine. As of a week ago, my artful daily was working just fine also. * /etc/resolv.conf is empty file on most images built, which is not right, it should point to ../run/systemd/resolve/stub-resolv.conf. Should be fixed in image generation? systemd? * Adding a hack, to create /etc/resolv.conf if it does not exist, or is empty. src:systemd * network-manager does not consider that dns is managed by resolved if .53 is present in /etc/resolv.conf or if it points to stub- resolv.conf. src:network-manager * netcfg has integrtation w.r.t. /etc/resolv.conf and resolvconf. Needs checking / fixing * caster has resolvconf integration * livecd-rootfs has resolvconf integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1712283/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant
** Branch linked: lp:~3v1n0/ubuntu-themes/gtk2-scrollbars-fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1723422 Title: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [Impact] Get that error now with each random package upgrade: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Looks like related to that change: * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP: #961679) -- Marco Trevisan (Treviño) Thu, 12 Oct 2017 05:19:32 + That installation is a default Ubuntu , no Mate installed [Test case] 1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal 2. App has to run without any error [Possible regression] Different scrollbars in gtk2 apps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171012.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 14:52:43 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1723422] Re: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant
** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => In Progress ** Description changed: + [Impact] + Get that error now with each random package upgrade: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Looks like related to that change: * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP: - #961679) + #961679) - -- Marco Trevisan (Treviño) Thu, 12 Oct 2017 05:19:32 + -- Marco Trevisan (Treviño) Thu, 12 Oct 2017 05:19:32 + + That installation is a default Ubuntu , no Mate installed - That installation is a default Ubuntu , no Mate installed + [Test case] + + 1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal + 2. App has to run without any error + + [Possible regression] + + Different scrollbars in gtk2 apps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171012.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 14:52:43 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1723422 Title: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [Impact] Get that error now with each random package upgrade: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Looks like related to that change: * gtk2: Ambiance, Radiance: inherit style fixes from MATE themes (LP: #961679) -- Marco Trevisan (Treviño) Thu, 12 Oct 2017 05:19:32 + That installation is a default Ubuntu , no Mate installed [Test case] 1. Run a gtk2 application (with ambiance/radiance set as theme) in terminal 2. App has to run without any error [Possible regression] Different scrollbars in gtk2 apps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171012.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Oct 13 14:52:43 2017 EcryptfsInUse: Yes PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1723422/+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 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
** Tags added: pulse11 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Confirmed Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720684/+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 1725306] Re: gnome-shell crashed with SIGSEGV
** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGSEGV + gnome-shell crashed with SIGSEGV in llvm_pipeline_generic() from llvm_middle_end_linear_run() ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1725306 Title: gnome-shell crashed with SIGSEGV in llvm_pipeline_generic() from llvm_middle_end_linear_run() Status in gnome-shell package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: Ubuntu 17.10 updated from 17.04. System stuck in a loop on boot (after Ubuntu logo appears). ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Oct 20 16:18:48 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-09-19 (761 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) ProcCmdline: /usr/bin/gnome-shell SegvAnalysis: Segfault happened at: 0x9586f257:movd 0x8(%ecx,%eax,1),%xmm3 PC (0x9586f257) ok source "0x8(%ecx,%eax,1)" (0x0008) not located in a known VMA region (needed readable region)! destination "%xmm3" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so ?? () from /usr/lib/i386-linux-gnu/dri/r300_dri.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725306/+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 1712302] Re: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1712302 Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным Status in openssh package in Ubuntu: Expired Bug description: Something wrong ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ssh 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Aug 14 11:26:10 2017 ErrorMessage: проблемы зависимостей — оставляем не настроенным InstallationDate: Installed on 2017-02-28 (175 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: openssh Title: package ssh 1:7.2p2-4ubuntu2.2 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1712302/+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 1712524] Re: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1712524 Title: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: No sounds work ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asgeir 1383 F pulseaudio asgeir 4491 F alsamixer CurrentDesktop: Unity Date: Wed Aug 23 11:51:02 2017 InstallationDate: Installed on 2017-08-17 (6 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asgeir 1383 F pulseaudio asgeir 4491 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [UX430UA, Realtek ALC295, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UA.201 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX430UA.201:bd12/16/2016:svnASUSTeKCOMPUTERINC.:pnUX430UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX430UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1712524/+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 1726074] Re: pulseaudio crashed with SIGSEGV in pa_mcalign_csize()
** Information type changed from Private to Public ** Summary changed: - pulseaudio crashed with SIGSEGV in pa_mcalign_csize() + pulseaudio crashed with SIGSEGV in pa_mcalign_csize() from pa_memblockq_push_align() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1726074 Title: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() from pa_memblockq_push_align() Status in pulseaudio package in Ubuntu: New Bug description: No action by user - listening to Pandora in Chromium while working in LibreOffice. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mike 10674 F pulseaudio /dev/snd/pcmC1D0p: mike 10674 F...m pulseaudio /dev/snd/controlC1: mike 10674 F pulseaudio CurrentDesktop: KDE Date: Sun Oct 22 12:56:26 2017 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2017-10-21 (0 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: pulseaudio StacktraceTop: pa_mcalign_csize () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so pa_memblockq_push_align () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-10.0.so pa_sink_input_peek () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so pa_sink_render_into () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-10.0.so Title: pulseaudio crashed with SIGSEGV in pa_mcalign_csize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse pulse-access sambashare sudo dmi.bios.date: 04/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/07/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-Gaming 3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1726074/+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 1720400] Re: /usr/bin/gnome-control-center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render
Same here, made a fresh install of the distro, added the google account and then the crash happened -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1720400 Title: /usr/bin/gnome-control- center:11:update_buffers:image_get_buffers:intel_update_image_buffers:intel_update_renderbuffers:intel_prepare_render Status in GTK+: Confirmed Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.26.0-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f738a467f5d04cbf9ac6cf7554a28bd064e4091a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1720400/+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 1719355] Re: Switcher widget background goes outside its border
** Description changed: + [Impact] + In both Ambiance and Radiance themes, the switcher background is visible outside the widget border when inside a headerbar. + See picture from Gnome Control Settings -> Search - See picture from Gnome Control Settings -> Search + [Test case] + + 1. Open Gnome Control Settings -> Search + 2. Ensure that no extra border is around the switcher (especially in the headerbar) + + [Regression potential] + + Switchers borders are incorrect -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1719355 Title: Switcher widget background goes outside its border Status in Ubuntu theme: In Progress Status in Ubuntu UX: New Status in ubuntu-themes package in Ubuntu: In Progress Bug description: [Impact] In both Ambiance and Radiance themes, the switcher background is visible outside the widget border when inside a headerbar. See picture from Gnome Control Settings -> Search [Test case] 1. Open Gnome Control Settings -> Search 2. Ensure that no extra border is around the switcher (especially in the headerbar) [Regression potential] Switchers borders are incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1719355/+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 1726187] Re: After 17.04 -> 17.10 upgrade, wifi often freezes
Correction: the wifi icon turns to question mark in the upper right corner, even though ifconfig and wifi connection selection still shows the connection as active. The wifi off/on quickly fixes the issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1726187 Title: After 17.04 -> 17.10 upgrade, wifi often freezes Status in network-manager package in Ubuntu: New Bug description: (might be incorrect package) About once every few hours, my wifi locks up until I use "turn off + turn on" in the network control - upper right corner drop down. This has started happening after the upgrade from 17.04 to 17.10. The wireless signal is very strong, and it remains strong even after lock up. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 22 20:41:31 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-04-13 (192 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) IpRoute: default via 192.168.2.1 dev wlp58s0 proto static metric 600 169.254.0.0/16 dev wlp58s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.2.0/24 dev wlp58s0 proto kernel scope link src 192.168.2.131 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2017-10-19 (3 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/3 docker0 c1be4834-7fc1-4167-8509-90e5d1946c14 /org/freedesktop/NetworkManager/ActiveConnection/2 wlp58s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 pups4bf35394-3e64-4dbe-b1b2-5d1953df7058 /org/freedesktop/NetworkManager/ActiveConnection/14 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1726187/+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 1725487] [NEW] Hot corner ripple animation is still blue in Ubuntu/Ambiance
You have been subscribed to a public bug:
Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
hot-corner' as true, the colour of the ripple is still blue (Adwaita
default scheme) since the compiled shell theme still uses the specified
asset resource:///org/gnome/shell/theme/corner-ripple-ltr.png - this is
also valid for the rtl asset.
I have solved the issue by appending an override to match the current
ubuntu.css overrides as follows:
.ripple-box {
border-radius: 0px 0px 64px 0px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
}
.ripple-box:rtl {
border-radius: 0px 0px 0px 64px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
}
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:25:06 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-themes (Ubuntu)
Importance: Low
Status: New
** Tags: amd64 apport-bug artful wayland-session
--
Hot corner ripple animation is still blue in Ubuntu/Ambiance
https://bugs.launchpad.net/bugs/1725487
You received this bug notification because you are a member of Ubuntu Touch
seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
--
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 1725487] Re: Hot corner ripple animation is still blue
** Summary changed:
- ubuntu.css styling issues - hot corner ripple box
+ Hot corner ripple animation is still blue
** Summary changed:
- Hot corner ripple animation is still blue
+ Hot corner ripple animation is still blue in Ubuntu/Ambiance
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Also affects: ubuntu-themes
Importance: Undecided
Status: New
** Changed in: ubuntu-themes
Importance: Undecided => Low
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
** No longer affects: ubuntu-themes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1725487
Title:
Hot corner ripple animation is still blue in Ubuntu/Ambiance
Status in gnome-shell package in Ubuntu:
Triaged
Bug description:
Enabling hot-corners using dconf-editor under 'org.gnome.shell enable-
hot-corner' as true, the colour of the ripple is still blue (Adwaita
default scheme) since the compiled shell theme still uses the
specified asset resource:///org/gnome/shell/theme/corner-ripple-
ltr.png - this is also valid for the rtl asset.
I have solved the issue by appending an override to match the current
ubuntu.css overrides as follows:
.ripple-box {
border-radius: 0px 0px 64px 0px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
}
.ripple-box:rtl {
border-radius: 0px 0px 0px 64px !important;
background: #e95420 !important;
width:64px !important;
height:64px !important;
}
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 20 17:25:06 2017
DisplayManager: gdm3
InstallationDate: Installed on 2017-10-20 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1725487/+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
