[Touch-packages] [Bug 1718717] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()
Since I executed sudo apt install --reinstall cups-daemon bug doesn't come up again. ** Changed in: cups (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1718717 Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() Status in CUPS: New Status in cups package in Ubuntu: Fix Released Bug description: after updates of cups-filter and reboot ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 21 17:43:42 2017 ExecutablePath: /usr/sbin/cupsd Lpstat: device for HP-LaserJet-4200: hp:/net/hp_LaserJet_4200?ip=192.168.10.21 device for PDF: cups-pdf:/ MachineType: Dell Inc. OptiPlex 960 Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer (w/ options) HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended) ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=b7879efd-332b-42e8-9e7c-4ec466c90bac ro agp=off quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f32dc0c7954 : cmpq $0x0,(%rdi) PC (0x7f32dc0c7954) ok source "$0x0" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() UpgradeStatus: Upgraded to artful on 2017-09-19 (2 days ago) UserGroups: dmi.bios.date: 08/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 0Y958C dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd08/06/2013:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0Y958C:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 960 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1718717/+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 1720083] [NEW] Profile defaults to headset mode instead of a2dp
Public bug reported: Using 17.10 # Reproduce: 1. Pair bluetooth headphone with mic (like Bose QC35) 2. Play music # What I get: Music is very bad quality because the "headset head unit (HSP/HFP)" profile is chosen by default. Switching to the "High Fidelity Playback (A2DP Sink)" profile fixes the audio. # What I expect: Music is good quality because A2DP profile is chosen by default. # Why should A2DP be chosen by default? 1. Given that HSP quality is so low, we can assume that the primary use for bluetooth headsets is to listen to music. As a result, setting it to A2DP by default will give good experience for the biggest amount of use-cases. 2. Bluez supports automatic switching from A2DP to HSP when a program identifies a recording stream as "Phone" (or optionally when it doesn't identify the recording stream with PulseAudio 11 [1]) so in many cases, it's not even needed to manually switch to HSP. [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful ** Description changed: Using 17.10 # Reproduce: 1. Pair bluetooth headphone with mic (like Bose QC35) 2. Play music # What I get: Music is very bad quality because the "headset head unit (HSP/HFP)" profile is chosen by default. Switching to the "High Fidelity Playback (A2DP Sink)" profile fixes the audio. # What I expect: Music is good quality because A2DP profile is chosen by default. # Why should A2DP be chosen by default? 1. Given that HSP quality is so low, we can assume that the primary use for bluetooth headsets is to listen to music. As a result, setting it to A2DP by default will give good experience for the biggest amount of use-cases. - 2. Bluez supports automatic switching from A2DP to HSP when a program identifies a recording stream as "Phone" (or optionally when it doesn't identify the recording stream with PulseAudio 11) + 2. Bluez supports automatic switching from A2DP to HSP when a program identifies a recording stream as "Phone" (or optionally when it doesn't identify the recording stream with PulseAudio 11) so in many cases, it's not even needed to manually switch to HSP. ** Description changed: Using 17.10 # Reproduce: 1. Pair bluetooth headphone with mic (like Bose QC35) 2. Play music # What I get: Music is very bad quality because the "headset head unit (HSP/HFP)" profile is chosen by default. Switching to the "High Fidelity Playback (A2DP Sink)" profile fixes the audio. # What I expect: Music is good quality because A2DP profile is chosen by default. # Why should A2DP be chosen by default? 1. Given that HSP quality is so low, we can assume that the primary use for bluetooth headsets is to listen to music. As a result, setting it to A2DP by default will give good experience for the biggest amount of use-cases. - 2. Bluez supports automatic switching from A2DP to HSP when a program identifies a recording stream as "Phone" (or optionally when it doesn't identify the recording stream with PulseAudio 11) so in many cases, it's not even needed to manually switch to HSP. + 2. Bluez supports automatic switching from A2DP to HSP when a program identifies a recording stream as "Phone" (or optionally when it doesn't identify the recording stream with PulseAudio 11 [1]) so in many cases, it's not even needed to manually switch to HSP. + + [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ -- 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/1720083 Title: Profile defaults to headset mode instead of a2dp Status in pulseaudio package in Ubuntu: New Bug description: Using 17.10 # Reproduce: 1. Pair bluetooth headphone with mic (like Bose QC35) 2. Play music # What I get: Music is very bad quality because the "headset head unit (HSP/HFP)" profile is chosen by default. Switching to the "High Fidelity Playback (A2DP Sink)" profile fixes the audio. # What I expect: Music is good quality because A2DP profile is chosen by default. # Why should A2DP be chosen by default? 1. Given that HSP quality is so low, we can assume that the primary use for bluetooth headsets is to listen to music. As a result, setting it to A2DP by default will give good experience for the biggest amount of use-cases. 2. Bluez supports automatic switching from A2DP to HSP when a program identifies a recording stream as "Phone" (or optionally when it doesn't identify the recording stream with PulseAudio 11 [1]) so in many cases, it's not even needed to manually switch to HSP. [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720083/+subs
[Touch-packages] [Bug 1720083] Re: Profile defaults to headset mode instead of a2dp
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720083 Title: Profile defaults to headset mode instead of a2dp Status in pulseaudio package in Ubuntu: New Bug description: Using 17.10 # Reproduce: 1. Pair bluetooth headphone with mic (like Bose QC35) 2. Play music # What I get: Music is very bad quality because the "headset head unit (HSP/HFP)" profile is chosen by default. Switching to the "High Fidelity Playback (A2DP Sink)" profile fixes the audio. # What I expect: Music is good quality because A2DP profile is chosen by default. # Why should A2DP be chosen by default? 1. Given that HSP quality is so low, we can assume that the primary use for bluetooth headsets is to listen to music. As a result, setting it to A2DP by default will give good experience for the biggest amount of use-cases. 2. Bluez supports automatic switching from A2DP to HSP when a program identifies a recording stream as "Phone" (or optionally when it doesn't identify the recording stream with PulseAudio 11 [1]) so in many cases, it's not even needed to manually switch to HSP. [1] https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720083/+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 1719579] Comment bridged from LTC Bugzilla
--- Comment From sthou...@in.ibm.com 2017-09-28 04:07 EDT--- (In reply to comment #38) > Created attachment 121204 [details] > Sosreport Portion of audit log: 4159727.044528] audit: type=1400 audit(1506504293.943:82): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-ee1b97ba-b85c-46ae-97a1-1b45afe8266c" pid=26937 comm="apparmor_parser" [4159727.059543] audit: type=1400 audit(1506504293.959:83): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="libvirt-ee1b97ba-b85c-46ae-97a1-1b45afe8266c//qemu_bridge_helper" pid=26937 comm="apparmor_parser" [4159727.322330] KVM guest htab at c03cbc00 (order 28), LPID 2 [4159727.344133] audit: type=1400 audit(1506504294.243:84): apparmor="DENIED" operation="open" profile="libvirt-ee1b97ba-b85c-46ae-97a1-1b45afe8266c" name="/etc/gss/mech.d/" pid=26939 comm="qemu-system-ppc" requested_mask="r" denied_mask="r" fsuid=64055 ouid=0 Attaching sosreport with this Bugzilla. -- 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/1719579 Title: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save Status in The Ubuntu-power-systems project: New Status in apparmor package in Ubuntu: New Bug description: == Comment: #1 - SEETEENA THOUFEEK - 2017-01-17 00:09:16 == Bala, Please mail me the machine information. == Comment: #3 - SEETEENA THOUFEEK - 2017-01-17 02:14:06 == 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on '/var/tmp/bala' 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on '/var/tmp/bala' to '0:0' 2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : failed to restore save state label on /var/tmp/bala 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala) 2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca535c0 2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with ret=-1 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 : prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 rerr=0x3fffa59be3c0 2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : Encode length as 172 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 offset=0 2017-01-16 12:09:37.707+: 7024: info : virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 serial=4 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 tx=0x100133d2590 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:192 : mode=3 2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : EVENT_POLL_UPDATE_HANDLE: watch=417 events=3 2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : Interrupting 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133caea0 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133d23c0 . 2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": "failed"}} 2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 : mon=0x3fff94004d90 obj=0x100133b5670 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : object=0x100133a8000 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : object=0x100133a8000 type=0 gen=0x100133d1160 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : object=0x100133d2a80 type=2 gen=0x100133d1160 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : result={"status":"failed"} 2017-01-1
[Touch-packages] [Bug 1662031] Re: Switching language and format broken
If nobody figures out what makes the variables in ~/.pam_environment be overridden by the variables in /etc/default/locale, I'm thinking of an ugly hack which may work. ~/.pam_environment is maintained by /usr/share/language-tools/save-to- pam-env. In case of a GNOME desktop we could make that file write to ~/.profile as well. ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- 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/1662031 Title: Switching language and format broken Status in Ubuntu GNOME: New Status in accountsservice package in Ubuntu: New Status in gdm3 package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: New Status in accountsservice source package in Artful: New Status in gdm3 source package in Artful: Confirmed Status in gnome-control-center source package in Artful: New Bug description: In Ubuntu GNOME 16.10 it doesn't matter what display language I select - the effective language is still the one stated in /etc/default/locale. ~/.pam_environment is changed as expected, but the variables set in /etc/default/locale override ~/.pam_environment. In Ubuntu GNOME 16.04 language switching takes effect, but the reason for that seems to be that /etc/default/locale is changed as well, so when a user changes the display language (or format), it changes it for all users on the system. The overriding by /etc/default/locale is probably caused by some other package(s) but g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1662031/+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 1720116] [NEW] apport-gtk sigfault in libgtk-3
Public bug reported: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "apport-gtk_error_0928.txt" https://bugs.launchpad.net/bugs/1720116/+attachment/4958036/+files/apport-gtk_error_0928.txt -- 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/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: New Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+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 1719579] Re: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save
You'll need to allow /etc/gss/mech.d/ r, and after that, I wouldn't be surprised if you get denials for files inside this directory ;-) -- 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/1719579 Title: [Ubuntu 16.04.2] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save Status in The Ubuntu-power-systems project: New Status in apparmor package in Ubuntu: New Bug description: == Comment: #1 - SEETEENA THOUFEEK - 2017-01-17 00:09:16 == Bala, Please mail me the machine information. == Comment: #3 - SEETEENA THOUFEEK - 2017-01-17 02:14:06 == 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on '/var/tmp/bala' 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on '/var/tmp/bala' to '0:0' 2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : failed to restore save state label on /var/tmp/bala 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala) 2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca535c0 2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with ret=-1 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 : prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 rerr=0x3fffa59be3c0 2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : Encode length as 172 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 offset=0 2017-01-16 12:09:37.707+: 7024: info : virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 serial=4 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 tx=0x100133d2590 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:192 : mode=3 2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : EVENT_POLL_UPDATE_HANDLE: watch=417 events=3 2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : Interrupting 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133caea0 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133d23c0 . 2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": "failed"}} 2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 : mon=0x3fff94004d90 obj=0x100133b5670 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : object=0x100133a8000 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : object=0x100133a8000 type=0 gen=0x100133d1160 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : object=0x100133d2a80 type=2 gen=0x100133d1160 2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : result={"status":"failed"} 2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : mon=0x3fff94004d90 event=MIGRATION 2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff94004d90 2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : vm=0x3fff4ca535c0 2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: obj=0x100133d2870 classname=virDomainQemuMonitorEvent 2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : obj=0x100133d2870 2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x100133d2870 2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : OBJECT_DISPOSE: obj=0x100133d2870 2017-01-16 12:14:28.445+: 7019: debug : virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870 2017-01-16 12:14:28.445+: 7019: de
[Touch-packages] [Bug 1719211] Re: Bad interface name
Thank you for using Ubuntu and reporting a bug. We restrict the interface name simply for input validation and after doing a bit of research, I see no reason why we can't allow '-' and '_' in the interface name. I'll adjust trunk for that, but it may be expanded further. ** Changed in: ufw (Ubuntu) Importance: Undecided => Medium ** Changed in: ufw (Ubuntu) Status: New => Triaged ** Changed in: ufw (Ubuntu) Assignee: (unassigned) => Jamie Strandboge (jdstrand) -- 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/1719211 Title: Bad interface name Status in ufw package in Ubuntu: Triaged Bug description: Is there a reason to restrict interface's name in ufw? Should ufw accept what iptables accept as iface name? I've a vpn with lot of nodes, its iface name contain a '-' so cannot use ufw on it. I've found the check here and cannot found a reason for it: http://bazaar.launchpad.net/~jdstrand/ufw/trunk/view/head:/src/common.py#L300 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1719211/+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 1720116] Re: apport-gtk sigfault in libgtk-3
In case it could help; an old solution: https://github.com/zpydr/gnome-shell-extension-taskbar/issues/62 ** Bug watch added: github.com/zpydr/gnome-shell-extension-taskbar/issues #62 https://github.com/zpydr/gnome-shell-extension-taskbar/issues/62 -- 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/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: New Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+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 1719211] Re: Bad interface name
** Changed in: ufw (Ubuntu) Status: Triaged => In Progress -- 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/1719211 Title: Bad interface name Status in ufw package in Ubuntu: In Progress Bug description: Is there a reason to restrict interface's name in ufw? Should ufw accept what iptables accept as iface name? I've a vpn with lot of nodes, its iface name contain a '-' so cannot use ufw on it. I've found the check here and cannot found a reason for it: http://bazaar.launchpad.net/~jdstrand/ufw/trunk/view/head:/src/common.py#L300 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1719211/+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 1720126] [NEW] [ip link] Message truncated error for large number of passthrough VFs
Public bug reported: I've ran into an issue when creating a large number of virtual functions on a SR-IOV capable device. ip link show reports a message truncated error: ip link show > /dev/null Message truncated Message truncated Message truncated A likely cause might be that when called in a system where the number of PCIe Virtual Functions are more than 30 for a given Physical Function, the netlink response is larger than 16K, meaning that a message is truncated. The issue is seen with Ubuntu14.04 and Ubuntu16.04. A possible solution for the issue is to increase the size of the receive buffer in libnetlink.c Additional information: = Ubuntu16 system stack@cluster04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial stack@cluster04:~$ uname -r 4.4.0-93-generic stack@cluster04:~$ apt-cache policy iproute2 iproute2: Installed: 4.3.0-1ubuntu3.16.04.1 Version table: *** 4.3.0-1ubuntu3.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages = Ubuntu14 system: root@boomslang:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.3 LTS Release:14.04 Codename: trusty root@boomslang:~# uname -r 4.4.0-96-generic root@boomslang:~# apt-cache policy iproute2 iproute2: Installed: 3.12.0-2ubuntu1 Version table: *** 3.12.0-2ubuntu1 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1720126 Title: [ip link] Message truncated error for large number of passthrough VFs Status in iproute2 package in Ubuntu: New Bug description: I've ran into an issue when creating a large number of virtual functions on a SR-IOV capable device. ip link show reports a message truncated error: ip link show > /dev/null Message truncated Message truncated Message truncated A likely cause might be that when called in a system where the number of PCIe Virtual Functions are more than 30 for a given Physical Function, the netlink response is larger than 16K, meaning that a message is truncated. The issue is seen with Ubuntu14.04 and Ubuntu16.04. A possible solution for the issue is to increase the size of the receive buffer in libnetlink.c Additional information: = Ubuntu16 system stack@cluster04:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial stack@cluster04:~$ uname -r 4.4.0-93-generic stack@cluster04:~$ apt-cache policy iproute2 iproute2: Installed: 4.3.0-1ubuntu3.16.04.1 Version table: *** 4.3.0-1ubuntu3.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages = Ubuntu14 system: root@boomslang:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.3 LTS Release: 14.04 Codename: trusty root@boomslang:~# uname -r 4.4.0-96-generic root@boomslang:~# apt-cache policy iproute2 iproute2: Installed: 3.12.0-2ubuntu1 Version table: *** 3.12.0-2ubuntu1 0 500 http://za.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1720126/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
No other wireless devices. I use the touchpad or a wired mouse on my laptop. I use a Wireless G AP (I'm guessing that is 2.4G) I will try using my bluetooth headset connecting to my phone while I use my laptop to see if it interferes. -- 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1720131] [NEW] logind holds open file descriptor to DRI nodes, preventing nvidia suspend
Public bug reported: The nvidia binary kernel driver now creates /dev/dri/card? nodes. When switching between the nvidia and intel drivers on a hybrid system, all holders of the DRI node need to relinquished so that the nvidia driver can be unloaded so that bbswitch can turn the card off. In order for switching hybrid graphics to not require a reboot, logind needs to close its file descriptor to the nvidia DRI node. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 28 08:36:13 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=ZFS=rpool/system ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1720131 Title: logind holds open file descriptor to DRI nodes, preventing nvidia suspend Status in systemd package in Ubuntu: New Bug description: The nvidia binary kernel driver now creates /dev/dri/card? nodes. When switching between the nvidia and intel drivers on a hybrid system, all holders of the DRI node need to relinquished so that the nvidia driver can be unloaded so that bbswitch can turn the card off. In order for switching hybrid graphics to not require a reboot, logind needs to close its file descriptor to the nvidia DRI node. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 28 08:36:13 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=ZFS=rpool/system ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1720131/+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 1719720] Comment bridged from LTC Bugzilla
On Thu, Sep 28, 2017 at 06:20:03AM -, bugproxy wrote: > Yeah. even I thought its touch issue. I did look into touch source code > as well. It uses below flag to create file. > O_WRONLY | O_CREAT | O_NONBLOCK | O_NOCTTY, MODE_RW_UGO); This is not about file creation flags, it's about memory maps. This is likely to be either a toolchain regression, or a bug in glibc, since touch itself should not be calling mmap() for anything that it does. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1719720 Title: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127 Status in The Ubuntu-power-systems project: Triaged Status in coreutils package in Ubuntu: Triaged Bug description: ---Problem Description--- Currently syslog is getting flooded with below log messages .. Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch /run/run.vpdd update' failed with exit code 127. This is on UBuntu 17.10 latest build.. ---uname output--- Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = ZZ-L ---Steps to Reproduce--- I have seen these messages logged more often when we do any hotplug operations.. ex. cpu hotplug.. Ok. .this is the continuation of LTC #144627 / Launchpad #1682774. As suggested in that bug, we did change udev script to create temporary file under /run and that patch is available in ubuntu 17.10. Looks like this is udev script issue. If I modify systemd-udevd like below it works fine. I've limited udev knowledge. I don't know if you have any other better solution to this issue. root@ltc-boston123:/lib/systemd/system# diff -Naurp systemd-udevd.service.org systemd-udevd.service --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500 +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500 @@ -25,7 +25,7 @@ KillMode=mixed WatchdogSec=3min TasksMax=infinity MountFlags=slave -MemoryDenyWriteExecute=yes +#MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 SystemCallArchitectures=native -Vasant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1719720/+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 1720133] [NEW] USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer
Public bug reported: [Impact] * This impacts all Ubuntu releases which received an update of x.org to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10 * End users are unable to use their USB displays unless they workaround the problem which currently involves disabling pageflip for modesetting in x.org.conf file * The fix which has been submitted to x.org extends blacklisting mechanism so the EVDI kernel module which is essential for DisplayLink USB 3.0 devices to work is correctly recognised by x.org. Then the PRIME sync is disabled in such case; The patch can be found here: https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1 [Test Case] 1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed requirements and instructions can be found here: 2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking station 3. Plug in an external monitor (HDMI or DisplayPort) to the docking station Expected result: The external monitor should light up and show the desktop Actual result: The monitor remains black or shows frozen desktop. [Regression Potential] * The patchset extends number of modules for which x.org changes its functionality. It checks if "evdi" string is in the syspath so it is quite unlikely there would be any impact on anything else then USB 3.0 displays which use EVDI module. [Other Info] * The patch has been applied to Ubuntu x.org source code built and tested. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1720133 Title: USB 3.0 displays are black on Ubuntu after x.org update to 1.18.3 or newer Status in xorg package in Ubuntu: New Bug description: [Impact] * This impacts all Ubuntu releases which received an update of x.org to 1.18.3 or newer, i.e. Ubuntu 16.04, 16.10, 17.04 & 17.10 * End users are unable to use their USB displays unless they workaround the problem which currently involves disabling pageflip for modesetting in x.org.conf file * The fix which has been submitted to x.org extends blacklisting mechanism so the EVDI kernel module which is essential for DisplayLink USB 3.0 devices to work is correctly recognised by x.org. Then the PRIME sync is disabled in such case; The patch can be found here: https://cgit.freedesktop.org/xorg/xserver/commit/?id=fbd80b2c8ebe9fd41229dc5438524d107c071ff1 [Test Case] 1. On a PC device with Ubuntu install DisplayLink SW for Ubuntu v1.3.54 downloaded from http://www.displaylink.com/downloads/ubuntu. Detailed requirements and instructions can be found here: 2. Plug in a DisplayLink USB 3.0 compatible device, e.g. Dell D3100 docking station 3. Plug in an external monitor (HDMI or DisplayPort) to the docking station Expected result: The external monitor should light up and show the desktop Actual result: The monitor remains black or shows frozen desktop. [Regression Potential] * The patchset extends number of modules for which x.org changes its functionality. It checks if "evdi" string is in the syspath so it is quite unlikely there would be any impact on anything else then USB 3.0 displays which use EVDI module. [Other Info] * The patch has been applied to Ubuntu x.org source code built and tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1720133/+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 1713175] Re: Obsolete backup ext2/3/4 superblocks can confuse e2fsck on an encrypted LUKS partition
I have to disagree; the only tool that uses the backup superblock is e2fsck, and if you accidentally run wipefs on the volume, you should be able to recover it with e2fsck. If you don't want to attempt to recover a filesystem there, then don't run e2fsck. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1713175 Title: Obsolete backup ext2/3/4 superblocks can confuse e2fsck on an encrypted LUKS partition Status in cryptsetup package in Ubuntu: Confirmed Status in e2fsprogs package in Ubuntu: New Status in util-linux package in Ubuntu: Invalid Bug description: fsck.ext4 runs on a LUKS partition and starts to correct inode entries, rendering the partition corrupted and useless. It seems like it should defensively check where it is an isLuks partition using "cryptsetup isLuks /dev/sda1" before continuing to modify it. I hope such a defensive check can be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1713175/+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 1720138] Re: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate()
*** This bug is a duplicate of bug 1664886 *** https://bugs.launchpad.net/bugs/1664886 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1664886, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1720138/+attachment/4958063/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1720138/+attachment/4958066/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1720138/+attachment/4958074/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1720138/+attachment/4958076/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1720138/+attachment/4958077/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1720138/+attachment/4958078/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1720138/+attachment/4958081/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1664886 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1720138 Title: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate() Status in systemd package in Ubuntu: New Bug description: randon crash ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu11 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 28 15:02:56 2017 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2017-05-19 (131 days ago) InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA TECRA Z50-A ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=UUID=e258a8fb-763e-4568-b5e9-b4ebbddb079e ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f0e7dec5baa:movzbl 0x2f(%rdi),%r8d PC (0x7f0e7dec5baa) ok source "0x2f(%rdi)" (0x706f746b73656494) not located in a known VMA region (needed readable region)! destination "%r8d" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: systemd StacktraceTop: ?? () from /lib/systemd/libsystemd-shared-234.so internal_hashmap_iterate () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () ?? () Title: systemd-resolved crashed with SIGSEGV in internal_hashmap_iterate() UpgradeStatus: Upgraded to artful on 2017-08-07 (51 days ago) UserGroups: dmi.bios.date: 09/02/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 4.20 dmi.board.asset.tag: 00 dmi.board.name: TECRA Z50-A dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion4.20:bd09/02/2015:svnTOSHIBA:pnTECRAZ50-A:pvrPT544E-04S02SDU:rvnTOSHIBA:rnTECRAZ50-A:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: TECRA Z50-A dmi.product.version: PT544E-04S02SDU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1720138/+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 1720116] Re: apport-gtk sigfault in libgtk-3
This error has shown up in last week or so. Been running Artful for over a month. Usually on every boot will open a command shell and update/upgrade for the latest updates then open chrome. By then the popup box shows up indicating the an error had occurred and asking if it should be reported. After hitting the Yes button nothing else happens. Have a syslog snippet and I think a corresponding crash from 9/22 if it would help. -- 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/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: Incomplete Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+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 1720116] Re: apport-gtk sigfault in libgtk-3
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem. ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Status: New => Incomplete -- 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/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: Incomplete Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+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 1720131] Re: logind holds open file descriptor to DRI nodes, preventing nvidia suspend
** Bug watch added: github.com/systemd/systemd/issues #6908 https://github.com/systemd/systemd/issues/6908 ** Also affects: systemd via https://github.com/systemd/systemd/issues/6908 Importance: Unknown Status: Unknown -- 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/1720131 Title: logind holds open file descriptor to DRI nodes, preventing nvidia suspend Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: The nvidia binary kernel driver now creates /dev/dri/card? nodes. When switching between the nvidia and intel drivers on a hybrid system, all holders of the DRI node need to relinquished so that the nvidia driver can be unloaded so that bbswitch can turn the card off. In order for switching hybrid graphics to not require a reboot, logind needs to close its file descriptor to the nvidia DRI node. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 28 08:36:13 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=ZFS=rpool/system ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1720131/+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 1313550] Re: ping does not work as a normal user on trusty tarball cloud images.
The remaining trusty task is fixed in curtin according to c#29 as well, updating the tasks to match that. ** Changed in: maas (Ubuntu Trusty) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1313550 Title: ping does not work as a normal user on trusty tarball cloud images. Status in curtin: Fix Committed Status in MAAS: Fix Released Status in curtin package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Fix Released Status in maas package in Ubuntu: Fix Released Status in tar package in Ubuntu: Fix Released Status in tar source package in Precise: Confirmed Status in maas source package in Saucy: Won't Fix Status in tar source package in Saucy: Won't Fix Status in curtin source package in Trusty: Fix Released Status in maas source package in Trusty: Fix Released Status in tar source package in Trusty: Fix Released Status in maas source package in Vivid: Won't Fix Status in maas source package in Wily: Fix Released Bug description: With trusty, /bin/ping relies on having extended attributes and kernel capabilities to gain the cap_net_raw+p capability. This allows removing the suid bit. However, the tarball cloud images do not preserve the extended attributes, and thus /bin/ping does not work on a system derived from them. Summary of problem per package: * lxc: ubuntu cloud template needs to extract * download template needs to extract with xattr flags * server side download creation tools need xattr flags * [unconfirmed] tarball caches need creation and extraction with xattr flags * tar: need the '--xattr' and '--acl' flags backported * maas: uec2roottgz needs to use xattr/acl flags * curtin: extraction needs to use xattr/acl flags. * cloud-image-build: needs to create -root.tar.gz with xattr/acl flags Related Bugs: * bug 1382632: horizon insecure key file permissions * bug 1386237: tar strange behavior with --acl and xattr * bug 1313550: ping broken (xattrs lost in tar extraction) To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1313550/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I can't even get vpn and/or socks5 to work. This is dangerous, perhaps it should be stressed that people shouldn't use 11.10 as a daily OS until this is fixed. I know, I know, me should know better. I'm just glad I checked before assuming I was in a secure tunnel. Otherwise 11.10 is working fine without any show stoppers for moi. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Confirmed Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+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 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH
** Changed in: snapd (Ubuntu) Status: New => Invalid ** Changed in: bash (Ubuntu) Status: Triaged => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1711254 Title: 16.04.3 deployments include non-existent directories in $PATH Status in bash package in Ubuntu: Opinion Status in snapd package in Ubuntu: Invalid Bug description: Noticed this while doing regression testing on 16.04.3, and a number of customers have asked with concerns as well during their testing. I don't know exactly when this started, but we just started noticing it with 16.04.3 (4.10) but $PATH by default now includes several directories that do not exist: ubuntu@above-ox:~$ find $(echo "$PATH" | sed -e 's/:/ /g') -maxdepth 1 -type d find: ‘/home/ubuntu/bin’: No such file or directory find: ‘/home/ubuntu/.local/bin’: No such file or directory /usr/local/sbin /usr/local/bin /usr/sbin /usr/bin /sbin /bin /usr/games /usr/local/games find: ‘/snap/bin’: No such file or directory We noticed this because it was causing a resource job in the certification suite to suddenly start failing (the failure was not catastrophic, but it did appear to customers who were concerned. I've verified this on both s390x and amd64 16.04.3 deployments via MAAS 2.2. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.10.0-32-generic 4.10.0-32.36~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic s390x ApportVersion: 2.20.1-0ubuntu2.10 Architecture: s390x Date: Wed Aug 16 18:59:34 2017 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en.US_UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1711254/+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 1716143] Re: Vertical separator of left sidebar is misaligned with vertical separator of window decoration
This bug was fixed in the package ubuntu-themes - 16.10+17.10.20170925-0ubuntu1 --- ubuntu-themes (16.10+17.10.20170925-0ubuntu1) artful; urgency=medium [ Carlo Lobrano ] * Fix misaligned Entry widget borders (LP: #1712996) [ Marco Trevisan (Treviño) ] * Ambiance,Radiance: fix vertical linked buttons borders, corners and backgrounds (LP: #1718234) * Ambiance, Radiance: be less restrictive in setting headerbar minimum height (LP: #1712011) * Ambiance,Radiance: refactor .titlebar theming to properly support headerbar children (LP: #1716143) -- Marco Trevisan (Treviño) Mon, 25 Sep 2017 15:58:56 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1716143 Title: Vertical separator of left sidebar is misaligned with vertical separator of window decoration Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: To reproduce: 1. Open gnome-control-center (latest 1:3.25.92.1-0ubuntu1) 2. Look at the vertical separator of the sidebar; between the categories and settings; it is misaligned with the vertical separator above it in the window decoration 3. Select Dock; the sidebar separator becomes darker and it is still misaligned It also happens in gnome-tweak-tool. This bug does not happen in Adwaita. See the attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170817-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 17:27:36 2017 InstallationDate: Installed on 2017-09-09 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1716143/+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 1718234] Re: Vertically linked buttons have wrong gradients and borders when in the middle
This bug was fixed in the package ubuntu-themes - 16.10+17.10.20170925-0ubuntu1 --- ubuntu-themes (16.10+17.10.20170925-0ubuntu1) artful; urgency=medium [ Carlo Lobrano ] * Fix misaligned Entry widget borders (LP: #1712996) [ Marco Trevisan (Treviño) ] * Ambiance,Radiance: fix vertical linked buttons borders, corners and backgrounds (LP: #1718234) * Ambiance, Radiance: be less restrictive in setting headerbar minimum height (LP: #1712011) * Ambiance,Radiance: refactor .titlebar theming to properly support headerbar children (LP: #1716143) -- Marco Trevisan (Treviño) Mon, 25 Sep 2017 15:58:56 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1718234 Title: Vertically linked buttons have wrong gradients and borders when in the middle Status in Ubuntu theme: In Progress Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1718234/+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 1719067] Re: log entry "unattended-upgrade -d" implies "debug" option but "download only" is meant
** Changed in: apt (Ubuntu) Status: New => Triaged ** Changed in: apt (Ubuntu) Importance: Undecided => Low ** Tags added: artful ** Summary changed: - log entry "unattended-upgrade -d" implies "debug" option but "download only" is meant + apt.systemd.daily job logs about incorrect switch being used -- 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/1719067 Title: apt.systemd.daily job logs about incorrect switch being used Status in apt package in Ubuntu: Triaged Bug description: The script /usr/lib/apt/apt.systemd.daily produces log entries in the systemd journal like unattended-upgrade -d (success) or unattended-upgrade -d (error) These seem to imply that "unattended-upgrade" was run with the command line flag "-d", which according to the manpage means "debug". But actually "unattended-upgrade" was run with the option "--download- only". I would be easier to understand and debug the u-a behavior if the log entries would reflect this clearly. (Ubuntu 16.04.3 LTS, apt 1.2.24) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 10:18:06 2017 InstallationDate: Installed on 2014-08-28 (1121 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-20 (490 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1719067/+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 1718900] Re: typo in manpage "statisfy"
This is correct in artful. upgrade (apt-get(8)) upgrade is used to install available upgrades of all packages currently installed on the system from the sources configured via sources.list(5). New packages will be installed if required to satisfy dependencies, but existing packages will never be removed. If an upgrade for a package requires the remove of an installed package the upgrade for this package isn't performed. ** Changed in: apt (Ubuntu) Status: New => Fix Released -- 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/1718900 Title: typo in manpage "statisfy" Status in apt package in Ubuntu: Fix Released Bug description: the description for "upgrade" in the apt manpage says: New packages will be installed if required to statisfy dependencies, but existing packages will never be removed. this should probably rather read "satisfy" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1718900/+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 1712996] Re: Misaligned Entry borders in horizontally linked Box
This bug was fixed in the package ubuntu-themes - 16.10+17.10.20170925-0ubuntu1 --- ubuntu-themes (16.10+17.10.20170925-0ubuntu1) artful; urgency=medium [ Carlo Lobrano ] * Fix misaligned Entry widget borders (LP: #1712996) [ Marco Trevisan (Treviño) ] * Ambiance,Radiance: fix vertical linked buttons borders, corners and backgrounds (LP: #1718234) * Ambiance, Radiance: be less restrictive in setting headerbar minimum height (LP: #1712011) * Ambiance,Radiance: refactor .titlebar theming to properly support headerbar children (LP: #1716143) -- Marco Trevisan (Treviño) Mon, 25 Sep 2017 15:58:56 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1712996 Title: Misaligned Entry borders in horizontally linked Box Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Ambiance and Radiance themes both show a misaligned Entry widget when it is placed inside a horizontally linked Box. Ubuntu release: Ubuntu 17.04 Same behavior observed on Artful Package version: apt-cache policy light-themes light-themes: Installed: 16.10+17.04.20170406-0ubuntu1 Candidate: 16.10+17.04.20170406-0ubuntu1 Application affected: - Evince: page X of Y entry - Image viewer: zoom percentage entry ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: light-themes 16.10+17.04.20170406-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Aug 25 08:30:11 2017 InstallationDate: Installed on 2017-04-14 (132 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1712996/+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 1712011] Re: Unable to close Printer properties
This bug was fixed in the package ubuntu-themes - 16.10+17.10.20170925-0ubuntu1 --- ubuntu-themes (16.10+17.10.20170925-0ubuntu1) artful; urgency=medium [ Carlo Lobrano ] * Fix misaligned Entry widget borders (LP: #1712996) [ Marco Trevisan (Treviño) ] * Ambiance,Radiance: fix vertical linked buttons borders, corners and backgrounds (LP: #1718234) * Ambiance, Radiance: be less restrictive in setting headerbar minimum height (LP: #1712011) * Ambiance,Radiance: refactor .titlebar theming to properly support headerbar children (LP: #1716143) -- Marco Trevisan (Treviño) Mon, 25 Sep 2017 15:58:56 + ** Changed in: ubuntu-themes (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1712011 Title: Unable to close Printer properties Status in gnome-control-center: Confirmed Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: From settings I open Printers and click on settings (gear icon) for my printer which bring up a pop-up with printer details (name , location, address, etc). There is no way to close this pop-up. Instead of a top toolbar there is thin dark line. The pop-up cannot be moved. Occurs using 17.10 default and Wayland. Screenshot added Workaround -- Press the Esc key to close the dialog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu6 Architecture: i386 BootLog: /dev/sda1: clean, 261728/30531584 files, 8847848/122096128 blocks CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Aug 21 08:55:08 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 6670 [1028:0b0e] InstallationDate: Installed on 2017-07-14 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170606.1) MachineType: Dell Inc. OptiPlex 9010 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=5a1aae5a-efbf-41a8-bfb3-c460b0bda660 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0M9KCM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd09/19/2012:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn0M9KCM:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Aug 21 08:45:01 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSennheiser Sennheiser USB Headset KEYBOARD, id 8 inputDELL Dell USB Entry Keyboard KEYBOARD, id 9 inputUSB OPTICAL MOUSEMOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu3 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1712011/+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 1720131] Re: logind holds open file descriptor to DRI nodes, preventing nvidia suspend
** Changed in: systemd Status: Unknown => 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/1720131 Title: logind holds open file descriptor to DRI nodes, preventing nvidia suspend Status in systemd: New Status in systemd package in Ubuntu: New Bug description: The nvidia binary kernel driver now creates /dev/dri/card? nodes. When switching between the nvidia and intel drivers on a hybrid system, all holders of the DRI node need to relinquished so that the nvidia driver can be unloaded so that bbswitch can turn the card off. In order for switching hybrid graphics to not require a reboot, logind needs to close its file descriptor to the nvidia DRI node. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Sep 28 08:36:13 2017 InstallationDate: Installed on 2017-09-20 (8 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=ZFS=rpool/system ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1720131/+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 1687647] Re: udev version 232-21ubuntu3 from ports is broken on Zesty s390x
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1687647 Title: udev version 232-21ubuntu3 from ports is broken on Zesty s390x Status in systemd package in Ubuntu: Confirmed Bug description: I'm attempting to install some cert tools on a z/KVM instance of Zesty. This is failing because udev exits with an error during installation. The apt logs show this: Setting up udev (232-21ubuntu3) ... addgroup: The group `input' already exists as a system group. Exiting. cat: '/sys/class/net/eth*/address': No such file or directory dpkg: error processing package udev (--configure): subprocess installed post-installation script returned error exit status 1 and because of that, all other packages up the dependency chain fail to install. Interestingly, this is resolved by installing the older version of udev and libudev1 ubuntu@s1lp9g003:~$ apt-cache policy udev udev: Installed: 232-21ubuntu3 Candidate: 232-21ubuntu3 Version table: *** 232-21ubuntu3 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty-updates/main s390x Packages 100 /var/lib/dpkg/status 232-21ubuntu2 500 500 http://us.ports.ubuntu.com/ubuntu-ports zesty/main s390x Packages ubuntu@s1lp9g003:~$ sudo apt-get install udev=232-21ubuntu2 libudev1=232-21ubuntu2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-4.8.0-36-generic linux-image-4.8.0-46-generic linux-image-extra-4.8.0-36-generic linux-image-extra-4.8.0-46-generic Use 'sudo apt autoremove' to remove them. The following packages will be DOWNGRADED: libudev1 udev 0 upgraded, 0 newly installed, 2 downgraded, 0 to remove and 0 not upgraded. 6 not fully installed or removed. Need to get 0 B/1056 kB of archives. After this operation, 3072 B disk space will be freed. Do you want to continue? [Y/n] y dpkg: warning: downgrading udev from 232-21ubuntu3 to 232-21ubuntu2 (Reading database ... 99656 files and directories currently installed.) Preparing to unpack .../udev_232-21ubuntu2_s390x.deb ... Unpacking udev (232-21ubuntu2) over (232-21ubuntu3) ... dpkg: warning: downgrading libudev1:s390x from 232-21ubuntu3 to 232-21ubuntu2 Preparing to unpack .../libudev1_232-21ubuntu2_s390x.deb ... Unpacking libudev1:s390x (232-21ubuntu2) over (232-21ubuntu3) ... Setting up libudev1:s390x (232-21ubuntu2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Setting up udev (232-21ubuntu2) ... addgroup: The group `input' already exists as a system group. Exiting. update-initramfs: deferring update (trigger activated) Processing triggers for systemd (232-21ubuntu3) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up python3-checkbox-support (0.34.0~rc1+git201704041517+pkg52~ubuntu17.04.1) ... Setting up plainbox-provider-resource-generic (0.31.0+git201704241134+pkg28~ubuntu17.04.1) ... Setting up plainbox-provider-checkbox (0.35.0+git201705012258+pkg34~ubuntu17.04.1) ... Setting up plainbox-provider-certification-server (0.33.0+git201705021508+pkg60~ubuntu17.04.1) ... Setting up canonical-certification-server (0.33.0+git201705021508+pkg60~ubuntu17.04.1) ... Processing triggers for initramfs-tools (0.125ubuntu9) ... update-initramfs: Generating /boot/initrd.img-4.10.0-20-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: vda (). Done. As you can see, once I installed the original zesty version of udev and libudev1, my packages succeeded in completing installation. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: udev 232-21ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: s390x CustomUdevRuleFiles: 41-generic-ccw-0.0.0003.rules 41-generic-ccw-0.0.0004.rules 41-generic-ccw-0.0..rules 41-generic-ccw-0.0.0005.rules 41-cio-ignore.rules 41-generic-ccw-0.0.0001.rules 41-generic-ccw-0.0.0002.rules Date: Tue May 2 11:41:16 2017 Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcKernelCmdLine: ro
[Touch-packages] [Bug 1717737] Re: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status '
We'll need more than just the final error message to even start to imagine what's happening here. ** Changed in: graphite2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1717737 Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in graphite2 package in Ubuntu: Incomplete Bug description: tried to install gcc ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgraphite2-3:amd64 1.3.6-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 AptOrdering: libgraphite2-3: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 16 19:44:19 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 DpkgHistoryLog: Start-Date: 2017-09-16 19:44:19 Commandline: apt-get install gcc Requested-By: kev (1000) DpkgTerminalLog: dpkg: error processing package libgraphite2-3:amd64 (--configure): package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-07-03 (75 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: graphite2 Title: package libgraphite2-3:amd64 1.3.6-1ubuntu1 failed to install/upgrade: package libgraphite2-3:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1717737/+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 1642447] Re: package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 tem uma versão
You'll need to install the same version of the i386 package together. I don't know what you were running, but please try to contact user support instead. ** Changed in: graphite2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1642447 Title: package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1) Status in graphite2 package in Ubuntu: Invalid Bug description: Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 libgraphite2-3: Instalado: 1.3.9-1 Candidato: 1.3.9-1 Tabela de versão: *** 1.3.9-1 500 500 http://cz.archive.ubuntu.com/ubuntu zesty-proposed/main amd64 Packages 500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty-proposed/main amd64 Packages 500 http://mirror.ufscar.br/ubuntu zesty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.3.8-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 500 http://cz.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 500 http://ubuntu.c3sl.ufpr.br/ubuntu zesty/main amd64 Packages 500 http://mirror.ufscar.br/ubuntu zesty/main amd64 Packages ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libgraphite2-3:amd64 1.3.9-1 ProcVersionSignature: Ubuntu 4.9.0-1.2-generic 4.9.0-rc5 Uname: Linux 4.9.0-1-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Nov 17 00:03:37 2016 Dependencies: gcc-6-base 6.2.0-13ubuntu1 libc6 2.24-3ubuntu1 libgcc1 1:6.2.0-13ubuntu1 ErrorMessage: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1) InstallationDate: Installed on 2016-02-11 (279 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: graphite2 Title: package libgraphite2-3:amd64 1.3.9-1 failed to install/upgrade: pacote libgraphite2-3:amd64 1.3.9-1 não pode ser configurado pois libgraphite2-3:i386 tem uma versão diferente (1.3.8-1ubuntu1) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1642447/+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 1352322] Re: gdebi FTBFS when the locale is not en_US
This bug was fixed in the package gdebi - 0.9.5.3ubuntu3 --- gdebi (0.9.5.3ubuntu3) trusty-proposed; urgency=medium * Backport a fix from 0.9.5.5 to fix FTBFS with non en_US locales (LP: #1352322) -- Vlad Orlov Tue, 12 Sep 2017 13:34:30 -0700 ** Changed in: gdebi (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1352322 Title: gdebi FTBFS when the locale is not en_US Status in gdebi package in Ubuntu: Fix Released Status in gdebi source package in Trusty: Fix Released Status in gdebi package in Debian: Fix Released Bug description: [Impact] It's impossible to build gdebi from source with the locale other than en_US in Trusty. It had been fixed in gdebi 0.9.5.5, which is available in newer releases, starting from Vivid. The backported fix can be applied in Trusty. The debdiff which is attached to this report contains the fix. [Test Case] Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first log attached to this report. [Regression Potential] The patch only affects a test which is launched during the build, it doesn't affect runtime at all. The test is passed successfully with the patch. All the tests are independent from each other, so the patch can't introduce any regressions to other tests. [Original Description] System: Xubuntu 14.04. Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates). Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first attachment. Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+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 1352322] Update Released
The verification of the Stable Release Update for gdebi has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1352322 Title: gdebi FTBFS when the locale is not en_US Status in gdebi package in Ubuntu: Fix Released Status in gdebi source package in Trusty: Fix Released Status in gdebi package in Debian: Fix Released Bug description: [Impact] It's impossible to build gdebi from source with the locale other than en_US in Trusty. It had been fixed in gdebi 0.9.5.5, which is available in newer releases, starting from Vivid. The backported fix can be applied in Trusty. The debdiff which is attached to this report contains the fix. [Test Case] Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first log attached to this report. [Regression Potential] The patch only affects a test which is launched during the build, it doesn't affect runtime at all. The test is passed successfully with the patch. All the tests are independent from each other, so the patch can't introduce any regressions to other tests. [Original Description] System: Xubuntu 14.04. Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates). Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first attachment. Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+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 1717794] Re: apport-gtk crashed with SIGABRT in g_assertion_message()
** Information type changed from Private Security to Public -- 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/1717794 Title: apport-gtk crashed with SIGABRT in g_assertion_message() Status in apport package in Ubuntu: New Bug description: just this say ERROR ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: apport-gtk 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 17 13:38:44 2017 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2017-07-24 (54 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720) InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_AR.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.2, python3-minimal, 3.6.1-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14rc1, python-minimal, 2.7.13-2 Signal: 6 SourcePackage: apport StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1717794/+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 1719821] Re: haven't been able to truely downn
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1719821 Title: haven't been able to truely downn Status in xorg package in Ubuntu: Invalid Bug description: packages. everything is only halfoperating . I am a newbie to computers as it is so I dont fully understand what needs tobe done all the time or how to adjust thing to fitwhat I'm doing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-36.40~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 27 05:20:21 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.40, 4.10.0-35-generic, x86_64: installed virtualbox, 5.0.40, 4.10.0-36-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems 2nd Generation Core Processor Family Integrated Graphics Controller [1179:fb20] InstallationDate: Installed on 2017-09-21 (5 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: TOSHIBA Satellite C855 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-36-generic.efi.signed root=UUID=40c6e0e5-3568-4c9a-92dd-13d7316eb99f ro nopat plymouth:debug vesafb.invalid=1 drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/14/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.60 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.60:bd01/14/2013:svnTOSHIBA:pnSatelliteC855:pvrPSCBLU-02J006:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite C855 dmi.product.version: PSCBLU-02J006 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Sep 27 03:47:53 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719821/+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 1719782] Re: problem
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1719782 Title: problem Status in xorg package in Ubuntu: Invalid Bug description: give me proper update for my system ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 4.4.0-97.120-generic 4.4.87 Uname: Linux 4.4.0-97-generic x86_64 NonfreeKernelModules: openafs wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Sep 27 11:33:32 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics [103c:80c2] InstallationDate: Installed on 2016-11-24 (306 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Notebook ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-97-generic.efi.signed root=UUID=f110cba6-8b9c-4548-8ed4-f543954307e6 ro plymouth:debug splash quiet drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/14/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80C2 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd04/14/2017:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C2:rvr96.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.5 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: Tue Sep 26 23:06:47 2017 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 20049 vendor SDC xserver.version: 2:1.18.4-0ubuntu0.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719782/+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 1720169] [NEW] [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front] Background noise or low volume
Public bug reported: White noise all the time, no matter volume level. I tried disable power save option. It didn't work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: efrain 1971 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 28 10:10:31 2017 InstallationDate: Installed on 2017-04-03 (178 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.9 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.9:bd02/06/2017:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7040 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-28T10:04:33.733342 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1720169 Title: [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: White noise all the time, no matter volume level. I tried disable power save option. It didn't work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: efrain 1971 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 28 10:10:31 2017 InstallationDate: Installed on 2017-04-03 (178 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio Interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [OptiPlex 7040, Realtek Generic, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.9 dmi.board.name: 0Y7WYT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.9:bd02/06/2017:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 7040 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-28T10:04:33.733342 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720169/+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 1712308] Re: systemd-journald crashed with SIGABRT in stpcpy()
** Information type changed from Public Security to Public -- 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/1712308 Title: systemd-journald crashed with SIGABRT in stpcpy() Status in systemd package in Ubuntu: New Bug description: I don't know this bug ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu6 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 Date: Mon Aug 21 21:30:00 2017 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2017-08-19 (2 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: ASUSTeK COMPUTER INC. X555UB ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic.efi.signed root=UUID=c14d5ef3-dd2e-428f-a5c1-60b487802de7 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: sd_device_new_from_subsystem_sysname () from /lib/systemd/libsystemd-shared-234.so sd_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so udev_device_new_from_device_id () from /lib/systemd/libsystemd-shared-234.so ?? () ?? () from /lib/systemd/libsystemd-shared-234.so Title: systemd-journald crashed with SIGABRT in sd_device_new_from_subsystem_sysname() UpgradeStatus: Upgraded to artful on 2017-08-19 (2 days ago) UserGroups: audio pulse pulse-access video dmi.bios.date: 10/18/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UB.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UB 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.:bvrX555UB.204:bd10/18/2015:svnASUSTeKCOMPUTERINC.:pnX555UB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555UB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712308/+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 1617620] Re: Autorun files from Removable Media
Hi, To get the default changed, could you please file a bug with the upstream GNOME project here: https://bugzilla.gnome.org/ Once you've filed the bug, please like the upstream bug to this one. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1617620 Title: Autorun files from Removable Media Status in gsettings-desktop-schemas package in Ubuntu: New Status in unity-control-center package in Ubuntu: Confirmed Bug description: Ubuntu 16 is still automatically executing software that resides in an external resource (removable media), such as USB or CD. I don't need to tell you how bad this is.. --- You can see the default value that allows to autoplay / autorun files by doing the following steps: 1. In Ubuntu 16.04, go to Settings -> Details. 2. In the left pane choose "Removable Media". 3. On the right pane you'll see "Software", while the value in the drop-down menu is "Run Software". --- A fix suggestion: Instead of "Run Software", the default value should be "Do nothing". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1617620/+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 1481038] Re: iproute2 crashes being reported since kernel version 3.13-0-59-generic
Per former comments and no new related issues closing the bug to clean up. ** Changed in: iproute2 (Ubuntu) Status: Triaged => Invalid ** Changed in: iproute2 (Ubuntu Trusty) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Trusty) Status: Triaged => Invalid ** Changed in: linux (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux (Ubuntu Trusty) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1481038 Title: iproute2 crashes being reported since kernel version 3.13-0-59-generic Status in iproute2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: Invalid Status in linux source package in Trusty: Fix Released Bug description: There has recently been a tremendous uptick in the number of crashes being reported about iproute2 since 2015-07-27. This was initially noticed as the phasing of the iproute2 package in -updates for 14.04 (SRU bug 1470091) was stopped. Its worth noting that the same increase in crashes was not detected with the Vivid SRU. Additionally, it appears that the increase in crash rate is unrelated to the iproute2 SRU as it occurs with the version of the package in the release pocket or the updates pocket for 14.04. The following is a database query showing the quantity of crashes on a daily basis about the iproute2 package for the version of the package in the release pocket and then the updates pocket. ipdb> old_version '3.12.0-2' ipdb> counters_cf.get(old_vers_column, column_start='20150803', column_reversed=True) OrderedDict([(u'20150803', 15), (u'20150802', 4), (u'20150801', 2), (u'20150731', 13), (u'20150730', 39), (u'20150729', 50), (u'20150728', 51), (u'20150727', 1), (u'20150623', 1), (u'20150523', 1), (u'20150519', 1), (u'20150511', 1), (u'20150509', 1), (u'20150419', 1), (u'20150413', 1), (u'20150329', 1), (u'20150302', 1), (u'20150220', 1), (u'20150130', 1), (u'20150129', 1), (u'20150128', 1), (u'20150103', 1), (u'20141021', 1), (u'20140930', 1), (u'20140917', 1), (u'20140904', 1), (u'20140826', 1), (u'20140818', 1), (u'20140808', 1), (u'20140801', 1), (u'20140723', 1)]) ipdb> new_version '3.12.0-2ubuntu1' ipdb> counters_cf.get(new_vers_column, column_start='20150803', column_reversed=True) OrderedDict([(u'20150803', 7), (u'20150802', 1), (u'20150731', 8), (u'20150730', 24), (u'20150729', 25), (u'20150728', 2), (u'20150727', 1)]) Notice the increase starting on 20150728 for the old version of the package. I've reviewed the individual crashes from 20150729 and all of them (regardless of the iproute2 package version) were using the following kernel version. I'd attribute the drop in crashes on 20150801 and 20150802 to it being the weekend. 3.13.0-59-generic Unfortunately, all the crashes from the iproute2 package are incomplete / corrupt so there isn't much to go on. Here is one example crash: https://errors.ubuntu.com/oops/331373ac-3596-11e5-9ed9-fa163e22e467 I'll add all the OOPSes from 20150729 as an attachment if somebody wants to have a look at them. I'm also happy to run more queries of the OOPSes to see if we can determine a pattern. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1481038/+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 1720177] [NEW] [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI] Background noise or low volume
Public bug reported: Sound Quality is poor. When I am powering up the volume to 100% audio sounds distorted. I am using Windows 8.1 in this very laptop as well where the audio is working perfectly. So, it's not a hardware related problem. Audio level is low too. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: rafin 1677 F...m pulseaudio /dev/snd/controlC0: rafin 1677 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 28 22:02:35 2017 InstallationDate: Installed on 2017-09-25 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: High background noise, or volume is too low Title: [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.40 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.asset.tag: 2CE3070VGQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.40:bd01/29/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1009002:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1009002 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1720177 Title: [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI] Background noise or low volume Status in alsa-driver package in Ubuntu: New Bug description: Sound Quality is poor. When I am powering up the volume to 100% audio sounds distorted. I am using Windows 8.1 in this very laptop as well where the audio is working perfectly. So, it's not a hardware related problem. Audio level is low too. Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: rafin 1677 F...m pulseaudio /dev/snd/controlC0: rafin 1677 F pulseaudio CurrentDesktop: Unity Date: Thu Sep 28 22:02:35 2017 InstallationDate: Installed on 2017-09-25 (3 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: High background noise, or volume is too low Title: [HP ProBook 4540s, Intel PantherPoint HDMI, Digital Out, HDMI] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/29/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.40 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.asset.tag: 2CE3070VGQ dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.40:bd01/29/2013:svnHewlett-Packard:pnHPProBook4540s:pvrA1009002:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1009002 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720177/+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 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718966 Title: Cannot install snaps on Ubuntu 14.04 with /var on its own partition Status in snapd: Confirmed Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: Confirmed Bug description: Installing snaps is not possible on Ubuntu 14.04 when having /var on its own partition, whether its LVM or not. The issue is with the core snap being unable to mount: The error with /var isolated and using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) The error with /var isolated but without using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service' for details. ) The same error happens if I try to install the hello-world snap (with LVM in this example): root@ubuntu:~# snap install hello-world error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) I cannot reproduce the issue in Ubuntu 16.04. I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image which doesn't isolate /var on its own partition. I tried adding a secondary disk to that cloud image VM and create a dummy VG and LV, but couldn't reproduce the issue. Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with only a / partition and swap. Steps to reproduce: === # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and configure /, /var and swap on their own partitions (with LVM or not, the issue happens in both situations). root@ubuntu:~# lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert rootvol vg00 -wi-ao--- 3.72g swap vg00 -wi-ao--- 3.72g varvol vg00 -wi-ao--- 3.72g root@ubuntu:~# df -h Filesystem Size Used Avail Use% Mounted on udev 484M 4.0K 484M 1% /dev tmpfs100M 988K 99M 1% /run /dev/dm-03.7G 1.7G 1.8G 49% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 497M 0 497M 0% /run/shm none 100M 0 100M 0% /run/user /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var # Upgrade system, install snapd and reboot root@ubuntu:~# apt update root@ubuntu:~# apt upgrade -y root@ubuntu:~# apt install -y snapd root@ubuntu:~# reboot # After reboot, check kernel version and try to install the canonical-livepatch snap: root@ubuntu:~# uname -a Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# snap list No snaps are installed yet. Try "snap install hello-world". root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1718966/+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 1717946] Re: UIFe: Drop xterm and xdiagnose from default install
** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1717946 Title: UIFe: Drop xterm and xdiagnose from default install Status in ubuntu-meta package in Ubuntu: Triaged Bug description: Impact == I'm proposing to drop 3 apps from the default Ubuntu 17.10 install: XTerm UXTerm xdiagnose These are visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = These were only in the default install because of the FailsafeX feature. Timo Aaltonen (tjaalton), maintainer of Ubuntu's X stack and co-maintainer in Debian, has said that feature isn't important any more, considering the transition to Wayland. xdiagnose also provided some apport hooks for diagnosing display problems but that was moved to xorg itself earlier this release cycle. xdiagnose currently doesn't run in the Ubuntu session on Wayland. https://irclogs.ubuntu.com/2017/09/18/%23ubuntu-desktop.html#t14:18 Discussed earlier in the cycle: https://lists.ubuntu.com/archives/ubuntu-desktop/2017-June/004980.html https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005059.html List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1717946/+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 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition
** Changed in: systemd (Ubuntu Trusty) Assignee: (unassigned) => Rafael David Tinoco (inaddy) -- 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/1718966 Title: Cannot install snaps on Ubuntu 14.04 with /var on its own partition Status in snapd: Confirmed Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: Confirmed Bug description: Installing snaps is not possible on Ubuntu 14.04 when having /var on its own partition, whether its LVM or not. The issue is with the core snap being unable to mount: The error with /var isolated and using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) The error with /var isolated but without using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service' for details. ) The same error happens if I try to install the hello-world snap (with LVM in this example): root@ubuntu:~# snap install hello-world error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) I cannot reproduce the issue in Ubuntu 16.04. I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image which doesn't isolate /var on its own partition. I tried adding a secondary disk to that cloud image VM and create a dummy VG and LV, but couldn't reproduce the issue. Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with only a / partition and swap. Steps to reproduce: === # Install Ubuntu 14.04 in KVM (I used the 14.04.4 server iso) and configure /, /var and swap on their own partitions (with LVM or not, the issue happens in both situations). root@ubuntu:~# lvs LV VG Attr LSize Pool Origin Data% Move Log Copy% Convert rootvol vg00 -wi-ao--- 3.72g swap vg00 -wi-ao--- 3.72g varvol vg00 -wi-ao--- 3.72g root@ubuntu:~# df -h Filesystem Size Used Avail Use% Mounted on udev 484M 4.0K 484M 1% /dev tmpfs100M 988K 99M 1% /run /dev/dm-03.7G 1.7G 1.8G 49% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 497M 0 497M 0% /run/shm none 100M 0 100M 0% /run/user /dev/mapper/vg00-varvol 3.7G 716M 2.8G 21% /var # Upgrade system, install snapd and reboot root@ubuntu:~# apt update root@ubuntu:~# apt upgrade -y root@ubuntu:~# apt install -y snapd root@ubuntu:~# reboot # After reboot, check kernel version and try to install the canonical-livepatch snap: root@ubuntu:~# uname -a Linux ubuntu 4.4.0-96-generic #119~14.04.1-Ubuntu SMP Wed Sep 13 08:40:48 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# snap list No snaps are installed yet. Try "snap install hello-world". root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1718966/+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 1714493] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania.
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1714493 Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania. Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: not working ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: util-linux:amd64: Configure python3-jwt:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Sep 1 14:01:58 2017 DpkgHistoryLog: Start-Date: 2017-09-01 14:01:56 Commandline: /usr/bin/unattended-upgrade Upgrade: python3-jwt:amd64 (1.4.2-1, 1.4.2-1ubuntu0.1) DpkgTerminalLog: dpkg: błąd przetwarzania pakietu util-linux (--configure): Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania. ErrorMessage: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania. InstallationDate: Installed on 2017-02-23 (190 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: Pakiet jest w złym stanie - powinien zostać zainstalowany ponownie przed próbą jego skonfigurowania. UpgradeStatus: Upgraded to zesty on 2017-04-18 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1714493/+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 1720116] Re: apport-gtk sigfault in libgtk-3
Unable to run apport-retrace. Get the following cliff@cliffps:~/tmp$ apport-retrace _usr_share_apport_apport-gtk.0.crash ERROR: report file does not contain one of the required fields: Package First part of the crash file ProblemType: Crash Architecture: amd64 Date: Fri Sep 22 05:36:27 2017 DistroRelease: Ubuntu 17.10 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1504050301 InterpreterPath: /usr/bin/python3.6 ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /root ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 PATH=(custom, no user) ProcMaps: -- 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/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: Incomplete Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+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 1544942] Update Released
The verification of the Stable Release Update for unattended-upgrades has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1544942 Title: Marks unneeded packages as manually installed, if --dry-run is used Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: marking linux-headers-4.2.0-16-generic for remove marking linux-headers-4.2.0-16 for remove marking linux-image-4.2.0-16-generic for remove marking linux-image-extra-4.2.0-16-generic for remove Packages that are auto removed: 'linux-headers-4.2.0-16-generic linux-headers-4.2.0-16 linux-image-4.2.0-16-generic linux-image-extra-4.2.0-16-generic' /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64 /usr/bin/dpkg --status-fd 11 --configure --pending Packages were successfully auto-removed InstCount=0 DelCount=4 BrokenCount=0 $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux- headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux- image-4.2.0-16-generic:amd64 $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals Expect the packages to remain automatically installed after each `sudo unattended-upgrade --dry-run -d`. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unattended-upgrades 0.86.2ubuntu1.1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 12 13:58:29 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-24 (18 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2016-02-12T13:53:13.426454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1544942/+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 1544942] Re: Marks unneeded packages as manually installed, if --dry-run is used
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.8 --- unattended-upgrades (0.90ubuntu0.8) xenial; urgency=medium * Do not mark packages for deletion / autoremoval if unattended-upgrades is being run in dry-run mode. (LP: #1544942) -- Brian Murray Mon, 18 Sep 2017 13:36:57 -0700 ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1544942 Title: Marks unneeded packages as manually installed, if --dry-run is used Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] Option --dry-run given, *not* performing real actions Packages that will be upgraded: marking linux-headers-4.2.0-16-generic for remove marking linux-headers-4.2.0-16 for remove marking linux-image-4.2.0-16-generic for remove marking linux-image-extra-4.2.0-16-generic for remove Packages that are auto removed: 'linux-headers-4.2.0-16-generic linux-headers-4.2.0-16 linux-image-4.2.0-16-generic linux-image-extra-4.2.0-16-generic' /usr/bin/dpkg --status-fd 9 --force-depends --force-remove-essential --remove linux-headers-4.2.0-16-generic:amd64 linux-headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux-image-4.2.0-16-generic:amd64 /usr/bin/dpkg --status-fd 11 --configure --pending Packages were successfully auto-removed InstCount=0 DelCount=4 BrokenCount=0 $ apt-mark showauto linux-headers-4.2.0-16-generic:amd64 linux- headers-4.2.0-16:all linux-image-extra-4.2.0-16-generic:amd64 linux- image-4.2.0-16-generic:amd64 $ sudo unattended-upgrade --dry-run -d Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: ['o=Ubuntu,a=wily-security'] pkgs that look like they should be upgraded: Fetched 0 B in 0s (0 B/s) fetch.run() result: 0 blacklist: [] whitelist: [] No packages found that can be upgraded unattended and no pending auto-removals Expect the packages to remain automatically installed after each `sudo unattended-upgrade --dry-run -d`. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unattended-upgrades 0.86.2ubuntu1.1 ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Feb 12 13:58:29 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-24 (18 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2016-02-12T13:53:13.426454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1544942/+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 1717946] Re: UIFe: Drop xterm and xdiagnose from default install
** Changed in: ubuntu-meta (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1717946 Title: UIFe: Drop xterm and xdiagnose from default install Status in ubuntu-meta package in Ubuntu: Fix Committed Bug description: Impact == I'm proposing to drop 3 apps from the default Ubuntu 17.10 install: XTerm UXTerm xdiagnose These are visible in the Show Applications view of the Activities Overview so this could impact screenshots. Justification = These were only in the default install because of the FailsafeX feature. Timo Aaltonen (tjaalton), maintainer of Ubuntu's X stack and co-maintainer in Debian, has said that feature isn't important any more, considering the transition to Wayland. xdiagnose also provided some apport hooks for diagnosing display problems but that was moved to xorg itself earlier this release cycle. xdiagnose currently doesn't run in the Ubuntu session on Wayland. https://irclogs.ubuntu.com/2017/09/18/%23ubuntu-desktop.html#t14:18 Discussed earlier in the cycle: https://lists.ubuntu.com/archives/ubuntu-desktop/2017-June/004980.html https://lists.ubuntu.com/archives/ubuntu-desktop/2017-July/005059.html List Notifications == https://lists.ubuntu.com/archives/ubuntu-doc/2017-September/020534.html https://lists.ubuntu.com/archives/ubuntu-translators/2017-September/007403.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1717946/+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 1697769] Re: tracker doesn't automatically start when installed until after log out and log in
** Description changed: One problem with Ubuntu not enabling tracker by default is that several apps depend on tracker for basic functionality. A user installs gnome-photos, opens the app and sees none of the pictures from her ~/Pictures/ directory. She needs to log out and then log back in for the tracker services to start running and her app to work. tracker uses systemd user services now. + Workaround + -- + Log out and log back in after installing tracker + Affected GNOME apps --- Books Documents Games Music Photos ** Bug watch added: Debian Bug tracker #865496 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865496 ** Also affects: tracker (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865496 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1697769 Title: tracker doesn't automatically start when installed until after log out and log in Status in tracker package in Ubuntu: Confirmed Status in tracker package in Debian: Unknown Bug description: One problem with Ubuntu not enabling tracker by default is that several apps depend on tracker for basic functionality. A user installs gnome-photos, opens the app and sees none of the pictures from her ~/Pictures/ directory. She needs to log out and then log back in for the tracker services to start running and her app to work. tracker uses systemd user services now. Workaround -- Log out and log back in after installing tracker Affected GNOME apps --- Books Documents Games Music Photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1697769/+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 1379536] Re: Coarse-grained kernel keyring mediation
** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** No longer affects: linux (Ubuntu) -- 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/1379536 Title: Coarse-grained kernel keyring mediation Status in AppArmor: In Progress Status in apparmor package in Ubuntu: Triaged Bug description: Tracking bug to support coarse-grained kernel keyring mediation. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1379536/+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 1719750] Re: QSystemTrayIcon creates an icon in the wrong place.
Hi! The first patch in your list is already applied in 5.2.1 and even in 5.2.0. It won’t help on Unity though, as Unity does not support legacy X11 tray since Raring. You are using Unity, right? The other three patches are from Qt 5.4 / 5.5 only and do not apply cleanly to 5.2. It is also too much code and not suitable for SRU. You can try building and installing the latest version of lp:appmenu- qt5, that might help you to get tray icons on Unity. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1719750 Title: QSystemTrayIcon creates an icon in the wrong place. Status in qtbase-opensource-src package in Ubuntu: Won't Fix Bug description: This is probably a long shot given the age, but any chance of getting the following patches backported to the Trusty build from upstream? https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1&id=d8090022f66cc6cff6af5ed2ae702212fd172ff7 https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1&id=612953a626ec21b8518ee23a4f5268b566cf41e5 https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1&id=cec103897f5109c70f2fd69460d10d21fa4feded https://code.qt.io/cgit/qt/qtbase.git/commit/?h=v5.2.1&id=38abd653774aa0b3c5cdfd9a8b78619605230726 Upstream issue: https://bugreports.qt.io/browse/QTBUG-31762 I am experiencing this with the Dash Core Wallet, built from their git tag v0.12.1.5. The tray icon is being rendered outside the tray area. Always the top-left of the left-most monitor. Ubuntu 14.04.5 (fully patched as of posting) libqt5core5a is at 5.2.1+dfsg-1ubuntu14.3, which should have these patches already being as they were merged in the 5.2 upstream series. I did not see them in the source tree here on launchpad, though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1719750/+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 1720213] [NEW] Word moving with left-arrow-ctrl broken in wayland
Public bug reported: Ubuntu 17.10, Wayland session. In the terminal, the keycombination `ctrl-left-arrow` and `ctrl-right- arrow` moves the cursor one word to the left and to the right. In Xorg this works, no matter which key you press first (ctrl or arrow). In wayland, you have to press the ctrl key first, otherwise, the cursor will not move. # How to reproduce: type some words in gnome terminal press `left-arrow` key, wait for the cursor to move and, and press `ctrl`. # What happens The cursor first moves one character per "tick", and stops immediately when you press `ctrl`. # What should happen The cursor first moves one character per "tick", and starts moving one word per "tick" when you press `ctrl`. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: artful wayland ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags added: artful ** Tags added: wayland -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1720213 Title: Word moving with left-arrow-ctrl broken in wayland Status in gnome-terminal package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Ubuntu 17.10, Wayland session. In the terminal, the keycombination `ctrl-left-arrow` and `ctrl-right- arrow` moves the cursor one word to the left and to the right. In Xorg this works, no matter which key you press first (ctrl or arrow). In wayland, you have to press the ctrl key first, otherwise, the cursor will not move. # How to reproduce: type some words in gnome terminal press `left-arrow` key, wait for the cursor to move and, and press `ctrl`. # What happens The cursor first moves one character per "tick", and stops immediately when you press `ctrl`. # What should happen The cursor first moves one character per "tick", and starts moving one word per "tick" when you press `ctrl`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720213/+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 1720116] Re: apport-gtk sigfault in libgtk-3
apport-retrace needs both: python-cffi-backend & python3-cffi-backend installed to work -- 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/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: Incomplete Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+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 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device
Hello Dan, or anyone else affected, Accepted initramfs-tools into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.103ubuntu4.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: initramfs-tools (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- 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/1718055 Title: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Fix Committed Bug description: [impact] On a trusty system, if using MODULES=dep with lvm-on-nvme then update- initramfs fails to rebuild the initramfs. This prevents using MODULES=dep for building an initramfs on trusty, with a rootfs that uses lvm on nvme. [test case] install a system where the rootfs uses a LVM logical volume that is located on a physical volume on a NVMe drive. Edit the /etc /initramfs-tools/initramfs.conf file and change the MODULES line to MODULES=dep and save the file. Then run sudo update-initramfs -u which will fail with: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1. [regression potential] This changes initramfs creation for rootfs that are on nvme or lvm, so has the potential to break it for any system with its rootfs on either or both of those. It is likely to only break initramfs creation, not system booting. [other info] related to bug 1532146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+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 1713175] Re: Obsolete backup ext2/3/4 superblocks can confuse e2fsck on an encrypted LUKS partition
My intention was to attempt to recover a filesystem. It just happened to be the wrong block device on which there was a functioning LUKS partition. Being defensive to prevent such a circumstance would call for two things: cryptsetup forcing a user to write zeros so such a situation isn't created in the future, and e2fsck checking for a LUKS partition and re-verifying the user really wants to continue despite there being a LUKS header and backup superblocks on the partition. If such checks can be added without additional dependencies, I think they just might prevent future similar mishaps. Maybe this mistake doesn't commonly happen, but this configuration of layering ext4 on LUKS is the default for most linux distributions, even for USB and external drives. In fact, e2fsck could've figured out through lsblk what I was really trying to do and corrected me. I had a relatively simple configuration. It wouldn't have been that hard to figure out what I was doing was wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1713175 Title: Obsolete backup ext2/3/4 superblocks can confuse e2fsck on an encrypted LUKS partition Status in cryptsetup package in Ubuntu: Confirmed Status in e2fsprogs package in Ubuntu: New Status in util-linux package in Ubuntu: Invalid Bug description: fsck.ext4 runs on a LUKS partition and starts to correct inode entries, rendering the partition corrupted and useless. It seems like it should defensively check where it is an isLuks partition using "cryptsetup isLuks /dev/sda1" before continuing to modify it. I hope such a defensive check can be added. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1713175/+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 1720116] Re: apport-gtk sigfault in libgtk-3
Both of these are installed python-cffi-backend is already the newest version (1.9.1-2build2). python-cffi-backend set to manually installed. python3-cffi-backend is already the newest version (1.9.1-2build2). python3-cffi-backend set to manually installed. -- 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/1720116 Title: apport-gtk sigfault in libgtk-3 Status in apport package in Ubuntu: Incomplete Bug description: Daily notification of system error and request to report it but nothing get sent. Syslog shows apport-gtk sigfault in libgtk-3. There us usually no crash dump generated. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:6940216:2017-09-22 05:36:31.895203406 -0400:2017-09-22 05:36:27.979332060 -0400:/var/crash/_usr_share_apport_apport-gtk.0.crash CurrentDesktop: GNOME-Classic:GNOME Date: Thu Sep 28 06:54:23 2017 InstallationDate: Installed on 2017-07-24 (65 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170723) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1720116/+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 1698967] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1698967 Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: Confirmed Bug description: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: bsdutils:amd64: Configure axel:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 18 17:43:58 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-15 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1698967/+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 1714705] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1714705 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: jefff@jefff-System-Product-Name:~$ sudo apt-get -f install util-linux Reading package lists... Done Building dependency tree Reading state information... Done util-linux is already the newest version (2.27.1-6ubuntu3.3). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). jefff@jefff-System-Product-Name:~$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.8.0-36 linux-headers-4.8.0-36-generic linux-headers-4.8.0-53 linux-headers-4.8.0-53-generic linux-image-4.8.0-36-generic linux-image-4.8.0-53-generic linux-image-extra-4.8.0-36-generic linux-image-extra-4.8.0-53-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: grub-common grub-pc grub-pc-bin grub2-common Suggested packages: multiboot-doc grub-emu xorriso desktop-base The following packages will be upgraded: grub-common grub-pc grub-pc-bin grub2-common 4 upgraded, 0 newly installed, 0 to remove and 221 not upgraded. 2 not fully installed or removed. Need to get 4,337 kB of archives. After this operation, 5,120 B of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 util-linux i386 2.27.1-6ubuntu3.3 [875 kB] Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-pc i386 2.02~beta2-36ubuntu3.12 [197 kB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-pc-bin i386 2.02~beta2-36ubuntu3.12 [915 kB] Get:4 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub2-common i386 2.02~beta2-36ubuntu3.12 [545 kB] Get:5 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 grub-common i386 2.02~beta2-36ubuntu3.12 [1,806 kB] Fetched 4,337 kB in 0s (6,404 kB/s) Preconfiguring packages ... dpkg: error processing package util-linux (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) jefff@jefff-System-Product-Name:~$ jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub2-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed grub-pc-bin : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 2.02~beta2-36ubuntu3.12 is to be installed grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.11) but 2.02~beta2-36ubuntu3.12 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). jefff@jefff-System-Product-Name:~$ jefff@jefff-System-Product-Name:~$ sudo apt-get -f install grub2-common Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: grub-pc : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed Depends: grub-pc-bin (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed grub2-common : Depends: grub-common (= 2.02~beta2-36ubuntu3.12) but 2.02~beta2-36ubuntu3.11 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). jefff@jefff-System-Produ
[Touch-packages] [Bug 1698967] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed')
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: dpkg (Ubuntu) Importance: Undecided => Low ** Changed in: dpkg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1698967 Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') Status in dpkg package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Confirmed Bug description: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: bsdutils:amd64: Configure axel:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 18 17:43:58 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package bsdutils is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-06-15 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package bsdutils is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1698967/+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 1720213] Re: Word moving with left-arrow-ctrl broken in wayland
Is the behavior the same in other apps, e.g. gedit, libreoffice writer, firefox, etc...? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1720213 Title: Word moving with left-arrow-ctrl broken in wayland Status in gnome-terminal package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: Ubuntu 17.10, Wayland session. In the terminal, the keycombination `ctrl-left-arrow` and `ctrl-right- arrow` moves the cursor one word to the left and to the right. In Xorg this works, no matter which key you press first (ctrl or arrow). In wayland, you have to press the ctrl key first, otherwise, the cursor will not move. # How to reproduce: type some words in gnome terminal press `left-arrow` key, wait for the cursor to move and, and press `ctrl`. # What happens The cursor first moves one character per "tick", and stops immediately when you press `ctrl`. # What should happen The cursor first moves one character per "tick", and starts moving one word per "tick" when you press `ctrl`. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1720213/+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 1718055] Re: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device
$ dpkg -l | grep initramfs-tools ii initramfs-tools 0.103ubuntu4.7 all tools for generating an initramfs ii initramfs-tools-bin 0.103ubuntu4.7 amd64binaries used by initramfs-tools $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1. after update to proposed: $ dpkg -l | grep initramfs-tools ii initramfs-tools 0.103ubuntu4.8 all tools for generating an initramfs ii initramfs-tools-bin 0.103ubuntu4.8 amd64binaries used by initramfs-tools $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic initramfs successfully built. ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- 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/1718055 Title: update-initramfs fails for MODULES=dep when root is on LVM wich uses nvme device Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Trusty: Fix Committed Bug description: [impact] On a trusty system, if using MODULES=dep with lvm-on-nvme then update- initramfs fails to rebuild the initramfs. This prevents using MODULES=dep for building an initramfs on trusty, with a rootfs that uses lvm on nvme. [test case] install a system where the rootfs uses a LVM logical volume that is located on a physical volume on a NVMe drive. Edit the /etc /initramfs-tools/initramfs.conf file and change the MODULES line to MODULES=dep and save the file. Then run sudo update-initramfs -u which will fail with: $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-3.13.0-129-generic mkinitramfs: for root /dev/dm-0 missing nvme /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for /boot/initrd.img-3.13.0-129-generic with 1. [regression potential] This changes initramfs creation for rootfs that are on nvme or lvm, so has the potential to break it for any system with its rootfs on either or both of those. It is likely to only break initramfs creation, not system booting. [other info] related to bug 1532146 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718055/+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 1720241] [NEW] package linux-image-extra-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139
Public bug reported: idk ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-extra-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adnan 1634 F pulseaudio Date: Thu Sep 28 21:40:52 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA SATELLITE C50-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=0682e23e-0102-4c73-8dff-36bb174743fe 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~beta3-4ubuntu2.2 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.30:bd03/24/2014:svnTOSHIBA:pnSATELLITEC50-A:pvrPSCJGE-001006G5:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C50-A dmi.product.version: PSCJGE-001006G5 dmi.sys.vendor: TOSHIBA ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1720241 Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 Status in initramfs-tools package in Ubuntu: New Bug description: idk ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-extra-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adnan 1634 F pulseaudio Date: Thu Sep 28 21:40:52 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA SATELLITE C50-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=0682e23e-0102-4c73-8dff-36bb174743fe 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~beta3-4ubuntu2.2 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.30:bd03/24/2014:svnTOSHIBA:pnSATELLITEC50-A:pvrPSCJGE-001006G5:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C50-A dmi.product.version: PSCJGE-001006G5 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1720241/+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 1718966] Re: Cannot install snaps on Ubuntu 14.04 with /var on its own partition
Ok so in systemd-204, in TRUSTY, you will find the following logic to create the mount units: - manager_loop - process-event (WATCH_MOUNT) - mount_fd_event - mount_load_proc_self_mountinfo - mount_add_one (if load_extras == true) - mount_add_extras - mount_add_device_links The last function will add: device/mount/socket/swap/path/requires/... dependencies in the mount unit to be created. The first one "device" is handled by "mount_add_device_links" and, according to logic: if (p->passno > 0 && UNIT(m)->manager->running_as == SYSTEMD_SYSTEM) { char *name; Unit *fsck; /* Let's add in the fsck service */ /* aka SPECIAL_FSCK_SERVICE */ name = unit_name_from_path_instance("systemd-fsck", p->what, ".service"); if (!name) return -ENOMEM; If filesystem option passno is 0, it won't have the systemd-fsck unit as a requirement, meaning that no error will be given, allowing the mount unit, created by snappy, to work. Check it out: 1) ## /etc/fstab LABEL=LVROOT / ext4 errors=remount-ro 0 1 LABEL=LVVAR /var ext4 defaults 0 1 LABEL=TESTE /teste ext4 defaults 0 1 $ sudo snap install hello-world error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-disk-by\x2dlabel-LVVAR.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-disk-by\x2dlabel-LVVAR.service' for details. 2) ## /etc/fstab LABEL=LVROOT / ext4 errors=remount-ro 0 1 LABEL=LVVAR /var ext4 defaults 0 0 LABEL=TESTE /teste ext4 defaults 0 0 $ sudo snap install hello-world hello-world 6.3 from 'canonical' installed Now I'm checking why debian/rules in systemd-204 didn't include fsck@.service files in the final .deb for "systemd" package. Possibly this wasn't noticed because at the time systemd was running in Trusty, it wasn't imagined that mount units would be managed by systemd (like snappy is doing now). I'll check if adding the units for fsck (plus having systemd-fsck binary, already there) is enough for the mount logic to work. For now, use the workaround above ^. ** Changed in: systemd (Ubuntu Trusty) Status: Confirmed => In Progress ** Changed in: snapd Status: Confirmed => In Progress -- 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/1718966 Title: Cannot install snaps on Ubuntu 14.04 with /var on its own partition Status in snapd: In Progress Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: In Progress Bug description: Installing snaps is not possible on Ubuntu 14.04 when having /var on its own partition, whether its LVM or not. The issue is with the core snap being unable to mount: The error with /var isolated and using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) The error with /var isolated but without using LVM: root@ubuntu:~# snap install canonical-livepatch error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-disk-by\x2duuid-7383abd2\x2d019c\x2d46c2\x2d8b36\x2d34633cc8f3ca.service' for details. ) The same error happens if I try to install the hello-world snap (with LVM in this example): root@ubuntu:~# snap install hello-world error: cannot perform the following tasks: - Mount snap "core" (2898) ([start snap-core-2898.mount] failed with exit status 6: Failed to issue method call: Unit systemd-fsck@dev-mapper-vg00\x2dvarvol.service failed to load: No such file or directory. See system logs and 'systemctl status systemd-fsck@dev-mapper-vg00\x2dvarvol.service' for details. ) I cannot reproduce the issue in Ubuntu 16.04. I couldn't reproduce this issue by using the Ubuntu 14.04 cloud image which doesn't isolate /var on its own partition. I tried adding a secondary disk to that cloud image VM and create a dummy VG and LV, but couldn't reproduce the issue. Also could not reproduce using Ubuntu 14.04 (with LVM or not) but with only a / partition and swap. Steps to
[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install
This bug was fixed in the package python3.5 - 3.5.3-1ubuntu0~17.04.1 --- python3.5 (3.5.3-1ubuntu0~17.04.1) zesty; urgency=medium * Explicitly use the system python for byte compilation in postinst scripts. (LP: #1682934) -- Brian Murray Thu, 14 Sep 2017 15:58:41 -0700 ** Changed in: python3.5 (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Fix Released Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Zesty: New Status in python3.5 source package in Zesty: Fix Released Status in python3.5 package in Debian: Fix Released Bug description: [Impact] An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5. [Test Case] 1) Ensure the version of python3.5 from the release pocket is installed 2) Install python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ 3) Confirm that python3.5 from /usr/local/bin/ is being used / the default 4) Upgrade to a newer version of python3.5 from -proposed Observe the following Traceback: Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: python3.5-minimal python3-minimal With the version of python3.5 from -proposed this Traceback will not be encountered. [Regression Potential] It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg. [Original Description] Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+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 1682934] Update Released
The verification of the Stable Release Update for python3.5 has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Fix Released Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Zesty: New Status in python3.5 source package in Zesty: Fix Released Status in python3.5 package in Debian: Fix Released Bug description: [Impact] An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5. [Test Case] 1) Ensure the version of python3.5 from the release pocket is installed 2) Install python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ 3) Confirm that python3.5 from /usr/local/bin/ is being used / the default 4) Upgrade to a newer version of python3.5 from -proposed Observe the following Traceback: Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: python3.5-minimal python3-minimal With the version of python3.5 from -proposed this Traceback will not be encountered. [Regression Potential] It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg. [Original Description] Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+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 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install
This bug was fixed in the package python3.5 - 3.5.2-2ubuntu0~16.04.3 --- python3.5 (3.5.2-2ubuntu0~16.04.3) xenial; urgency=medium * Explicitly use the system python for byte compilation in postinst scripts. (LP: #1682934) -- Brian Murray Thu, 14 Sep 2017 15:51:06 -0700 ** Changed in: python3.5 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python2.7 package in Ubuntu: Fix Released Status in python3.5 package in Ubuntu: Fix Released Status in python2.7 source package in Xenial: New Status in python3.5 source package in Xenial: Fix Released Status in python2.7 source package in Zesty: New Status in python3.5 source package in Zesty: Fix Released Status in python3.5 package in Debian: Fix Released Bug description: [Impact] An upgrade of python3.5 will fail if someone has installed a different version of python3.5 in their path e.g. in /usr/local/bin. This is because the postinst scripts do not specify the complete path to python3.5. [Test Case] 1) Ensure the version of python3.5 from the release pocket is installed 2) Install python3 using the instructions at https://passingcuriosity.com/2015/installing-python-from-source/ 3) Confirm that python3.5 from /usr/local/bin/ is being used / the default 4) Upgrade to a newer version of python3.5 from -proposed Observe the following Traceback: Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: python3.5-minimal python3-minimal With the version of python3.5 from -proposed this Traceback will not be encountered. [Regression Potential] It's possible I missed a postinst script so other python3.5 binary packages should be installed to ensure they are all fixed e.g. python3.5-dbg. [Original Description] Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: PackageDistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1682934/+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 1697769] Re: tracker doesn't automatically start when installed until after log out and log in
** Changed in: tracker (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1697769 Title: tracker doesn't automatically start when installed until after log out and log in Status in tracker package in Ubuntu: Confirmed Status in tracker package in Debian: New Bug description: One problem with Ubuntu not enabling tracker by default is that several apps depend on tracker for basic functionality. A user installs gnome-photos, opens the app and sees none of the pictures from her ~/Pictures/ directory. She needs to log out and then log back in for the tracker services to start running and her app to work. tracker uses systemd user services now. Workaround -- Log out and log back in after installing tracker Affected GNOME apps --- Books Documents Games Music Photos To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1697769/+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 1702078] Re: Boot to blank screen
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1702078 Title: Boot to blank screen Status in linux package in Ubuntu: Fix Released Bug description: Made the test case Install (entire disk) in Ubuntu Desktop amd64 in Artful Daily Installation went OK. At boot the grub menu is shown. After selection of Ubuntu the screen gets blank. The plymouth screen isn't shown. When I press Ctrl repeatedly the plymouth screen is shown and then the login screen. The installation is set to use the swedish keyboard, but the english keyboard is used. Except for that the installation behaves OK. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 BootLog: /dev/sdc1: clean, 153910/39075840 files, 4226467/156282624 blocks CompositorRunning: None CurrentDesktop: GNOME Date: Mon Jul 3 13:56:41 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] [1002:6739] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 6850] [174b:e174] InstallationDate: Installed on 2017-07-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170703) MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e83ef1bc-3743-4dde-a4e8-b774b544ef66 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/13/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-990FXA-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-990FXA-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Jul 3 15:28:22 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY Compaq USB Keyboard KEYBOARD, id 8 inputCHICONY Compaq USB Keyboard KEYBOARD, id 9 inputMicrosoft Corporation Microsoft ® Laser Mouse 6000 MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702078/+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 1654730] Re: Resuming from suspend, network manager can only see 1 WiFi network
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1654730 Title: Resuming from suspend, network manager can only see 1 WiFi network Status in network-manager package in Ubuntu: Confirmed Bug description: Hardware: Dell XPS15 9550 Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter Software: Ubuntu 16.04.1 LTS 4.4.0-58-generic network-manager 1.2.4-0ubuntu0.16.04.1 network-manager-gnome 1.2.0-0ubuntu0.16.04.4 02:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Flags: bus master, fast devsel, latency 0, IRQ 136 Memory at dd20 (64-bit, non-prefetchable) [size=2M] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=8/8 Maskable+ 64bit- Capabilities: [70] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [148] Virtual Channel Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00 Capabilities: [178] Latency Tolerance Reporting Capabilities: [180] L1 PM Substates Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci When resuming from suspend, network-manager only displays one random network (random/different one each time). Switching WiFi off and on does not fix it. iwlist scanning does not fix it. After running "sudo iwlist scanning", network manager works normally again immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1654730/+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 1720241] Re: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in the application being used for the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: package-install-segfault ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1720241 Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 Status in initramfs-tools package in Ubuntu: Invalid Bug description: idk ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-extra-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adnan 1634 F pulseaudio Date: Thu Sep 28 21:40:52 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 InstallationDate: Installed on 2017-09-28 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA SATELLITE C50-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=0682e23e-0102-4c73-8dff-36bb174743fe 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~beta3-4ubuntu2.2 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-35-generic 4.10.0-35.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.30 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: MP dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.30:bd03/24/2014:svnTOSHIBA:pnSATELLITEC50-A:pvrPSCJGE-001006G5:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C50-A dmi.product.version: PSCJGE-001006G5 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1720241/+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 1629102] Re: Unable to start or initialise any ceph process (ceph-mon)
[Expired for google-perftools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: google-perftools (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1629102 Title: Unable to start or initialise any ceph process (ceph-mon) Status in ceph package in Ubuntu: Invalid Status in google-perftools package in Ubuntu: Expired Status in libunwind package in Ubuntu: Expired Bug description: Latest yakkety server build, with ceph 10.2.2; creation of the ceph- mon FS hangs: ceph-mon --mkfs -i juju- 3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15 --keyring /var/lib/ceph/tmp/juju- 3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15.mon.keyring spinning in: nanosleep({0, 201}, NULL) = 0 top of backtrace: #0 0x7f5a619efd10 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:84 No locals. #1 0x7f5a624b9193 in base::internal::SpinLockDelay(int volatile*, int, int) () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #2 0x7f5a624b9026 in SpinLock::SlowLock() () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #3 0x7f5a624adb78 in tcmalloc::ThreadCache::InitModule() () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #4 0x7f5a624bbe55 in tc_malloc () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #5 0x7f5a5fc05f7d in __fopen_internal (filename=0x7f5a6291c4a0 "/usr/lib/libtcmalloc.so.4", mode=0x7f5a5f984c6a "r", is32=1) at iofopen.c:69 new_f = #6 0x7f5a5f982ab8 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #7 0x7f5a5f983624 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #8 0x7f5a5f983710 in _ULx86_64_dwarf_find_debug_frame () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #9 0x7f5a5f983cde in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #10 0x7f5a5fcdc0a4 in __GI___dl_iterate_phdr (callback=0x7f5a5f983940, data=0x7fff3a02ba90) at dl-iteratephdr.c:76 __clframe = {__cancel_routine = , __cancel_arg = 0x0, __do_it = 1, __cancel_type = } nloaded = 26 ns = caller = l = 0x7f5a6291c4c0 info = {dlpi_addr = 140026172706816, dlpi_name = 0x7f5a6291c4a0 "/usr/lib/libtcmalloc.so.4", dlpi_phdr = 0x7f5a62489040, dlpi_phnum = 8, dlpi_adds = 26, dlpi_subs = 0, dlpi_tls_modid = 2, dlpi_tls_data = 0x7f5a62906760} ret = 0 looks like initial setup of tcmalloc is spinning - I've seen the same happen on start of the ceph-mon daemon (which I thought was the original problem). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ceph-mon 10.2.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 29 20:43:51 2016 Ec2AMI: ami-045c Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small.osci Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1629102/+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 1629102] Re: Unable to start or initialise any ceph process (ceph-mon)
[Expired for libunwind (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libunwind (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunwind in Ubuntu. https://bugs.launchpad.net/bugs/1629102 Title: Unable to start or initialise any ceph process (ceph-mon) Status in ceph package in Ubuntu: Invalid Status in google-perftools package in Ubuntu: Expired Status in libunwind package in Ubuntu: Expired Bug description: Latest yakkety server build, with ceph 10.2.2; creation of the ceph- mon FS hangs: ceph-mon --mkfs -i juju- 3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15 --keyring /var/lib/ceph/tmp/juju- 3da7bf0b-0062-4a2f-8949-d85e6579b759-machine-15.mon.keyring spinning in: nanosleep({0, 201}, NULL) = 0 top of backtrace: #0 0x7f5a619efd10 in __nanosleep_nocancel () at ../sysdeps/unix/syscall-template.S:84 No locals. #1 0x7f5a624b9193 in base::internal::SpinLockDelay(int volatile*, int, int) () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #2 0x7f5a624b9026 in SpinLock::SlowLock() () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #3 0x7f5a624adb78 in tcmalloc::ThreadCache::InitModule() () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #4 0x7f5a624bbe55 in tc_malloc () from /usr/lib/libtcmalloc.so.4 No symbol table info available. #5 0x7f5a5fc05f7d in __fopen_internal (filename=0x7f5a6291c4a0 "/usr/lib/libtcmalloc.so.4", mode=0x7f5a5f984c6a "r", is32=1) at iofopen.c:69 new_f = #6 0x7f5a5f982ab8 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #7 0x7f5a5f983624 in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #8 0x7f5a5f983710 in _ULx86_64_dwarf_find_debug_frame () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #9 0x7f5a5f983cde in ?? () from /usr/lib/x86_64-linux-gnu/libunwind.so.8 No symbol table info available. #10 0x7f5a5fcdc0a4 in __GI___dl_iterate_phdr (callback=0x7f5a5f983940, data=0x7fff3a02ba90) at dl-iteratephdr.c:76 __clframe = {__cancel_routine = , __cancel_arg = 0x0, __do_it = 1, __cancel_type = } nloaded = 26 ns = caller = l = 0x7f5a6291c4c0 info = {dlpi_addr = 140026172706816, dlpi_name = 0x7f5a6291c4a0 "/usr/lib/libtcmalloc.so.4", dlpi_phdr = 0x7f5a62489040, dlpi_phnum = 8, dlpi_adds = 26, dlpi_subs = 0, dlpi_tls_modid = 2, dlpi_tls_data = 0x7f5a62906760} ret = 0 looks like initial setup of tcmalloc is spinning - I've seen the same happen on start of the ceph-mon daemon (which I thought was the original problem). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ceph-mon 10.2.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Thu Sep 29 20:43:51 2016 Ec2AMI: ami-045c Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small.osci Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: ceph UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1629102/+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 1719720] Comment bridged from LTC Bugzilla
--- Comment From hegdevas...@in.ibm.com 2017-09-29 01:44 EDT--- (In reply to comment #7) > On Thu, Sep 28, 2017 at 06:20:03AM -, bugproxy wrote: > > Yeah. even I thought its touch issue. I did look into touch source code > > as well. It uses below flag to create file. > > > O_WRONLY | O_CREAT | O_NONBLOCK | O_NOCTTY, MODE_RW_UGO); > > This is not about file creation flags, it's about memory maps. This is > likely to be either a toolchain regression, or a bug in glibc, since touch > itself should not be calling mmap() for anything that it does. Looks like this is new flag introduced recently in systemd-udevd.service script. -Vasant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1719720 Title: [LTCTest][libvpd] Process '/bin/touch /run/run.vpdupdate' failed with exit code 127 Status in The Ubuntu-power-systems project: Triaged Status in coreutils package in Ubuntu: Triaged Bug description: ---Problem Description--- Currently syslog is getting flooded with below log messages .. Sep 25 03:16:41 ubuntu1710 systemd-udevd[2654]: Process '/bin/touch /run/run.vpdd update' failed with exit code 127. This is on UBuntu 17.10 latest build.. ---uname output--- Linux ubuntu1710 4.12.0-11-generic #12-Ubuntu SMP Fri Aug 11 12:23:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = ZZ-L ---Steps to Reproduce--- I have seen these messages logged more often when we do any hotplug operations.. ex. cpu hotplug.. Ok. .this is the continuation of LTC #144627 / Launchpad #1682774. As suggested in that bug, we did change udev script to create temporary file under /run and that patch is available in ubuntu 17.10. Looks like this is udev script issue. If I modify systemd-udevd like below it works fine. I've limited udev knowledge. I don't know if you have any other better solution to this issue. root@ltc-boston123:/lib/systemd/system# diff -Naurp systemd-udevd.service.org systemd-udevd.service --- systemd-udevd.service.org 2017-09-26 04:37:47.090057318 -0500 +++ systemd-udevd.service 2017-09-26 04:37:55.381739372 -0500 @@ -25,7 +25,7 @@ KillMode=mixed WatchdogSec=3min TasksMax=infinity MountFlags=slave -MemoryDenyWriteExecute=yes +#MemoryDenyWriteExecute=yes RestrictRealtime=yes RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 SystemCallArchitectures=native -Vasant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1719720/+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 1720300] [NEW] List items become invisible when selected in g-c-c
Public bug reported: Steps: 1. Open gnome-control-center 2. Select the Search panel 3. Select any of the items in the list 4. They become invisible when selected They should be visibly selected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170925-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 08:17:05 2017 InstallationDate: Installed on 2017-09-21 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1720300 Title: List items become invisible when selected in g-c-c Status in gnome-control-center package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Steps: 1. Open gnome-control-center 2. Select the Search panel 3. Select any of the items in the list 4. They become invisible when selected They should be visibly selected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170925-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 08:17:05 2017 InstallationDate: Installed on 2017-09-21 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1720300/+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