[Touch-packages] [Bug 1660105] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1660105/+attachment/4810306/+files/ThreadStacktrace.txt ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1660105 Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: Steps: 1. Play a video from the channel 'Apple Movie Trailers' 2. Go back while the video is playing 3. Select another video from the same channel Totem hanged and crashed while trying to play the second video over the first one from the same channel. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 29 08:04:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-04-26 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x7fb975a370c9:mov0x1d8(%rbx),%rsi PC (0x7fb975a370c9) ok source "0x1d8(%rbx)" (0x01d8) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1660105/+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 1660105] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1660105/+attachment/4810305/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1660105 Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: Steps: 1. Play a video from the channel 'Apple Movie Trailers' 2. Go back while the video is playing 3. Select another video from the same channel Totem hanged and crashed while trying to play the second video over the first one from the same channel. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 29 08:04:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-04-26 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x7fb975a370c9:mov0x1d8(%rbx),%rsi PC (0x7fb975a370c9) ok source "0x1d8(%rbx)" (0x01d8) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1660105/+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 1660105] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libfribidi0 no debug symbol package found for libflac8 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1660105/+attachment/4810292/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1660105 Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: Steps: 1. Play a video from the channel 'Apple Movie Trailers' 2. Go back while the video is playing 3. Select another video from the same channel Totem hanged and crashed while trying to play the second video over the first one from the same channel. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 29 08:04:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-04-26 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x7fb975a370c9:mov0x1d8(%rbx),%rsi PC (0x7fb975a370c9) ok source "0x1d8(%rbx)" (0x01d8) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1660105/+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 1660105] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1660105/+attachment/4810304/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1660105 Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: Steps: 1. Play a video from the channel 'Apple Movie Trailers' 2. Go back while the video is playing 3. Select another video from the same channel Totem hanged and crashed while trying to play the second video over the first one from the same channel. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 29 08:04:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-04-26 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x7fb975a370c9:mov0x1d8(%rbx),%rsi PC (0x7fb975a370c9) ok source "0x1d8(%rbx)" (0x01d8) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1660105/+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 1660105]
StacktraceTop: ir_call::generate_inline (this=0x555fea0877c0, next_ir=0x0) at ../../../src/compiler/glsl/opt_function_inlining.cpp:100 ?? () ?? () ?? () ?? () from /tmp/apport_sandbox_eE_Tjl/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1660105 Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() Status in gstreamer1.0 package in Ubuntu: Invalid Bug description: Steps: 1. Play a video from the channel 'Apple Movie Trailers' 2. Go back while the video is playing 3. Select another video from the same channel Totem hanged and crashed while trying to play the second video over the first one from the same channel. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 29 08:04:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-04-26 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x7fb975a370c9:mov0x1d8(%rbx),%rsi PC (0x7fb975a370c9) ok source "0x1d8(%rbx)" (0x01d8) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1660105/+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 1660105] [NEW] totem crashed with SIGSEGV in glXMakeCurrentReadSGI()
Public bug reported: Steps: 1. Play a video from the channel 'Apple Movie Trailers' 2. Go back while the video is playing 3. Select another video from the same channel Totem hanged and crashed while trying to play the second video over the first one from the same channel. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 29 08:04:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-04-26 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x7fb975a370c9: mov0x1d8(%rbx),%rsi PC (0x7fb975a370c9) ok source "0x1d8(%rbx)" (0x01d8) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1660105 Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() Status in gstreamer1.0 package in Ubuntu: New Bug description: Steps: 1. Play a video from the channel 'Apple Movie Trailers' 2. Go back while the video is playing 3. Select another video from the same channel Totem hanged and crashed while trying to play the second video over the first one from the same channel. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.2-1~ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jan 29 08:04:00 2017 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2016-04-26 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LogAlsaMixer: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] ProcCmdline: totem SegvAnalysis: Segfault happened at: 0x7fb975a370c9:mov0x1d8(%rbx),%rsi PC (0x7fb975a370c9) ok source "0x1d8(%rbx)" (0x01d8) not located in a known VMA region (needed readable region)! destination "%rsi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so Title: totem crashed with SIGSEGV in glXMakeCurrentReadSGI() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1660105/+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 1658519] Re: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1658519 Title: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alain 1597 F pulseaudio Date: Sun Jan 22 21:38:50 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=0f6e45e9-1db8-424f-b077-e221aa9ab057 InstallationDate: Installed on 2017-01-03 (19 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=c7441fe3-cc4b-485e-9f5a-5934116777fb ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-59-generic 4.4.0-59.80 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2017-01-06 (16 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1658519/+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 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)
Thank you Theodore. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1645232 Title: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL) Status in e2fsprogs package in Ubuntu: Confirmed Bug description: The original installed e2fsprogs did not support mke2fs -d /directory " option . So , git cloned from e2fsprogs packages from repository and installed it and followed below steps to reproduce this : 1. set the ACL rules as below to one of the binary : $ setfacl -m u:vipatil:r-- rootfs/usr/bin/helloworld $ getfacl rootfs/usr/bin/helloworld # file: rootfs/usr/bin/helloworld # owner: shkumar # group: hardev user::rwx user:vipatil:r-- group::--- mask::r-- other::--- 2. $ dd if=/dev/zero of=test.ext4 bs=1M count=60 3. $ mke2fs -t ext4 test.ext4 -d rootfs/ mke2fs 1.43.3 (04-Sep-2016) Discarding device blocks: done Creating filesystem with 61440 1k blocks and 15360 inodes Filesystem UUID: 495713b3-5f1f-427a-8359-a736dfb2ece9 Superblock backups stored on blocks: 8193, 24577, 40961, 57345 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Copying files into the device: done Writing superblocks and filesystem accounting information: done 4. sudo mount -o loop,acl,user_xattr,rw,sync test.ext4 mountpoint 5.@/mountpoint$ getfacl usr/bin/helloworld getfacl: usr/bin/helloworld: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+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 1645232] Re: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL)
I've committed a complete fix to the master branch of the e2fsprogs git tree. One of the reasons why I don't want to commit a partial fix is because the potential for corruption of production file systems by programs such as fuse2fs was extremely high. Users of mke2fs -d are generally embedded developers. Users of fuse2fs are more likely to be civilians. We've had this bug for a long time, and no one has complained. Taking some time to have a fix that doesn't corrupt file systems is far more important to me as the maintainer. For any distribution, but especially for Ubuntu, civilian users >>> embedded developers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1645232 Title: e2fsprogs - could not preserve ACL permissions : The getxattr() returns with (EINVAL) Status in e2fsprogs package in Ubuntu: Confirmed Bug description: The original installed e2fsprogs did not support mke2fs -d /directory " option . So , git cloned from e2fsprogs packages from repository and installed it and followed below steps to reproduce this : 1. set the ACL rules as below to one of the binary : $ setfacl -m u:vipatil:r-- rootfs/usr/bin/helloworld $ getfacl rootfs/usr/bin/helloworld # file: rootfs/usr/bin/helloworld # owner: shkumar # group: hardev user::rwx user:vipatil:r-- group::--- mask::r-- other::--- 2. $ dd if=/dev/zero of=test.ext4 bs=1M count=60 3. $ mke2fs -t ext4 test.ext4 -d rootfs/ mke2fs 1.43.3 (04-Sep-2016) Discarding device blocks: done Creating filesystem with 61440 1k blocks and 15360 inodes Filesystem UUID: 495713b3-5f1f-427a-8359-a736dfb2ece9 Superblock backups stored on blocks: 8193, 24577, 40961, 57345 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Copying files into the device: done Writing superblocks and filesystem accounting information: done 4. sudo mount -o loop,acl,user_xattr,rw,sync test.ext4 mountpoint 5.@/mountpoint$ getfacl usr/bin/helloworld getfacl: usr/bin/helloworld: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1645232/+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 1660100] Re: Unable to enable or disable repository in Software & Updates
When software-properties-gtk is run from the terminal, the following error is displayed: $ software-properties-gtk ERROR:root:Authentication canceled, changes have not been saved -- 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/1660100 Title: Unable to enable or disable repository in Software & Updates Status in software-properties package in Ubuntu: New Bug description: The Software & Updates dialog (software-properties-gtk) does not allow the user to activate or deactivate repositories. RECREATE ISSUE: Launch Software & Updates. Select Other Sources tab. Click on a check box next to a repository to enable or disable it. RESULT: The window seems to lose focus, but noting happens. EXPECTED RESULT: A dialog should appear prompting the user to enter the administrator password. After the password is successfully entered, the repository check box should be toggled (enabled or disabled). OTHER DETAILS: This issue was tested on Ubuntu-Gnome. $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety $ uname -a Linux PS001 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 28 23:14:17 2017 InstallationDate: Installed on 2017-01-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 16.10.0 2017.01.23 amd64 "Custom Yakkety Yak" 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/1660100/+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 1660100] [NEW] Unable to enable or disable repository in Software & Updates
Public bug reported: The Software & Updates dialog (software-properties-gtk) does not allow the user to activate or deactivate repositories. RECREATE ISSUE: Launch Software & Updates. Select Other Sources tab. Click on a check box next to a repository to enable or disable it. RESULT: The window seems to lose focus, but noting happens. EXPECTED RESULT: A dialog should appear prompting the user to enter the administrator password. After the password is successfully entered, the repository check box should be toggled (enabled or disabled). OTHER DETAILS: This issue was tested on Ubuntu-Gnome. $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety $ uname -a Linux PS001 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 28 23:14:17 2017 InstallationDate: Installed on 2017-01-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 16.10.0 2017.01.23 amd64 "Custom Yakkety Yak" 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) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1660100 Title: Unable to enable or disable repository in Software & Updates Status in software-properties package in Ubuntu: New Bug description: The Software & Updates dialog (software-properties-gtk) does not allow the user to activate or deactivate repositories. RECREATE ISSUE: Launch Software & Updates. Select Other Sources tab. Click on a check box next to a repository to enable or disable it. RESULT: The window seems to lose focus, but noting happens. EXPECTED RESULT: A dialog should appear prompting the user to enter the administrator password. After the password is successfully entered, the repository check box should be toggled (enabled or disabled). OTHER DETAILS: This issue was tested on Ubuntu-Gnome. $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety $ uname -a Linux PS001 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jan 28 23:14:17 2017 InstallationDate: Installed on 2017-01-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 16.10.0 2017.01.23 amd64 "Custom Yakkety Yak" 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/1660100/+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 1616413] Re: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1616413 Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: I am not getting any sound at all from my Dell Optiplex 7040 (running Ubuntu 16.04). The volume control icon is showing up next to the clock, and I am able to change the volume levels: but this has no effect. There is absolutely NO sound at all. In Settings -> Output, no devices are listed. Strangely enough, aplay -l results in: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3234 Analog [ALC3234 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 which indicates that the sound card is getting detected. I tried sudo alsa force-reload following which I rebooted. That doesn't fix the problem. I opened alsamixer: it is detecting the sound card perfectly and nothing is muted. Still, there is no audio. I then tried the following: sudo apt-get remove --purge alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio sudo alsa force-reload And still there is no audio. I'd be really grateful if you could look into this. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suvam 4522 F pulseaudio suvam 5594 F alsamixer CurrentDesktop: Unity Date: Wed Aug 24 15:59:21 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-02-12 (193 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: suvam 4522 F pulseaudio suvam 5594 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [OptiPlex 7040, Realtek ALC3234, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-08-11 (13 days ago) dmi.bios.date: 12/04/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd12/04/2015:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7040 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1616413/+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 1659950] Re: rsync -u --inplace --partial -a can't resume transfer
rsync version: rsync version 3.1.1 protocol version 31 ubuntu version: 3.1.1-3ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1659950 Title: rsync -u --inplace --partial -a can't resume transfer Status in rsync package in Ubuntu: New Bug description: Suppose you have a file in hostA: hostA$ ls -l /tmp/files -rw-rw-r-- 2 root root 563016 Jan 10 15:01 test.txt You download it from the hostB using: hostB$ rsync -u --inplace --partial -a hostA::files/* . If the transfer is aborted, hostB will get only a partial file: hostB$ ls -l /tmp/files -rw-rw-r-- 2 root root 2024 Jan 11 18:00 test.txt BUT the ctime/mtime of hostB/test.txt now is NEWER than hostA/test.txt(and mtime == ctime). So, if you run the same rsync -u command again: hostB$ rsync -u --inplace --partial -a hostA::files/* . Rsync will SKIP THE FILE, because hostB/test.txt is "newer" than hostA/test.txt. So you CAN'T resume using rsync -u command, and you will think there are no differences. To avoid this bug, rsync must create the file with ctime=mtime=0. And if the file already exists before transfer, rsync -u must not change his current ctime/mtime. Ctime/mtime must be updated ONLY after the transfer was successfully completed. Note this is really need because there are scenarios where checksum comparison can't be used, only comparison by time. For example, to avoid deleting changes made in hostB to test.txt. Also I need to use --inplace. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1659950/+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 1628956] Re: From v49.0, Firefox needs read access to @{PROC}/net/arp
A patch which might fix this issue, too, is available at 1659988.
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1659988
Everyone affected, please give it a try and report back.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1628956
Title:
From v49.0, Firefox needs read access to @{PROC}/net/arp
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
Since the latest upgrade of Firefox to 49.0, it will need read access
to @{PROC}/net/arp
I don't know what the security implications are, so I don't know if we
want to give read access to explicitely deny it. Both seem to work.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apparmor-profiles 2.10.95-0ubuntu2.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Sep 29 16:55:21 2016
InstallationDate: Installed on 2015-10-04 (361 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002)
PackageArchitecture: all
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent kaslr threadirqs quiet
splash vt.handoff=7
SourcePackage: apparmor
Syslog:
Sep 29 10:37:52 franck-ThinkPad-T430s dbus[2546]: [system] AppArmor D-Bus
mediation is enabled
Sep 29 16:50:57 franck-ThinkPad-T430s dbus[2410]: [system] AppArmor D-Bus
mediation is enabled
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apparmor.d.sbin.klogd: [modified]
modified.conffile..etc.apparmor.d.sbin.syslogd: [modified]
modified.conffile..etc.apparmor.d.usr.bin.chromium-browser: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.avahi-daemon: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dnsmasq: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.dovecot: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.identd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.mdnsd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nmbd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.nscd: [modified]
modified.conffile..etc.apparmor.d.usr.sbin.smbd: [modified]
mtime.conffile..etc.apparmor.d.sbin.klogd: 2015-10-05T12:04:03.854535
mtime.conffile..etc.apparmor.d.sbin.syslogd: 2015-10-05T12:03:15.705968
mtime.conffile..etc.apparmor.d.usr.bin.chromium-browser:
2015-10-05T12:02:05.273141
mtime.conffile..etc.apparmor.d.usr.sbin.avahi-daemon:
2016-04-13T19:13:25.829679
mtime.conffile..etc.apparmor.d.usr.sbin.dnsmasq: 2016-04-13T19:13:05.941424
mtime.conffile..etc.apparmor.d.usr.sbin.dovecot: 2015-10-05T12:00:55.356323
mtime.conffile..etc.apparmor.d.usr.sbin.identd: 2015-10-05T12:01:02.204403
mtime.conffile..etc.apparmor.d.usr.sbin.mdnsd: 2015-10-05T12:02:37.861523
mtime.conffile..etc.apparmor.d.usr.sbin.nmbd: 2015-10-05T12:00:10.119794
mtime.conffile..etc.apparmor.d.usr.sbin.nscd: 2016-04-13T19:14:17.520643
mtime.conffile..etc.apparmor.d.usr.sbin.smbd: 2015-10-05T12:00:26.103981
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1628956/+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 1656399] Re: Unable to unlock session after suspend using lightdm-gtk-greeter.
It happens to me, too. == Something (big) cropped up. When I returned to my NetBook, the screen had locked. Typed my password in. System then (visually) unlocked itself, paused briefly and then locked me back out again. You can test this more quickly by using the keyboard shortcut of CTRL+ALT+l Naturally I thought I'd got the password wrong. Tried typing in the password in upper case and it didn't do the above - it gave a red error message, pretty much expected. The only way I could get into a locked system again was to chose a "Shutdown" menu option. Played around with it for a bit. Managed to unlock the NetBook successfully once - then it resumed its unhelpful behaviour. And here are my system's details. = On 28 January 2017 at 02:55, Simon Quigley wrote: Lubuntu Zesty Zapus Alpha 2 (soon to be 17.04) has been released! OK. Used your link and downloaded MD5SUMS and zesty-desktop-i386.iso. Ran md5sum and it checked out OK:- 1c3f420bb80754bc3b31eb479d77e3b5 zesty-desktop-i386.iso Used Startup Disc Creator on a 4GB USB flash drive. Hardware used to install iso on: Samsung NC10 - hawking Intel Atom N270, 1.66GHz, 32-bit, 2GiB RAM, 149.05 GiB hard drive, no optical drive, Ethernet and WiFi connections Full details see here:- https://gist.github.com/21b61903871ee685fc79 Booted install media without Ethernet cable connected. Had to reboot system after connecting Ethernet cable before it was happy to continue the update. Opted for "Download updates while installing Lubuntu" and "Install third-party software". Chose option to wipe hard drive and install Lubuntu on top of it. Put in a hostname of "hawking" for this NetBook. Installer said there was already another system on the network called "hawking". Decided not to argue so named the system "hawking2". Install completed successfully and asked for the (installation) storage medium at a suitable time. Rebooted system, logged in. The start/swift menu icon isn't present. Ran Software Updater OK. Saw an email on lubuntu-devel complaining about Firefox not working. On my NetBook, ran Firefox (version 50.1.0) ran fine and I Googled "Hello World". Normally I only use the "alternate" iso images and in the install I repartition the hard drive manually. For some reason I did it a little differently this time :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1656399 Title: Unable to unlock session after suspend using lightdm-gtk-greeter. Status in light-locker package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: In Progress Bug description: Unable to unlock Xubuntu XFCE session after suspend. I'm presented with unlock screen, and entering credentials will redirect to a black screen with "This session is locked", and "you will be redirected to unlock screen". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1656399/+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 1660072] [NEW] Missing depends on xkb-data-i18n
Public bug reported: A reverse depends for xkb-data-i18n shows that nothing depends on it. Surely xkb-data should depend or recommend it's installation? ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1660072 Title: Missing depends on xkb-data-i18n Status in xkeyboard-config package in Ubuntu: New Bug description: A reverse depends for xkb-data-i18n shows that nothing depends on it. Surely xkb-data should depend or recommend it's installation? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1660072/+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 1656280] Re: Support installing subordinate systemd on Ubuntu Desktop 14.04.5
** No longer affects: systemd (Ubuntu) -- 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/1656280 Title: Support installing subordinate systemd on Ubuntu Desktop 14.04.5 Status in systemd source package in Trusty: Fix Committed Bug description: Add support for installing deputy systemd for snapd on Ubuntu Desktop 14.04.5 When installed, deputy systemd provides a subset of functionality as required for snapd: * Providing necessary units for power management via systemctl * Provides private socket API access (and thus systemctl as root) only, and is not present on the system D-Bus * Does not conflict with systemd-shim * Does not change behaviour of systemd-services nor udeb build in anyway [Impact] * Users can install snapd without regressing Desktop support, lxc/lxc1/lxd abilities. [Test Case] * Power management works (e.g. shutdown/reboot via indicator-system and via systemctl) * Timedatectl commands report NTP status enable/disabled correctly, and can change it * Can install and use snapd * Can install and use lxc / lxc1 / lxd [Regression Potential] * Minimal, as bin:systemd uses a separate build in the package with additional patches to not intefere with cgmanager's name=systemd cgroup; and instead deputy bin:systemd uses name=dsystemd cgroup for process management. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/trusty/+source/systemd/+bug/1656280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659727] Re: Xorg freeze - blank screen - Enlightenment + nvidia driver
** Summary changed: - Xorg freeze + Xorg freeze - blank screen - Enlightenment + nvidia driver -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1659727 Title: Xorg freeze - blank screen - Enlightenment + nvidia driver Status in xorg package in Ubuntu: New Bug description: I helped my friend Roger setup five systems running ubuntu with boinc running in the background for the Einstein@home project. One has a AMD Phenom 9950 CPU, and the others have AMD FX-8320E, FX-8150, FX-8350, and FX-8370 CPUs. All have the X64 version of ubuntu installed. In an effort to speed up processing, we install NVidia GTX 1060 graphics cards in three of them. We added the nvidia-367 kernel driver to two systems that were already upgraded to 16.04 LTS (they use Lightdm and Unity with Xorg). They now use the GPU for one of the processes without problems. This problem system (with the FX-8150 CPU) was originally using Ubuntu Precise Pangolin and running Enlightenment instead of Unity. It was using Trusty when we installed the new graphics card. It still used the Nouveau video driver. I had problems installing the NVidia kernel driver on that, so I gave up and used the 'do-release-upgrade' script to do the upgrade to 16.04.1 LTS (Xenial). Everything seemed OK until I added the NVidia driver to the system. Now, after every reboot the display goes thru the text boot sequence, and flashes briefly when loading X, but then the screen goes blank until rebooting again. Fortunately, I found I could open a ssh session (or use scp to copy files) to the system. The NVidia GPU is being used by one of the BOINC jobs, even with the blank screen on the console! After a lot of horsing around, I moved the file failsafe-x.conf from /etc/init to /root, so I could try various hacks to get the display to work. It took me a long time to find the error message in file /home/roger/.xsession-errors. It says: openConnection: connect: No such file or directory cannot connect to brltty at :0 main init win: 1920x1080 for 1d4 screen region screen 0x6e4140: 0 0 1920x1080 CRI: modules/evas/engines/gl_x11/evas_engine.c:2511 eng_image_native_set() eina_log_print() unknown domain -1, original message format 'GLX Pixmap create fail' action halt 3 action reboot 3 action suspend 3 action hibernate 3 The 5th line (starting with 'CRI') led me to the efl source package associated with enlightenment, (which I installed in /usr/src). It seems to have source for a number of DLLs for e17. I found the line from the message in file: '/usr/src/efl-1.8.6/src/modules/evas/engines/gl_x11/evas_engine.c'. I don't know how to proceed from here. I assume the apport-bug job gave most of the system state information. Is there a way to look at the various X processes that are running? Please advise.. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.57 Mon Oct 3 20:37:01 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Thu Jan 26 22:54:02 2017 DistUpgraded: 2017-01-16 22:52:51,433 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 3.13.0-107-generic, x86_64: installed bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed nvidia-367, 367.57, 4.4.0-59-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last week or two GraphicsCard: NVIDIA Corporation Device [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2012-07-09 (1662 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcEnviron: TERM=rxvt-unico
[Touch-packages] [Bug 1468103] Re: rc.local runs earlier than cloud-init.service
** No longer affects: systemd (Ubuntu)
--
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/1468103
Title:
rc.local runs earlier than cloud-init.service
Status in cloud-init package in Ubuntu:
Confirmed
Bug description:
per https://www.debian.org/doc/manuals/debian-faq/ch-customizing.en.html
| The rc.local script is executed at the end of each multiuser runlevel.
Generally speaking people expect rc.local to be run as "the last thing
in boot".
currently it is being run by systemd much earlier.
Provided in the attached is user-data that tells cloud-init to write a
file in /usr/local/bin/rc-local-message and edit set rc.local to
execute it.
On current wily, under most scenarios the script will not be executed
as rc.local will most likely run before the cloud-init service has a
chance to update /etc/rc.local.
To reproduce:
a.) launch an instance with provided user-data
Expected behavior would be:
1. /run/rc-local-message exists with contents of /proc/uptime at the time
it was run
2. /rc-local-message.mark exists with the number of times this script has
been run ('1' after first boot)
3. /var/log/rc-local-message.log exists with a message like:
[/var/log/rc-local-message.log] === successful boot 1
4. console log should also have message like in 3 with '/dev/console'
4 is broken as rc.local output is not sent to console as reported
separately at bug 1468102.
Related bugs:
* bug 1468102: rc.local output does not go to console
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: systemd 220-7ubuntu1
ProcVersionSignature: User Name 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux 3.19.0-22-generic x86_64
ApportVersion: 2.17.3-0ubuntu4
Architecture: amd64
Date: Tue Jun 23 20:21:50 2015
Ec2AMI: ami-0434
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: OpenStack Foundation OpenStack Nova
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2011
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias:
dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2014.1.4:cvnBochs:ct1:cvr:
dmi.product.name: OpenStack Nova
dmi.product.version: 2014.1.4
dmi.sys.vendor: OpenStack Foundation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1468103/+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 1658374] Re: package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/ch
Fixed on my system with the following: $ apt-get --reinstall install libkmod2 $ apt-get install libkmod2:i386 Not certain what would have caused the mismatch between the changelogs in the first place, especially since this package is Multi-Arch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1658374 Title: package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 Status in One Hundred Papercuts: Confirmed Status in kmod package in Ubuntu: Confirmed Bug description: where can i found this information ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sat Jan 21 18:45:51 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libkmod2:22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (22-1ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/libkmod2_22-1ubuntu4_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2014-05-04 (993 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: kmod Title: package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to xenial on 2016-09-25 (118 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1658374/+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 1636912] Re: systemd-networkd runs too late for cloud-init.service (net)
** Tags removed: verification-needed -- 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/1636912 Title: systemd-networkd runs too late for cloud-init.service (net) Status in cloud-init: New Status in systemd: Fix Released Status in cloud-init package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in systemd source package in Xenial: Fix Released Status in cloud-init source package in Yakkety: New Status in systemd source package in Yakkety: Fix Released Bug description: Ubuntu Core 16 images using cloud-init fail to function when the DataSource is over the network (Like OpenStack) as networking is not yet available when cloud-init.service runs. cloud-init service unit deps look like this: [Unit] Description=Initial cloud-init job (metadata service crawler) DefaultDependencies=no Wants=cloud-init-local.service Wants=local-fs.target Wants=sshd-keygen.service Wants=sshd.service After=cloud-init-local.service After=networking.service Requires=networking.service Before=basic.target Before=dbus.socket Before=network-online.target Before=sshd-keygen.service Before=sshd.service Before=systemd-user-sessions.service Conflicts=shutdown.target Here's networkd unit deps: [Unit] Description=Network Service Documentation=man:systemd-networkd.service(8) ConditionCapability=CAP_NET_ADMIN DefaultDependencies=no # dbus.service can be dropped once on kdbus, and systemd-udevd.service can be # dropped once tuntap is moved to netlink After=systemd-udevd.service dbus.service network-pre.target systemd-sysusers.service systemd-sysctl.service Before=network.target multi-user.target shutdown.target Conflicts=shutdown.target Wants=network.target # On kdbus systems we pull in the busname explicitly, because it # carries policy that allows the daemon to acquire its name. Wants=org.freedesktop.network1.busname After=org.freedesktop.network1.busname And a critical-chain output: root@snap-test7:~# systemd-analyze critical-chain systemd-networkd Failed to get ID: Unit name systemd-networkd is not valid. The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. root@snap-test7:~# systemd-analyze critical-chain systemd-networkd.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. systemd-networkd.service +440ms └─dbus.service @11.461s └─basic.target @11.403s └─sockets.target @11.401s └─dbus.socket @11.398s └─cloud-init.service @10.127s +1.266s └─networking.service @9.305s +799ms └─network-pre.target @9.295s └─cloud-init-local.service @3.822s +5.469s └─local-fs.target @3.813s └─run-cgmanager-fs.mount @12.687s └─local-fs-pre.target @1.393s └─systemd-tmpfiles-setup-dev.service @1.116s +195ms └─kmod-static-nodes.service @887ms +193ms └─system.slice @783ms └─-.slice @721ms cloud-init would need networkd to run at or before 'networking.service' so it can raise networking to then find and use network-based datasources. # grep systemd /usr/share/snappy/dpkg.list ii libnss-resolve:amd64 229-4ubuntu11 amd64nss module to resolve names via systemd-resolved ii libpam-systemd:amd64 229-4ubuntu11 amd64system and service manager - PAM module ii libsystemd0:amd64 229-4ubuntu11 amd64systemd utility library ii systemd 229-4ubuntu11 amd64system and service manager ii systemd-sysv 229-4ubuntu11 amd64system and service manager - SysV links # grep cloud-init /usr/share/snappy/dpkg.list ii cloud-init 0.7.8-201610260005-gf7a5756-0ubuntu1~trunk~ubuntu16.04.1 all Init scripts for cloud instances SRU INFORMATION FOR systemd === Fix: For xenial it is sufficient to drop systemd-networkd's After=dbus.service (https://github.com/systemd/systemd/commit/5f004d1e32) and (for xenial only) drop the useless org.freedesktop.network1.busname unit (which is always "condition failed" as there is no kdbus, but it moves systemd-network.service after sockets.target which is too late for cloud-init). Regression po
[Touch-packages] [Bug 1640139] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1640139 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in pulseaudio package in Ubuntu: Confirmed Bug description: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.1 LTS Release: 16.04 Codename: xenial # uname -a Linux rotem-laptop 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux tried removing pulseaudio ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rotemfo2383 F pulseaudio /dev/snd/controlC0: rotemfo2383 F pulseaudio Date: Tue Nov 8 12:46:09 2016 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2016-10-25 (14 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PulseList: Error: command ['pacmd', 'list'] failed with exit code 127: pacmd: error while loading shared libraries: libpulse.so.0: cannot open shared object file: No such file or directory RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/17/2016:svnDellInc.:pnLatitudeE7450:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7450 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1640139/+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 1616422] Re: [trusty SRU/FFE] Add systemd binary package for snapd
** No longer affects: init-system-helpers (Ubuntu) ** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1616422 Title: [trusty SRU/FFE] Add systemd binary package for snapd Status in init-system-helpers source package in Trusty: Fix Released Status in systemd source package in Trusty: Fix Released Bug description: Rationale: For backporting snapd to 14.04 LTS, we need to provide systemd's service manager (not just logind and auxiliary services like logind or timesyncd). upstart will continue to do the actual booting, and systemd will act as a "deputy init" which by default does not ship with/start any services by itself. We will only support this on server (at the first iteration at least), not on desktops. Regression potential: This is a new binary package in universe, so existing systems are unaffected (provided that we ensure that the other binary packages do not change and there are no code changes that affect processes other than the "deputy pid 1" service manager). So for plain upgrades the regression potential is very low. However, there is a medium potential for breakage when actually installing the new systemd package, as it might interfere with upstart jobs or other running processes, cause boot/shutdown hangs, etc. For init-system-helpers, the regression potential is near-zero: We never had (and never will) systemd as pid 1 in trusty, so deb-systemd- invoke was previously never called. It does get called now if you install Ubuntu packages that ship a systemd unit, so we need to make that a no-op to retain the current behaviour. Test plan: 1. Dist-upgrade a trusty installation to the proposed versions. Ensure this does not pull in "systemd", and that booting, shutdown, desktop startup, suspend on lid close, resume, logout, and user switching all still work. 2. Install the "systemd" binary package (this will replace/remove systemd-shim). Verify that you can talk to the service manager with "sudo systemctl status". Check that booting and shutdown continues to work without (significant) delays. 3. Ensure that "sudo journalctl" works and that "sudo systemctl status systemd-journald" is running and has a few lines of log at the end (unlike what you get when you run systemctl as user). 4. Install a package that ships a systemd .service file, such as "haveged". Ensure that the service file is ignored, "pgrep -af haveged" should only have *one* process and "systemctl status haveged" should not be running (it should not exist, or not be enabled and be inactive). [This part also needs the updated init-system-helpers]. The only services that are running are expected to be systemd- journald.service and systemd-journald.socket. 5. Ensure that the standard targets are active, as that is where third-party/snap services hook into: systemctl status sysinit.target multi-user.target default.target 6. Install snapd (not in trusty yet, e. g. from Thomas' PPA) and ensure you can install a snap, and its services start after installing the snap and after rebooting. 7. Run "sudo apt-get install --reinstall systemd" to ensure that upgrades to newer systemd trusty versions work. The running systemd should *not* be restarted as that would disrupt snapd and its services (verify that the pid in "initctl status systemd" is the same before and after the upgrade). 8. Run "sudo apt install -y colord && sudo apt purge -y colord". This should succeed. 9. Dist-upgrade to 16.04 to ensure that there are no file conflicts, dependency issues, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/trusty/+source/init-system-helpers/+bug/1616422/+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 1660053] Re: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1660053 Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2 Status in apport package in Ubuntu: New Bug description: A marker instead of cursor comes on my screen now and then. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.4 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportLog: ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, signal 11, core limit 0 ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: /usr/lib/firefox/plugin-container (command line "/usr/lib/firefox/plugin-container /usr/lib/flashplugin-installer/libflashplayer.so -greomni /usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir /usr/lib/firefox/browser 2196 true plugin") ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is blacklisted, ignoring ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashReports: 644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload 640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash 600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 22:32:37.371843338 +0530:/var/crash/apport.0.crash 600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded Date: Sat Jan 28 22:32:37 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 2 InstallationDate: Installed on 2016-12-04 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1660053/+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 1660053] [NEW] package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2
Public bug reported: A marker instead of cursor comes on my screen now and then. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.4 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportLog: ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, signal 11, core limit 0 ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: /usr/lib/firefox/plugin-container (command line "/usr/lib/firefox/plugin-container /usr/lib/flashplugin-installer/libflashplayer.so -greomni /usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir /usr/lib/firefox/browser 2196 true plugin") ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is blacklisted, ignoring ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashReports: 644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload 640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash 600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 22:32:37.371843338 +0530:/var/crash/apport.0.crash 600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded Date: Sat Jan 28 22:32:37 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 2 InstallationDate: Installed on 2016-12-04 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1660053 Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2 Status in apport package in Ubuntu: New Bug description: A marker instead of cursor comes on my screen now and then. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.4 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportLog: ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, signal 11, core limit 0 ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: /usr/lib/firefox/plugin-container (command line "/usr/lib/firefox/plugin-container /usr/lib/flashplugin-installer/libflashplayer.so -greomni /usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir /usr/lib/firefox/browser 2196 true plugin") ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is blacklisted, ignoring ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CrashReports: 644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload 640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash 600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 22:32:37.371843338 +0530:/var/crash/apport.0.crash 600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded Date: Sat Jan 28 22:32:37 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 2 InstallationDate: Installed on 2016-12-04 (54 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1660053/+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
Re: [Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
It should be clear Bernd that English is the way to go with everything
tailored for an International Community.(in this case KDE) That some
German people are so focused on their own inability to understand the
language. (That is needet in every Internation Community) And start
demanding that the far bigger part of the community writes in there
language, even if they just could fix that by learning English in the
first place is really hard for me to understand. Im German too but i
would not demand from others to speak a language that is clearly not the
most spoken in the internet in any professional or most other
communitys. So please write with us in english and back to topic please :).
On 01/28/2017 03:16 PM, Asa-Jane Stuart-Campbell wrote:
> Nei Bernd, skriv norsk da.
>
> Or English, so everyone can understand without google translate.
>
> 2017-01-27 23:27 GMT+01:00 Bernd :
>
>> bitte deutsch schreiben
>>
>>
>> Am 27.01.2017 um 14:15 schrieb malvonni:
>>> Thanks!
>>>
>>> Em sex, 27 de jan de 2017 11:11, Bernd escreveu:
>>>
bitte deutsch schreiben
Am 26.01.2017 um 19:36 schrieb N H:
> I have experienced this problem as well, while adding KDE to the
>> desktop
> environments on my copy of Ubuntu. As I like XFCE for most things, but
> decided to see how recent versions of KDE look. During installation,
>> the
> KDE accounts config package kept trying to overwrite files provides by
> other packages. Apt-get install -f did not do it's job, and threw the
> same errors. I eventually just grabbed the .deb files using pkgs.org
>> and
> installed them with dpkg --force-all. This resulted in all sorts of
>> file
> conflicts, which as I used the --force-all option, it overrided and
> installed anyway. KDE seems to be working normally. If I need to, I
>> will
> reinstalled the package that got overwritten, once again with the
> --force-all option to make sure it does it's job. However is packaging
> those two packages, need to decided who provides what, or move the
> configs off to a third package that they both could depend on instead
>> of
> conflicting.
>
--
You received this bug notification because you are subscribed to a
duplicate bug report (1572183).
https://bugs.launchpad.net/bugs/1451728
Title:
[master] kde-config-telepathy-accounts package install error
Status in Kubuntu PPA:
Fix Released
Status in Telepathy KDE:
Fix Released
Status in kaccounts-integration package in Ubuntu:
In Progress
Status in kaccounts-providers package in Ubuntu:
Triaged
Status in ktp-accounts-kcm package in Ubuntu:
Triaged
Status in libaccounts-glib package in Ubuntu:
Fix Released
Status in kaccounts-providers source package in Wily:
Triaged
Status in ktp-accounts-kcm source package in Wily:
Triaged
Bug description:
Installing from Kubuntu 15.04 backports:
Unpacking kde-config-telepathy-accounts
(15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ...
dpkg: error processing archive
/var/cache/apt/archives/kde-config-telepathy-accounts_15.
>> 04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
(--unpack):
trying to overwrite '/usr/share/accounts/services/
>> facebook-im.service',
which is also in package account-plugin-facebook
0.12+15.04.20150415.1-0ubuntu1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
SRU information
===
[Impact] It's not possible to install KDE and Unity in co-existence
because of several file conflicts: many files under
/usr/share/accounts/{providers,services}/ are provided by both the
package "kaccounts-providers" and packages build from the "account-
plugins" source package, for example 'account-plugin-facebook'.
[Test case] Install both kaccounts-providers and
account-plugin-facebook: you'll get file conflicts for
/usr/share/accounts/services/facebook-im.service and
/usr/share/accounts/providers/facebook.provider.
You might get other conflicts as well, but those are due to bug
>> 1565772
(also nominated for SRU).
[Regression potential] Minimal: the changed packages belong to the
default KDE installation, and have already landed in Yakkety. Things
appear to be working fine there: account creation is still possible
under KDE, even after changing the file paths as per this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1628428).
>> https://bugs.launchpad.net/bugs/1451728
>>
>> Title:
>>[master] kde-config-
[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
I've recently upgraded from 12.04 to 14.04. In 12.04 all worked perfectly. I see the same sort of thing as discussed. I attach a log from dbus-monitor. PrepareForSleep True is sent, sleep state is never reached, PrepareForSleep false is never sent I have no problem suspend/hybernate via pm-suspend. sudo /lib/systemd/systemd-sleep suspend also works fine for suspend, hibernate and hybrid-sleep systemd/network manager get in a mess. seemingly together (see test results below) Since I'm on 14.04, I don't have systemd-shim, so this seems to be a systemd problem, not just -shim I used to have tlp installed, but have purged it, and re-installed systemd, the problem has not cleared. Test results: $ sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true >> network manager disables, no suspend 2nd call: $ sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true Error: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit systemd-suspend.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-suspend.service' for details. $ sudo killall NetworkManager >> Network returns. $ sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true >> network manager disables, no suspend - Test results2: $ systemctl suspend >> network manager disables, no suspend (no error msg) $ systemctl suspend Failed to issue method call: Unit systemd-suspend.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-suspend.service' for details. Failed to issue method call: Access denied $ sudo killall NetworkManager >> Network returns. $ systemctl suspend >> network manager disables, no suspend (no error msg) $ sudo systemctl status systemd-suspend.service systemd-suspend.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) $ sudo nmcli nm sleep false >> NM restarts, however, it is NOT as 'cleansing' as killing NM As: $ systemctl suspend Failed to issue method call: Unit systemd-suspend.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-suspend.service' for details. ** Attachment added: "dbus log, kill NetworkManager, wait, try to suspend, wait, kill N-Mgr" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+attachment/4810108/+files/dbus.log ** No longer affects: systemd (Ubuntu Saucy) -- 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/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in systemd package in Ubuntu: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd source package in Trusty: New Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+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 1660042] [NEW] problem mouse notebook not work
Public bug reported: the mouse embedded in my notebook asux does not work. Only works one connected with USB ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jan 28 16:46:10 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2017-01-13 (15 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X556UB ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=fb5d428d-a22c-43e8-8e66-c0b89de0d30a ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UB.405:bd06/28/2016:svnASUSTeKCOMPUTERINC.:pnX556UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X556UB 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.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jan 28 16:43:42 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 14573 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 ** 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/1660042 Title: problem mouse notebook not work Status in xorg package in Ubuntu: New Bug description: the mouse embedded in my notebook asux does not work. Only works one connected with USB ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat Jan 28 16:46:10 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:246a] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:246a] InstallationDate: Installed on 2017-01-13 (15 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK COMPUTER INC. X556UB ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic root=UUID=fb5d428d-a22c-43e8-8e66-c0b89de0d30a ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UB.405 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chass
[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
** Also 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/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in systemd package in Ubuntu: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd source package in Saucy: New Status in systemd-shim source package in Saucy: Won't Fix Status in systemd source package in Trusty: New Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1252121/+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 1660040] [NEW] old-fashioned ufw structure reduces usability
Public bug reported: Hi, ufw makes it difficult to deploy firewall rules through management systems like puppet, ansible or other scripts. ufw has three points where to put rules in: before.rules user.rules after.rules the ufw command accepts only a very limited sort of rules, and user.rules should not be used to deploy files, since user changes would be overwritten. before.rules and after.rules could easily be used for that purpose, but then the machine is cut from automated updates through apt, since apt refuses (for good reason) to replace modified files in /etc. It would be much better to have a directory like /etc/ufw/rules_v4.d , to put the old-fashioned three files into 20_before, 50_user and 70_after, and to execute all rules in this directory, thus allowing to have additional rules in separate files. regards ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ufw 0.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Jan 28 16:21:02 2017 PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to xenial on 2016-04-06 (297 days ago) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1660040 Title: old-fashioned ufw structure reduces usability Status in ufw package in Ubuntu: New Bug description: Hi, ufw makes it difficult to deploy firewall rules through management systems like puppet, ansible or other scripts. ufw has three points where to put rules in: before.rules user.rules after.rules the ufw command accepts only a very limited sort of rules, and user.rules should not be used to deploy files, since user changes would be overwritten. before.rules and after.rules could easily be used for that purpose, but then the machine is cut from automated updates through apt, since apt refuses (for good reason) to replace modified files in /etc. It would be much better to have a directory like /etc/ufw/rules_v4.d , to put the old-fashioned three files into 20_before, 50_user and 70_after, and to execute all rules in this directory, thus allowing to have additional rules in separate files. regards ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ufw 0.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: LXDE Date: Sat Jan 28 16:21:02 2017 PackageArchitecture: all SourcePackage: ufw UpgradeStatus: Upgraded to xenial on 2016-04-06 (297 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1660040/+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 1660037] [NEW] dvd Problems on Sony notebook
Public bug reported: Some Dvds and some sd cards can not be read ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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 Date: Sat Jan 28 21:56:08 2017 DistUpgraded: 2016-06-19 19:11:47,079 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] [1002:9480] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation RV730/M96 [Mobility Radeon HD 4650/5165] [104d:9035] InstallationDate: Installed on 2015-09-13 (502 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Sony Corporation VGN-FW54M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=4eb91ccb-550d-41c3-bc43-4e409be3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-19 (223 days ago) dmi.bios.date: 09/04/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R4070Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR4070Y0:bd09/04/2009:svnSonyCorporation:pnVGN-FW54M:pvrC6037WYQ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-FW54M dmi.product.version: C6037WYQ dmi.sys.vendor: Sony 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.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Jan 28 21:00:06 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-0LVDS VGA-0 xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 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/1660037 Title: dvd Problems on Sony notebook Status in xorg package in Ubuntu: New Bug description: Some Dvds and some sd cards can not be read ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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 Date: Sat Jan 28 21:56:08 2017 DistUpgraded: 2016-06-19 19:11:47,079 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96 [Mobility Radeon HD 4650/5165] [1002:9480] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation RV730/M96 [Mobility Radeon HD 4650/5165] [104d:9035] InstallationDate: Installed on 2015-09-13 (502 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Sony Corporation VGN-FW54M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=4eb91ccb-550d-41c3-bc43-4e409be3 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-06-19 (223 days ago) dmi.bios.date: 09/04/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R4070Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR4070Y0:bd09/0
Re: [Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error
Nei Bernd, skriv norsk da.
Or English, so everyone can understand without google translate.
2017-01-27 23:27 GMT+01:00 Bernd :
> bitte deutsch schreiben
>
>
> Am 27.01.2017 um 14:15 schrieb malvonni:
> > Thanks!
> >
> > Em sex, 27 de jan de 2017 11:11, Bernd escreveu:
> >
> >> bitte deutsch schreiben
> >>
> >>
> >>
> >> Am 26.01.2017 um 19:36 schrieb N H:
> >>> I have experienced this problem as well, while adding KDE to the
> desktop
> >>> environments on my copy of Ubuntu. As I like XFCE for most things, but
> >>> decided to see how recent versions of KDE look. During installation,
> the
> >>> KDE accounts config package kept trying to overwrite files provides by
> >>> other packages. Apt-get install -f did not do it's job, and threw the
> >>> same errors. I eventually just grabbed the .deb files using pkgs.org
> and
> >>> installed them with dpkg --force-all. This resulted in all sorts of
> file
> >>> conflicts, which as I used the --force-all option, it overrided and
> >>> installed anyway. KDE seems to be working normally. If I need to, I
> will
> >>> reinstalled the package that got overwritten, once again with the
> >>> --force-all option to make sure it does it's job. However is packaging
> >>> those two packages, need to decided who provides what, or move the
> >>> configs off to a third package that they both could depend on instead
> of
> >>> conflicting.
> >>>
> >> --
> >> You received this bug notification because you are subscribed to a
> >> duplicate bug report (1572183).
> >> https://bugs.launchpad.net/bugs/1451728
> >>
> >> Title:
> >>[master] kde-config-telepathy-accounts package install error
> >>
> >> Status in Kubuntu PPA:
> >>Fix Released
> >> Status in Telepathy KDE:
> >>Fix Released
> >> Status in kaccounts-integration package in Ubuntu:
> >>In Progress
> >> Status in kaccounts-providers package in Ubuntu:
> >>Triaged
> >> Status in ktp-accounts-kcm package in Ubuntu:
> >>Triaged
> >> Status in libaccounts-glib package in Ubuntu:
> >>Fix Released
> >> Status in kaccounts-providers source package in Wily:
> >>Triaged
> >> Status in ktp-accounts-kcm source package in Wily:
> >>Triaged
> >>
> >> Bug description:
> >>Installing from Kubuntu 15.04 backports:
> >>
> >>Unpacking kde-config-telepathy-accounts
> >> (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ...
> >>dpkg: error processing archive
> >> /var/cache/apt/archives/kde-config-telepathy-accounts_15.
> 04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
> >> (--unpack):
> >> trying to overwrite '/usr/share/accounts/services/
> facebook-im.service',
> >> which is also in package account-plugin-facebook
> >> 0.12+15.04.20150415.1-0ubuntu1
> >>dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> >>
> >>SRU information
> >>===
> >>
> >>[Impact] It's not possible to install KDE and Unity in co-existence
> >>because of several file conflicts: many files under
> >>/usr/share/accounts/{providers,services}/ are provided by both the
> >>package "kaccounts-providers" and packages build from the "account-
> >>plugins" source package, for example 'account-plugin-facebook'.
> >>
> >>[Test case] Install both kaccounts-providers and
> >> account-plugin-facebook: you'll get file conflicts for
> >> /usr/share/accounts/services/facebook-im.service and
> >> /usr/share/accounts/providers/facebook.provider.
> >>You might get other conflicts as well, but those are due to bug
> 1565772
> >> (also nominated for SRU).
> >>
> >>[Regression potential] Minimal: the changed packages belong to the
> >>default KDE installation, and have already landed in Yakkety. Things
> >>appear to be working fine there: account creation is still possible
> >>under KDE, even after changing the file paths as per this fix.
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions
> >>
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1628428).
> https://bugs.launchpad.net/bugs/1451728
>
> Title:
> [master] kde-config-telepathy-accounts package install error
>
> Status in Kubuntu PPA:
> Fix Released
> Status in Telepathy KDE:
> Fix Released
> Status in kaccounts-integration package in Ubuntu:
> In Progress
> Status in kaccounts-providers package in Ubuntu:
> Triaged
> Status in ktp-accounts-kcm package in Ubuntu:
> Triaged
> Status in libaccounts-glib package in Ubuntu:
> Fix Released
> Status in kaccounts-providers source package in Wily:
> Triaged
> Status in ktp-accounts-kcm source package in Wily:
> Triaged
>
> Bug description:
> Installing from Kubuntu 15.04 backports:
>
> Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1)
> over (0.9.0-0ubuntu1) ...
> dpkg: error processing archive /var/cache/apt/archives/kde-
> config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~pp
[Touch-packages] [Bug 1656785] Re: nc -d -l does not return data (only empty strings)
** Changed in: netcat-openbsd (Debian) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu. https://bugs.launchpad.net/bugs/1656785 Title: nc -d -l does not return data (only empty strings) Status in netcat-openbsd package in Ubuntu: New Status in netcat-openbsd package in Debian: New Bug description: The Zesty (17.04) version of nc (1.130-1ubuntu1) no longer returns the received data when using the '-d' (do not listen on stdin) flag together with the '-l' (listen on socket) flag. This used to work in previous releases (1.105-7ubuntu1 Trusty-Yakkety). In fact, in the previous version, the '-d' flag seems to be required to make the data transfer more reliable in scripts. Testcase: Attached script passes on older versions, fails with the current version of nc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1656785/+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 1654624] Re: dhcp apparmor profile complains about lxd client
> Which are the perceivable consequences of this bug? I currently cannot survey the consequences, since I am not familiar with the recent semantic changes of apparmor (are there any docs? Any hints to the users about changes? Any release notes?) For some time now I am spending and wasting lots of time to hunt bugs in all sorts of software like firefox, chromium, ejabberd, lxd,... which is all caused by sudden apparmor trouble. A side effect of all these bugs is that log files (and desktops through aa-notify) are flooded with hundres, thousands, millions of log messages, which jams a system and makes it impossible to find really important log messages, and, btw., can ruin flash memory in SSDs and SD-Cards within short time. Why on earth has one backported this pile of bugs into a LTS version? This rendered Ubuntu so unreliable, that I have to consider to change to CentOS or something like this for servers in order to get SELinux instead. Is there any way to get 16.04 stable again? BTW: How should I answer the question about the consequences of the bug, if I don't see any docs about was has changed with apparmor? ** Changed in: isc-dhcp (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1654624 Title: dhcp apparmor profile complains about lxd client Status in apparmor package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Hi, strange problem recently occured: I'm having some ubuntu machines running in LXD (nothing unusual, just based on the regular ubuntu LXD images) on a ubuntu host. Worked well for some time. But now the host generates messages like Jan 6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400 audit(1483726625.388:247): apparmor="DENIED" operation="file_perm" namespace="root//lxd-rackadmin_" profile="/sbin/dhclient" name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=165536 ouid=0 in /var/log/kern.log. For some reason the apparmor running on the host interferes with the containers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.6 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jan 6 19:19:12 2017 SourcePackage: isc-dhcp UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1654624/+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 1654624] Re: dhcp apparmor profile complains about lxd client
> Removing the LXD task, this is yet another apparmor bug from the apparmor > stacking/namespacing change which was backported to Xenial. Well, that explains a lot. 16.04 was formerly stable but recently began to drive me crazy because of so many apparmor problems with almost every major daemon or browser, and an aa-notify which just vomates hundreds of messages onto the desktop faster than one can click them away. I am not an apparmor expert, but was able to deal with it for years, but suddenly have the problem that adding permissions to the local-files for local extensions does not solve problems as expected. I think it is not overestimated to say that this apparmor thing broke the usability of 16.04. What in the world was the reason to backport these problems into a stable release? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1654624 Title: dhcp apparmor profile complains about lxd client Status in apparmor package in Ubuntu: New Status in isc-dhcp package in Ubuntu: Incomplete Bug description: Hi, strange problem recently occured: I'm having some ubuntu machines running in LXD (nothing unusual, just based on the regular ubuntu LXD images) on a ubuntu host. Worked well for some time. But now the host generates messages like Jan 6 19:17:05 monstrum kernel: [ 1063.263531] audit: type=1400 audit(1483726625.388:247): apparmor="DENIED" operation="file_perm" namespace="root//lxd-rackadmin_" profile="/sbin/dhclient" name="/apparmor/.null" pid=5125 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=165536 ouid=0 in /var/log/kern.log. For some reason the apparmor running on the host interferes with the containers. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu12.6 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Jan 6 19:19:12 2017 SourcePackage: isc-dhcp UpgradeStatus: Upgraded to xenial on 2016-04-06 (275 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1654624/+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
Re: [Touch-packages] [Bug 1659936] Re: package apt 1.2.18 failed to install/upgrade: subprocess new pre-removal script returned error exit status 135
many thanks, I suspect a hdd failure, system reports even SECTOR ERROR about 2 x full records on POST screen. I think problem is solved. Rob 2017-01-27 21:32 GMT+01:00 Ubuntu Foundations Team Bug Bot < 1659...@bugs.launchpad.net>: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Reviewing your dmesg attachment in this bug report it > seems that there is a problem with your hardware. I recommend > performing a back up and then investigating the situation. Measures you > might take include checking cable connections and using software tools > to investigate the health of your hardware. In the event that is is not > in fact an error with your hardware please set the bug's status back to > New. Thanks and good luck! > > [This is an automated message. I apologize if it reached you > inappropriately; please just reply to this message indicating so.] > > ** Tags added: hardware-error > > ** Changed in: apt (Ubuntu) >Importance: Undecided => Low > > ** Changed in: apt (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1659936 > > Title: > package apt 1.2.18 failed to install/upgrade: subprocess new pre- > removal script returned error exit status 135 > > Status in apt package in Ubuntu: > Invalid > > Bug description: > as mentioned above; other: system reports a lot of bugs by start (in > terminal), starting with problems (time), after has temporary graphic > problems e.g. firefox suddenly is shuting down; system doesn't execute > terminal commands and reports errors; recently often hang on shut down > (only by switch); some signs of destabilization? i don't instal any > new applets from about 3 months, i only write a lot and send emails / > surf. > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: apt 1.2.18 > ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 > Uname: Linux 4.4.0-59-generic i686 > ApportVersion: 2.20.1-0ubuntu2.5 > Architecture: i386 > Date: Fri Jan 27 13:54:26 2017 > ErrorMessage: subprocess new pre-removal script returned error exit > status 135 > InstallationDate: Installed on 2016-12-07 (51 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 > (20160719) > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.1 >apt 1.2.18 > SourcePackage: apt > Title: package apt 1.2.18 failed to install/upgrade: subprocess new > pre-removal script returned error exit status 135 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1659936/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1659936 Title: package apt 1.2.18 failed to install/upgrade: subprocess new pre- removal script returned error exit status 135 Status in apt package in Ubuntu: Invalid Bug description: as mentioned above; other: system reports a lot of bugs by start (in terminal), starting with problems (time), after has temporary graphic problems e.g. firefox suddenly is shuting down; system doesn't execute terminal commands and reports errors; recently often hang on shut down (only by switch); some signs of destabilization? i don't instal any new applets from about 3 months, i only write a lot and send emails / surf. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt 1.2.18 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic i686 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: i386 Date: Fri Jan 27 13:54:26 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 135 InstallationDate: Installed on 2016-12-07 (51 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: apt Title: package apt 1.2.18 failed to install/upgrade: subprocess new pre-removal script returned error exit status 135 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1659936/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial
In my main computer 64-bit Ubuntu 16.04 LTS, it is working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1547297 Title: No auto login in Ubuntu GNOME Xenial Status in Ubuntu GNOME: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in sddm package in Ubuntu: Confirmed Bug description: Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto login during installation, but once the installation was complete and I booted into Ubuntu GNOME I was asked for my password. I looked in the user UI and auto login was set to off, so I unlocked it, selected auto login = on, clicked on lock again, and rebooted but was once again asked for my password and the user UI once again showed auto login = off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gdm3 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Feb 18 20:26:14 2016 InstallationDate: Installed on 2016-02-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+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 1547297] Re: No auto login in Ubuntu GNOME Xenial
I have a problem. Im using auto-login in my laptop. When im editing Users and Groups and selecting auto-login off in my user account. It not working. When reboot the computer. My account auto-login to desktop. Using Ubuntu MATE 16.04 32-bit. I have full upgraded system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1547297 Title: No auto login in Ubuntu GNOME Xenial Status in Ubuntu GNOME: Fix Released Status in accountsservice package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in sddm package in Ubuntu: Confirmed Bug description: Just installed Ubuntu GNOME Xenial 20160218 amd64 and selected to auto login during installation, but once the installation was complete and I booted into Ubuntu GNOME I was asked for my password. I looked in the user UI and auto login was set to off, so I unlocked it, selected auto login = on, clicked on lock again, and rebooted but was once again asked for my password and the user UI once again showed auto login = off. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gdm3 3.18.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Feb 18 20:26:14 2016 InstallationDate: Installed on 2016-02-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160218) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1547297/+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
