[Touch-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook
Hi, I need your help, I am a newbie and wonder how can I download the patch for my machine under Linux Mint 18.1 System: Kernel: 4.4.0-53, Desktop: KDE Plasma 5.8.7, UBUNTU_CODENAME=xenial -- 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/1590590 Title: Touchpad not recognized on Dell Latitude E7470 Ultrabook Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in xserver-xorg-input-synaptics source package in Xenial: New Status in linux source package in Yakkety: Won't Fix Status in xserver-xorg-input-synaptics source package in Yakkety: New Bug description: Expected: Touchpad settings available in Mouse & Touchpad Settings dialog Actual result: Touchpad settings missing entirely Details: The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. The settings for the touchpad are not available at all in the Mouse and Touchpad settings (see http://i.imgur.com/YRGiOrj.png). Two-finger scrolling works as expected except it's using "Natural Scrolling" by default and there is no way to change it. xinput list does not display a touchpad at all: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎜ ↳ ImPS/2 Generic Wheel Mouse id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_FHD id=10 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=12 [slave keyboard (3)] ↳ Dell WMI hotkeysid=14 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] /proc/bus/input/devices lists the device as a "Generic Wheel Mouse" Output of `lsb_release -rd`: Description: Ubuntu 16.04 LTS Release: 16.04 xserver-xorg-input-synaptics version information: xserver-xorg-input-synaptics: Installed: 1.8.2-1ubuntu3 Candidate: 1.8.2-1ubuntu3 Version table: *** 1.8.2-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719062] Re: systemd-resolved malformed packet on cert dns lookup
I have upgraded to version 234-2ubuntu10. It doesn't make a difference. I double checked and requested the key (cert record) using dig and it works just fine, no malformed packet. It's only when gpg2 requests it combined with systemd-resolved where there is a problem as far as I can tell. -- 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/1719062 Title: systemd-resolved malformed packet on cert dns lookup Status in systemd package in Ubuntu: New Bug description: systemd-resolved returns a malformed packet when looking up an openpgp key (via a cert record rfc4398) from my internal authoritative dns server. The command I used was gpg2 -v --auto-key-locate=clear,cert,local --locate-keys [Email Address] This works correctly if I change /etc/resolv.conf symlink to point at /run/systemd/resolve/resolv.conf so that it doesn't use the local systemd-resolved resolver/cache instead of /run/resolvconf/resolv.conf I'm including a wireshark capture of the malformed packet (filtered for 127.0.0.53). I noticed that this was over udp. If I recall correctly, cert records are usually big enough that they require using tcp. Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 systemd: Installed: 233-8ubuntu3 Candidate: 233-8ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1719062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719062] Re: systemd-resolved malformed packet on cert dns lookup
To clarify, having dig request it from systemd-resolved works. Having dig request it directly from the server also works. -- 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/1719062 Title: systemd-resolved malformed packet on cert dns lookup Status in systemd package in Ubuntu: New Bug description: systemd-resolved returns a malformed packet when looking up an openpgp key (via a cert record rfc4398) from my internal authoritative dns server. The command I used was gpg2 -v --auto-key-locate=clear,cert,local --locate-keys [Email Address] This works correctly if I change /etc/resolv.conf symlink to point at /run/systemd/resolve/resolv.conf so that it doesn't use the local systemd-resolved resolver/cache instead of /run/resolvconf/resolv.conf I'm including a wireshark capture of the malformed packet (filtered for 127.0.0.53). I noticed that this was over udp. If I recall correctly, cert records are usually big enough that they require using tcp. Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 systemd: Installed: 233-8ubuntu3 Candidate: 233-8ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1719062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719146] Re: package libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libicu57/changel
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1719146 Title: package libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 Status in icu package in Ubuntu: New Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-4Ckrar/08-libkrb5support0_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/09-libkrb5support0_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/10-libk5crypto3_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/11-libk5crypto3_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/14-libkrb5-3_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/15-libkrb5-3_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/16-libgssapi-krb5-2_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/17-libgssapi-krb5-2_1.15-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 23 21:46:20 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2 libgcc1 1:6.3.0-12ubuntu2 libstdc++6 6.3.0-12ubuntu2 DuplicateSignature: package:libicu57:57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] Unpacking libicu57:i386 (57.1-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-B97i8c/14-libicu57_57.1-5_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 InstallationDate: Installed on 2014-04-08 (1265 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: icu Title: package libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1719146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719146] [NEW] package libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libicu57/chang
Public bug reported: Errors were encountered while processing: /tmp/apt-dpkg-install-4Ckrar/08-libkrb5support0_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/09-libkrb5support0_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/10-libk5crypto3_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/11-libk5crypto3_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/14-libkrb5-3_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/15-libkrb5-3_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/16-libgssapi-krb5-2_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/17-libgssapi-krb5-2_1.15-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 23 21:46:20 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2 libgcc1 1:6.3.0-12ubuntu2 libstdc++6 6.3.0-12ubuntu2 DuplicateSignature: package:libicu57:57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] Unpacking libicu57:i386 (57.1-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-B97i8c/14-libicu57_57.1-5_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 InstallationDate: Installed on 2014-04-08 (1265 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: icu Title: package libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: icu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1719146 Title: package libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 Status in icu package in Ubuntu: New Bug description: Errors were encountered while processing: /tmp/apt-dpkg-install-4Ckrar/08-libkrb5support0_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/09-libkrb5support0_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/10-libk5crypto3_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/11-libk5crypto3_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/14-libkrb5-3_1.15-1_amd64.deb /tmp/apt-dpkg-install-4Ckrar/15-libkrb5-3_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/16-libgssapi-krb5-2_1.15-1_i386.deb /tmp/apt-dpkg-install-4Ckrar/17-libgssapi-krb5-2_1.15-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83 Uname: Linux 4.4.0-96-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sat Sep 23 21:46:20 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2 libgcc1 1:6.3.0-12ubuntu2 libstdc++6 6.3.0-12ubuntu2 DuplicateSignature: package:libicu57:57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] Unpacking libicu57:i386 (57.1-5) ... dpkg: error processing archive /tmp/apt-dpkg-install-B97i8c/14-libicu57_57.1-5_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 InstallationDate: Installed on 2014-04-08 (1265 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: icu Title: package libicu57 57.1-5 [modified: usr/share/doc/libicu57/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libicu57/changelog.Debian.gz', which is different from other instances of package libicu57:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/
[Touch-packages] [Bug 1705166] Re: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
[Expired for apport (Ubuntu) because there has been no activity for 60 days.] ** Changed in: apport (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1705166 Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in apport package in Ubuntu: Expired Bug description: bug ProblemType: Package DistroRelease: Ubuntu 17.04 Package: apport 2.20.4-0ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Tue Jul 18 22:24:17 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-07-19 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: apport Title: package apport 2.20.4-0ubuntu4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1705166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713560] Re: Lenovo Ideapad 320 touchpad not detected
*** This bug is a duplicate of bug 1708852 *** https://bugs.launchpad.net/bugs/1708852 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1713560 Title: Lenovo Ideapad 320 touchpad not detected Status in xorg package in Ubuntu: Confirmed Bug description: Ubuntu 17.04 xserver-xorg-input-synaptics: Installed: 1.9.0-1ubuntu1 Candidate: 1.9.0-1ubuntu1 Version table: *** 1.9.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status I get no response from touchpad. External mouse working. Touchpad not detected in /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input7 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=101400800100c03 430 0 2 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=0bda Product=58ea Version=0008 N: Name="EasyCamera" P: Phys=usb-:00:14.0-8/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input13 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0005 Vendor=046d Product=b012 Version=0014 N: Name="MX Master" P: Phys=C8:3D:D4:F8:3E:78 S: Sysfs=/devices/virtual/misc/uhid/0005:046D:B012.0001/input/input14 U: Uniq=CB:2B:20:FA:A0:6B H: Handlers=sysrq kbd mouse0 event12 B: PROP=0 B: EV=100017 B: KEY= 10007 ff8007ff febeffdfffef fffe B: REL=143 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Aug 28 21:57:00 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: elantech-0608, 0.2, 4.10.0-33-generic, x86_64: installed (WARNING! Diff between built and installe
[Touch-packages] [Bug 1626454] Re: can't connect with owncloud calendars
The new server require a new header info that has been fixed but not implemented on the Ubuntu touch image. I've ask Ubport project to implement it. Regarding my problem of password, it's not linked to Ubuntu touch but nextcloud ... i found it recently. With the App password nextcloud doesn't allow POST request identification information : https://github.com/nextcloud/server/issues/6626 ** Bug watch added: github.com/nextcloud/server/issues #6626 https://github.com/nextcloud/server/issues/6626 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1626454 Title: can't connect with owncloud calendars Status in Canonical System Image: Fix Released Status in Ubuntu Calendar App: New Status in account-plugins package in Ubuntu: Fix Released Bug description: Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar App The httpS certificate is official, up to date and not self-signed I use 7 calendars in my ownCloud-calendar-app. (yes, username and password is correct) This I tried: https://mydomain/owncloud/(suggested minimal path on the phone) Error message: Invalid username or password https://mydomain/owncloud/remote.php/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/ --> (This is the primary caldav address suggested by ownCloud calendar-app) Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/ Error message: Invalid host URL --> This direct path to one of my calendars I use for example to connect my different calendars with Thunderbird lightning (its working) I tried all with and without ending "/" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719121] Re: solved
** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1719121 Title: solved Status in xorg package in Ubuntu: Invalid Bug description: corrected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)"
Just to see tried current 17.10 to an image with lightdm rather than gdm3. It was able to exit the live session cleanly every time over multiple attempts ** Tags added: release-blocker -- 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/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (21s / no limit)" Status in gdm3 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Test case: Boot to live session using current or recent image Attempt to restart, shutdown or even log out. Hangs basically forever with: [ *** ] (2 of 2) A start job is running for Hold until boot process finishes up (21s / no limit) or [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit) --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: GNOME Date: Thu Jul 27 10:15:57 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1706939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1271839] Re: ibus-ui-gtk3 big memory leak
I'm impacted with this issue in Ubuntu 17.04. It consumed 6.5GB of my RAM and I killed it after I noticed freezes. I believe it because I used "Suspend" instead of "Turn off" 3 days in a row(though my computer was working 3-5 hours per day. So its around 12-15 hours). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1271839 Title: ibus-ui-gtk3 big memory leak Status in ibus package in Ubuntu: Confirmed Bug description: ubuntu 13.10 64bit 2gb of memory leak Also seen on Ubuntu 14.04 64Bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+subscriptions -- Mailing list: https://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 1704171] Re: WiFi connections unstable
Is there a PPA I need to install? If so, where? I tried "add-apt-repository ppa:kernel-ppa/ppa" but it fails to update with "Err:30 http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu zesty Release 404 Not Found On 09/23/2017 09:44 AM, Kai-Heng Feng wrote: > Try mainline kernel here: > > http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/ > -- 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/1704171 Title: WiFi connections unstable Status in network-manager package in Ubuntu: New Bug description: I have 3 WiFi signals here, and use them all without issue most of the time. Since upgrading to 17.04 I have issues where my wifi will not connect to one of the other 2 signals, then also won't re-connect to the signal that was just in use. When this happens, I can do a 'restart' and it will connect just fine to any of the 3 signals. While it was failing a bit ago, I captured the syslog of whats going on and will include it below. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' (58396782-9fe4-4ce3-b0e6-f72df56c72d5) Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2720] audit: op="connection-activate" uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 result="success" Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2723] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2725] manager: NetworkManager state is now CONNECTING Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to C4:D9:87:6E:9B:0F (permanent) Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.891148] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898132] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898220] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.183332] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190314] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190403] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.274573] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> disabled Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has security, but secrets are required. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has security, and secrets exist. No new secrets needed. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6739] Config: added 'ssid' value 'LisaN' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'scan_ssid' value '1' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'psk' value '' Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:
[Touch-packages] [Bug 1719121] Re: corrected
** Attachment removed: "LightdmLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955783/+files/LightdmLog.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955785/+files/Lsusb.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955784/+files/Lspci.txt ** Summary changed: - corrected + solved ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955786/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955787/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955790/+files/ProcModules.txt ** Attachment removed: "xserver.devices.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955797/+files/xserver.devices.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955788/+files/ProcEnviron.txt ** Attachment removed: "UnitySupportTest.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955792/+files/UnitySupportTest.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955789/+files/ProcInterrupts.txt ** Attachment removed: "Xrandr.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955795/+files/Xrandr.txt ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955793/+files/XorgLog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955791/+files/UdevDb.txt ** Attachment removed: "xdpyinfo.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955796/+files/xdpyinfo.txt ** Attachment removed: "xserver.outputs.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955798/+files/xserver.outputs.txt -- 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/1719121 Title: solved Status in xorg package in Ubuntu: New Bug description: corrected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719121] Re: No wallpaper, borders etc
** Description changed: - I installed some programs (wine, etc) and updated everything that I - could in the Ubuntu Software, after that I restarted the computer and - when I logged in the wallpaper was all black, the characters are darker - (it is harder to see on terminal), there are no border in buttons, etc. - - What can I do? - - ProblemType: Bug - DistroRelease: Ubuntu 16.04 - Package: xorg 1:7.7+13ubuntu3 - ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 - Uname: Linux 4.10.0-35-generic x86_64 - .tmp.unity_support_test.0: - - ApportVersion: 2.20.1-0ubuntu2.10 - Architecture: amd64 - CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' - CompositorRunning: compiz - CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' - CompositorUnredirectFSW: true - CurrentDesktop: Unity - Date: Sat Sep 23 15:45:55 2017 - DistUpgraded: Fresh install - DistroCodename: xenial - DistroVariant: ubuntu - ExtraDebuggingInterest: I just need to know a workaround - GraphicsCard: - Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] - InstallationDate: Installed on 2017-09-23 (0 days ago) - InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) - MachineType: LENOVO 80GA - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=c3654c7e-0369-4b87-b60a-a7b164cdcda5 ro quiet splash vt.handoff=7 - SourcePackage: xorg - Symptom: display - UpgradeStatus: No upgrade log present (probably fresh install) - dmi.bios.date: 10/20/2014 - dmi.bios.vendor: LENOVO - dmi.bios.version: 9ACN29WW - dmi.board.asset.tag: No Asset Tag - dmi.board.name: Lancer 4A2 - dmi.board.vendor: LENOVO - dmi.board.version: SDK0E50515STD - dmi.chassis.asset.tag: No Asset Tag - dmi.chassis.type: 10 - dmi.chassis.vendor: LENOVO - dmi.chassis.version: Lenovo G40-70 - dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn80GA:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrSDK0E50515STD:cvnLENOVO:ct10:cvrLenovoG40-70: - dmi.product.name: 80GA - dmi.product.version: Lenovo G40-70 - dmi.sys.vendor: LENOVO - version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 - version.ia32-libs: ia32-libs N/A - version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 - version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 - version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A - version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 - version.xserver-xorg-core: xserver-xorg-core N/A - version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A - version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A - version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A - version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A - xserver.bootTime: Sat Sep 23 15:27:37 2017 - xserver.configfile: default - xserver.errors: - - xserver.logfile: /var/log/Xorg.0.log - xserver.version: 2:1.19.3-1ubuntu1~16.04.2 - xserver.video_driver: modeset + corrected ** Tags removed: amd64 apport-bug compiz-0.9 ubuntu xenial ** Attachment removed: "BootLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955777/+files/BootLog.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955778/+files/CurrentDmesg.txt ** Summary changed: - No wallpaper, borders etc + corrected ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955779/+files/Dependencies.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955794/+files/XorgLogOld.txt ** Attachment removed: "DpkgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955780/+files/DpkgLog.txt ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955781/+files/JournalErrors.txt ** Attachment removed: "LightdmDisplayLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+attachment/4955782/+files/LightdmDisplayLog.txt -- 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/1719121 Title: corrected Status in xorg package in Ubuntu: New Bug description: corrected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1719121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context
** Changed in: debian-installer-utils (Ubuntu) Status: Confirmed => 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/1714505 Title: systemd kmod builtin uses out of date kmod context Status in systemd: Fix Released Status in debian-installer package in Ubuntu: New Status in debian-installer-utils package in Ubuntu: New Status in systemd package in Ubuntu: Won't Fix Status in debian-installer source package in Trusty: New Status in debian-installer source package in Xenial: New Status in debian-installer source package in Zesty: New Status in debian-installer source package in Artful: New Bug description: [Impact] udev's rules use a built-in 'kmod' instead of the system modprobe/insmod, and this built-in kmod only validates/refreshes its kmod 'context' every 3 seconds (or longer) during event processing. However, because other parts of the system rely on udev to load modules correctly, it is not acceptable for it to use an out of date module context. For example, during a system installation: -the system boots with kernel and initrd with a reduced set of modules, not including nvme module -udevd starts, and creates its kmod module context, which does not include nvme module -system installer adds 'block-modules' udeb, which adds nvme module to system -system installer immediately calls hw-detect->update-dev->udevadm trigger -udevd sees its kmod module context is not more than 3 seconds old, and does not update it -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to load matching driver -udevd kmod builtin does not find NVMe pci modalias because its context is out of date this results in the system installer complaining to the user that it found no disks, even though there is a NVMe drive in the system, and the nvme module is installed in the system. [Test Case] This is reproducable when trying to install using debian-installer and a preseed file that skips all questions, although not on all systems, since other events can cause udevd to reload all its builtins, or the installer may take longer than 3 seconds to call udevadm trigger after installing the nvme module udeb. However, the bug is easily reproducable on any system with a nvme drive using this script: #!/bin/bash MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host modprobe -rq nvme mv $MOD_DIR/nvme.ko . depmod -a sleep 3 udevadm trigger sleep 1 mv nvme.ko $MOD_DIR/ depmod -a udevadm trigger sleep 3 grep -q nvme /proc/partitions && echo PASS || echo FAIL that script does: 1) remove nvme module from the system, reproducing situation where nvme module had not yet been installed 2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds 3) triggers udev, which forces it to reload its kmod context (this could be done with udevadm control -R instead) 4) waits 1 second for the udev trigger to finish, then puts the nvme module back into the system, reproducing the initial installation of the deb/udeb containing the nvme module 5) immediately triggers udev, which should load the nvme module when it sees the nvme pci device 6) wait 3 seconds for udev trigger to finish (plenty of time), and check if the nvme module was loaded this script reproduces the error every time, due to the stale kmod context. With a fixed udev, this should succeed in loading the nvme module. [Regression Potential] The most potential for regression with a fix to this involves slowing down udev due to validating the kmod context for every kmod load call. However, slightly higher performance does not make up for broken operation. [Other Info] This needs fixing upstream, which I'm in progress on. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719136] Re: Ubuntu Budgie - again there is no background picture on try/install
apport information ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** No longer affects: xorg (Ubuntu) ** Tags added: apport-collected staging ** Description changed: the latest daily from which I'm reporting this again has the same reoccurance of the observation in \1713662 i.e. no background wallpaper. Worse - there is no window decoration at all ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: Budgie:GNOME Date: Sat Sep 23 23:06:36 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu-budgie.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170923) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.7-0ubuntu1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ubuntu-budgie 3965 F pulseaudio + CasperVersion: 1.384 + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 17.10 + IwConfig: + lono wireless extensions. + + enp0s3no wireless extensions. + LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170923) + Lsusb: + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + MachineType: innotek GmbH VirtualBox + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 vboxdrmfb + ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity + ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-11-generic N/A + linux-backports-modules-4.13.0-11-generic N/A + linux-firmware 1.168 + RfKill: + + StagingDrivers: vboxvideo + Tags: artful staging + Uname: Linux 4.13.0-11-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/01/2006 + dmi.bios.vendor: innotek GmbH + dmi.bios.version: VirtualBox + dmi.board.name: VirtualBox + dmi.board.vendor: Oracle Corporation + dmi.board.version: 1.2 + dmi.chassis.type: 1 + dmi.chassis.vendor: Oracle Corporation + dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: + dmi.product.family: Virtual Machine + dmi.product.name: VirtualBox + dmi.product.version: 1.2 + dmi.sys.vendor: innotek GmbH ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1719136/+attachment/4955916/+files/AlsaInfo.txt -- 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/1719136 Title: Ubuntu Budgie - again there is no background picture on try/install Status in ubiquity package in Ubuntu: New Bug description: the latest daily from which I'm reporting this again has the same reoccurance of the observation in #1713662 i.e. no background wallpaper. Worse - there is no window decoration at all No idea what has gone wrong this time :( the move to kernel 4.13? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity 17.10.7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: Budgie:GNOME Date: Sat Sep 23 23:06:36 2017 InstallCmdLine: file=/cdrom/preseed/ubuntu-budgie.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu-Budgie 17.10 "Artful Aardvark" - Alpha amd64 (20170923) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1719136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714505] Re: systemd kmod builtin uses out of date kmod context
** Changed in: debian-installer-utils (Ubuntu) Status: New => Confirmed ** Changed in: debian-installer-utils (Ubuntu) Milestone: None => ubuntu-17.09 ** Changed in: debian-installer-utils (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: debian-installer-utils (Ubuntu) Importance: Undecided => Critical -- 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/1714505 Title: systemd kmod builtin uses out of date kmod context Status in systemd: Fix Released Status in debian-installer package in Ubuntu: New Status in debian-installer-utils package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in debian-installer source package in Trusty: New Status in debian-installer source package in Xenial: New Status in debian-installer source package in Zesty: New Status in debian-installer source package in Artful: New Bug description: [Impact] udev's rules use a built-in 'kmod' instead of the system modprobe/insmod, and this built-in kmod only validates/refreshes its kmod 'context' every 3 seconds (or longer) during event processing. However, because other parts of the system rely on udev to load modules correctly, it is not acceptable for it to use an out of date module context. For example, during a system installation: -the system boots with kernel and initrd with a reduced set of modules, not including nvme module -udevd starts, and creates its kmod module context, which does not include nvme module -system installer adds 'block-modules' udeb, which adds nvme module to system -system installer immediately calls hw-detect->update-dev->udevadm trigger -udevd sees its kmod module context is not more than 3 seconds old, and does not update it -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to load matching driver -udevd kmod builtin does not find NVMe pci modalias because its context is out of date this results in the system installer complaining to the user that it found no disks, even though there is a NVMe drive in the system, and the nvme module is installed in the system. [Test Case] This is reproducable when trying to install using debian-installer and a preseed file that skips all questions, although not on all systems, since other events can cause udevd to reload all its builtins, or the installer may take longer than 3 seconds to call udevadm trigger after installing the nvme module udeb. However, the bug is easily reproducable on any system with a nvme drive using this script: #!/bin/bash MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host modprobe -rq nvme mv $MOD_DIR/nvme.ko . depmod -a sleep 3 udevadm trigger sleep 1 mv nvme.ko $MOD_DIR/ depmod -a udevadm trigger sleep 3 grep -q nvme /proc/partitions && echo PASS || echo FAIL that script does: 1) remove nvme module from the system, reproducing situation where nvme module had not yet been installed 2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds 3) triggers udev, which forces it to reload its kmod context (this could be done with udevadm control -R instead) 4) waits 1 second for the udev trigger to finish, then puts the nvme module back into the system, reproducing the initial installation of the deb/udeb containing the nvme module 5) immediately triggers udev, which should load the nvme module when it sees the nvme pci device 6) wait 3 seconds for udev trigger to finish (plenty of time), and check if the nvme module was loaded this script reproduces the error every time, due to the stale kmod context. With a fixed udev, this should succeed in loading the nvme module. [Regression Potential] The most potential for regression with a fix to this involves slowing down udev due to validating the kmod context for every kmod load call. However, slightly higher performance does not make up for broken operation. [Other Info] This needs fixing upstream, which I'm in progress on. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719062] Re: systemd-resolved malformed packet on cert dns lookup
The systemd version you have installed appears to be quite out of date. Could you please upgrade to 234-2ubuntu10? Note that I don't expect that to resolve the issue that you are reporting, but it would significantly reduce the amount of upstream code checks I will need to do before forwarding this bug report to them. -- 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/1719062 Title: systemd-resolved malformed packet on cert dns lookup Status in systemd package in Ubuntu: New Bug description: systemd-resolved returns a malformed packet when looking up an openpgp key (via a cert record rfc4398) from my internal authoritative dns server. The command I used was gpg2 -v --auto-key-locate=clear,cert,local --locate-keys [Email Address] This works correctly if I change /etc/resolv.conf symlink to point at /run/systemd/resolve/resolv.conf so that it doesn't use the local systemd-resolved resolver/cache instead of /run/resolvconf/resolv.conf I'm including a wireshark capture of the malformed packet (filtered for 127.0.0.53). I noticed that this was over udp. If I recall correctly, cert records are usually big enough that they require using tcp. Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 systemd: Installed: 233-8ubuntu3 Candidate: 233-8ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1719062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I was able to work around this issue by following the suggestions on: https://askubuntu.com/questions/833322/pair-bose-quietcomfort-35-with-ubuntu-over-bluetooth and: https://askubuntu.com/questions/689281/pulseaudio-can-not-load-bluetooth-module-15-10-16-04-16-10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
as I don't want to rebuild now again, did anyone try eg. chmod +x ~/myshutdown.sh sudo ~/myshutdown.sh # with echo r > /proc/sysrq-trigger echo e > /proc/sysrq-trigger echo s > /proc/sysrq-trigger echo i > /proc/sysrq-trigger echo u > /proc/sysrq-trigger echo o > /proc/sysrq-trigger -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no
[Touch-packages] [Bug 1719121] [NEW] No wallpaper, borders etc
Public bug reported: I installed some programs (wine, etc) and updated everything that I could in the Ubuntu Software, after that I restarted the computer and when I logged in the wallpaper was all black, the characters are darker (it is harder to see on terminal), there are no border in buttons, etc. What can I do? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 23 15:45:55 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] InstallationDate: Installed on 2017-09-23 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80GA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=c3654c7e-0369-4b87-b60a-a7b164cdcda5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50515STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn80GA:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrSDK0E50515STD:cvnLENOVO:ct10:cvrLenovoG40-70: dmi.product.name: 80GA dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Sep 23 15:27:37 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1719121 Title: No wallpaper, borders etc Status in xorg package in Ubuntu: New Bug description: I installed some programs (wine, etc) and updated everything that I could in the Ubuntu Software, after that I restarted the computer and when I logged in the wallpaper was all black, the characters are darker (it is harder to see on terminal), there are no border in buttons, etc. What can I do? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 23 15:45:55 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380c] InstallationDate: Installed on 2017-09-23 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 80GA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=c3654c7e-0369-4b87-b60a-a7b164cdcda5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (
[Touch-packages] [Bug 1708375] Re: Add support for purple-telegram (telepathy-haze)
Patch updated ** Patch added: "telepathy-purple.patch" https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+attachment/4955775/+files/telepathy-purple.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1708375 Title: Add support for purple-telegram (telepathy-haze) Status in telepathy-mission-control-5 package in Ubuntu: Confirmed Bug description: When using purple telegram through telepathy-haze, it requires following permissions: # for purple telegram /etc/telegram-purple/server.tglpub r, /usr/lib/purple-2*/ r, /usr/lib/purple-2/*.somr, /usr/share/locale/*/LC_MESSAGES/*.mo r, /usr/share/pixmaps/pidgin/protocols/{16,32,48}/*.png r, @{HOME}/.purple/telegram-purple/** rw, @{HOME}/.telegram-purple/** rw, under /usr/lib/telepathy/telepathy-* section. See issue https://github.com/majn/telegram-purple/issues/346 for more details. I have attached the necessary patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1708375/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719038] Re: X Server crashes during log in VM starting from Kubuntu 16.04.2
** Summary changed: - X Server crashes during login in VM 16.04.3 + X Server crashes during log in VM starting from Kubuntu 16.04.2 -- 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/1719038 Title: X Server crashes during log in VM starting from Kubuntu 16.04.2 Status in X.Org X server: Confirmed Status in xorg package in Ubuntu: New Bug description: If I change screen resolution in my VM with Kubuntu 16.04.3 and then make log off and then log on X server is crashes doesn't able me to log in. Please, look in Xorg.0.log.old for backtrace. Also the appropriate report on freedesktop.org: https://bugs.freedesktop.org/show_bug.cgi?id=102554 Host: Kubuntu 17.04 Linux 4.13.2 libvirt-bin 3.6.0 qemu 2.10 Guest: Kubuntu 16.04.3 Linux 4.10.0-35-generic xserver-xorg-video-qxl 0.1.4-3ubuntu3 xserver-common 1.18.4-0ubuntu0.3 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 01:27:49 2017 InstallationDate: Installed on 2016-09-16 (371 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719077] Re: Unable to find codecs to play videos
** Also affects: grilo-plugins via https://bugzilla.gnome.org/show_bug.cgi?id=771215 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1719077 Title: Unable to find codecs to play videos Status in Grilo Plugins: Unknown Status in packagekit package in Ubuntu: In Progress Bug description: To reproduce: 1. Open Totem 2. Go to Channels and select The Guardian Videos 3. Select any video 4. Totem complains about missing codecs 5. GNOME Software then complains that app-install-data is missing See screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 11:54:53 2017 InstallationDate: Installed on 2017-09-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/grilo-plugins/+bug/1719077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719077] Re: Unable to find codecs to play videos
As far as guardian videos this bug doesn't seem to have ever been fixed, if that's true it should be removed from grilo or grilo-plugins https://bugzilla.gnome.org/show_bug.cgi?id=771215 ** Bug watch added: GNOME Bug Tracker #771215 https://bugzilla.gnome.org/show_bug.cgi?id=771215 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1719077 Title: Unable to find codecs to play videos Status in packagekit package in Ubuntu: In Progress Bug description: To reproduce: 1. Open Totem 2. Go to Channels and select The Guardian Videos 3. Select any video 4. Totem complains about missing codecs 5. GNOME Software then complains that app-install-data is missing See screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 11:54:53 2017 InstallationDate: Installed on 2017-09-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1719077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718729] Re: Black screen with a few white pixels on Virtualbox VM
*** This bug is a duplicate of bug 1718679 *** https://bugs.launchpad.net/bugs/1718679 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1718729 Title: Black screen with a few white pixels on Virtualbox VM Status in xorg package in Ubuntu: Confirmed Bug description: I installed Ubuntu 17.04 from a daily image downloaded yesterday in a Virtualbox VM (Host Ubuntu version is 17.04). The installation works fine and without any issues. However, when I install all the updates and reboot, I am no longer able to log in. GDM doesn't start. Instead, I see a completely black screen with a few (one or two) white pixels. I am still able to SSH into the installation after this. Steps to reproduce: * Create a Virtualbox VM * Install Ubuntu 17.10 from daily image (I downloaded mine on 9/20/2017 @ 12:49pm Eastern) * Install all updates (sudo apt-get update && sudo apt-get dist-upgrade) * Reboot ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 Date: Thu Sep 21 12:11:34 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-09-21 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic root=UUID=17aae2c8-ba3d-4c56-92cc-ab06d2c85d68 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.82-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.1-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.1-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1718729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718953] Re: Shift key not working during login
** Description changed: Unable to use capital letters for login password using the shift key. The caps lock key works, as does the graphical keyboard input. After - login, the shift key seems to work. A possible work-around which seems - to be working is to change the keyboard input method from Ibus to none. + login, the shift key seems to work. I am using Ubuntu 16.04.3 with the HWE kernel 4.10.0-35 Description: Ubuntu 16.04.3 LTS Release: 16.04 ** Tags removed: hidpi -- 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/1718953 Title: Shift key not working during login Status in lightdm package in Ubuntu: New Bug description: Unable to use capital letters for login password using the shift key. The caps lock key works, as does the graphical keyboard input. After login, the shift key seems to work. I am using Ubuntu 16.04.3 with the HWE kernel 4.10.0-35 Description: Ubuntu 16.04.3 LTS Release: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1718953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704171] Re: WiFi connections unstable
Try mainline kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/ -- 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/1704171 Title: WiFi connections unstable Status in network-manager package in Ubuntu: New Bug description: I have 3 WiFi signals here, and use them all without issue most of the time. Since upgrading to 17.04 I have issues where my wifi will not connect to one of the other 2 signals, then also won't re-connect to the signal that was just in use. When this happens, I can do a 'restart' and it will connect just fine to any of the 3 signals. While it was failing a bit ago, I captured the syslog of whats going on and will include it below. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' (58396782-9fe4-4ce3-b0e6-f72df56c72d5) Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2720] audit: op="connection-activate" uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 result="success" Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2723] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2725] manager: NetworkManager state is now CONNECTING Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to C4:D9:87:6E:9B:0F (permanent) Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.891148] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898132] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898220] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.183332] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190314] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190403] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.274573] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> disabled Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has security, but secrets are required. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has security, and secrets exist. No new secrets needed. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6739] Config: added 'ssid' value 'LisaN' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'scan_ssid' value '1' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'psk' value '' Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[104
[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
I too am having this issue, and at times now it will not reconnect. *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlan0 version: 3a serial: f0:d5:bf:e6:21:39 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-96-generic firmware=16.242414.0 ip=192.168.37.145 latency=0 link=yes multicast=yes wireless=IEEE 802.11abg resources: irq:134 memory:ddc0-ddc01fff Dell precision 5510, Ubuntu 16.04 lts. I only use WiFi, no hardwired Ethernet connection. -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.15 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi
[Touch-packages] [Bug 1718682] Re: package linux-image-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1718682 Title: package linux-image-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: no idea, suddenly it is showing partial upgrading problem ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-96-generic 4.4.0-96.119 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sivaadmin 3460 F pulseaudio Date: Thu Sep 21 19:19:45 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=a4723785-6d39-41b0-9715-918c218979fa InstallationDate: Installed on 2016-07-31 (417 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80G0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=72a9183c-f5e9-463f-bdf8-5207bded6d76 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82990WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719077] Re: Unable to find codecs to play videos
Just tried latest image updated. See no issue with local files that gst supports As far as channels the guardian one is broken, apple trailers is ok Ex. guardian - $ totem (totem:1847): GLib-CRITICAL **: g_key_file_load_from_file: assertion 'file != NULL' failed ** Message: Missing plugin: gstreamer|1.0|totem|text/html decoder|decoder-text/html (text/html decoder) apple-trailers $ totem (totem:1847): GLib-CRITICAL **: g_key_file_load_from_file: assertion 'file != NULL' failed ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)2, base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder) ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, level=(string)3, profile=(string)main, colorimetry=(string)bt709 (H.264 (Main Profile) decoder) ** Message: PackageKit: xid = 39845909 ** Message: PackageKit: desktop_id = org.gnome.Totem.desktop ** Message: PackageKit: Codec nice name: MPEG-4 AAC decoder ** Message: PackageKit: ignoring field named level ** Message: PackageKit: ignoring field named base-profile ** Message: PackageKit: ignoring field named profile ** Message: PackageKit: field is: mpegversion, type: gint ** Message: PackageKit: structure: gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit) ** Message: PackageKit: Codec nice name: H.264 (Main Profile) decoder ** Message: PackageKit: ignoring field named level ** Message: PackageKit: ignoring field named profile ** Message: PackageKit: ignoring field named colorimetry ** Message: PackageKit: structure: gstreamer1(decoder-video/x-h264)()(64bit) ** Message: Missing plugins installed. Updating plugin registry ... ** Message: Plugin registry updated, trying again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1719077 Title: Unable to find codecs to play videos Status in packagekit package in Ubuntu: In Progress Bug description: To reproduce: 1. Open Totem 2. Go to Channels and select The Guardian Videos 3. Select any video 4. Totem complains about missing codecs 5. GNOME Software then complains that app-install-data is missing See screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 11:54:53 2017 InstallationDate: Installed on 2017-09-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1719077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704171] Re: WiFi connections unstable
lisa@lisa-Inspiron-7720:~$ uname -a Linux lisa-Inspiron-7720 4.10.0-35-generic #39-Ubuntu SMP Wed Sep 13 07:46:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Still an issue! I REALLY hate it when I have to say WINDOWS works perfectly fine when I dual-boot to it vs. Ubuntu 17.04. Even when I switch to a different Wifi this issue happens. I end up rebooting and it will work once again... -- 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/1704171 Title: WiFi connections unstable Status in network-manager package in Ubuntu: New Bug description: I have 3 WiFi signals here, and use them all without issue most of the time. Since upgrading to 17.04 I have issues where my wifi will not connect to one of the other 2 signals, then also won't re-connect to the signal that was just in use. When this happens, I can do a 'restart' and it will connect just fine to any of the 3 signals. While it was failing a bit ago, I captured the syslog of whats going on and will include it below. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' (58396782-9fe4-4ce3-b0e6-f72df56c72d5) Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2720] audit: op="connection-activate" uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 result="success" Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2723] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2725] manager: NetworkManager state is now CONNECTING Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to C4:D9:87:6E:9B:0F (permanent) Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.891148] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898132] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898220] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.183332] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190314] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190403] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.274573] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> disabled Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has security, but secrets are required. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has security, and secrets exist. No new secrets needed. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6739] Config: added 'ssid' value 'LisaN' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'scan_ssid' value '1' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'psk' value '' Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget wh
[Touch-packages] [Bug 1719096] [NEW] package libsigc++-2.0-0v5 2.10.0-1 [modified: usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz] failed to install/upgrade: a tentar sobreescrever '/usr/share/do
Public bug reported: vbam-gtk emulator install failed ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libsigc++-2.0-0v5 2.10.0-1 [modified: usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: libsigc++-2.0-0v5:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 23 11:40:35 2017 Dependencies: gcc-7-base 7-20170407-0ubuntu2 [origin: LP-PPA-ubuntu-toolchain-r-test] libc6 2.24-9ubuntu2.2 libgcc1 1:7-20170407-0ubuntu2 [origin: LP-PPA-ubuntu-toolchain-r-test] libstdc++6 7-20170407-0ubuntu2 [origin: LP-PPA-ubuntu-toolchain-r-test] DpkgTerminalLog: A preparar para desempacotar .../libsigc++-2.0-0v5_2.10.0-1_i386.deb ... A descompactar libsigc++-2.0-0v5:i386 (2.10.0-1) sobre (2.6.2-1) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/libsigc++-2.0-0v5_2.10.0-1_i386.deb (--unpack): a tentar sobreescrever '/usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libsigc++-2.0-0v5:i386 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libsigc++-2.0-0v5:i386 InstallationDate: Installed on 2017-09-21 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: libsigc++-2.0 Title: package libsigc++-2.0-0v5 2.10.0-1 [modified: usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz] failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libsigc++-2.0-0v5:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libsigc++-2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsigc++-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1719096 Title: package libsigc++-2.0-0v5 2.10.0-1 [modified: usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz] failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libsigc++-2.0-0v5:i386 Status in libsigc++-2.0 package in Ubuntu: New Bug description: vbam-gtk emulator install failed ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libsigc++-2.0-0v5 2.10.0-1 [modified: usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 AptOrdering: libsigc++-2.0-0v5:i386: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 23 11:40:35 2017 Dependencies: gcc-7-base 7-20170407-0ubuntu2 [origin: LP-PPA-ubuntu-toolchain-r-test] libc6 2.24-9ubuntu2.2 libgcc1 1:7-20170407-0ubuntu2 [origin: LP-PPA-ubuntu-toolchain-r-test] libstdc++6 7-20170407-0ubuntu2 [origin: LP-PPA-ubuntu-toolchain-r-test] DpkgTerminalLog: A preparar para desempacotar .../libsigc++-2.0-0v5_2.10.0-1_i386.deb ... A descompactar libsigc++-2.0-0v5:i386 (2.10.0-1) sobre (2.6.2-1) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/libsigc++-2.0-0v5_2.10.0-1_i386.deb (--unpack): a tentar sobreescrever '/usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libsigc++-2.0-0v5:i386 ErrorMessage: a tentar sobreescrever '/usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libsigc++-2.0-0v5:i386 InstallationDate: Installed on 2017-09-21 (1 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: libsigc++-2.0 Title: package libsigc++-2.0-0v5 2.10.0-1 [modified: usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz] failed to install/upgrade: a tentar sobreescrever '/usr/share/doc/libsigc++-2.0-0v5/changelog.Debian.gz' partilhado, que é diferente de outras instâncias do pacote libsigc++-2.0-0v5:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsigc++-2.0/+bug/1719096/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
Used the same test that Sondra on #43 and also with no luck on any theme Lubuntu 17.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: In Progress Status in abiword package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Confirmed Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround for Ubuntu 16.04 LTS === 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716137] Re: Error message using easy-codec-install (gstreamer1.0-packagekit) is not useful & confusing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: packagekit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1716137 Title: Error message using easy-codec-install (gstreamer1.0-packagekit) is not useful & confusing Status in packagekit package in Ubuntu: Confirmed Bug description: See attached screen Test case: On a fresh install or if on existing make sure the gst bad, ugly, libav & vaapi plugins aren't installed. Try to open a h.264 video or .mp3, .m4a in totem When prompted click on the find in Software button Error message will appear at top of Software window ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gstreamer1.0-packagekit 1.1.6-2 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 9 10:56:17 2017 InstallationDate: Installed on 2017-09-07 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: packagekit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1716137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719077] Re: Unable to find codecs to play videos
Indeed, I can reproduce this. This issue affects Debian as well, and I wonder why nobody noticed it so far. I have an idea on how to fix it. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Matthias Klumpp (ximion) ** Changed in: gnome-software (Ubuntu) Status: Confirmed => In Progress ** Package changed: gnome-software (Ubuntu) => packagekit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1719077 Title: Unable to find codecs to play videos Status in packagekit package in Ubuntu: In Progress Bug description: To reproduce: 1. Open Totem 2. Go to Channels and select The Guardian Videos 3. Select any video 4. Totem complains about missing codecs 5. GNOME Software then complains that app-install-data is missing See screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 11:54:53 2017 InstallationDate: Installed on 2017-09-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1719077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719077] [NEW] Unable to find codecs to play videos
You have been subscribed to a public bug: To reproduce: 1. Open Totem 2. Go to Channels and select The Guardian Videos 3. Select any video 4. Totem complains about missing codecs 5. GNOME Software then complains that app-install-data is missing See screenshots. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-software 3.26.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 23 11:54:53 2017 InstallationDate: Installed on 2017-09-21 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.26.0-0ubuntu2 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: packagekit (Ubuntu) Importance: Undecided Assignee: Matthias Klumpp (ximion) Status: In Progress ** Tags: amd64 apport-bug artful -- Unable to find codecs to play videos https://bugs.launchpad.net/bugs/1719077 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658273] Re: Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
Same error. Ubuntu 17.04 last updated on 23/09/2017. -- 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/1658273 Title: Failed to preset unit: Unit file /etc/systemd/system/samba-ad- dc.service is masked. Status in samba package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: On a standalone desktop running zesty with a gnome-shell session, when upgrading the samba packages, i get: Setting up samba (2:4.4.5+dfsg-2ubuntu7) ... Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked. /usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory note: ubuntu-bug ask questions about a possible windows relationship, but there is no option for a standalone system like that one; so as samba is installed to satisfy qemu, these questions completly ignore such case and send inappropriate report. and smbd still crashing on cold boot ( lp:1658293 ) (standalone desktop) note2: a more recent Debian version seems workaround that output: samba (2:4.4.5+dfsg-3) [ Mathieu Parent ] * Remove /etc/systemd/system/samba-ad-dc.service (from postinst) on purge. Closes: #832352 and samba (2:4.4.6+dfsg-1) Only fix PIDFile in {nmbd,samba-ad-dc,smbd,winbind}.service (i.e. not ctdb.service) Closes: #838000. and samba (2:4.4.6+dfsg-2) * Remove uses of tevent internals. This fixes segfault. Closes: #840382, #840298. http://metadata.ftp-master.debian.org/changelogs/main/s/samba/samba_4.5.2+dfsg-2_changelog ... time to get package synced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1658273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620636] Re: Fails to pair with Bose QC35 headphones
The head phone pairs, the microphone does not. Further, the sound still is very low and jittery. Useless to listen to music over this device under these conditions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1620636 Title: Fails to pair with Bose QC35 headphones Status in Canonical System Image: In Progress Status in bluez package in Ubuntu: In Progress Bug description: I am unable to pair the Bose QC35 BT headphones with Ubuntu, either Ubuntu desktop running 16.04 LTS with bluez 5.37 (also tried bluez 5.41 from installed from yakkety archive), nor using Ubuntu Touch rc- proposed build for Turbo #174. I'm trying to pair through the normal bluetooth control panel brought up through the bluetooth indicator. I've attached some logs that show it failing to pair. If I can provide anymore useful information about the headphones, please let me know. Syslog with bluetoothd debugging enabled: http://pastebin.ubuntu.com/23141394/ btmon output: http://pastebin.ubuntu.com/23141446/ bluetoothctl output: http://pastebin.ubuntu.com/23141510/ With Linux kernel 4.8.0 and bluez 4.52: --- bluetoothctl: http://pastebin.ubuntu.com/23256457/ btmon: http://pastebin.ubuntu.com/23256471/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620636/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1600351] Re: package libsm6:i386 2:1.2.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
the contents of the postinst script is: #!/bin/sh set -e # Automatically added by dh_makeshlibs if [ "$1" = "configure" ]; then ldconfig fi # End automatically added section nothing unusual there, your system was messed up somehow, so closing the bug ** Changed in: libsm (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libsm in Ubuntu. https://bugs.launchpad.net/bugs/1600351 Title: package libsm6:i386 2:1.2.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in libsm package in Ubuntu: Invalid Bug description: boot system error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsm6:i386 2:1.2.2-1 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Jul 8 15:42:34 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-07-08 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libsm Title: package libsm6:i386 2:1.2.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsm/+bug/1600351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1187730] Re: Missing "sys/resource.ph"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: perl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1187730 Title: Missing "sys/resource.ph" Status in perl package in Ubuntu: Confirmed Bug description: "sys/resource.ph" is missing in perl package. $ dpkg -l perl | tail -n1 ii perl5.14.2-21 i386 Larry Wall's Practical Extraction and Report Language $ perl -e "require 'sys/resource.ph';" Can't locate sys/resource.ph in @INC (did you run h2ph?) (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at -e line 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1187730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install
** Changed in: gstreamer1.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1562875 Title: Totem can't play H264 on fresh 16.04 beta install Status in gstreamer1.0 package in Ubuntu: Fix Released Bug description: Totem can't play neither find the correct codec to play H264 *.mp4 video in last 16.04 beta. Terminal says : ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile) decoder|decoder-video/x-h264, stream-format=(string)avc, alignment=(string)au, level=(string)4, profile=(string)main, max- input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile) decoder) Totem tries to find the correct codec but fails, see attachment ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 28 15:51:47 2016 InstallationDate: Installed on 2016-03-26 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: amixer: Mixer attach default error: No such file or directory ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1562875/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1712979] Re: Installation of missing plugins/codecs fails or is gstreamer1.0-packagekit what's needed?
I filed a new bug #1719077. ** Changed in: gnome-software (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1712979 Title: Installation of missing plugins/codecs fails or is gstreamer1.0-packagekit what's needed? Status in GNOME Software: Confirmed Status in gnome-software package in Ubuntu: Confirmed Status in totem package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: Test case: Fresh install Try to play any file requiring one or more gst plugins What happens: pop up informs plugin(s) missing, offers to 'find in software' Clicking on that option fails Ex. totem /home/doug/Videos/bbb_sunflower_1080p_30fps_normal.mp4 ** Message: Missing plugin: gstreamer|1.0|totem|MPEG-1 Layer 3 (MP3) decoder|decoder-audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder) ** Message: Missing plugin: gstreamer|1.0|totem|AC-3 (ATSC A/52) decoder|decoder-audio/x-ac3 (AC-3 (ATSC A/52) decoder) ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (High Profile) decoder|decoder-video/x-h264, level=(string)4.1, profile=(string)high (H.264 (High Profile) decoder) ** Message: Automatic missing codec installation not supported (helper script missing) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 25 01:51:47 2017 InstallationDate: Installed on 2017-08-20 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1712979/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719067] Re: log entry "unattended-upgrade -d" implies "debug" option but "download only" is meant
** Summary changed: - log entry "unattended-upgrade -d" is misleading + log entry "unattended-upgrade -d" implies "debug" option but "download only" is meant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1719067 Title: log entry "unattended-upgrade -d" implies "debug" option but "download only" is meant Status in apt package in Ubuntu: New Bug description: The script /usr/lib/apt/apt.systemd.daily produces log entries in the systemd journal like unattended-upgrade -d (success) or unattended-upgrade -d (error) These seem to imply that "unattended-upgrade" was run with the command line flag "-d", which according to the manpage means "debug". But actually "unattended-upgrade" was run with the option "--download- only". I would be easier to understand and debug the u-a behavior if the log entries would reflect this clearly. (Ubuntu 16.04.3 LTS, apt 1.2.24) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 10:18:06 2017 InstallationDate: Installed on 2014-08-28 (1121 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-20 (490 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1719067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719067] [NEW] log entry "unattended-upgrade -d" is misleading
Public bug reported: The script /usr/lib/apt/apt.systemd.daily produces log entries in the systemd journal like unattended-upgrade -d (success) or unattended-upgrade -d (error) These seem to imply that "unattended-upgrade" was run with the command line flag "-d", which according to the manpage means "debug". But actually "unattended-upgrade" was run with the option "--download- only". I would be easier to understand and debug the u-a behavior if the log entries would reflect this clearly. (Ubuntu 16.04.3 LTS, apt 1.2.24) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 10:18:06 2017 InstallationDate: Installed on 2014-08-28 (1121 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-20 (490 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1719067/+attachment/4955510/+files/JournalErrors.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1719067/+attachment/4955512/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1719067/+attachment/4955511/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1719067 Title: log entry "unattended-upgrade -d" is misleading Status in apt package in Ubuntu: New Bug description: The script /usr/lib/apt/apt.systemd.daily produces log entries in the systemd journal like unattended-upgrade -d (success) or unattended-upgrade -d (error) These seem to imply that "unattended-upgrade" was run with the command line flag "-d", which according to the manpage means "debug". But actually "unattended-upgrade" was run with the option "--download- only". I would be easier to understand and debug the u-a behavior if the log entries would reflect this clearly. (Ubuntu 16.04.3 LTS, apt 1.2.24) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apt 1.2.24 ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 23 10:18:06 2017 InstallationDate: Installed on 2014-08-28 (1121 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: apt UpgradeStatus: Upgraded to xenial on 2016-05-20 (490 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1719067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624644] Re: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software.
Anyway, in my view Unattended-Upgrade::Remove-Unused-Dependencies "true"; would be the default setting to have now, and advanced users should mark the dependencies of their unpackaged software as "manual". -- 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/1624644 Title: By default settings unattended-upgrade is unable to automatically remove packages that become unused in conjunction with updating by other software. Status in apt package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: New Status in update-manager package in Ubuntu: New Status in apt source package in Artful: New Status in gnome-software source package in Artful: New Status in unattended-upgrades source package in Artful: New Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrade i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, unattended-upgrade is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because unattended-upgrade compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. Consequently, if user installs new kernels using e.g. update-manager, the excessive kernels will not be removed by unattended-upgrade, and eventually (small) /boot will become full. Expected behavior: handle removing of unused packages differently at least until other package management software installed by default can handle removing of new unused packages. ProblemType: Bug DistroRelease: 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:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 231675] Re: yay just a note
Hello! I've just wished to say Hi and show you some cool things, check it out http://www.77dfg.com/admin_XySetSail/ueditor/third-party/SyntaxHighlighter/quality.php?UE8yMzE2NzVAYnVncy5sYXVuY2hwYWQubmV0 Bests, Sean Heron - You may choose to restrict the collection or use of your personal information in the following ways: whenever you are asked to fill in a form on the website, look for the box that you can click to indicate that you do not want the information to be used by anybody for direct marketing purposes if you have previously agreed to us using your personal information for direct marketing purposes, you may change your mind at any time by writing to or emailing us. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/231675 Title: wanted to install skype (manually), but it gave errors Status in qt4-x11 package in Ubuntu: Invalid Bug description: I downloaded the package from the skype website and when I wanted to install it, the package manager said it was unable to open/ unpack a dependency. ProblemType: Package Architecture: i386 Date: Sun May 18 17:28:03 2008 Dependencies: DistroRelease: Ubuntu 8.04 ErrorMessage: nicht ganz gelesen in buffer_copy (Backend dpkg-deb während »./usr/lib/libQtGui.so.4.3.4«) NonfreeKernelModules: fglrx Package: libqt4-gui None [modified: /var/lib/dpkg/info/libqt4-gui.list] PackageArchitecture: i386 SourcePackage: qt4-x11 Title: package libqt4-gui None [modified: /var/lib/dpkg/info/libqt4-gui.list] failed to install/upgrade: nicht ganz gelesen in buffer_copy (Backend dpkg-deb während »./usr/lib/libQtGui.so.4.3.4«) Uname: Linux 2.6.24-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/231675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp