[Touch-packages] [Bug 1553150] Re: Ubuntu One account does not stay logged in or does not sign in at all
This problem has hit me in the last two weeks (Meizu MX4), and I can't install *any* upgrades. HELP! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1553150 Title: Ubuntu One account does not stay logged in or does not sign in at all Status in ubuntuone-credentials package in Ubuntu: Confirmed Bug description: I looked up for updates this morning, but after finding an update for the Clock app, appeared the message: "Sign in to Ubuntu One to receive updates for apps." And below a button to sign in. I found it strange because I never seen this message when updating before, but the real problem is that even if I push the button and sign in, nothing changes and I can't update, same message there. I also added my Ubuntu One account to the account section of the System Settings panel, but again nothing changes, and when checking the account it had disappeared. Seems that it can't stay logged in to the Ubuntu One account or sign in at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1553150/+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 1639853] Re: Unity8 crash while locking/unlocking with HDMI plugged
@vanvug, I'll reproduce it again later today and update the bug with new logs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639853 Title: Unity8 crash while locking/unlocking with HDMI plugged Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Environment: current build number: 76 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-07 08:03:44 version version: 76 version ubuntu: 20161105 version device: 20161014.0 version custom: 20161105 Steps to reproduce: 1º Connect hdmi 2º Lock/unlock device several times Current result: locking/unlocking device causes greeter to misbehave and finally the ubuntu boot logo appears. Attached some logs and crash files, hope it helps Expected result: unity8 should not crash Add info: time stamp 16:07 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639853/+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 1639249] Re: Result art not displayed when run in a snap
** Changed in: unity-scopes-api (Ubuntu) Assignee: (unassigned) => Paweł Stołowski (stolowski) ** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-api package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1639249/+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 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation
Calin: This sounds like something entirely unrelated. Can you please file a new bug? -- 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/1624071 Title: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Bug description: The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the hosts line of /etc/nsswitch.conf. This makes DNSSEC validation impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because if libnss_resolve returns a validation failure, glibc will simply fall back to libnss_dns. It also makes NXDOMAIN lookups twice as slow. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624071/+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 1639745] Re: Mir GL clients never appear at all on VirtualBox
** Changed in: mir Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639745 Title: Mir GL clients never appear at all on VirtualBox Status in Mir: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Mir GL clients never appear at all on VirtualBox. After digging for a while, it appears the issue is that vboxvideo does not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly Mir is the opposite now: Mir only supports PRIME but not flink names. Internally some exceptions are being thrown in Mir at present, but we seem to catch and silence them all. So you never see any error messages at all. Just Mir GL clients never appear on screen in VirtualBox. For the record, Wayland supports falling back to flink names in the absence of PRIME. We should too. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1639745/+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 1639759] Re: dhclient does not work on eth1 (xenial)
Looking through the other bugs, this might be a duplicate bug of #1606051 ** Description changed: When running dhclient on eth1 on a server with 2 Ethernet interfaces, I get no ip address, when i run ubuntu xenial. The problem is not there with ubuntu trusty, and is also not there on servers with only 1 Ethernet interface. I have debugged with tshark on the client, and looking at syslog on the server, and the DHCPDISCOVER is sent, and the server responds with a DHCPOFFER, and that can be seen on the interface of the client, but the software seems to ignore it. - The software version is 4.3.3-5ubuntu12.3 for both isc-dhsp-client and + The software version is 4.3.3-5ubuntu12.3 for both isc-dhcp-client and isc-dhcp-common. The client is a Cisco UCSB-B200-M4 if that makes a difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1639759 Title: dhclient does not work on eth1 (xenial) Status in isc-dhcp package in Ubuntu: New Bug description: When running dhclient on eth1 on a server with 2 Ethernet interfaces, I get no ip address, when i run ubuntu xenial. The problem is not there with ubuntu trusty, and is also not there on servers with only 1 Ethernet interface. I have debugged with tshark on the client, and looking at syslog on the server, and the DHCPDISCOVER is sent, and the server responds with a DHCPOFFER, and that can be seen on the interface of the client, but the software seems to ignore it. The software version is 4.3.3-5ubuntu12.3 for both isc-dhcp-client and isc-dhcp-common. The client is a Cisco UCSB-B200-M4 if that makes a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1639759/+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 1639745] Re: Mir GL clients never appear at all on VirtualBox
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639745 Title: Mir GL clients never appear at all on VirtualBox Status in Mir: New Status in mesa package in Ubuntu: Confirmed Bug description: Mir GL clients never appear at all on VirtualBox. After digging for a while, it appears the issue is that vboxvideo does not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly Mir is the opposite now: Mir only supports PRIME but not flink names. Internally some exceptions are being thrown in Mir at present, but we seem to catch and silence them all. So you never see any error messages at all. Just Mir GL clients never appear on screen in VirtualBox. For the record, Wayland supports falling back to flink names in the absence of PRIME. We should too. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1639745/+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 1393578] Re: Subpixel order not included in Mir display information
Optionally we may also want the subpixel order information delivered in MirSurfaceOutputEvent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: In Progress Status in QtMir: Triaged Status in qtubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+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 1393578] Re: Subpixel order not included in Mir display information
Not quite done - needs plumbing through nested platform, which needs nested platform migration onto non-deprecated display configuration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: In Progress Status in QtMir: Triaged Status in qtubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+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 1508407] Re: libre office impress display broken gradient in slide show
I have this bug after upgrading to yakkety -- 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/1508407 Title: libre office impress display broken gradient in slide show Status in xorg package in Ubuntu: New Bug description: While testing ubuntu gnome iso: 20151020, I have this issue: Libre office impress display broken gradient in slide show mode. When editing gradient displayed normally. attached screen shot i'm using Intel VGA ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: libreoffice-impress 1:5.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CurrentDesktop: GNOME Date: Wed Oct 21 10:27:37 2015 LiveMediaBuild: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151019) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5021] Subsystem: Lenovo Device [17aa:5021] LiveMediaBuild: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20DCA02WIA Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/iso/username-15.10-desktop-amd64.iso locale=en_US.UTF-8 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Tags: wily ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: J5ET46WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20DCA02WIA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJ5ET46WW(1.17):bd07/15/2015:svnLENOVO:pn20DCA02WIA:pvrThinkPadE450:rvnLENOVO:rn20DCA02WIA:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20DCA02WIA dmi.product.version: ThinkPad E450 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Oct 26 03:07:28 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1530 vendor BOE xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1508407/+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 1624071] Re: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation
Glad to see this has been reported. On my system, I can no longer get to any local nodes by referring to the hostname, so it is pretty clear that hostname resolution is not working. I was able to circumvent the behavior for only 1 Linux machine by specifying nodename.local, but that doesn't work with my NAS device. So, I'm kinda stuck... I think this package is currently in yakkety-proposed (sorry, I still haven't learned how to be able to tell where a "fix" was released and in what repository it is currently in). Any idea when this will be released to yakkety-updates ? -- 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/1624071 Title: libnss-resolve: Fallback from resolve to dns breaks DNSSEC validation Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Bug description: The libnss-resolve postinst script inserts ‘resolve’ before ‘dns’ in the hosts line of /etc/nsswitch.conf. This makes DNSSEC validation impossible, even with DNSSEC=yes in /etc/systemd/resolved.conf, because if libnss_resolve returns a validation failure, glibc will simply fall back to libnss_dns. It also makes NXDOMAIN lookups twice as slow. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624071/+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 1640001] [NEW] package libpam-modules 1.1.8-1ubuntu2.2 failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied
Public bug reported: Running `do-release-upgrade` on ubuntu for windows died half way through. This automatic bug report was created ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-modules 1.1.8-1ubuntu2.2 Uname: Linux 3.4.0+ x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Nov 8 16:01:32 2016 Dmesg: DpkgTerminalLog: Preparing to unpack .../libpam-modules_1.1.8-3.2ubuntu2_amd64.deb ... Unpacking libpam-modules:amd64 (1.1.8-3.2ubuntu2) over (1.1.8-1ubuntu2.2) ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.1.8-3.2ubuntu2_amd64.deb (--unpack): unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied DuplicateSignature: package:libpam-modules:1.1.8-1ubuntu2.2:unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied ErrorMessage: unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: pam Title: package libpam-modules 1.1.8-1ubuntu2.2 failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied UpgradeStatus: Upgraded to xenial on 2016-11-08 (0 days ago) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages uec-images xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1640001 Title: package libpam-modules 1.1.8-1ubuntu2.2 failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied Status in pam package in Ubuntu: New Bug description: Running `do-release-upgrade` on ubuntu for windows died half way through. This automatic bug report was created ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpam-modules 1.1.8-1ubuntu2.2 Uname: Linux 3.4.0+ x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Nov 8 16:01:32 2016 Dmesg: DpkgTerminalLog: Preparing to unpack .../libpam-modules_1.1.8-3.2ubuntu2_amd64.deb ... Unpacking libpam-modules:amd64 (1.1.8-3.2ubuntu2) over (1.1.8-1ubuntu2.2) ... dpkg: error processing archive /var/cache/apt/archives/libpam-modules_1.1.8-3.2ubuntu2_amd64.deb (--unpack): unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied DuplicateSignature: package:libpam-modules:1.1.8-1ubuntu2.2:unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied ErrorMessage: unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: pam Title: package libpam-modules 1.1.8-1ubuntu2.2 failed to install/upgrade: unable to open '/lib/x86_64-linux-gnu/security/pam_unix.so.dpkg-new': Permission denied UpgradeStatus: Upgraded to xenial on 2016-11-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1640001/+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 1639745] Re: Mir GL clients never appear at all on VirtualBox
** Tags added: black-screen -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639745 Title: Mir GL clients never appear at all on VirtualBox Status in Mir: New Status in mesa package in Ubuntu: New Bug description: Mir GL clients never appear at all on VirtualBox. After digging for a while, it appears the issue is that vboxvideo does not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly Mir is the opposite now: Mir only supports PRIME but not flink names. Internally some exceptions are being thrown in Mir at present, but we seem to catch and silence them all. So you never see any error messages at all. Just Mir GL clients never appear on screen in VirtualBox. For the record, Wayland supports falling back to flink names in the absence of PRIME. We should too. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1639745/+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 1639314] Re: webbrowser app crashes saving an image in Xenial
** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1639314 Title: webbrowser app crashes saving an image in Xenial Status in webbrowser-app package in Ubuntu: New Bug description: Test case. - Open webbrowser app - Go to http://apod.nasa.gov/ - Long tap on the image. - Tap to save the image. Expected result. - Image can be saved locally. Actual result. - Webbrowser app freezes and crashes. current build number: 75 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu I see no webbrowser-app crash files in /var/crash. In the logs I see this (not sure whether it's related): libpng error: Read Error propsReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.1498\" (uid=32011 pid=6867 comm=\"webbrowser-app \") interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=953 comm=\"/usr/sbin/NetworkManager --no-daemon \")" nmReply "An AppArmor policy prevents this sender from sending this message to this recipient; type=\"method_call\", sender=\":1.1498\" (uid=32011 pid=6867 comm=\"webbrowser-app \") interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\" error name=\"(unset)\" requested_reply=\"0\" destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=953 comm=\"/usr/sbin/NetworkManager --no-daemon \")" "Object path cannot be empty" [1104/161741:ERROR:object_proxy.cc(583)] Failed to call method: org.freedesktop.ScreenSaver.Inhibit: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.AccessDenied: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.7787" (uid=32011 pid=6867 comm="webbrowser-app ") interface="org.freedesktop.ScreenSaver" member="Inhibit" error name="(unset)" requested_reply="0" destination="org.freedesktop.ScreenSaver" (uid=32011 pid=2691 comm="unity8 --mode=full-greeter ") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1639314/+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 1639853] Re: Unity8 crash while locking/unlocking with HDMI plugged
The crash was a fatal error from QtMir, but I can't find the corresponding message in unity8.log... (?) Stacktrace: #0 0x007f9db46528 in raise () from /lib/aarch64-linux-gnu/libc.so.6 No symbol table info available. #1 0x007f9db479e0 in abort () from /lib/aarch64-linux-gnu/libc.so.6 No symbol table info available. #2 0x007f9dea18cc in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5 No symbol table info available. #3 0x007f98b70c0c in QMirServer::start() () from /usr/lib/aarch64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so No symbol table info available. #4 0x007f98b8a294 in MirServerIntegration::initialize() () from /usr/lib/aarch64-linux-gnu/qt5/plugins/platforms/libqpa-mirserver.so No symbol table info available. #5 0x007f9e88a6dc in QGuiApplicationPrivate::eventDispatcherReady() () from /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5 No symbol table info available. #6 0x007f9e08e7ac in QCoreApplicationPrivate::init() () from /usr/lib/aarch64-linux-gnu/libQt5Core.so.5 No symbol table info available. #7 0x007f9e88c1c8 in QGuiApplicationPrivate::init() () from /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5 No symbol table info available. #8 0x007f9e88ce54 in QGuiApplication::QGuiApplication(int&, char**, int) () from /usr/lib/aarch64-linux-gnu/libQt5Gui.so.5 No symbol table info available. #9 0x0040a158 in ?? () No symbol table info available. #10 0x00406a7c in ?? () No symbol table info available. #11 0x007f9db348a0 in __libc_start_main () from /lib/aarch64-linux-gnu/libc.so.6 No symbol table info available. #12 0x00406be0 in _start () No symbol table info available. ** Summary changed: - Unity8 crash while locking/unlocking with hdmi plugged + Unity8 crash while locking/unlocking with HDMI plugged ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: qtmir (Ubuntu) Status: New => Confirmed ** Tags added: android multimonitor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639853 Title: Unity8 crash while locking/unlocking with HDMI plugged Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Environment: current build number: 76 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-07 08:03:44 version version: 76 version ubuntu: 20161105 version device: 20161014.0 version custom: 20161105 Steps to reproduce: 1º Connect hdmi 2º Lock/unlock device several times Current result: locking/unlocking device causes greeter to misbehave and finally the ubuntu boot logo appears. Attached some logs and crash files, hope it helps Expected result: unity8 should not crash Add info: time stamp 16:07 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639853/+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 1626435] Re: Keyboard layout not applied on the shell
** No longer affects: mir/0.25 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1626435 Title: Keyboard layout not applied on the shell Status in Canonical System Image: In Progress Status in Mir: Fix Committed Status in Mir 0.24 series: Fix Released Status in mir package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Split out from bug #1611859: Steps: * connect a BT or a physical keyboard * wipe or remove ~/.config/ubuntu-system-settings/wizard-has-run* and reboot * go through the wizard Expected: * I can use the selected layout in the wizard * and in snap decisions Current: * you can only use us layout in the shell ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.14+16.04.20160914-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-landing-078] ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 22 10:07:47 2016 InstallationDate: Installed on 2016-05-06 (138 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626435/+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 1639745] Re: Mir GL clients never appear at all on VirtualBox
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags added: egl-platform-mir ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Changed in: mir Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639745 Title: Mir GL clients never appear at all on VirtualBox Status in Mir: New Status in mesa package in Ubuntu: New Bug description: Mir GL clients never appear at all on VirtualBox. After digging for a while, it appears the issue is that vboxvideo does not support DRM_CAP_PRIME and so only supports GEM flink names. Sadly Mir is the opposite now: Mir only supports PRIME but not flink names. Internally some exceptions are being thrown in Mir at present, but we seem to catch and silence them all. So you never see any error messages at all. Just Mir GL clients never appear on screen in VirtualBox. For the record, Wayland supports falling back to flink names in the absence of PRIME. We should too. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1639745/+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 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content
This bug was fixed in the package unattended-upgrades - 0.92ubuntu3 --- unattended-upgrades (0.92ubuntu3) zesty; urgency=medium * Create the directory /var/lib/apt/periodic/, if it does not exist, so that we don't receive a Traceback when trying to write a stampfile there. (LP: #1639977) -- Brian Murray Mon, 07 Nov 2016 16:07:36 -0800 ** Changed in: unattended-upgrades (Ubuntu Zesty) Status: In Progress => 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/1590321 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Yakkety: In Progress Status in unattended-upgrades source package in Zesty: Fix Released Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo /usr/bin/unattended-upgrades (to update the system) 4) sudo /usr/bin/unattended-upgrades (a second time for some reason) 5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 6) sudo /usr/bin/unattended-upgrades Observe the following crash: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1406, in main log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content with io.open(logfile_dpkg, encoding='utf-8') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' With the version of the package from -proposed you won't receive the crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades- dpkg.log will exist. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1590321/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
** Also affects: unattended-upgrades (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Triaged ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: New => Triaged ** Changed in: unattended-upgrades (Ubuntu Xenial) Importance: Undecided => High ** Changed in: unattended-upgrades (Ubuntu Yakkety) Importance: Undecided => High -- 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/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1419, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. Regression Potential This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
This bug was fixed in the package unattended-upgrades - 0.92ubuntu3 --- unattended-upgrades (0.92ubuntu3) zesty; urgency=medium * Create the directory /var/lib/apt/periodic/, if it does not exist, so that we don't receive a Traceback when trying to write a stampfile there. (LP: #1639977) -- Brian Murray Mon, 07 Nov 2016 16:07:36 -0800 ** Changed in: unattended-upgrades (Ubuntu) Status: New => 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/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1419, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. Regression Potential This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1639926] Re: Update to 3.22.2
This bug was fixed in the package evolution-data-server - 3.22.2-1ubuntu1 --- evolution-data-server (3.22.2-1ubuntu1) zesty; urgency=medium * Merge with Debian (LP: #1639926). Remaining Ubuntu changes: - debian/control: + Build-depend on libaccounts-glib-dev and libsignon-glib-dev - debian/rules: + Enable Ubuntu online accounts - debian/control, debian/evolution-data-server.install: debian/evolution-data-server-online-accounts.install: + Split online accounts support into a separate package evolution-data-server (3.22.2-1) unstable; urgency=medium * New upstream release. evolution-data-server (3.22.1-2) unstable; urgency=medium * Add a Build-Depends-Package line to all symbols files to get proper dependencies when a package build-depends on a higher version of a dev package than what it gets from the used symbols. * Remove a few obsolete Breaks. -- Jeremy Bicha Mon, 07 Nov 2016 15:10:38 -0500 ** Changed in: evolution-data-server (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1639926 Title: Update to 3.22.2 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Yakkety: New Bug description: Impact == https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22 Test Case = Regression Potential To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+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 1629552] Re: files with the same name installed in / and /usr
This bug was fixed in the package json-c - 0.12.1-1ubuntu1 --- json-c (0.12.1-1ubuntu1) zesty; urgency=medium * debian/libjson-c-dev.links: Fix library symlinks to not collide between /lib/ and /usr/lib/. (Closes: #843145, LP: #1629552) -- Martin Pitt Mon, 07 Nov 2016 23:18:06 +0100 ** Changed in: json-c (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1629552 Title: files with the same name installed in / and /usr Status in cgroup-lite package in Ubuntu: Fix Released Status in genwqe package in Ubuntu: Invalid Status in grub package in Ubuntu: Invalid Status in json-c package in Ubuntu: Fix Released Status in json-c package in Debian: New Bug description: A few remaining packages in Ubuntu are incompatible with a merged /usr because they ship the same file in /bin and /usr/bin; it looks like Debian will soon default to that, and we surely want to follow suit. The duplicate file/symlink needs to be removed, or created in postinst. https://bugs.debian.org/cgi- bin/pkgreport.cgi?tag=usrmerge;users=m...@linux.it cgroup-lite: lrwxrwxrwx root/root 0 2016-03-02 07:56 ./usr/bin/cgroups-umount -> /bin/cgroups-umount lrwxrwxrwx root/root 0 2016-03-02 07:56 ./usr/bin/cgroups-mount -> /bin/cgroups-mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1629552/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
The attachment "Updated patch including the crash fix" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: dnsmasq fails to send queries out after suspend disconnects the interface Status in dnsmasq package in Ubuntu: New Bug description: Failure is caused by ENODEV return for all dns queries like: sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device) Problem is reported and fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b I didn't yet test if applying that patch to ubuntu package works. I will try the patch in a few hours. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq-base 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 7 14:11:51 2016 InstallationDate: Installed on 2037-12-25 (-7718 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
** Description changed: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1468, in - main(options) - File "/usr/bin/unattended-upgrade", line 1419, in main - write_stamp_file() - File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file - with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): + File "/usr/bin/unattended-upgrade", line 1468, in + main(options) + File "/usr/bin/unattended-upgrade", line 1419, in main + write_stamp_file() + File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file + with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. + Regression Potential + + This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. -- 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/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: New Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1419, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. Regression Potential This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1637387] Re: Online accounts and snap login integration
** Changed in: unity-scope-snappy (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 ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1637387 Title: Online accounts and snap login integration Status in ubuntuone-credentials package in Ubuntu: Fix Released Status in unity-scope-snappy package in Ubuntu: Fix Released Bug description: Currently, one has to log in manually via "snap login" from the terminal in order to install snaps. We need this login to be integrated into online accounts such that logging into your ubuntu one account authenticates you with snapd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1637387/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
** Description changed: + Test Case + - + 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 + 2) sudo apt-get update + 3) sudo rm -fr /var/lib/apt/periodic + 4) sudo /usr/bin/unattended-upgrade + 5) observe the following Traceback + + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 1468, in + main(options) + File "/usr/bin/unattended-upgrade", line 1419, in main + write_stamp_file() + File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file + with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): + FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' + + With the version of the package from -proposed you'll receive no such + Traceback. + + + Original description + The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. -- 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/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: New Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo rm -fr /var/lib/apt/periodic 4) sudo /usr/bin/unattended-upgrade 5) observe the following Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1419, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' With the version of the package from -proposed you'll receive no such Traceback. Regression Potential This patch just ends up creating a directory if it does not exist. Potential regressions would be a result of the patch being typo'ed e.g. typo'ing os.path.exits instead of os.path.exists and the code failing when a statedir does exist. So read the patch carefully! Original description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1639977] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
Here's the Traceback: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1331, in main write_stamp_file() File "/usr/bin/unattended-upgrade", line 1011, in write_stamp_file with open(os.path.join(statedir, "unattended-upgrades-stamp"), "w"): FileNotFoundError: [Errno 2] No such file or directory: '/var/lib/apt/periodic/unattended-upgrades-stamp' -- 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/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1639977] [NEW] /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:write_stamp_file
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- 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/1639977 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:write_stamp_file Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.90ubuntu0.1, the problem page at https://errors.ubuntu.com/problem/4f4644d58ccc3231b270311abe8fec67b6c7ca36 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639977/+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 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
It appears there is a crash bug in the patch which needs a minor change: http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=16800ea072dd0cdf14d951c4bb8d2808b3dfe53d ** Patch added: "Updated patch including the crash fix" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4774168/+files/rebind-after-suspend.diff ** Patch removed: "Linked fix refreshed with quilt to apply cleanly" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4774167/+files/rebind-after-suspend.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: dnsmasq fails to send queries out after suspend disconnects the interface Status in dnsmasq package in Ubuntu: New Bug description: Failure is caused by ENODEV return for all dns queries like: sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device) Problem is reported and fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b I didn't yet test if applying that patch to ubuntu package works. I will try the patch in a few hours. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq-base 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 7 14:11:51 2016 InstallationDate: Installed on 2037-12-25 (-7718 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content
** Description changed: - The Ubuntu Error Tracker has been receiving reports about a problem - regarding unattended-upgrades. This problem was most recently seen with - version 0.90, the problem page at - https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a - contains more details. + Test Case + - + 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 + 2) sudo apt-get update + 3) sudo /usr/bin/unattended-upgrades (to update the system) + 4) sudo /usr/bin/unattended-upgrades (a second time for some reason) + 5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log + 6) sudo /usr/bin/unattended-upgrades + + Observe the following crash: + + Traceback (most recent call last): + File "/usr/bin/unattended-upgrade", line 1468, in + main(options) + File "/usr/bin/unattended-upgrade", line 1406, in main + log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) + File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content + with io.open(logfile_dpkg, encoding='utf-8') as fp: + FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' + + With the version of the package from -proposed you won't receive the + crash in step 6. + + Original Description + + The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. ** Description changed: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo /usr/bin/unattended-upgrades (to update the system) 4) sudo /usr/bin/unattended-upgrades (a second time for some reason) 5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 6) sudo /usr/bin/unattended-upgrades Observe the following crash: Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1468, in - main(options) - File "/usr/bin/unattended-upgrade", line 1406, in main - log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) - File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content - with io.open(logfile_dpkg, encoding='utf-8') as fp: + File "/usr/bin/unattended-upgrade", line 1468, in + main(options) + File "/usr/bin/unattended-upgrade", line 1406, in main + log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) + File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content + with io.open(logfile_dpkg, encoding='utf-8') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' With the version of the package from -proposed you won't receive the - crash in step 6. + crash in step 6 and /var/log/unattended-upgrades/unattended-upgrades- + dpkg.log will exist. Original Description The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. -- 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/1590321 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Yakkety: In Progress Status in unattended-upgrades source package in Zesty: In Progress Bug description: Test Case - 1) edit /etc/apt/apt.conf.d/20auto-upgrades so that Update-Package-Lists is 1 and Unattended-Upgrade is 1 2) sudo apt-get update 3) sudo /usr/bin/unattended-upgrades (to update the system) 4) sudo /usr/bin/unattended-upgrades (a second time for some reason) 5) sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 6) sudo /usr/bin/unattended-upgrades Observe the following crash: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1406, in main log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content with io.open(logfile_dpkg, encoding='utf-8') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended
[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
I tested the linked patch. DNS queries work now after suspend and resume. ** Patch added: "Linked fix refreshed with quilt to apply cleanly" https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+attachment/4774167/+files/rebind-after-suspend.diff ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: dnsmasq fails to send queries out after suspend disconnects the interface Status in dnsmasq package in Ubuntu: New Bug description: Failure is caused by ENODEV return for all dns queries like: sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device) Problem is reported and fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b I didn't yet test if applying that patch to ubuntu package works. I will try the patch in a few hours. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq-base 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 7 14:11:51 2016 InstallationDate: Installed on 2037-12-25 (-7718 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1595715] Re: Tab behavior is broken
This bug was fixed in the package ubuntuone-credentials - 15.11+17.04.20161107 --- ubuntuone-credentials (15.11+17.04.20161107) zesty; urgency=medium * Use snapd-glib to log in with snapd. (LP: #1637387) * Don't do manual tab key handling in the UI. (LP: #1595715) -- Rodney Dawes Mon, 07 Nov 2016 13:48:41 + ** Changed in: ubuntuone-credentials (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 ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1595715 Title: Tab behavior is broken Status in ubuntuone-credentials package in Ubuntu: Fix Released Bug description: On my M10 with OTA-11 with a keyboard connected, I was not able to tab between fields. This was a minor annoyance as I had to tap the field on the screen to get to the next step. I would expect tab and shift+tab to work as they normally do, taking me back and forth between available fields. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1595715/+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 1637387] Re: Online accounts and snap login integration
This bug was fixed in the package ubuntuone-credentials - 15.11+17.04.20161107 --- ubuntuone-credentials (15.11+17.04.20161107) zesty; urgency=medium * Use snapd-glib to log in with snapd. (LP: #1637387) * Don't do manual tab key handling in the UI. (LP: #1595715) -- Rodney Dawes Mon, 07 Nov 2016 13:48:41 + ** Changed in: ubuntuone-credentials (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 ubuntuone-credentials in Ubuntu. https://bugs.launchpad.net/bugs/1637387 Title: Online accounts and snap login integration Status in ubuntuone-credentials package in Ubuntu: Fix Released Status in unity-scope-snappy package in Ubuntu: In Progress Bug description: Currently, one has to log in manually via "snap login" from the terminal in order to install snaps. We need this login to be integrated into online accounts such that logging into your ubuntu one account authenticates you with snapd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-credentials/+bug/1637387/+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 1639654] Re: Ubuntu version on login screen says 16.10 not 17.04
Fixed in trunk, will be released soon. ** Changed in: lightdm (Ubuntu) Status: New => Fix Committed ** Changed in: lightdm (Ubuntu) Importance: Undecided => Medium ** Package changed: lightdm (Ubuntu) => unity-greeter (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1639654 Title: Ubuntu version on login screen says 16.10 not 17.04 Status in unity-greeter package in Ubuntu: Fix Committed Bug description: The version number in the bottom-left of the LightDM login screen should read 17.04 but it actually reads 16.10. Computer info: VirtualBox Graphical User Interface Version 5.1.6_Ubuntu r110634 (I don't have access to spare hardware to test on at the moment) Allocated 2GB RAM Host OS: Ubuntu 16.10 64-bit Lenovo ThinkPad X201 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 6 23:31:40 2016 InstallationDate: Installed on 2016-10-10 (27 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2016-11-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1639654/+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 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content
** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: unattended-upgrades (Ubuntu Yakkety) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: unattended-upgrades (Ubuntu Zesty) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu Zesty) Status: New => In Progress -- 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/1590321 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Yakkety: In Progress Status in unattended-upgrades source package in Zesty: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1590321/+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 1629598] Re: Apps failing to load on M10 (OTA13)
Hi FionaC, do you know if the SD card has an issue or is this card working in other devices. When it is only an issue with the M10 can you provide technical data of the SD Card? Thanks, Torsten ** Changed in: ubuntu-docviewer-app Status: New => Invalid ** Changed in: music-app Status: New => Invalid ** Changed in: camera-app (Ubuntu) Status: New => Invalid ** Changed in: gallery-app (Ubuntu) Status: New => Invalid ** Changed in: canonical-devices-system-image Status: New => Incomplete ** Summary changed: - Apps failing to load on M10 (OTA13) + Apps failing to load on M10 (OTA13) by using a SD card -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1629598 Title: Apps failing to load on M10 (OTA13) by using a SD card Status in Canonical System Image: Incomplete Status in Ubuntu Music App: Invalid Status in Ubuntu Document Viewer App: Invalid Status in camera-app package in Ubuntu: Invalid Status in gallery-app package in Ubuntu: Invalid Bug description: Over the last few months, apps have started failing to start on my M10. Apps affected currently: - camera (stops at 'Loading...' screen), - gallery (stops at 'Gallery' splash screen), - document viewer (stops with white screen and 'Documents' header) I have had issues with Telegram too, which now just goes to a white screen, but that may stem from setup problems I have with the app on my M10 and E4.5 (see https://bugs.launchpad.net/unity-webapps- telegram/+bug/1626728) I had hoped OTA13 would fix it, but sadly not. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629598/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
@cpollock, I don't know your situation specifically so I would be speculating at best. But, if I were in your position I might do the following (but only do these steps at your own risk and have backups of your data elsewhere): 1. delete any and all listed printers in your printer manager. 2. purge the foo2zjs drivers (I'm not familiar with the "correct" way of doing this so ask someone else.) 3. ensure hplip is fully-purged from your system by doing something like a "sudo apt purge hplip hplip-data" 4. now, install hplip and use hp's own drivers as explained in #22. Something curious from your log: hpmud is a component of hplip so perhaps it was installed at one time and wasn't properly purged before you installed the foo2zjs drivers and now colord is complaining that it can't see your 1020's color profile because foo2zjs isn't allowing it (pure speculation again.) 5. If those steps don't solve it, then perhaps purging and re-installing cups and then re-doing the steps over again might. Good luck. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1638492] Re: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- 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/1638492 Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 2 09:21:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-07-29 (95 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-09-14T10:24:20.453516 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1638492/+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 1639815] Re: apt list output format
Reinforcing point 2: on my system (fairly default 16.10 install), running 'apt list firefox*' to see the available locales fails due to bash interference when there is e.g. a file called firefox.txt in this directory. -- 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/1639815 Title: apt list output format Status in apt package in Ubuntu: New Bug description: I'm trying to get used to the new 'apt' utility and have three wishlist items (don't want to clutter the tracker with multiple feature requests) in descending priority: 1. apt list firefox In the output, can we please have a space after the package name, before the slash? A very convenient feature of apt-cache/aptitude is to search for a package, then double click + middle click the name of a result to speedily select it and paste it into the current prompt (which is prepared with e.g. an install, show or depends command). 'apt list' appends '/repo,XXX' (where XXX is most often garbage... ehm, I mean strings like 'now' or again 'other_repo,now') right after the package name, which makes the double click select more than just a package name. E.g. 'apt policy firefox/yakkety-updates' fails. This would also be more convenient for awk scripts (despite the stable interface warning). 2. apt list fox Can we please have substring matching by default (or a storable user pref) for 'apt list'? 'apt search' is _way_ too noisy (the three line output per package instead of one line is just clutter). But 'apt list' doesn't match like 'apt-cache search' (or aptitude). The alternative is defaulting to 'apt l **' and then filling in between the asterisks, or resorting to 'apt l|grep' as standard 'apt-cache search' replacement. I don't see the justification for the current exact searching in only the package names. And there's still 'apt search' for searching the description. 3. apt sh A minor complaint: all current apt commands complete once they are tabbed when their string becomes unique, and append a space. Only 'apt show' in 16.10 (as opposed to 16.04) does not due to the undocumented showsrc command. This often leads to 'apt showfirefox' after writing 'apt shfirefox', because it's inconsistent with the other commands. So, find another name for showsrc? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1639815/+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 1590321] Re: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1468:main:get_dpkg_log_content
I was able to recreate this by performing the following: bdmurray@clean-xenial-amd64:~$ sudo rm /var/log/unattended-upgrades/unattended-upgrades-dpkg.log rm: cannot remove '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log': No such file or directory bdmurray@clean-xenial-amd64:~$ sudo /usr/bin/unattended-upgrade Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1468, in main(options) File "/usr/bin/unattended-upgrade", line 1406, in main log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) File "/usr/bin/unattended-upgrade", line 1075, in get_dpkg_log_content with io.open(logfile_dpkg, encoding='utf-8') as fp: FileNotFoundError: [Errno 2] No such file or directory: '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' I did this after installing all updates and enabling options in /etc/apt/apt.conf.d/20auto-upgrades. -- 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/1590321 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1468:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with version 0.90, the problem page at https://errors.ubuntu.com/problem/db5f0a803afdf5bb5e20a42ce68f4fda3ce0df8a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1590321/+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 1639558] Re: regression-update from #1624641
The FileNotFoundError is covered by bug 1590321 and I'm working on fixing it now. -- 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/1639558 Title: regression-update from #1624641 Status in unattended-upgrades package in Ubuntu: New Bug description: Regression problem, (in the sense it didn't happen before the update although not directly from the code changes) Since update to 0.90ubuntu0.1 (ubuntu 16.04) I am constantly now getting this notification performing anything with apt. N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension Secondly I am also now getting this, triggering apport bug report on every boot (program is not checking/creating a dir before trying to write to log in it) syslog.1:Nov 6 10:36:26 PortegeR830 apt.systemd.daily[815]: FileNotFoundError: [Errno 2] No such file or directory: '/var/log /unattended-upgrades/unattended-upgrades-dpkg.log' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: 2016-11-06 10:36:05,682 INFO Initial blacklisted packages: 2016-11-06 10:36:05,682 INFO Initial whitelisted packages: 2016-11-06 10:36:05,683 INFO Starting unattended upgrades script 2016-11-06 10:36:05,683 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates', 'o=Ubuntu,a=xenial-backports'] 2016-11-06 10:36:21,473 INFO Packages that will be upgraded: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 6 10:59:28 2016 PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "7"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-05-30T16:31:54.137714 mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2015-05-30T16:31:21.861600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1639558/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
And if one doesn't have Samba installed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1639440] Re: [desktop] apps don't start, missing logs
This is related to the other open bugs caused by systemd starting to mount the unified hierarchy. There had been a branch of cgmanager able to handle unified, around June 2015, but it was only experimental. Does unity still require cgmanager? Note that cgmanager's deprecation (https://linuxcontainers.org/) was announced some time ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in ubuntu-app-launch package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1574324] Please test proposed package
There is a version of PulseAudio in yakkety-proposed as well, please follow the above instructions, but for yakkety instead. -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Xenial: Fix Committed Status in pulseaudio source package in Yakkety: Fix Committed Bug description: Impact: A patch we carry for Ubuntu touch introduced a change that originally was required to make sure PulseAudio did not crash. This patch was ported to PulseAudio 8 in Xenial, but the patch author's bluetooth hardware that was to hand at the time worked so was assumed to be ok. However, the opposite is now happening, i.e PulseAudio is crashing with a subset of Bluetooth hardware. Regression potential: Very low to none. As can be read in this report, much debugging and testing has been done to find the problem, and the eventual fix. Moreover the change is the removal of a patch hunk that removed a line of code originally present in PulseAudio. Test case: NOTE that this test case applies to bluetooth hardware that is identified as not working in this bug report. 1. Install, or upgrade to Xenial or yakkety. 2. Pair your bluetooth device in the bluetooth settings in the relevant settings application for your desktop environment. 3. Once paired, you will notice that sound stops working, as pulseaudio has thrown an assertion error. 4. You do not have to remove your audio device from the paired device list, but it may be easier to do so for the next part of the testing. 5. Update to the version of PulseAudio in xenial-proposed which is 1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1. 6. Re-pair your device. Audio should continue to work, and you should be able to switch to your bluetooth device and use it. Original bug report: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1639440] Re: [desktop] apps don't start, missing logs
journalctl -u cgmanager -- Logs begin at Mon 2016-11-07 22:43:26 EET, end at Mon 2016-11-07 23:17:01 EET. -- Nov 07 22:43:41 pixel-MS-7369 systemd[1]: Started Cgroup management daemon. Nov 07 22:43:41 pixel-MS-7369 cgmanager[1140]: cgmanager: Error mounting unified: No such file or directory Nov 07 22:43:41 pixel-MS-7369 cgmanager[1140]: cgmanager: failed to collect cgroup subsystems Nov 07 22:43:45 pixel-MS-7369 systemd[1]: cgmanager.service: Main process exited, code=exited, status=1/FAILURE Nov 07 22:43:45 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state. Nov 07 22:43:45 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'. Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Service hold-off time over, scheduling restart. Nov 07 22:43:46 pixel-MS-7369 systemd[1]: Stopped Cgroup management daemon. Nov 07 22:43:46 pixel-MS-7369 systemd[1]: Started Cgroup management daemon. Nov 07 22:43:46 pixel-MS-7369 cgmanager[1383]: cgmanager: Error mounting unified: No such file or directory Nov 07 22:43:46 pixel-MS-7369 cgmanager[1383]: cgmanager: failed to collect cgroup subsystems Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Main process exited, code=exited, status=1/FAILURE Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state. Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'. Nov 07 22:43:46 pixel-MS-7369 systemd[1]: cgmanager.service: Service hold-off time over, scheduling restart. Nov 07 22:43:46 pixel-MS-7369 systemd[1]: Stopped Cgroup management daemon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in ubuntu-app-launch package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1624641] Re: security updates with a new dependency don't get installed
I think it would be wise to run a regression analysis on all previous patches across all packages where, similarly, patches failed to apply and were not caught by dutifully diligent security-minded persons. i would suspect you have thousands of failed applications of patches across the board. a simple grep told me so just spending a couple minutes looking -- 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/1624641 Title: security updates with a new dependency don't get installed Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: In Progress Bug description: Test Case - 1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed 2) Install the release version of chromium browser e.g. "sudo apt-get install chromium-browser=49.0.2623.108-0ubuntu1.1233 chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233" 3) Run apt-get update if you didn't already 4) Run "sudo /usr/bin/unattended-upgrades -v -d" 5) Observe the following output "Checking: chromium-browser ([, ]) pkg 'libspeechd2' not in allowed origin sanity check failed" With the version of unattended-upgrades from -proposed libspeechd2 should be from an allowed origin and chromium-browser will get updated. Regression Potential This change modifies the behavior of unattended-upgrades such that new packages will be installed on a user's system and they may not except such behavior (e.g. why was libspeechd2 insalled?). However, this seems better than not installing security updates and leaving people's systems vulnerable to attack. Original Description E.g. chromium-browser has an update, but U-U does not update it. I saw in update-manager that the security update is available before running U-U. Afterwards I can install the update by update-manager. ProblemType: BugDistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:13:40 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: allSourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624641/+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 1639440] Re: [desktop] apps don't start, missing logs
** No longer affects: systemd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in ubuntu-app-launch package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1624641] Re: security updates with a new dependency don't get installed
I've reuploaded this to the Yakkety queue for review as the patch was not properly applied to the package because the package's source format was native not quilt. The new upload does not use quilt and just modifies the file directly. ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: Fix Released => In Progress -- 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/1624641 Title: security updates with a new dependency don't get installed Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in unattended-upgrades source package in Yakkety: In Progress Bug description: Test Case - 1) Boot a xenial system w/o chromium browser and w/o libspeechd2 installed 2) Install the release version of chromium browser e.g. "sudo apt-get install chromium-browser=49.0.2623.108-0ubuntu1.1233 chromium-browser-l10n=49.0.2623.108-0ubuntu1.1233 chromium-codecs-ffmpeg-extra=49.0.2623.108-0ubuntu1.1233" 3) Run apt-get update if you didn't already 4) Run "sudo /usr/bin/unattended-upgrades -v -d" 5) Observe the following output "Checking: chromium-browser ([, ]) pkg 'libspeechd2' not in allowed origin sanity check failed" With the version of unattended-upgrades from -proposed libspeechd2 should be from an allowed origin and chromium-browser will get updated. Regression Potential This change modifies the behavior of unattended-upgrades such that new packages will be installed on a user's system and they may not except such behavior (e.g. why was libspeechd2 insalled?). However, this seems better than not installing security updates and leaving people's systems vulnerable to attack. Original Description E.g. chromium-browser has an update, but U-U does not update it. I saw in update-manager that the security update is available before running U-U. Afterwards I can install the update by update-manager. ProblemType: BugDistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:13:40 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: allSourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624641/+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 1632687] Re: /usr/bin/signonpluginprocess:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivat
*** This bug is a duplicate of bug 1630765 *** https://bugs.launchpad.net/bugs/1630765 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: signon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1632687 Title: /usr/bin/signonpluginprocess:11:QExplicitlySharedDataPointer:QNetworkConfiguration::~QNetworkConfiguration:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivate:QNetworkAccessManagerPrivate::~QNetworkAccessManagerPrivate:QScopedPointerDeleter Status in signon package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding signon. This problem was most recently seen with package version 8.59+16.10.20160916-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/cdb7a4fc6d47e3ba3ce18606745c27933f9a7f57 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1632687/+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 1629797] Re: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up
** Also affects: dbus (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: dbus (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Yakkety) Status: Confirmed => Fix Released ** Changed in: dbus (Ubuntu Xenial) Status: New => Invalid ** Changed in: dbus (Ubuntu Yakkety) Status: New => Invalid ** No longer affects: dbus (Ubuntu Xenial) ** No longer affects: dbus (Ubuntu Yakkety) ** Description changed: - During boot, cloud-init does DNS resolution checks to if particular - metadata services are available (in order to determine which cloud it is - running on). These checks happen before systemd-resolved is up[0] and - if they resolve unsuccessfully they take 25 seconds to complete. + === Begin SRU Template === + [Impact] + In cases where cloud-init used dns during early boot and system was + configured in nsswitch.conf to use systemd-resolvd, the system would + timeout on dns attempts making system boot terribly slow. + + [Test Case] + Boot a system on GCE. + check for WARN in /var/log/messages + check that time to boot is reasonable (<30 seconds). In failure case the + times would be minutes. + + [Regression Potential] + Changing order in boot can be dangerous. There is real chance for + regression here, but it should be fairly small as xenial does not include + systemd-resolved usage. This was first noticed on yakkety where it did. + + [Other Info] + It seems useful to SRU this in the event that systemd-resolvd is used + on 16.04 or the case where user upgrades components (admittedly small use + case). + + === End SRU Template === + + + + During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete. This has substantial impact on boot time in all contexts, because cloud- init attempts to resolve three known-invalid addresses ("does-not- exist.example.com.", "example.invalid." and a random string) to enable it to detect when it's running in an environment where a DNS server will always return some sort of redirect. As such, we're talking a minimum impact of 75 seconds in all environments. This increases when cloud- init is configured to check for multiple environments. This means that yakkety is consistently taking 2-3 minutes to boot on EC2 and GCE, compared to the ~30 seconds of the first boot and ~10 seconds thereafter in xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1629797 Title: resolve service in nsswitch.conf adds 25 seconds to failed lookups before systemd-resolved is up Status in cloud-init: Fix Committed Status in D-Bus: Unknown Status in cloud-init package in Ubuntu: Fix Released Status in dbus package in Ubuntu: Won't Fix Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Fix Released Bug description: === Begin SRU Template === [Impact] In cases where cloud-init used dns during early boot and system was configured in nsswitch.conf to use systemd-resolvd, the system would timeout on dns attempts making system boot terribly slow. [Test Case] Boot a system on GCE. check for WARN in /var/log/messages check that time to boot is reasonable (<30 seconds). In failure case the times would be minutes. [Regression Potential] Changing order in boot can be dangerous. There is real chance for regression here, but it should be fairly small as xenial does not include systemd-resolved usage. This was first noticed on yakkety where it did. [Other Info] It seems useful to SRU this in the event that systemd-resolvd is used on 16.04 or the case where user upgrades components (admittedly small use case). === End SRU Template === During boot, cloud-init does DNS resolution checks to if particular metadata services are available (in order to determine which cloud it is running on). These checks happen before systemd-resolved is up[0] and if they resolve unsuccessfully they take 25 seconds to complete. This has substantial impact on boot time in all contexts, because cloud-init attempts to resolve three known-invalid addresses ("do
[Touch-packages] [Bug 1639440] Re: [desktop] apps don't start, missing logs
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in systemd package in Ubuntu: New Status in ubuntu-app-launch package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1639440] Re: [desktop] apps don't start, missing logs
so i've removed the snap session but nothing changed systemctl --failed UNITLOAD ACTIVE SUBDESCRIPTION ● cgmanager.service loaded failed failed Cgroup management daemon ● isc-dhcp-server.service loaded failed failed ISC DHCP IPv4 server -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in ubuntu-app-launch package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
Btw, for those of you with the cups scheduler messages as well and still want to share with samba shares, you can disable just printer sharing and that will also effectively get rid of these messages as well. The guide to do that is here: https://forums.linuxmint.com/viewtopic.php?p=1231018#p1231018 Be sure to reboot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1639926] Re: Update to 3.22.2
** Also affects: evolution-data-server (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1639926 Title: Update to 3.22.2 Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Yakkety: New Bug description: Impact == https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22 Test Case = Regression Potential To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
This is happening on a machine I just upgraded to 16.10. AFAICT, from looking back at the logs, it only started happening, regularly, after this upgrade. :) Only comes about every three hours here. Just wanted to confirm it seems to exist in the latest release. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1639926] [NEW] Update to 3.22.2
Public bug reported: Impact == https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22 Test Case = Regression Potential ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1639926 Title: Update to 3.22.2 Status in evolution-data-server package in Ubuntu: New Bug description: Impact == https://git.gnome.org/browse/evolution-data-server/tree/NEWS/?h=gnome-3-22 https://git.gnome.org/browse/evolution-data-server/log/?h=gnome-3-22 Test Case = Regression Potential To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1639926/+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 1611078] Re: Support snaps inside of lxd containers
note: that for xenial there are several pieces that must land as different SRUs. Just using the xenial SRU kernel is not sufficient. There is an apparmor userspace SRU that is required, and squashfuse sru ... -- 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/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in lxd source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+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 1611078] Re: Support snaps inside of lxd containers
Based on feedback from @jjohansen there will be follow-up patches to fix the problems, but the patches already applied should be kept and do not need to be reverted. -- 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/1611078 Title: Support snaps inside of lxd containers Status in Snappy: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lxd package in Ubuntu: Fix Released Status in apparmor source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Committed Status in lxd source package in Xenial: Fix Committed Status in apparmor source package in Yakkety: Fix Released Status in linux source package in Yakkety: Fix Released Status in lxd source package in Yakkety: Fix Released Bug description: I tried following the instructions on snapcraft.io and got a failure. See the output below. I've also attached the relevant output from running "journalctl -xe". uname: Linux 3.19.0-65-generic x86_64 release: Ubuntu 16.04 package: snapd 2.11+0.16.04 Notably, I'm running this in an LXD container (version: 2.0.0.rc9). - $ sudo snap install hello-world 64.75 MB / 64.75 MB [==] 100.00 % 2.85 MB/s error: cannot perform the following tasks: - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See "systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for details. ) $ ls -la /snap total 4K drwxr-xr-x 3 root root 4096 Aug 8 17:49 ubuntu-core $ ls -la /snap/ubuntu-core/ total 4K drwxr-xr-x 2 root root 4096 Aug 8 17:49 122 $ ls -la /snap/ubuntu-core/122/ total 0K $ systemctl status "snap-ubuntu\\x2dcore-122.mount" ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min ago Where: /snap/ubuntu-core/122 What: /var/lib/snapd/snaps/ubuntu-core_122.snap Process: 31781 ExecMount=/bin/mount /var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs (code=exited, status=32) Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core... Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount failed: Unknown error -1 Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount process exited, code=exited status=32 Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for ubuntu-core. Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit entered failed state. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1611078/+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 1639622] Re: Nux is uninstallable/unbuildable in zesty-proposed (Depends on glewmx)
This bug was fixed in the package nux - 4.0.8+17.04.20161107-0ubuntu1 --- nux (4.0.8+17.04.20161107-0ubuntu1) zesty; urgency=medium * Don't build-depend on libglew-dev. It should be sufficient to build against libglewmx-dev (LP: #1639622) -- Jeremy Bicha Mon, 07 Nov 2016 01:33:29 + ** Changed in: nux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1639622 Title: Nux is uninstallable/unbuildable in zesty-proposed (Depends on glewmx) Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Nux uses glewmx. glew was updated to 2.0 in Debian but since glewmx support was dropped upstream in the new version, a glewmx source package was introduced. See https://bugs.debian.org/836942 Both the new glew and glewmx packages were autosynced to Ubuntu zesty. But libglewmx-dev is no longer co-installable with libglew-dev. This makes nux and Unity unbuildable in zesty. $ sudo apt install libnux-4.0-dev The following packages have unmet dependencies: libnux-4.0-dev : Depends: libglewmx-dev but it is not going to be installed $ apt show libglewmx-dev Package: libglewmx-dev Version: 1.13.0-3 Source: glewmx Original-Maintainer: Paul Wise Provides: libglewmx1.5-dev, libglewmx1.6-dev Depends: libglewmx1.13 (= 1.13.0-3) Conflicts: libglew-dev, libglewmx1.6-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1639622/+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 1639897] Re: lxc / lxc1 uninstallable
Strange side effect: Launchpad didn't let me report the bug against the package lxc1 because launchpad insists that there is no lxc1 package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1639897 Title: lxc / lxc1 uninstallable Status in lxc package in Ubuntu: New Bug description: Hi, I just upgraded a server machine from 14.04 to 16.04.1 and lost lxc during upgrade, because the upgrade process removed it. Now I can't install lxc due to broken dependencies/incomplete package upload: lxc : Depends: lxc1 (>= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed lxc1 : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed Depends: python3-lxc (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed Recommends: libpam-cgfs but it is not going to be installed Recommends: lxc-templates (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed liblxc1 is already the newest version (2.0.5-0ubuntu3~ubuntu14.04.1~ppa1). python3-lxc : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed Obviously someone has rendered lxc uninstallable by putting an incomplete set of packages in the 16.04 repository. Please fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1639897/+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 1639896] Re: Backport support for Polaris
** Summary changed: - Backport userland support for Polaris + Backport support for Polaris -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport support for Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: New Status in xserver-xorg-video-amdgpu source package in Xenial: New Bug description: Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1639897] [NEW] lxc / lxc1 uninstallable
Public bug reported: Hi, I just upgraded a server machine from 14.04 to 16.04.1 and lost lxc during upgrade, because the upgrade process removed it. Now I can't install lxc due to broken dependencies/incomplete package upload: lxc : Depends: lxc1 (>= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed lxc1 : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed Depends: python3-lxc (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed Recommends: libpam-cgfs but it is not going to be installed Recommends: lxc-templates (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed liblxc1 is already the newest version (2.0.5-0ubuntu3~ubuntu14.04.1~ppa1). python3-lxc : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed Obviously someone has rendered lxc uninstallable by putting an incomplete set of packages in the 16.04 repository. Please fix. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1639897 Title: lxc / lxc1 uninstallable Status in lxc package in Ubuntu: New Bug description: Hi, I just upgraded a server machine from 14.04 to 16.04.1 and lost lxc during upgrade, because the upgrade process removed it. Now I can't install lxc due to broken dependencies/incomplete package upload: lxc : Depends: lxc1 (>= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed lxc1 : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed Depends: python3-lxc (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed Recommends: libpam-cgfs but it is not going to be installed Recommends: lxc-templates (= 2.0.5-0ubuntu1~ubuntu16.04.2) but it is not going to be installed liblxc1 is already the newest version (2.0.5-0ubuntu3~ubuntu14.04.1~ppa1). python3-lxc : Depends: liblxc1 (= 2.0.5-0ubuntu1~ubuntu16.04.2) but 2.0.5-0ubuntu3~ubuntu14.04.1~ppa1 is to be installed Obviously someone has rendered lxc uninstallable by putting an incomplete set of packages in the 16.04 repository. Please fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1639897/+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 1175302] Re: lighdm and pulseudio startup error...
Every time whenever this bug occur, the machine reboots. Any workaround for this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1175302 Title: lighdm and pulseudio startup error... Status in lightdm package in Ubuntu: Confirmed Bug description: Description: Ubuntu 13.04 Release: 13.04 lightdm: Installato: 1.6.0-0ubuntu2.1 Candidato: 1.6.0-0ubuntu2.1 Tabella versione: *** 1.6.0-0ubuntu2.1 0 500 http://archive.ubuntu.com/ubuntu/ raring-updates/main i386 Packages 100 /var/lib/dpkg/status 1.6.0-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages pulseaudio: Installato: 1:3.0-0ubuntu6 Candidato: 1:3.0-0ubuntu6 Tabella versione: *** 1:3.0-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages 100 /var/lib/dpkg/status The system at send a message telling "file not found" give an enter made the system continue Seems this error i see it into system log... ... May 1 22:10:11 localhost pulseaudio[2193]: [pulseaudio] authkey.c: Failed to open cookie file '/var/lib/lightdm/.config/pulse/cookie': File o directory non esistente May 1 22:10:11 localhost pulseaudio[2193]: [pulseaudio] authkey.c: Failed to load authorization key '/var/lib/lightdm/.config/pulse/cookie': File o directory non esistente Thank you ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: lightdm 1.6.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Wed May 1 21:39:11 2013 InstallationDate: Installed on 2011-07-11 (659 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) LightdmConfig: [SeatDefaults] greeter-session=unity-greeter user-session=ubuntu MarkForUpload: True SourcePackage: lightdm UpgradeStatus: Upgraded to raring on 2013-04-27 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1175302/+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 1639896] [NEW] Backport userland support for Polaris
Public bug reported: Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Invalid ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: Invalid ** Affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: xserver-xorg-video-amdgpu (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-amdgpu (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1639896 Title: Backport userland support for Polaris Status in mesa package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Status in mesa source package in Xenial: New Status in xserver-xorg-video-amdgpu source package in Xenial: New Bug description: Xenial has x-x-v-amdgpu 1.1.0 but 1.1.2 adds more PCI-ID's and fixes bugs. Mesa needs a bunch of commits backported from 12.0.x. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1639896/+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 1639440] Re: [desktop] apps don't start, missing logs
ok, so "gedit -- --desktop_file_hint=unity8.desktop" starts but "ubuntu-app-launch gedit" doesn't so.. it's probably related to U-A-L and cgmanager and systemd (i have no idea what i'm talking about lol) ** Also affects: ubuntu-app-launch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in ubuntu-app-launch package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1637437] Re: linux 3.13.0-101.148 ADT test failure with linux 3.13.0-101.148
This appears to be a problem with the test ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1637437 Title: linux 3.13.0-101.148 ADT test failure with linux 3.13.0-101.148 Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux/20161024_111739_42e49@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1637437/+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 237164] Re: kvm needs to correctly simulate a proper monitor
Since cirrus is not the prefered graphics card in QEMU anymore, and there hasn't been any update to this within the last four years, I think nobody will take care of this ticket anymore, so setting the status to "Won't fix" now. ** Changed in: qemu Status: Triaged => Won't Fix -- 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/237164 Title: kvm needs to correctly simulate a proper monitor Status in QEMU: Won't Fix Status in kvm package in Ubuntu: Won't Fix Status in xorg package in Ubuntu: Invalid Bug description: Binary package hint: xorg With xserver-xor-video-cirrus 1.2.1, there should be no need to require special handling for kvm in dexconf any longer. See also: bug 193323. If kvm would properly simulate an attached monitor, we could drop the dexconf quirks. they are currently forcing the driver to use a 1024x768 display where the driver could autodetect the monitor correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/237164/+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 1637440] Re: linux 4.4.0-46.67 ADT test failure with linux 4.4.0-46.67
This appears to be an issue with the test. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1637440 Title: linux 4.4.0-46.67 ADT test failure with linux 4.4.0-46.67 Status in apparmor package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20161027_080747_183c5@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1637440/+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 1536279] Re: Mir does not reset key states when paused or resumed
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1536279 Title: Mir does not reset key states when paused or resumed Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in QtMir: New Status in mir package in Ubuntu: Confirmed Bug description: Mir switches away from the current VT when ALT+FXX is pressed. During that key sequence the alt modifier is pressed. While away and mir does not receive the alt release. When you switch back to mir there is a chance that mir is not receiving the alt release either. So switching away and back to mir makes the alt key stick... Proposed solution: - track regular keys in mir::input::Seat or in SurfaceDispatcher - inform client(s) about pause / resume with a focus lost / focus gain event - attach key state to focus event or send separate key state event - adapt gdk/qt backends - fix alt key tracking in unity8 to rely on the provided modifier state To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536279/+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 1393578] Re: Subpixel order not included in Mir display information
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1393578 Title: Subpixel order not included in Mir display information Status in Mir: In Progress Status in QtMir: Triaged Status in qtubuntu: Triaged Status in mir package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: Just capturing something mentioned by Trevinho on IRC this morning. MirDisplayOutput does not include subpixel ordering, it could and should though. The information is exposed on the drm side (drmModeSubPixel). Marking as wishlist in absence of other information. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1393578/+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 1600220] Re: Nested server needs full control over cursor position
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1600220 Title: Nested server needs full control over cursor position Status in Mir: In Progress Status in mir package in Ubuntu: Confirmed Bug description: Unity 8, a nested server of unity-system-compositor, needs full control over the cursor position. Mir doesn't have the needed context information to know how to move or position the cursor in all situations. Only Unity 8 has this information, which lives mainly in its QML scene. Once this is granted Unity 8 can dump its QML cursor implementation and move to use the more performant hardware cursor that mir has access to. Related to bug 1513883. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1600220/+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 1539896] Re: [enhancement] Support Vulkan
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1539896 Title: [enhancement] Support Vulkan Status in Mir: In Progress Status in Ubuntu SDK IDE: Invalid Status in mir package in Ubuntu: Triaged Bug description: full support to the libraries vulkan in mir and in canonical system image. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1539896/+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 1569836] Re: demo server with CanonicalWindowManagerPolicy hides titlebar when vertmaximized
** Changed in: mir Milestone: 0.25.0 => 0.24.2 ** Changed in: mir Milestone: 0.24.2 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1569836 Title: demo server with CanonicalWindowManagerPolicy hides titlebar when vertmaximized Status in Mir: In Progress Status in mir package in Ubuntu: New Bug description: run mir_demo_server with the CanonicalWindowManagerPolicy. Connect a client (like egltriangle). Hit Shift+F11 to transition client to vertmaximized. The titlebar is hidden (or off the top of the screen). It should be shown at the top. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1569836/+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 1588237] Re: Inconsistent behaviour of Num Lock
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1588237 Title: Inconsistent behaviour of Num Lock Status in Canonical System Image: Confirmed Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: How to reproduce: M10 with external Keyboard and Screen, after restart on OTA11. To use numbers in the unlock screen, the num key has to be active. After unlocking, use a search field in the homescope or any other scope. Expected behaviour: The numblock should work, as the num key is still active. Actual behaviour: The numblock only works, when you deactivate the num key. This is the same for the browserbar or the telegram chat. After some time, the behaviour changes, so the numblock behaviour seems to be inconsistent. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588237/+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 1591328] Re: Pointer/cursor input lag in unity8 session
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1591328 Title: Pointer/cursor input lag in unity8 session Status in Canonical System Image: In Progress Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Mouse pointer suffers of heavy input lag on my laptop, might also affect tablet To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591328/+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 1612012] Re: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1612012 Title: Valgrind errors in NesterServer.* cause subsequent tests (ServerDisconnect, ServerStartup, UnresponsiveClient) to fail Status in Mir: Confirmed Status in Mir 0.24 series: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Tests always fail together: ServerDisconnect, ServerStartup, UnresponsiveClient 17:27:52 9: [ FAILED ] 5 tests, listed below: 17:27:52 9: [ FAILED ] ServerDisconnect.is_detected_by_client 17:27:52 9: [ FAILED ] ServerDisconnect.doesnt_stop_client_calling_API_functions 17:27:52 9: [ FAILED ] ServerStartup.creates_endpoint_on_filesystem 17:27:52 9: [ FAILED ] ServerStartup.after_server_sigkilled_can_start_new_instance 17:27:52 9: [ FAILED ] UnresponsiveClient.does_not_hang_server [https://mir-jenkins.ubuntu.com/job/build-2-binpkg- mir/arch=amd64,compiler=clang,platform=mesa,release=vivid+overlay/1772/consoleFull] This is happening regularly in CI. These failures occur together. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1612012/+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 1639622] Re: Nux is uninstallable/unbuildable in zesty-proposed (Depends on glewmx)
This is fixed now. This bug will be closed completely once the glew transition finishes. ** Changed in: unity (Ubuntu) Status: In Progress => Fix Committed ** Changed in: nux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: unity (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1639622 Title: Nux is uninstallable/unbuildable in zesty-proposed (Depends on glewmx) Status in nux package in Ubuntu: Fix Committed Status in unity package in Ubuntu: Fix Released Bug description: Nux uses glewmx. glew was updated to 2.0 in Debian but since glewmx support was dropped upstream in the new version, a glewmx source package was introduced. See https://bugs.debian.org/836942 Both the new glew and glewmx packages were autosynced to Ubuntu zesty. But libglewmx-dev is no longer co-installable with libglew-dev. This makes nux and Unity unbuildable in zesty. $ sudo apt install libnux-4.0-dev The following packages have unmet dependencies: libnux-4.0-dev : Depends: libglewmx-dev but it is not going to be installed $ apt show libglewmx-dev Package: libglewmx-dev Version: 1.13.0-3 Source: glewmx Original-Maintainer: Paul Wise Provides: libglewmx1.5-dev, libglewmx1.6-dev Depends: libglewmx1.13 (= 1.13.0-3) Conflicts: libglew-dev, libglewmx1.6-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1639622/+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@lists.launchpad.net
Alright I have replicated and there is indeed a problem here. It will work if the first profile starts with a / but fails when it doesn't ** Changed in: apparmor (Ubuntu) Status: New => Confirmed ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => John Johansen (jjohansen) -- 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/1639660 Title: apparmor-parse cannot parse profile with stacking //& Status in apparmor package in Ubuntu: Confirmed Bug description: I am experimenting with the new profile stacking feature of AppArmor on Ubuntu 16.10. However, when trying the load a profile with stacking ("//&" ), the apparmor-parser will report the following erros: AppArmor parser error for /etc/apparmor.d/root.test.shell in /etc/apparmor.d/root.test.shell at line 8: syntax error, unexpected TOK_ID, expecting TOK_END_OF_RULE. The system is Ubuntu 16.10 Server edition. I am trying to confine a test program at /root/test/shell. The profile looks like the following: #include /root/test/shell { #include /bin/touch ix, /root/test/read px -> readtest1 //& readtest2, /root/test/shell mr, profile readtest1 { #include /root/test/file1 r, /root/test/read mr, } profile readtest2 { #include /root/test/file2 r, /root/test/read mr, } } If the stacking works, when the /root/test/shell execs /root/test/read, it should not be able to read either file1 or file2. I am not sure if I am using the stacking in the wrong way, or there is a bug in userspace support for stacking. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1639660/+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 1628478] Re: Mir servers crash when using the Nvidia driver
** Changed in: mir Milestone: 0.25.0 => 0.26.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1628478 Title: Mir servers crash when using the Nvidia driver Status in Mir: In Progress Status in mir package in Ubuntu: Triaged Bug description: I select Unity8 from the log in screen, type in my credentials and it just hangs. Intel® Core™ i7-4710HQ CPU @ 2.50GHz × 8 GeForce GTX 860M/PCIe/SSE2 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1628478/+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 1600592] Re: package whoopsie 0.2.52.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: whoopsie (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1600592 Title: package whoopsie 0.2.52.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 Status in whoopsie package in Ubuntu: Confirmed Bug description: insserv: exiting now without changing boot order! update-rc.d: error: insserv rejected the script header dpkg: erro ao processar o pacote whoopsie (--configure): sub-processo script post-installation instalado retornou estado de saída de erro 1 Configurando lsb-release (9.20160110ubuntu0.2) ... Configurando snapd (2.0.10) ... Erros foram encontrados durante o processamento de: whoopsie E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: whoopsie 0.2.52.1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: libnss3-tools: Install whoopsie: Configure libnss3-tools: Configure NULL: ConfigurePending Architecture: amd64 Date: Sat Jul 9 13:58:01 2016 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2016-04-24 (76 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.52.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1600592/+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 1639440] Re: [desktop] apps don't start, missing logs
systemctl --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● cgmanager.service loaded failed failed Cgroup management daemon ● isc-dhcp-server.service loaded failed failed ISC DHCP IPv4 server ● snap.unity8-session.cgmanager.service loaded failed failed Service for snap application unity8-session.cgmanager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1639440] Re: [desktop] apps don't start, missing logs
unity8-desktop-session-mir/zesty,zesty,now 1.0.13+17.04.20161103.1-0ubuntu1 all [installed] unity8-session-snap/zesty,zesty,now 1.0.13+17.04.20161103.1-0ubuntu1 all [installed] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1450009] Re: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock
I have the same issue with Dell M4800 using docking station and am a new Ubuntu user (coming from windows), so a lot of the dicussion above does not make sense :( -- 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/1450009 Title: [HP, Dell notebooks] suspends on closed lid, does not recognized external monitors/dock Status in systemd package in Ubuntu: Fix Released Bug description: Using systemd as init system on a HP zbook15 notebook having 2 external monitors connected using a docking station and starting with lid closed the system goes to sleep after successfully booting and starting lightdm greeter. Sometimes there's enough time to enter username and password but system goes to sleep every time after a few seconds. The system can be woken up and used after this happens but it will not let me shutdown later. The problem is just present in docked situation starting with closed lid using systemd a init system. If notebook is used in non-docked situation with open lid and systemd the problem does not occur. Workaround: A switch back to upstart as init system resolves the issue. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd-sysv 219-7ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Wed Apr 29 14:46:09 2015 InstallationDate: Installed on 2015-04-27 (1 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450009/+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 1639249] Re: Result art not displayed when run in a snap
** Also affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1639249 Title: Result art not displayed when run in a snap Status in unity-scopes-api package in Ubuntu: New Status in unity-scopes-shell package in Ubuntu: New Bug description: When a scope calls result.set_art() the path is not adjusted to take in consideration $SNAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1639249/+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 1639440] Re: [desktop] apps don't start, missing logs
sudo systemctl status cgmanager ● cgmanager.service - Cgroup management daemon Loaded: loaded (/lib/systemd/system/cgmanager.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2016-11-07 19:18:01 EET; 27min ago Main PID: 1698 (code=exited, status=1/FAILURE) CPU: 0 Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Main process exited, code=exited, status=1/FAILURE Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state. Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'. Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Service hold-off time over, scheduling restart. Nov 07 19:18:01 pixel-MS-7369 systemd[1]: Stopped Cgroup management daemon. Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Start request repeated too quickly. Nov 07 19:18:01 pixel-MS-7369 systemd[1]: Failed to start Cgroup management daemon. Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Unit entered failed state. Nov 07 19:18:01 pixel-MS-7369 systemd[1]: cgmanager.service: Failed with result 'exit-code'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1639440] Re: [desktop] apps don't start, missing logs
looks similar to this bug https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1535058 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1639440] Re: [desktop] apps don't start, missing logs
cgmanager/zesty,now 0.41-2 amd64 [installed,automatic] ** Also affects: cgmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in cgmanager package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+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 1600782] Re: Not translated string
Salut Olivier, Oupsss, j'ai cru qu'il s'agissait d'un de mes bogues. Et comme j'ai vu les boutons traduits, j'ai passé à « Fix Released ». Je te laisse reprendre la main et repasser à « Confirmed » si c'est le cas. Mille excuses Jean-Marc -- 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/1600782 Title: Not translated string Status in NetworkManager: New Status in Ubuntu Translations: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: See https://dl.dropboxusercontent.com/u/26959244/Capture%20du%202016-07-08%2011-57-24.png To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1600782/+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 1639440] Re: [desktop] apps don't start, missing logs
from .xsession-errors (when i try to launch apps) upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.developer.robert-ancell.dotty_dotty_18) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539157340067) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539157340067) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (tiled-1478539421897621) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (tiled-1478539421897621) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (tiled-1478539423294864) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (tiled-1478539423294864) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539424742531) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (com.ubuntu.terminal-1478539424742531) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (ubuntu-system-settings-) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (ubuntu-system-settings-) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.music_music_2.4.1003) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-click (com.ubuntu.music_music_2.4.1003) post-stop process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (libertine-1478539437006542) main process: unable to connect to CGManager: Unknown error 196609 upstart: Failed to spawn application-legacy (libertine-1478539437006542) post-stop process: unable to connect to CGManager: Unknown error 196609 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639440 Title: [desktop] apps don't start, missing logs Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Ubuntu 17.04 + proposed (unity8 desktop session) unity8/zesty-proposed,now 8.14+17.04.20161027-0ubuntu1 amd64 [installed,automatic] apps don't load and i can't find the logs in ~/.cache/upstart for the apps. i'll upload the logs that i do have for unity8 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1639440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1639853] Re: Unity8 crash while locking/unlocking with hdmi plugged
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639853 Title: Unity8 crash while locking/unlocking with hdmi plugged Status in unity8 package in Ubuntu: Confirmed Bug description: Environment: current build number: 76 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-07 08:03:44 version version: 76 version ubuntu: 20161105 version device: 20161014.0 version custom: 20161105 Steps to reproduce: 1º Connect hdmi 2º Lock/unlock device several times Current result: locking/unlocking device causes greeter to misbehave and finally the ubuntu boot logo appears. Attached some logs and crash files, hope it helps Expected result: unity8 should not crash Add info: time stamp 16:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1639853/+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 1639852] [NEW] Phone button appears on non-number messages
Public bug reported: When looking at text messages from a company, which is identified by name rather than phone number, the phone button is still present and will open the dialer app with no number. I'd expect the phone button to be removed when there is no phone number present. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1639852 Title: Phone button appears on non-number messages Status in messaging-app package in Ubuntu: New Bug description: When looking at text messages from a company, which is identified by name rather than phone number, the phone button is still present and will open the dialer app with no number. I'd expect the phone button to be removed when there is no phone number present. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1639852/+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 1639853] [NEW] Unity8 crash while locking/unlocking with hdmi plugged
Public bug reported: Environment: current build number: 76 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-07 08:03:44 version version: 76 version ubuntu: 20161105 version device: 20161014.0 version custom: 20161105 Steps to reproduce: 1º Connect hdmi 2º Lock/unlock device several times Current result: locking/unlocking device causes greeter to misbehave and finally the ubuntu boot logo appears. Attached some logs and crash files, hope it helps Expected result: unity8 should not crash Add info: time stamp 16:07 ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "logs&video.zip" https://bugs.launchpad.net/bugs/1639853/+attachment/4774072/+files/logs%26video.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1639853 Title: Unity8 crash while locking/unlocking with hdmi plugged Status in unity8 package in Ubuntu: New Bug description: Environment: current build number: 76 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-07 08:03:44 version version: 76 version ubuntu: 20161105 version device: 20161014.0 version custom: 20161105 Steps to reproduce: 1º Connect hdmi 2º Lock/unlock device several times Current result: locking/unlocking device causes greeter to misbehave and finally the ubuntu boot logo appears. Attached some logs and crash files, hope it helps Expected result: unity8 should not crash Add info: time stamp 16:07 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1639853/+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 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
** Changed in: dbus (Ubuntu Yakkety) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: dbus (Ubuntu Yakkety) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Unknown Status in systemd: Unknown Status in dbus package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in dbus source package in Yakkety: Confirmed Status in systemd source package in Yakkety: Invalid Bug description: I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Most definitely my comments above are with regard to SRU, because I know that the point of this bug is to be SRU'd. > d) is "unavoidable" if we're do make use of ROUNDTTT, and to be frank, > seems like a reasonable side-effect. There's only so much that can be > done to handle both IPv4 and IPv6 in the initramfs, and I think we can > live we a few extra seconds booting. Furthermore, systems that do not > get their IP addresses in the first few seconds probably deserve a good > revision -- it is likely happening due to suboptimal network > configuration (you shouldn't have to wait multiple seconds for the DHCP > server to respond). In the case where there is no IPv4 available, it > won't change the end result -- the system will still fail to boot, it > will just take longer doing so (and on IPv6-only, people should set > ip=off explicitly, and that use case was not previously supported). How is not doing a 'sleep' unavoidable? The new code path only uses dhclient in some cases for ipv4. In cases where it still allows the ipconfig path (kernel command line of 'ip=dhcp') the initramfs will now sleep in between re-tries when previously it would not. It will take longer to boot, and that is a regression. It is definitely fixable. > In the context of an SRU, it seems like a better deal to cause things to > take a little longer in the less used, deprecated method of using > ipconfig than to change ipconfig parameters in a way that might cause How are you "deprecate" ing this ? Can you show me where deprecating behavior is allowed in an SRU? > other issues (reducing the timeout generally, and using the sleep > "alone" means systems that are genuinely slow might fail completely for > no good reason. Making the timeout 2 seconds every time would yield to > such an effect; whereas making the timeout 30 every time would lead to a > substantial delay in bringing up the network if the first tries fail). > b) I haven't seen a proper use case where this was important. There > isn't straightforward way to set the hostname request for dhclient; and > properly configuring the DHCP server would get you the right hostname. > Furthermore, the hostname in use when enlisting or deploying MAAS > systems should not matter, as it's the kind of information that should > be written out to the final system (and doesn't matter on ephemeral, > "get how many disks this machine has" instances -- the hostname there is > already known and set by MAAS). see bug 1069570 for a real world example (even affecting MAAS) of how a hostname is important. Something being "not straight forward" doesn't mean that you can just regress behavior in an SRU. MAAS is not the only consumer of ipv4 dhcp boot. > a) A valid concern, but let's focus on making things work at all before > optimizing. This should be verified in the devel release before a SRU. > c) I don't know what it will do; it will need to be properly watched in > SRUs and the devel release. My initial testing shows absolutely no > adverse effects. Did you ever boot a system and look? I suggest you need to account for that and test and see what happens. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Fix Committed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: Won't Fix Status in open-iscsi package in Ubuntu: In Progress Status in initramfs-tools source package in Xenial: Triaged Status in isc-dhcp source package in Xenial: In Progress Status in klibc source package in Xenial: Won't Fix Status in open-iscsi source package in Xenial: In Progress Status in initramfs-tools source package in Yakkety: In Progress Status in isc-dhcp source package in Yakkety: In Progress Status in klibc source package in Yakkety: Won't Fix Status in open-iscsi source package in Yakkety: In Progress Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627164 Related bugs: * bug 1229458: grub2 needed changes * bug 1621615: network not configured when ipv6 netbooted into cloud-init * bug 1635716: Can't bring up a machine on a dual network (ipv4 and ipv6) [Impact] It is not possible to netboot Ubuntu with a network-based root filesystem in an ipv6-only environment. Anyone wanting to netboot in an ipv6-only environment is affected. These uploads address this by replacing the one-off klibc dhcp client (IPv4-only) with the defacto standard isc-dhcp-client, and thereby provide both ipv6 and ipv4 DHCP configuration. [Test Case] See Bug 1229458. Co
[Touch-packages] [Bug 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
@ChristianEhrhardt, I installed 1:7.2p2-4ubuntu2.1 version of openssh- client package from Xenial after purging 1:7.3p1-1 version. With this version, I can ssh to any host without using LC_ALL=C variable. ssh launchpad.net ssh: connect to host launchpad.net port 22: Connection refused ssh gitlab.com Permission denied (publickey). LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.2p2-4ubuntu2.1 Candidate: 1:7.3p1-1 Version table: 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages *** 1:7.2p2-4ubuntu2.1 100 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: Incomplete Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1577596] Re: ntpd not started when using ntpdate
hhl@ILS-AP2:~$ which ntpdate /usr/sbin/ntpdate hhl@ILS-AP2:~$ dpkg -l | grep ntpdate ii ntpdate 1:4.2.8p4+dfsg-3ubuntu5.3 i386 client for setting system time from NTP servers hhl@ILS-AP2:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate Status in init-system-helpers package in Ubuntu: Confirmed Status in ntp package in Ubuntu: Won't Fix Bug description: After updating from 14.04 to 16.04 on a number of my systems, ntpd no longer starts at boot on any of those systems. `systemctl status ntp` shows: ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon. May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon. Manually starting it using `systemctl start ntp` works fine. However, systemd does not seem to want to start it automatically at boot time. As best as I can tell based on trial and error, there is something special about the combination of the service being named "ntp.service" and the service depending on network.target. However, I haven't been able to identify exactly what is causing this. If I copy the init script to any other name, everything works fine: cp /etc/init.d/ntp /etc/init.d/ntpd Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd" systemctl enable ntpd # After a reboot, ntpd.service is started, but ntp.service is not. If I remove "$network" from the "# Required-Start: $network $remote_fs $syslog" line in /etc/init.d/ntp, then systemd starts it automatically ... But of course it is started before the network comes up, so it fails. If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot: #!/bin/sh ### BEGIN INIT INFO # Provides: ntp # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 1 # Short-Description: Start NTP daemon ### END INIT INFO echo "script was run" >> /ntp.log If I rename that same dummy script to /etc/init.d/ntp2, it is started automatically at boot. However, grepping the systemd source code and my systemd config files for ntp doesn't seem to find anything that might cause this behavior: /etc/systemd# grep -iR ntp * timesyncd.conf:#NTP= timesyncd.conf:#FallbackNTP=ntp.ubuntu.com /lib/systemd# grep -R ntp * system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd Binary file systemd-networkd matches Binary file systemd-timedated matches Binary file systemd-timesyncd matches What else can I do to debug this further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1638338] Re: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options)
@ChristianEhrhardt, you are welcome. I thank you for trying to help me! Yes, I reported this problem in AskUbuntu, then decided to report it as a bug. Is there a way for me to debug ssh? Or "bisect" it? I am going to try to install a previous version of ssh package. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1638338 Title: Can not ssh with tr_TR.UTF-8 locales (Bad configuration options) Status in openssh package in Ubuntu: Incomplete Bug description: I can not ssh to any host with Turkish locales. What I expected to happen: I expected that 'ssh some_host' command would successfully run. What actually happened 'ssh some_host' command failed with an error. Steps to produce: 1. Open a terminal 2. Run LANG=tr_TR.UTF-8 ssh some_host If I run ssh with tr_TR.UTF-8 locale, the first error I get is: $HOME/.ssh/config: line 7: Bad configuration option: Identityfile $HOME/.ssh/config: terminating, 1 bad configuration options If I commend IdentityFile option from $HOME/.ssh/config file and re- run the command, I get this: debug1: Reading configuration data ~/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * /etc/ssh/ssh_config: line 55: Bad configuration option: gssapIauthentication /etc/ssh/ssh_config: line 56: Bad configuration option: gssapIdelegatecredentials /etc/ssh/ssh_config: terminating, 2 bad configuration options If I commend GSSAPIAuthentication and GSSAPIDelegateCredentials option, I can ssh to a host. So to ssh to a host with tr_TR.UTF-8 locale, one must commend out IdentityFile, if it is used, GSSAPIAuthentication and GSSAPIDelegateCredentials optons. Workaround: LC_ALL=C ssh some_host LC_ALL=C apt-cache policy openssh-client openssh-client: Installed: 1:7.3p1-1 Candidate: 1:7.3p1-1 Version table: *** 1:7.3p1-1 500 500 http://archive.ubuntu.com/ubuntu yakkety/main amd64 Packages 100 /var/lib/dpkg/status LC_ALL=C lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.10 Release: 16.10 Codename: yakkety ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: openssh-client 1:7.3p1-1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 19:37:35 2016 InstallationDate: Installed on 2016-10-23 (9 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome N/A SSHClientVersion: OpenSSH_7.3p1 Ubuntu-1, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1638338/+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 1639708] Re: package libopenal1 1:1.17.2-4 [modified: usr/share/doc/libopenal1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libopena
** 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 openal-soft in Ubuntu. https://bugs.launchpad.net/bugs/1639708 Title: package libopenal1 1:1.17.2-4 [modified: usr/share/doc/libopenal1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libopenal1/changelog.Debian.gz', which is different from other instances of package libopenal1:i386 Status in openal-soft package in Ubuntu: New Bug description: dont know ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libopenal1 1:1.17.2-4 [modified: usr/share/doc/libopenal1/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.8.0-27.29-lowlatency 4.8.1 Uname: Linux 4.8.0-27-lowlatency x86_64 NonfreeKernelModules: openafs nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Fri Nov 4 04:05:58 2016 DuplicateSignature: package:libopenal1:1:1.17.2-4 [modified: usr/share/doc/libopenal1/changelog.Debian.gz] Unpacking libopenal1:i386 (1:1.17.2-4) ... dpkg: error processing archive /tmp/apt-dpkg-install-zxWHdS/239-libopenal1_1%3a1.17.2-4_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libopenal1/changelog.Debian.gz', which is different from other instances of package libopenal1:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libopenal1/changelog.Debian.gz', which is different from other instances of package libopenal1:i386 InstallationDate: Installed on 2016-02-11 (269 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: openal-soft Title: package libopenal1 1:1.17.2-4 [modified: usr/share/doc/libopenal1/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libopenal1/changelog.Debian.gz', which is different from other instances of package libopenal1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openal-soft/+bug/1639708/+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 433055] Re: 9.10 Internal Microphone Does not Work on Aspire One
** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => farzam mpm (codmaghz) -- 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/433055 Title: 9.10 Internal Microphone Does not Work on Aspire One Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: The internal mic works fine with 9.04. There is no sound now with 9.10 and any level of amplification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/433055/+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 1639815] [NEW] apt list output format
Public bug reported: I'm trying to get used to the new 'apt' utility and have three wishlist items (don't want to clutter the tracker with multiple feature requests) in descending priority: 1. apt list firefox In the output, can we please have a space after the package name, before the slash? A very convenient feature of apt-cache/aptitude is to search for a package, then double click + middle click the name of a result to speedily select it and paste it into the current prompt (which is prepared with e.g. an install, show or depends command). 'apt list' appends '/repo,XXX' (where XXX is most often garbage... ehm, I mean strings like 'now' or again 'other_repo,now') right after the package name, which makes the double click select more than just a package name. E.g. 'apt policy firefox/yakkety-updates' fails. This would also be more convenient for awk scripts (despite the stable interface warning). 2. apt list fox Can we please have substring matching by default (or a storable user pref) for 'apt list'? 'apt search' is _way_ too noisy (the three line output per package instead of one line is just clutter). But 'apt list' doesn't match like 'apt-cache search' (or aptitude). The alternative is defaulting to 'apt l **' and then filling in between the asterisks, or resorting to 'apt l|grep' as standard 'apt-cache search' replacement. I don't see the justification for the current exact searching in only the package names. And there's still 'apt search' for searching the description. 3. apt sh A minor complaint: all current apt commands complete once they are tabbed when their string becomes unique, and append a space. Only 'apt show' in 16.10 (as opposed to 16.04) does not due to the undocumented showsrc command. This often leads to 'apt showfirefox' after writing 'apt shfirefox', because it's inconsistent with the other commands. So, find another name for showsrc? ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- 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/1639815 Title: apt list output format Status in apt package in Ubuntu: New Bug description: I'm trying to get used to the new 'apt' utility and have three wishlist items (don't want to clutter the tracker with multiple feature requests) in descending priority: 1. apt list firefox In the output, can we please have a space after the package name, before the slash? A very convenient feature of apt-cache/aptitude is to search for a package, then double click + middle click the name of a result to speedily select it and paste it into the current prompt (which is prepared with e.g. an install, show or depends command). 'apt list' appends '/repo,XXX' (where XXX is most often garbage... ehm, I mean strings like 'now' or again 'other_repo,now') right after the package name, which makes the double click select more than just a package name. E.g. 'apt policy firefox/yakkety-updates' fails. This would also be more convenient for awk scripts (despite the stable interface warning). 2. apt list fox Can we please have substring matching by default (or a storable user pref) for 'apt list'? 'apt search' is _way_ too noisy (the three line output per package instead of one line is just clutter). But 'apt list' doesn't match like 'apt-cache search' (or aptitude). The alternative is defaulting to 'apt l **' and then filling in between the asterisks, or resorting to 'apt l|grep' as standard 'apt-cache search' replacement. I don't see the justification for the current exact searching in only the package names. And there's still 'apt search' for searching the description. 3. apt sh A minor complaint: all current apt commands complete once they are tabbed when their string becomes unique, and append a space. Only 'apt show' in 16.10 (as opposed to 16.04) does not due to the undocumented showsrc command. This often leads to 'apt showfirefox' after writing 'apt shfirefox', because it's inconsistent with the other commands. So, find another name for showsrc? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1639815/+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