[Touch-packages] [Bug 1713391] Re: glib-compile-schemas invalid free in per session override
IIRC, the override is using an invalid gsettings key (hence gsettings
erroring out instead of segfault). Maybe somebody should fix it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1713391
Title:
glib-compile-schemas invalid free in per session override
Status in glib2.0 package in Ubuntu:
Triaged
Bug description:
reinstall nautilus error with package sogoupinyin
# sudo nautilus
sys:1: PyGIWarning: Nautilus was imported without specifying a version
first. Use gi.require_version('Nautilus', '3.0') before import to
ensure that the right version gets loaded.
** Message: Init Stock Icons
(nautilus:10235): GLib-GIO-ERROR **: Settings schema
'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'
#sudo apt-get install --reinstall nautilus nautilus-share nautilus-data
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
需要下载 0 B/3,298 kB 的归档。
解压缩后会消耗 0 B 的额外空间。
您希望继续执行吗？ [Y/n] y
(正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb ...
正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb ...
正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb ...
正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb ...
正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb ...
正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb ...
正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb ...
正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
*** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double
free or corruption (fasttop): 0x58242808 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
/lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
/lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
=== Memory map:
5659b000-565a5000 r-xp 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a6000-565a7000 r--p a000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a7000-565a8000 rw-p b000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
58113000-5829 rw-p 00:00 0
[heap]
f6e0-f6e21000 rw-p 00:00 0
f6e21000-f6f0 ---p 00:00 0
f6f75000-f712b000 r--p 002da000 08:01 25170585
/usr/lib/locale/locale-archive
f712b000-f732b000 r--p 08:01 25170585
/usr/lib/locale/locale-archive
f732b000-f732d000 rw-p 00:00 0
f732d000-f7346000 r-xp 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7346000-f7347000 r--p 00018000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7347000-f7348000 rw-p 00019000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7348000-f734a000 rw-p 00:00 0
f734a000-f73c1000 r-xp 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c1000-f73c2000 r--p 00076000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c2000-f73c3000 rw-p 00077000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c3000-f7576000 r-xp 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7576000-f7577000 ---p 001b3000 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7577000-f7579000 r--p 001b3000 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7579000-f757a000 rw-p 001b5000 08:01 50856273
[Touch-packages] [Bug 1052360] Re: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) for an unknown reason
Hello. Seen a crash report window appear on Ubuntu 16.04, mentioning DuplicateOf https://bugs.launchpad.net/bugs/1052360 . Also received the "unattended-upgrade" mail as usual. It said: > Écriture du journal de dpkg dans « > /var/log/unattended-upgrades/unattended-upgrades-dpkg.log » > Échec de l'installation des mises à niveau ! > message d'erreur : « installArchives() failed » > Dpkg a retourné une erreur ! Voir « > /var/log/unattended-upgrades/unattended-upgrades-dpkg.log » pour les détails Besides, /var/log/unattended-upgrades/unattended-upgrades-dpkg.log was > Log started: 2017-09-02 06:34:22 > Error in function: install > Log ended: 2017-09-02 06:34:22 > > Log started: 2017-09-04 06:08:45 > Error in function: install > Log ended: 2017-09-04 06:08:45 So, no real clue here either. Seen comment #24. Hard to open a new bug with so few information. Perhaps the *real* bug is that code paths don't propagate errors with enough details to allow proper tracing of what happends when things fail? My 2 cents. :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1052360 Title: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) for an unknown reason Status in unattended-upgrades package in Ubuntu: Invalid Bug description: Happens by itself ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: unattended-upgrades 0.73ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-26.42-generic 3.0.42 Uname: Linux 3.0.0-26-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Tue Sep 18 09:24:15 2012 ExecutablePath: /usr/bin/unattended-upgrade InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/unattended-upgrade ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/sh PythonArgs: ['/usr/bin/unattended-upgrade'] SourcePackage: unattended-upgrades Title: unattended-upgrade crashed with SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) Traceback: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2012-08-24T13:58:31.952771 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1052360/+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 1702502] Re: many messages
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1702502 Title: many messages Status in xorg package in Ubuntu: Expired Bug description: there are many messages of sending errors report when ubuntu starts ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jul 5 15:07:25 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:1477] Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 740M] [1043:1477] LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK COMPUTER INC. N46VB ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N46VB.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N46VB 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.:bvrN46VB.204:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnN46VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN46VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N46VB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jul 5 15:02:52 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702502/+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 1714866] [NEW] Update libproxy to 0.4.15
Public bug reported: https://github.com/libproxy/libproxy/releases Big change here is updating the dependency from mozjs185 (from Firefox 4!) to mozjs38. libproxy1-plugin-mozjs is in universe and has no Ubuntu reverse dependencies (Debian Edu uses it for something though.) I don't have any proxies so I haven't tested this beyond making sure it builds. ** Affects: libproxy (Ubuntu) Importance: Wishlist Status: New ** Tags: artful upgrade-software-version ** Description changed: + https://github.com/libproxy/libproxy/releases + Big change here is updating the dependency from mozjs185 (from Firefox - 4!) to mozjs38. + 4!) to mozjs38. libproxy1-plugin-mozjs is in universe and has no Ubuntu + reverse dependencies (Debian Edu uses it for something though.) - https://github.com/libproxy/libproxy/releases + I don't have any proxies so I haven't tested this beyond making sure it + builds. ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libproxy in Ubuntu. https://bugs.launchpad.net/bugs/1714866 Title: Update libproxy to 0.4.15 Status in libproxy package in Ubuntu: New Bug description: https://github.com/libproxy/libproxy/releases Big change here is updating the dependency from mozjs185 (from Firefox 4!) to mozjs38. libproxy1-plugin-mozjs is in universe and has no Ubuntu reverse dependencies (Debian Edu uses it for something though.) I don't have any proxies so I haven't tested this beyond making sure it builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libproxy/+bug/1714866/+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 1617290] Re: System Image fails with “FileNotFoundError”
** Tags removed: upgrade-software-version
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to system-image in Ubuntu.
https://bugs.launchpad.net/bugs/1617290
Title:
System Image fails with “FileNotFoundError”
Status in system-image package in Ubuntu:
New
Status in ubuntu-system-settings package in Ubuntu:
Invalid
Bug description:
Hello, I have a problem on my M10 FHD witch is on rc-proposed channel (r173
now). I can't receive any updates for system image or any installed app. I even
receive a notify in message indicator, but when I open update manager it
searches for updates and found nothing (saying that my system is up to date).
There should be updates at least for some apps and 2 system image updates since
then. Rebooting and shutdowning device didn't help. My Meizu MX4 is updating
normally with
the same network connection.
It would be very nice to have some workaround and fix this.
`system-image-cli -n -vv` ouput:
phablet@ubuntu-phablet:~$ system-image-cli -n -vv
[systemimage] Aug 25 12:31:41 2016 (5245) -> [ 1] _cleanup
[systemimage] Aug 25 12:31:41 2016 (5245) -> [ 2] _get_blacklist_1
[systemimage] Aug 25 12:31:41 2016 (5245) No valid image master key found,
downloading
[systemimage] Aug 25 12:31:41 2016 (5245) [0xf60d0850] Requesting group
download:
https://system-image.ubuntu.com/gpg/image-master.tar.xz ->
/android/cache/recovery/keyring.tar.xz
https://system-image.ubuntu.com/gpg/image-master.tar.xz.asc ->
/android/cache/recovery/keyring.tar.xz.asc
[systemimage] Aug 25 12:31:41 2016 (5245) Allow GSM? No
[systemimage] Aug 25 12:31:41 2016 (5245)
[/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc]
Running group download reactor
[systemimage] Aug 25 12:31:41 2016 (5245) self: , self._iface: :1.141
/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc
at 0xf60d0930> implementing 'com.canonical.applications.GroupDownload' at
0xf60d0890>
[systemimage] Aug 25 12:32:21 2016 (5245)
https://system-image.ubuntu.com/gpg/image-master.tar.xz:
[systemimage] Aug 25 12:32:21 2016 (5245)
[/com/canonical/applications/download/com_2eubuntu_2eterminal_5fterminal_5f0_2e7_2e198/fcef27f761f34d45a7cd71a17c0089dc]
Group download reactor done
[systemimage] Aug 25 12:32:21 2016 (5245) Reactor error:
https://system-image.ubuntu.com/gpg/image-master.tar.xz:
Exception occurred during dry-run; see log file for details
[systemimage] Aug 25 12:32:21 2016 (5245) system-image-cli exception
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/systemimage/main.py", line 365, in main
state.run_until('download_files')
File "/usr/lib/python3/dist-packages/systemimage/state.py", line 179, in
run_until
step()
File "/usr/lib/python3/dist-packages/systemimage/state.py", line 210, in
_get_blacklist_1
'image-master', 'gpg/image-master.tar.xz', 'archive-master')
File "/usr/lib/python3/dist-packages/systemimage/keyring.py", line 107, in
get_keyring
(ascxz_src, ascxz_dst),
File "/usr/lib/python3/dist-packages/systemimage/download.py", line 209, in
get_files
self._get_files(records, pausable, signal_started)
File "/usr/lib/python3/dist-packages/systemimage/udm.py", line 175, in
_get_files
raise FileNotFoundError(reactor.error)
FileNotFoundError: https://system-image.ubuntu.com/gpg/image-master.tar.xz:
phablet@ubuntu-phablet:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1617290/+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 1701928] Re: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701928 Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Installing Perl6 Though problem may be due to a previous failed upgrade. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: bsdutils:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jul 1 15:22:47 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-10-24 (251 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to zesty on 2017-04-17 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701928/+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 1701928] Re: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dpkg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701928 Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Installing Perl6 Though problem may be due to a previous failed upgrade. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: bsdutils:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jul 1 15:22:47 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-10-24 (251 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to zesty on 2017-04-17 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701928/+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 1714855] [NEW] Stucked in Airplane mode after suspend
Public bug reported: I have updated to the latest version (as of 2017/9/4) of all my package in my Artful. Hardware Platform: HP Spectre X360 (2015) Software Version: 1.8.2-1ubuntu5 Steps to Reproduce on my Laptop: 1. Login to my account. 2. Connect to the wireless network as usual. 3. Suspend the machine by closing the lit. 4. Open up the lit and login again. Expected: The machine works normally. Actually got: The machine stucked at Airplane mode. I can neither disable the airplane mode by the top right menu nor by the network settings UI. The airplane mode stays on every time after I switch it off. I have to reboot to resume the network. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1714855 Title: Stucked in Airplane mode after suspend Status in network-manager package in Ubuntu: New Bug description: I have updated to the latest version (as of 2017/9/4) of all my package in my Artful. Hardware Platform: HP Spectre X360 (2015) Software Version: 1.8.2-1ubuntu5 Steps to Reproduce on my Laptop: 1. Login to my account. 2. Connect to the wireless network as usual. 3. Suspend the machine by closing the lit. 4. Open up the lit and login again. Expected: The machine works normally. Actually got: The machine stucked at Airplane mode. I can neither disable the airplane mode by the top right menu nor by the network settings UI. The airplane mode stays on every time after I switch it off. I have to reboot to resume the network. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1714855/+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 1713391] Re: glib-compile-schemas invalid free in per session override
It was only showing this core dump when installing package with apt before. but
after upgrade to latest packages today (apt update && apt full-upgrade), I
can't login to GDM (black screen).
The workaround is remove the package sogoupinyin, which provide this file
/usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override
but now I can't use the best Chinese pinyin IME on linux...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1713391
Title:
glib-compile-schemas invalid free in per session override
Status in glib2.0 package in Ubuntu:
Triaged
Bug description:
reinstall nautilus error with package sogoupinyin
# sudo nautilus
sys:1: PyGIWarning: Nautilus was imported without specifying a version
first. Use gi.require_version('Nautilus', '3.0') before import to
ensure that the right version gets loaded.
** Message: Init Stock Icons
(nautilus:10235): GLib-GIO-ERROR **: Settings schema
'org.gnome.nautilus.preferences' does not contain a key named 'fts-default'
#sudo apt-get install --reinstall nautilus nautilus-share nautilus-data
rabbitvcs-nautilus ubuntu-desktop libglib2.0-0
正在读取软件包列表... 完成
正在分析软件包的依赖关系树
正在读取状态信息... 完成
升级了 0 个软件包，新安装了 0 个软件包，重新安装了 7 个软件包，要卸载 0 个软件包，有 0 个软件包未被升级。
需要下载 0 B/3,298 kB 的归档。
解压缩后会消耗 0 B 的额外空间。
您希望继续执行吗？ [Y/n] y
(正在读取数据库 ... 系统当前共安装有 265294 个文件和目录。)
正准备解包 .../0-libglib2.0-0_2.53.6-1ubuntu1_amd64.deb ...
正在将 libglib2.0-0:amd64 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../1-libglib2.0-0_2.53.6-1ubuntu1_i386.deb ...
正在将 libglib2.0-0:i386 (2.53.6-1ubuntu1) 解包到 (2.53.6-1ubuntu1) 上 ...
正准备解包 .../2-nautilus_1%3a3.25.90-0ubuntu1_amd64.deb ...
正在将 nautilus (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../3-nautilus-data_1%3a3.25.90-0ubuntu1_all.deb ...
正在将 nautilus-data (1:3.25.90-0ubuntu1) 解包到 (1:3.25.90-0ubuntu1) 上 ...
正准备解包 .../4-nautilus-share_0.7.3-2ubuntu2_amd64.deb ...
正在将 nautilus-share (0.7.3-2ubuntu2) 解包到 (0.7.3-2ubuntu2) 上 ...
正准备解包 .../5-rabbitvcs-nautilus_0.16-1.1_all.deb ...
正在将 rabbitvcs-nautilus (0.16-1.1) 解包到 (0.16-1.1) 上 ...
正准备解包 .../6-ubuntu-desktop_1.397_amd64.deb ...
正在将 ubuntu-desktop (1.397) 解包到 (1.397) 上 ...
正在设置 nautilus-data (1:3.25.90-0ubuntu1) ...
正在处理用于 mime-support (3.60ubuntu1) 的触发器 ...
正在设置 libglib2.0-0:i386 (2.53.6-1ubuntu1) ...
覆盖文件 /usr/share/glib-2.0/schemas/50_sogoupinyin.gschema.override 中指定的方案
org.gnome.settings-daemon.plugins.xsettings 中没有键 Gtk/IMModule；忽略对此键的覆盖。
*** Error in `/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas': double
free or corruption (fasttop): 0x58242808 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x67f5a)[0xf742af5a]
/lib/i386-linux-gnu/libc.so.6(+0x6eb57)[0xf7431b57]
/lib/i386-linux-gnu/libc.so.6(+0x6f496)[0xf7432496]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xf75ca0b0]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_strfreev+0x3f)[0xf75e59bf]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x345e)[0x5659e45e]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6)[0xf73db286]
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas(+0x34ca)[0x5659e4ca]
=== Memory map:
5659b000-565a5000 r-xp 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a6000-565a7000 r--p a000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
565a7000-565a8000 rw-p b000 08:01 28049954
/usr/lib/i386-linux-gnu/glib-2.0/glib-compile-schemas
58113000-5829 rw-p 00:00 0
[heap]
f6e0-f6e21000 rw-p 00:00 0
f6e21000-f6f0 ---p 00:00 0
f6f75000-f712b000 r--p 002da000 08:01 25170585
/usr/lib/locale/locale-archive
f712b000-f732b000 r--p 08:01 25170585
/usr/lib/locale/locale-archive
f732b000-f732d000 rw-p 00:00 0
f732d000-f7346000 r-xp 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7346000-f7347000 r--p 00018000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7347000-f7348000 rw-p 00019000 08:01 50856428
/lib/i386-linux-gnu/libpthread-2.24.so
f7348000-f734a000 rw-p 00:00 0
f734a000-f73c1000 r-xp 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c1000-f73c2000 r--p 00076000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c2000-f73c3000 rw-p 00077000 08:01 50856034
/lib/i386-linux-gnu/libpcre.so.3.13.3
f73c3000-f7576000 r-xp 08:01 50856273
/lib/i386-linux-gnu/libc-2.24.so
f7576000-f7577000 ---p 001b3000
[Touch-packages] [Bug 1419267] Re: libjpegturbo.so missing from -dev package
reopening. What is the reason to have this package, when you can use the standard jpeg8 headers? ** Changed in: libjpeg-turbo (Ubuntu) Status: Fix Released => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1419267 Title: libjpegturbo.so missing from -dev package Status in One Hundred Papercuts: Invalid Status in libjpeg-turbo package in Ubuntu: Incomplete Bug description: $ dpkg -L libjpeg-turbo8-dev /. /usr /usr/share /usr/share/doc /usr/share/doc/libjpeg-turbo8-dev /usr/share/doc/libjpeg-turbo8-dev/copyright /usr/share/doc/libjpeg-turbo8-dev/README.gz /usr/share/doc/libjpeg-turbo8-dev/structure.txt.gz /usr/share/doc/libjpeg-turbo8-dev/README-turbo.txt.gz /usr/share/doc/libjpeg-turbo8-dev/libjpeg.txt.gz /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libjpeg.a /usr/lib/x86_64-linux-gnu/libturbojpeg.a /usr/include /usr/include/jerror.h /usr/include/turbojpeg.h /usr/include/jmorecfg.h /usr/include/jpeglib.h /usr/include/jpegint.h /usr/include/x86_64-linux-gnu /usr/include/x86_64-linux-gnu/jconfig.h /usr/share/doc/libjpeg-turbo8-dev/changelog.Debian.gz /usr/lib/x86_64-linux-gnu/libjpeg.so See the libjpeg.so symlink. This is good. I also expect a libturbojpeg.so symlink. This is missing. Please add so that I can build software which depends on this dynamic library without manually creating this symlink. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libturbojpeg 1.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 Date: Sat Feb 7 08:41:19 2015 Dependencies: gcc-4.9-base 4.9.1-16ubuntu6 libc6 2.19-10ubuntu2.2 libgcc1 1:4.9.1-16ubuntu6 multiarch-support 2.19-10ubuntu2.2 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libjpeg-turbo UpgradeStatus: Upgraded to utopic on 2014-10-24 (105 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1419267/+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 1714839] Re: Xorg freezes on zesty default 4.10 kernel
** Attachment added: "Kernel log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+attachment/4943840/+files/kern.log -- 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/1714839 Title: Xorg freezes on zesty default 4.10 kernel Status in xorg package in Ubuntu: New Bug description: When running the 4.10 kernel I get the following errors an a X lockup when trying to login as a user. kern.log:Sep 3 18:13:58 xps kernel: [ 292.378581] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317] kern.log:Sep 3 18:14:26 xps kernel: [ 320.341897] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Sep 3 18:33:15 2017 DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell Device [1028:07be] InstallationDate: Installed on 2017-03-09 (178 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago) dmi.bios.date: 01/09/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+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 1714839] Re: Xorg freezes on zesty default 4.10 kernel
Workaround is to boot into the old 4.8 kernel. -- 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/1714839 Title: Xorg freezes on zesty default 4.10 kernel Status in xorg package in Ubuntu: New Bug description: When running the 4.10 kernel I get the following errors an a X lockup when trying to login as a user. kern.log:Sep 3 18:13:58 xps kernel: [ 292.378581] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317] kern.log:Sep 3 18:14:26 xps kernel: [ 320.341897] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Sep 3 18:33:15 2017 DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell Device [1028:07be] InstallationDate: Installed on 2017-03-09 (178 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago) dmi.bios.date: 01/09/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714839/+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 1714839] [NEW] Xorg freezes on zesty default 4.10 kernel
Public bug reported: When running the 4.10 kernel I get the following errors an a X lockup when trying to login as a user. kern.log:Sep 3 18:13:58 xps kernel: [ 292.378581] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317] kern.log:Sep 3 18:14:26 xps kernel: [ 320.341897] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Sep 3 18:33:15 2017 DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell Device [1028:07be] InstallationDate: Installed on 2017-03-09 (178 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago) dmi.bios.date: 01/09/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.3 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: 4.10 amd64 apport-bug freeze ubuntu zesty -- 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/1714839 Title: Xorg freezes on zesty default 4.10 kernel Status in xorg package in Ubuntu: New Bug description: When running the 4.10 kernel I get the following errors an a X lockup when trying to login as a user. kern.log:Sep 3 18:13:58 xps kernel: [ 292.378581] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317] kern.log:Sep 3 18:14:26 xps kernel: [ 320.341897] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17 Uname: Linux 4.8.0-59-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sun Sep 3 18:33:15 2017 DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07be] Subsystem: Dell Device [1028:07be] InstallationDate: Installed on 2017-03-09 (178 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: Dell Inc. XPS 15 9560 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1714834] [NEW] display is detected on a non-connected DP port
Public bug reported: I have my screen connected to HDMI, and I also have a DP cable plugged in. The single screen attached gets detected twice, xrands shows both HDMI-1 as connected (primary) and DP-1 connected as well. If I disconnect the DP cable xrandr does now show it as connected anymore. xrandr output below: $ xrandr Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 HDMI-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 553mm x 311mm 2560x1440 59.95*+ 2048x1152 60.00 1920x1200 59.95 1920x1080 60.0060.0050.0059.9430.0025.0024.00 29.9723.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1200x960 59.99 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 DP-1 connected (normal left inverted right x axis y axis) 2560x1440 59.95 + 2048x1152 60.00 1920x1200 59.88 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.95 1280x1024 75.0260.02 1200x960 59.99 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 HDMI-2 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Mon Sep 4 00:45:37 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.40, 4.10.0-28-generic, x86_64: installed virtualbox, 5.0.40, 4.10.0-32-generic, x86_64: installed virtualbox, 5.0.40, 4.10.0-33-generic, x86_64: installed virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake Integrated Graphics [8086:2063] InstallationDate: Installed on 2016-06-18 (441 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=04f11ff8-1726-4c69-9fec-69890c6d9f74 ro text SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corp. dmi.board.vendor: Intel corporation version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Sep 4 00:25:20 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1714834 Title: display is detected on a non-connected DP port Status in xorg package in Ubuntu: New Bug description: I have my screen connected to HDMI, and I also have a DP cable plugged in. The single screen attached gets detected twice, xrands shows both HDMI-1 as connected (primary) and DP-1 connected as well. If I disconnect the DP cable xrandr does now show it as
[Touch-packages] [Bug 1056566] Re: Missing pkgconfig file
** Changed in: libjpeg-turbo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1056566 Title: Missing pkgconfig file Status in libjpeg-turbo package in Ubuntu: Fix Released Bug description: Our packages do not contain a turbojpeg.pc file, meaning any pkgconfig-using build script that depends on it being in libjpeg-turbo may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1056566/+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 1419267] Re: libjpegturbo.so missing from -dev package
** Changed in: libjpeg-turbo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1419267 Title: libjpegturbo.so missing from -dev package Status in One Hundred Papercuts: Invalid Status in libjpeg-turbo package in Ubuntu: Fix Released Bug description: $ dpkg -L libjpeg-turbo8-dev /. /usr /usr/share /usr/share/doc /usr/share/doc/libjpeg-turbo8-dev /usr/share/doc/libjpeg-turbo8-dev/copyright /usr/share/doc/libjpeg-turbo8-dev/README.gz /usr/share/doc/libjpeg-turbo8-dev/structure.txt.gz /usr/share/doc/libjpeg-turbo8-dev/README-turbo.txt.gz /usr/share/doc/libjpeg-turbo8-dev/libjpeg.txt.gz /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libjpeg.a /usr/lib/x86_64-linux-gnu/libturbojpeg.a /usr/include /usr/include/jerror.h /usr/include/turbojpeg.h /usr/include/jmorecfg.h /usr/include/jpeglib.h /usr/include/jpegint.h /usr/include/x86_64-linux-gnu /usr/include/x86_64-linux-gnu/jconfig.h /usr/share/doc/libjpeg-turbo8-dev/changelog.Debian.gz /usr/lib/x86_64-linux-gnu/libjpeg.so See the libjpeg.so symlink. This is good. I also expect a libturbojpeg.so symlink. This is missing. Please add so that I can build software which depends on this dynamic library without manually creating this symlink. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libturbojpeg 1.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 Date: Sat Feb 7 08:41:19 2015 Dependencies: gcc-4.9-base 4.9.1-16ubuntu6 libc6 2.19-10ubuntu2.2 libgcc1 1:4.9.1-16ubuntu6 multiarch-support 2.19-10ubuntu2.2 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libjpeg-turbo UpgradeStatus: Upgraded to utopic on 2014-10-24 (105 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1419267/+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 1056566] Re: Missing pkgconfig file
in new queue :) ** Changed in: libjpeg-turbo (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1056566 Title: Missing pkgconfig file Status in libjpeg-turbo package in Ubuntu: Fix Committed Bug description: Our packages do not contain a turbojpeg.pc file, meaning any pkgconfig-using build script that depends on it being in libjpeg-turbo may fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1056566/+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 1419267] Re: libjpegturbo.so missing from -dev package
in new queue :) ** Changed in: libjpeg-turbo (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1419267 Title: libjpegturbo.so missing from -dev package Status in One Hundred Papercuts: Invalid Status in libjpeg-turbo package in Ubuntu: Fix Committed Bug description: $ dpkg -L libjpeg-turbo8-dev /. /usr /usr/share /usr/share/doc /usr/share/doc/libjpeg-turbo8-dev /usr/share/doc/libjpeg-turbo8-dev/copyright /usr/share/doc/libjpeg-turbo8-dev/README.gz /usr/share/doc/libjpeg-turbo8-dev/structure.txt.gz /usr/share/doc/libjpeg-turbo8-dev/README-turbo.txt.gz /usr/share/doc/libjpeg-turbo8-dev/libjpeg.txt.gz /usr/lib /usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libjpeg.a /usr/lib/x86_64-linux-gnu/libturbojpeg.a /usr/include /usr/include/jerror.h /usr/include/turbojpeg.h /usr/include/jmorecfg.h /usr/include/jpeglib.h /usr/include/jpegint.h /usr/include/x86_64-linux-gnu /usr/include/x86_64-linux-gnu/jconfig.h /usr/share/doc/libjpeg-turbo8-dev/changelog.Debian.gz /usr/lib/x86_64-linux-gnu/libjpeg.so See the libjpeg.so symlink. This is good. I also expect a libturbojpeg.so symlink. This is missing. Please add so that I can build software which depends on this dynamic library without manually creating this symlink. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libturbojpeg 1.3.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 Date: Sat Feb 7 08:41:19 2015 Dependencies: gcc-4.9-base 4.9.1-16ubuntu6 libc6 2.19-10ubuntu2.2 libgcc1 1:4.9.1-16ubuntu6 multiarch-support 2.19-10ubuntu2.2 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libjpeg-turbo UpgradeStatus: Upgraded to utopic on 2014-10-24 (105 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1419267/+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 1326954] Re: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate
** Changed in: modemmanager Status: Confirmed => Incomplete -- 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/1326954 Title: Sierra Wireless EM7305 (Fujitsu Lifebook S904) does not work after suspend/hibernate Status in ModemManager: Incomplete Status in libmbim package in Ubuntu: Confirmed Status in modemmanager package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... << RAW: << length = 16 << data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 16 << type= open (0x0001) << transaction = 1 << Contents: << max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... << RAW: << length = 12 << data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... << Header: << length = 12 << type= close (0x0002) << transaction = 2 [/dev/cdc-wdm0] Received message... >> RAW: >> length = 16 >> data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim), wwan0 (net)' - Numbers | own : 'unknown'
[Touch-packages] [Bug 1714818] [NEW] Display won't wake up , and some other problems
Public bug reported: Desktop pc ,ubuntu 17.04 ,Nvidia GTX1060 ,i7-6700K ,16gb RAM . Display 1 is a Philips 1920x1080 monitor ,connected via DVI-D cable , and LG TV 3840x2160 as display 2 ,connected via HDMI cable .When TV is turned on ,all icons on the desktop (on monitor) could dissapear ,if tv turned off ,they are again in place . Also all active opened windows ( skype ,firefox ,transmission , everything else ) are moved to TV when tv is turned on,i have to move mouse to tv screen and drag them back to monitor. Also main problem is when TV turned on ,when monitor goes sleep after 10minutes of inactivity , it can't wake up ,if tv is turned off first . Monitor and TV then both have no in input signal ,moving mouse or pressing keyboard does not wake up neither display .Workaround is to move mouse to wake up pc monitor first ,then tv can be turned off .Or otherwise ,when no displays working , i have to press Alt-Ctrl-F1 , login , then type reboot ,press enter ,then pc reboots ,and pc monitor functions again . ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-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 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .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. .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Sun Sep 3 22:32:10 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP106 [GeForce GTX 1060 3GB] [1458:3724] InstallationDate: Installed on 2017-05-21 (105 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=9d598b04-1c8d-4e74-86be-41205eda5f25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 xserver.bootTime: Sun Sep 3 15:27:21 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty -- 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/1714818 Title: Display won't wake
[Touch-packages] [Bug 1714803] [NEW] Search list in resolv.conf breaks resolving for that domain
Public bug reported: Ubuntu 17.04 systemd 232-21ubuntu5 Adding a domain to the search list in /etc/resolv.conf breaks resolving for that domain. Not only does the search list not get used as expected, but host names in the domain cannot be resolved by systemd-resolved at all. I just ran into this after upgrading from ubuntu 16.04 to 17.04 which enabled systemd-resolved. I have for a long time used resolveconf to add a 'search my-domain'-line to my /etc/resolv.conf. Example of expected behaviour. With Googles DNS server (8.8.8.8) and ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve can resolve www.ubuntu.com and www: $ cat /etc/resolv.conf nameserver 8.8.8.8 search ubuntu.com $ dig +nostat +nocmd www.ubuntu.com ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55037 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.ubuntu.com.IN A ;; ANSWER SECTION: www.ubuntu.com. 501 IN A 91.189.89.115 $ dig +search +nostat +nocmd www ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25772 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;www.ubuntu.com.IN A ;; ANSWER SECTION: www.ubuntu.com. 382 IN A 91.189.89.103 $ systemd-resolve www.ubuntu.com www.ubuntu.com: 91.189.89.115 -- Information acquired via protocol DNS in 2.7ms. -- Data is authenticated: no $ systemd-resolve www www: 91.189.90.59 (www.ubuntu.com) -- Information acquired via protocol DNS in 3.8ms. -- Data is authenticated: no Ubuntu 17.04 default config, with the systemd-resolved name server in /etc/resolv.conf and no search list. www.ubuntu.com can still be resolved correctly: $ cat /etc/resolv.conf nameserver 127.0.0.53 $ dig +nostat +nocmd www.ubuntu.com ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64646 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;www.ubuntu.com.IN A ;; ANSWER SECTION: www.ubuntu.com. 482 IN A 91.189.89.110 $ systemd-resolve www.ubuntu.com www.ubuntu.com: 91.189.90.58 -- Information acquired via protocol DNS in 18.2ms. -- Data is authenticated: no Broken behaviour, using the systemd-resolved name server and specify ubuntu.com in search list. Resolving fails for www.ubuntu.com and www, both using dig (DNS) and using sytemd-resolve: $ cat /etc/resolv.conf nameserver 127.0.0.53 search ubuntu.com $ dig +nostat +nocmd www.ubuntu.com ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 4 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;www.ubuntu.com.IN A $ dig +search +nostat +nocmd www ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50588 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;www.ubuntu.com.IN A $ systemd-resolve www.ubuntu.com www.ubuntu.com: resolve call failed: No appropriate name servers or networks for name found $ systemd-resolve www www: resolve call failed: All attempts to contact name servers or networks failed ** Affects: systemd (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/1714803 Title: Search list in resolv.conf breaks resolving for that domain Status in systemd package in Ubuntu: New Bug description: Ubuntu 17.04 systemd 232-21ubuntu5 Adding a domain to the search list in /etc/resolv.conf breaks resolving for that domain. Not only does the search list not get used as expected, but host names in the domain cannot be resolved by systemd-resolved at all. I just ran into this after upgrading from ubuntu 16.04 to 17.04 which enabled systemd-resolved. I have for a long time used resolveconf to add a 'search my-domain'-line to my /etc/resolv.conf. Example of expected behaviour. With Googles DNS server (8.8.8.8) and ubuntu.com in the search list in /etc/resolv.conf. Both dig and systemd-resolve can
[Touch-packages] [Bug 1704508] Re: add-apt-repository traceback when hitting ctrl-c
The attachment "Silent the exception raised when user press ctrl-c" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1704508 Title: add-apt-repository traceback when hitting ctrl-c Status in software-properties package in Ubuntu: Confirmed Bug description: add-apt-repository says to hit ctrl-c to cancel adding a PPA. Then it tracebacks when you do: ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next This PPA holds new upstream development releases, usually development releases. Currently, it is holding the 2.2 series. More info: https://launchpad.net/~maas/+archive/ubuntu/next Press [ENTER] to continue or ctrl-c to cancel adding it ^CTraceback (most recent call last): File "/usr/bin/add-apt-repository", line 143, in sys.stdin.readline() KeyboardInterrupt I understand why the trace is generated, but this is ugly (users should never see tracebacks for known conditions, IMO). The KeyboardInterrupt exception should be handled properly like any other exception. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.20.7 ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 Date: Fri Jul 14 23:17:57 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1704508/+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 1714793] Re: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befo
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1714793 Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in signon package in Ubuntu: New Bug description: hp envy dv6 finerprint reader authentication error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-92.115-lowlatency 4.4.76 Uname: Linux 4.4.0-92-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 3 08:41:03 2017 DuplicateSignature: package:libsignon-extension1:amd64:8.58+16.04.20151106-0ubuntu1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libsignon-extension1:amd64 (--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-02-17 (198 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: signon Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 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/signon/+bug/1714793/+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 1714793] [NEW] package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it be
Public bug reported: hp envy dv6 finerprint reader authentication error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-92.115-lowlatency 4.4.76 Uname: Linux 4.4.0-92-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 3 08:41:03 2017 DuplicateSignature: package:libsignon-extension1:amd64:8.58+16.04.20151106-0ubuntu1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libsignon-extension1:amd64 (--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-02-17 (198 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: signon Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 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: signon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1714793 Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in signon package in Ubuntu: New Bug description: hp envy dv6 finerprint reader authentication error. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-92.115-lowlatency 4.4.76 Uname: Linux 4.4.0-92-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 3 08:41:03 2017 DuplicateSignature: package:libsignon-extension1:amd64:8.58+16.04.20151106-0ubuntu1 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package libsignon-extension1:amd64 (--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-02-17 (198 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: signon Title: package libsignon-extension1:amd64 8.58+16.04.20151106-0ubuntu1 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/signon/+bug/1714793/+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 1704508] Re: add-apt-repository traceback when hitting ctrl-c
I made it to handle and siltent that traceback. ** Patch added: "Silent the exception raised when user press ctrl-c" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1704508/+attachment/4943580/+files/add-apt-repository.patch -- 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/1704508 Title: add-apt-repository traceback when hitting ctrl-c Status in software-properties package in Ubuntu: Confirmed Bug description: add-apt-repository says to hit ctrl-c to cancel adding a PPA. Then it tracebacks when you do: ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next This PPA holds new upstream development releases, usually development releases. Currently, it is holding the 2.2 series. More info: https://launchpad.net/~maas/+archive/ubuntu/next Press [ENTER] to continue or ctrl-c to cancel adding it ^CTraceback (most recent call last): File "/usr/bin/add-apt-repository", line 143, in sys.stdin.readline() KeyboardInterrupt I understand why the trace is generated, but this is ugly (users should never see tracebacks for known conditions, IMO). The KeyboardInterrupt exception should be handled properly like any other exception. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.20.7 ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 Date: Fri Jul 14 23:17:57 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1704508/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
@terry69lawson and other frustrated users: perhaps you are in a position to try *WireGuard* as a replacement for OpenVPN (or for other methods of connecting to a VPN). Your VPN provider will need to have WireGuard servers for this to work. If your provider does have such servers, then you are in luck, for not only does Wireguard work with the latest (unfixed) Network Manager, it's also fast and easy. Still, it's also still in development and, though it has had some testing and had good reviews, it is not guaranteed secure. Still, I am amazed and boggled that Canonical has not fixed the problem. Perhaps it's been fixed in a newer version of Ubuntu and not backported? A bit of information, clearly presented, would not go amiss (@cyphermox) -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Now NONE of my Ubuntu machines, on Xenial or Zesty, will use my VPN for even a brief time. I've tried several different versions of packages, but nothing. This is absolutely intolerable. Fix this soon Canonical or I will be forced to leave for a different Linux distro. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1704508] Re: add-apt-repository traceback when hitting ctrl-c
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- 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/1704508 Title: add-apt-repository traceback when hitting ctrl-c Status in software-properties package in Ubuntu: Confirmed Bug description: add-apt-repository says to hit ctrl-c to cancel adding a PPA. Then it tracebacks when you do: ubuntu@bysen:~$ sudo add-apt-repository ppa:maas/next This PPA holds new upstream development releases, usually development releases. Currently, it is holding the 2.2 series. More info: https://launchpad.net/~maas/+archive/ubuntu/next Press [ENTER] to continue or ctrl-c to cancel adding it ^CTraceback (most recent call last): File "/usr/bin/add-apt-repository", line 143, in sys.stdin.readline() KeyboardInterrupt I understand why the trace is generated, but this is ugly (users should never see tracebacks for known conditions, IMO). The KeyboardInterrupt exception should be handled properly like any other exception. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.20.7 ProcVersionSignature: User Name 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 Date: Fri Jul 14 23:17:57 2017 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties 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/1704508/+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 1117804] Re: ausearch doesn't show AppArmor denial messages
IMHO we have to ask John Johansen about this, he's working on kernel side. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+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
About the packages that were upgraded. This bug appeared a few days before it was reported here on 2017-07-29. I can remember I tried to investigate for a few days before finding and confirming this bug report. >From my file/var/log/apt/history.log.2.gz on my own computer I see that I installed "vdpauinfo" on 2017-07-27, probably in order to investigate this bug: Start-Date: 2017-07-27 22:30:56 Commandline: apt install vdpauinfo Requested-By: dimitri (1000) Install: vdpauinfo:amd64 (1.0-1) End-Date: 2017-07-27 22:31:01 So the updates responsible for this bug probably occurred hours to days before that. I think this update is responsible: Start-Date: 2017-07-27 21:32:51 Commandline: aptdaemon role='role-commit-packages' sender=':1.93' Install: libllvm4.0:amd64 (1:4.0-1ubuntu1~16.04.1, automatic), libllvm4.0:i386 (1:4.0-1ubuntu1~16.04.1, automatic), libwayland-bin:a md64 (1.12.0-1~ubuntu16.04.1, automatic), libinput-bin:amd64 (1.6.3-1ubuntu1~16.04.1, automatic), libsensors4:i386 (1:3.4.0-2, automatic) Upgrade: libgles2-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libdrm-nouveau2:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-nouveau2:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwacom-common:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), libegl1-mesa-dev:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libglapi-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libglapi-mesa:i386 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), gnome-software:amd64 (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 3.20.5-0ubuntu0.16.04.5), xfonts-utils:amd64 (1:7.7+3, 1:7.7+3ubuntu0.16.04.2), libxatracker2:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libwacom-bin:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), libegl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgbm1:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libwayland-client0:amd64 (1.9.0-1, 1.12.0-1~ubuntu16.04.1), x11proto-core-dev:amd64 (7.0.28- 2ubuntu1, 7.0.31-1~ubuntu16.04.1), libdrm-amdgpu1:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-amdgpu1:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwayland-dev:amd64 (1.9.0-1, 1.12.0-1~ubuntu16.04.1), ubuntu-software:amd64 (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 3.20.5-0ubuntu0.16.04.5), libwayland-egl1-mesa:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libxfont1:amd64 (1:1.5.1-1, 1:1.5.1-1ubuntu0.16.04.1), libdrm2:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm2:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libgl1-mesa-dri:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-dri:i386 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-glx:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libgl1-mesa-glx:i386 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), libdrm-intel1:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-intel1:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwacom2:amd64 (0.18-1, 0.22-1~ubuntu16.04.1), libdrm-radeon1:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libdrm-radeon1:i386 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (12.0.6-0ubuntu0.16.04.1, 17.0.7-0ubuntu0.16.04.1), virtualbox-5.1:amd64 (5.1.24-117012~Ubuntu~xenial, 5.1.26-117224~Ubuntu~xenial), gnome-software-common:amd64 (3.20.1+git20170524.0.ea2fe2b0-0ubuntu0.16.04.1, 3.20.5-0ubuntu0.16.04.5), libdrm-dev:amd64 (2.4.70-1~ubuntu16.04.1, 2.4.76-1~ubuntu16.04.1), libwayland-server0:amd64 (1.9.0-1, 1.12.0-1~ubuntu16.04.1), libinput10:amd64 (1.2.3-1ubuntu1, 1.6.3-1ubuntu1~16.04.1), libwayland-cursor0:amd64 (1.9.0-1, 1.12.0-1~ubuntu16.04.1) End-Date: 2017-07-27 21:35:59 -- 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
[Touch-packages] [Bug 1700930] Re: Default action policy for "Security Updates" changed between 14.04 and 16.04
Sorry, yes you are right. I've been working with lubuntu too much which doesn't. Ubuntu-mate didn't used to ship with it either, but that seems to have changed in recent versions. Carry on. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1700930 Title: Default action policy for "Security Updates" changed between 14.04 and 16.04 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04.5, the default policy under the "Updates" tab for "Security Updates" is set to "Display Immediately". In Ubuntu 16.04+, the default policy is now "Download and Install Immediately". I think this occurred due to the fix rolled out for bug #1554099. This has the following consequences: - Users may be denied apt lock when trying to install software because unattended-upgrades is running in the background. - If a shutdown is forced when the background update is running, users may be left with an unstable system - In case the update server is compromised and made to deliver malware, the blow to the userbase will be massive - From a PR standpoint, this moves away from the previous "your system won't ever do stuff without your permission" default policy. I'm of the opinion that the "Display Immediately" default should be rolled back. Failing that at least an official policy change announcement should be published so that users are made aware of this new default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1700930/+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
As a workaround switching the "Output" parameter from "Automatic" to "X11 video output (XCB)" restores video. But then vlc keeps printing these error messages: [7ff124060808] core blend error: blending YUVA to VDV0 failed [7ff124060808] blend blend error: no matching alpha blending routine (chroma: YUVA -> VDV0) ** Attachment added: "Screen captur showing the parameter to change." https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707393/+attachment/4943466/+files/Output.png -- 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 1700930] Re: Default action policy for "Security Updates" changed between 14.04 and 16.04
@adamsmith: you're wrong, the package is installed in stock ubuntu. This is an ubuntu problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1700930 Title: Default action policy for "Security Updates" changed between 14.04 and 16.04 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04.5, the default policy under the "Updates" tab for "Security Updates" is set to "Display Immediately". In Ubuntu 16.04+, the default policy is now "Download and Install Immediately". I think this occurred due to the fix rolled out for bug #1554099. This has the following consequences: - Users may be denied apt lock when trying to install software because unattended-upgrades is running in the background. - If a shutdown is forced when the background update is running, users may be left with an unstable system - In case the update server is compromised and made to deliver malware, the blow to the userbase will be massive - From a PR standpoint, this moves away from the previous "your system won't ever do stuff without your permission" default policy. I'm of the opinion that the "Display Immediately" default should be rolled back. Failing that at least an official policy change announcement should be published so that users are made aware of this new default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1700930/+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 1117804] Re: ausearch doesn't show AppArmor denial messages
FTR this was raised as a potential blocker for enabling AppArmor by default on Debian: https://bugs.debian.org/872726. I'm going to investigate why this is a blocker there. tl;dr: as the audit maintainers said in 2014 (https://www.redhat.com/archives/linux-audit/2014-May/msg00119.html) and 2016 (https://www.redhat.com/archives/linux- audit/2016-April/msg00129.html), we should use events ids from the range that has been allocated to us (1500-1599) instead of from the range assigned to SELinux. Any plans / ETA to fix this? Regardless of how you would prioritize this problem otherwise, the fact it might prevent AppArmor from being enabled by default in Debian could be a reason to handle it ASAP :) ** Bug watch added: Debian Bug tracker #872726 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872726 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to audit in Ubuntu. https://bugs.launchpad.net/bugs/1117804 Title: ausearch doesn't show AppArmor denial messages Status in AppArmor: Confirmed Status in audit package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The following command should display all AVC denials: ausearch -m avc However, it doesn't work with AppArmor denials. Here's a quick test case to generate a denial, search for it with ausearch, and see that no messages are displayed: $ aa-exec -p /usr/sbin/tcpdump cat /proc/self/attr/current cat: /proc/self/attr/current: Permission denied $ sudo ausearch -m avc -c cat ausearch claims that there are no matches, but there's a matching audit message if you look in audit.log: type=AVC msg=audit(1360193426.539:64): apparmor="DENIED" operation="open" parent=8253 profile="/usr/sbin/tcpdump" name="/proc/8485/attr/current" pid=8485 comm="cat" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1117804/+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 1700930] Re: Default action policy for "Security Updates" changed between 14.04 and 16.04
Unattended-upgrades is for server images and is not usually installed with a desktop. You should be moaning to Martin Wimpress about this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1700930 Title: Default action policy for "Security Updates" changed between 14.04 and 16.04 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04.5, the default policy under the "Updates" tab for "Security Updates" is set to "Display Immediately". In Ubuntu 16.04+, the default policy is now "Download and Install Immediately". I think this occurred due to the fix rolled out for bug #1554099. This has the following consequences: - Users may be denied apt lock when trying to install software because unattended-upgrades is running in the background. - If a shutdown is forced when the background update is running, users may be left with an unstable system - In case the update server is compromised and made to deliver malware, the blow to the userbase will be massive - From a PR standpoint, this moves away from the previous "your system won't ever do stuff without your permission" default policy. I'm of the opinion that the "Display Immediately" default should be rolled back. Failing that at least an official policy change announcement should be published so that users are made aware of this new default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1700930/+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 1714764] [NEW] Excessive dependency on gnome-session-canberra
Public bug reported: ubuntu-desktop package depends on gnome-session-canberra package in such a way that it's impossible to remove gnome-session-canberra without removing ubuntu-desktop. This is wrong, as aforementioned package contains only few loud sounds to be played at system start, and is not an essential part of Ubuntu Desktop. I think it should be in 'recommends' section, not in 'depends'. Corresponding discussion on Ask Ubuntu: https://askubuntu.com/posts/952353/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.398 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Sun Sep 3 13:07:41 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (73 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- 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/1714764 Title: Excessive dependency on gnome-session-canberra Status in ubuntu-meta package in Ubuntu: New Bug description: ubuntu-desktop package depends on gnome-session-canberra package in such a way that it's impossible to remove gnome-session-canberra without removing ubuntu-desktop. This is wrong, as aforementioned package contains only few loud sounds to be played at system start, and is not an essential part of Ubuntu Desktop. I think it should be in 'recommends' section, not in 'depends'. Corresponding discussion on Ask Ubuntu: https://askubuntu.com/posts/952353/ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.398 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Sun Sep 3 13:07:41 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (73 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1714764/+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 1714763] [NEW] No way to disable system startup sound
Public bug reported: Package gnome-session-canberra contains /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop file, which plays extremely annoying drum sound at every boot. This is a problem (at least for me, but I think for many others), and there is no way to disable this without changing package-provided files. Moreover, this package (gnome-session-canberra) couldn't be removed without breaking ubuntu-desktop package (I'll file separate bugreport for this). Propose: Create a way do disable those sounds in a user-available way. The simplest way I can propose is to mark /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop as conffile, which will keep user changes in this file during package upgrade. More user-friendly (visible) changes would be appreciated too, but conffile should, at least, give some way to manage loud 'blam-blam' at boot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session-canberra 0.30-3ubuntu1 [modified: usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop] ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Sun Sep 3 12:55:31 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (73 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: libcanberra UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libcanberra (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 libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1714763 Title: No way to disable system startup sound Status in libcanberra package in Ubuntu: New Bug description: Package gnome-session-canberra contains /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop file, which plays extremely annoying drum sound at every boot. This is a problem (at least for me, but I think for many others), and there is no way to disable this without changing package-provided files. Moreover, this package (gnome-session-canberra) couldn't be removed without breaking ubuntu-desktop package (I'll file separate bugreport for this). Propose: Create a way do disable those sounds in a user-available way. The simplest way I can propose is to mark /usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop as conffile, which will keep user changes in this file during package upgrade. More user-friendly (visible) changes would be appreciated too, but conffile should, at least, give some way to manage loud 'blam-blam' at boot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-session-canberra 0.30-3ubuntu1 [modified: usr/share/gdm/autostart/LoginWindow/libcanberra-ready-sound.desktop] ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Sun Sep 3 12:55:31 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-22 (73 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: libcanberra UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/1714763/+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
