[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working in Bionic
Another computer ** Attachment added: "T.txt" https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+attachment/5178023/+files/T.txt -- 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/1766872 Title: 'Enable Network' in recovery mode not working in Bionic Status in friendly-recovery package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions -- Mailing list: https://launchpad.net/~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 1766872] Re: 'Enable Network' in recovery mode not working in Bionic
Hello My ubuntu version is 18.04.1 cat /etc/lsb* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" It works very well. But thinking that someday, this could not be the case, I decided to check if the recovery mode works function "fsck" works function "dpg" works but function "enable network support" hangs. dmesg | grep vmlinuz [0.00] Command line: \\boot\vmlinuz-4.15.0-32-generic recovery root=UUID=cb50473a-5d9c-441a-9502-690c1c8684d6 ro initrd=\boot\initrd.img-4.15.0-32-generic [0.00] Kernel command line: \\boot\vmlinuz-4.15.0-32-generic recovery root=UUID=cb50473a- it is necessary to press the ctrl c keys to unlock the situation. (checked with two different computers. Attachment: contents of the start trace ** Attachment added: "dmesg trace" https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+attachment/5177864/+files/TRACE.txt -- 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/1766872 Title: 'Enable Network' in recovery mode not working in Bionic Status in friendly-recovery package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions -- Mailing list: https://launchpad.net/~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 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.
*** This bug is a duplicate of bug 1652282 *** https://bugs.launchpad.net/bugs/1652282 Hello With version 18.04.1 gparted works but two messages are displayed a@a:~$ sudo gparted Unit -.mount does not exist, proceeding anyway. Gtk-Message: 10:50:03.294: Failed to load module "canberra-gtk-module" == libparted : 3.2 == -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1744372 Title: gparted does not start - Unit -.mount does not exist, proceeding anyway. Status in gparted package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Invalid Bug description: 1. fresh ubuntu 18.04 daily: lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 2. install gparted with Software: gparted: Installiert: 0.30.0-3ubuntu1 Installationskandidat: 0.30.0-3ubuntu1 Versionstabelle: *** 0.30.0-3ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3. launch with icon - enter password - nothing. 4.launch in terminal: Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. How to Fix: run xhost +local: before gparted! # this only bypass the wayland restriction; meaning a security violation (not a fix !!! ) thomas@ubuntu-1804:~$ xhost +local: non-network local connections being added to access control list thomas@ubuntu-1804:~$ gparted Unit -.mount does not exist, proceeding anyway. Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/boot-efi.mount → /dev/null. Created symlink /run/systemd/system/home.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null. Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-120.mount → /dev/null. Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null. Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. Gtk-Message: Failed to load module "canberra-gtk-module" == libparted : 3.2 == Removed /run/systemd/system/-.mount. Removed /run/systemd/system/boot-efi.mount. Removed /run/systemd/system/home.mount. Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount. Removed /run/systemd/system/run-snapd-ns.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-120.mount. Removed /run/systemd/system/snap-core-3748.mount. Removed /run/systemd/system/snap-vlc-113.mount. Removed /run/systemd/system/tmp.mount. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gparted 0.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 19 19:45:14 2018 InstallationDate: Installed on 2018-01-18 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gparted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1744372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1738781] Re: networkmanager does not recognize the names of the internet servers
Hello I found a trick to work around the problem echo "servername 8.8.8.8"> /bin/resolvconf/resolv.conf You should not have too much trouble adding, at the end of the network activation sequence in recovery mode, a test of absence of this file and create it in order to avoid us to do it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~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 1738781] Re: networkmanager does not recognize the names of the internet servers
journalctl -xe ** Attachment added: "journalctl -xe" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024158/+files/T5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~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 1738781] Re: networkmanager does not recognize the names of the internet servers
manual copy of the network restarting command ** Attachment added: "manual copy of the network restarting command" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024124/+files/T3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~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 1738781] Re: networkmanager does not recognize the names of the internet servers
systemctl status Networkmanager.service ** Attachment added: "systemctl status Networkmanager.servic" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024125/+files/T4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~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 1738781] Re: networkmanager does not recognize the names of the internet servers
good ping ** Attachment added: "good ping" https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+attachment/5024123/+files/T2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~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 1738781] [NEW] networkmanager does not recognize the names of the internet servers
Public bug reported: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu version" https://bugs.launchpad.net/bugs/1738781/+attachment/5024121/+files/T1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1738781 Title: networkmanager does not recognize the names of the internet servers Status in resolvconf package in Ubuntu: New Bug description: Hello My 17.10 ubuntu session loops on the password request probably following the installation of version 4.13.0-19 I decide to use the RECOVERY mode fsck command network activation dpkg command choice to become the ROOT user command ping 8.8.8.8 gives excellent response times command ping www,google.com returns UNKNOWN HOST I decided to run an ubuntu instance 16.04 LTS which works perfectly well to check if ping www.google.com is known. It is well recognized. But when I decide to restart ubuntu 16.04 in recovery mode, i have the same problem (unkwon host). Here are some traces made in version 16.04 a) ubuntu version b) good ping c) manual copy of the network restarting command d) systemctl status Networkmanager.service e) journalctl -xe What to do to make the network work normally in RECOVERY mode? networkmanager does not recognize the names of the internet servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1738781/+subscriptions -- Mailing list: https://launchpad.net/~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 1608881] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Hello It when i accept upgrade from 14.04.4 to 16.04.1 I don't known if it is a problem of trigger. This bug is collected just after reboot on 16.04.1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Aug 1 17:08:48 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-11-02 (273 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1608881 Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: New Bug description: Hello It when i accept upgrade from 14.04.4 to 16.04.1 I don't known if it is a problem of trigger. This bug is collected just after reboot on 16.04.1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Aug 1 17:08:48 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2015-11-02 (273 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1608881/+subscriptions -- Mailing list: https://launchpad.net/~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 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)
*** This bug is a duplicate of bug 1584509 *** https://bugs.launchpad.net/bugs/1584509 So it it necessary to do this command sudo mount /dev/sr0/mnt and seeing the contents u1604@u1604:/mnt$ ls -l total 31 dr-xr-xr-x 3 root root 2048 avril 3 2012 boot dr-xr-xr-x 2 root root 2048 avril 21 2014 casper dr-xr-xr-x 2 root root 18432 avril 10 2012 isolinux -r--r--r-- 1 root root 8381 avril 21 2014 md5sum.txt u1604@u1604:/mnt$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1577768 Title: 16.04 some dvd do not mount automatically (but do in 14.04) Status in gvfs package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Fix Released Bug description: Hi, here is a dvd. And ubuntu 16.04. When I insert that dvd, it does not show anywhere, neither in launcher nor in nautilus. But I'm able to read that dvd using vlc through menu media / open a disc. I can manually mount that dvd with sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/ Once mounted there's a dvd icon in launcher and it appears also in nautilus left panel. That same dvd automatically mounts when running ubuntu 14.04 on the same computer. I have also tested other dvd's on ubuntu 16.04 and *most* of them show / mount as expected. But *all* of them automatically show / mount in ubuntu 14.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+subscriptions -- Mailing list: https://launchpad.net/~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 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)
*** This bug is a duplicate of bug 1584509 ***
https://bugs.launchpad.net/bugs/1584509
Hello
I have also this bug with 16.04
My kernel is 4.7
u1604@u1604:~$ dpkg -l | awk '/ +linux/ && /headers|generic/{
if(match($2,/([0-9]\.)+/)) {print $2} }'|sort -t- -rV -k3,4|paste -d" " -
linux-signed-image-4.4.0-24-generic
linux-image-extra-4.4.0-24-generic
linux-image-4.7.0-040700rc2-generic
linux-headers-4.7.0-040700rc2-lowlatency
linux-headers-4.7.0-040700rc2-generic
linux-headers-4.7.0-040700rc2
linux-image-4.4.0-24-generic
linux-headers-4.4.0-24-generic
linux-headers-4.4.0-24
u1604@u1604:~$
My dmesg
[ 727.495823] sr 4:0:0:0: [sr0] tag#19 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 727.495833] sr 4:0:0:0: [sr0] tag#19 Sense Key : Illegal Request [current]
[ 727.495839] sr 4:0:0:0: [sr0] tag#19 Add. Sense: Illegal mode for this track
[ 727.495844] sr 4:0:0:0: [sr0] tag#19 CDB: Read(10) 28 00 00 05 7a 82 00 00
02 00
[ 727.495848] blk_update_request: I/O error, dev sr0, sector 1436168
[ 729.934623] sr 4:0:0:0: [sr0] tag#21 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 729.934633] sr 4:0:0:0: [sr0] tag#21 Sense Key : Illegal Request [current]
[ 729.934638] sr 4:0:0:0: [sr0] tag#21 Add. Sense: Illegal mode for this track
[ 729.934644] sr 4:0:0:0: [sr0] tag#21 CDB: Read(10) 28 00 00 05 7a 83 00 00
01 00
[ 729.934648] blk_update_request: I/O error, dev sr0, sector 1436172
[ 729.934653] Buffer I/O error on dev sr0, logical block 359043, async page
read
My files 4.7 are
u1604@u1604:~/Téléchargements$ ls -l
total 124916
-rwxrwxrwx 1 root root 9964354 juin 7 18:57
linux-headers-4.7.0-040700rc2_4.7.0-040700rc2.201606051831_all.deb
-rwxrwxrwx 1 root root 1072436 juin 7 18:42
linux-headers-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb
-rwxrwxrwx 1 root root 1073438 juin 7 18:43
linux-headers-4.7.0-040700rc2-lowlatency_4.7.0-040700rc2.201606051831_amd64.deb
-rwxrwxrwx 1 root root 57911030 juin 7 19:52
linux-image-4.7.0-040700rc2-generic_4.7.0-040700rc2.201606051831_amd64.deb
-rwxrwxrwx 1 root root 57881694 juin 7 19:53
linux-image-4.7.0-040700rc2-lowlatency_4.7.0-040700rc2.201606051831_amd64.deb
u1604@u1604:~/Téléchargements$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1577768
Title:
16.04 some dvd do not mount automatically (but do in 14.04)
Status in gvfs package in Ubuntu:
Invalid
Status in nautilus package in Ubuntu:
Invalid
Status in util-linux package in Ubuntu:
Fix Released
Bug description:
Hi,
here is a dvd. And ubuntu 16.04.
When I insert that dvd, it does not show anywhere, neither in launcher
nor in nautilus.
But I'm able to read that dvd using vlc through menu media / open a
disc.
I can manually mount that dvd with
sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/
Once mounted there's a dvd icon in launcher and it appears also in
nautilus left panel.
That same dvd automatically mounts when running ubuntu 14.04 on the
same computer.
I have also tested other dvd's on ubuntu 16.04 and *most* of them show
/ mount as expected.
But *all* of them automatically show / mount in ubuntu 14.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+subscriptions
--
Mailing list: https://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 1424860] Re: Unable to mount iPad: Unhandled lockdown error (-20)
Le 29/03/2015 19:01, Timur Tabi a écrit : > I think updating to the latest libimobiledevice (v 1.2) might fix this > problem. That version is supposed to add iOS 8 support. > So , i load http://www.libimobiledevice.org/downloads/libimobiledevice-1.2.0.tar.bz2 The contents are -rw-r--r-- 1 bougron bougron 56634 janv. 28 23:15 aclocal.m4 -rw-r--r-- 1 bougron bougron294 oct. 21 2012 AUTHORS drwxr-xr-x 2 bougron bougron 4096 janv. 29 00:08 common -rwxr-xr-x 1 bougron bougron 7333 sept. 25 2014 compile -rwxr-xr-x 1 bougron bougron 45640 sept. 25 2014 config.guess -rw-r--r-- 1 bougron bougron 4713 janv. 28 23:15 config.h.in -rwxr-xr-x 1 bougron bougron 35521 sept. 25 2014 config.sub -rwxr-xr-x 1 bougron bougron 638745 janv. 28 23:15 configure -rw-r--r-- 1 bougron bougron 7469 janv. 28 23:14 configure.ac -rw-r--r-- 1 bougron bougron 17988 avril 11 2009 COPYING -rw-r--r-- 1 bougron bougron 26434 avril 11 2009 COPYING.LESSER drwxr-xr-x 2 bougron bougron 4096 janv. 29 00:08 cython -rwxr-xr-x 1 bougron bougron 23566 sept. 25 2014 depcomp drwxr-xr-x 3 bougron bougron 4096 janv. 28 23:15 docs -rw-r--r-- 1 bougron bougron 101703 janv. 28 23:14 doxygen.cfg.in drwxr-xr-x 3 bougron bougron 4096 janv. 29 00:08 include -rwxr-xr-x 1 bougron bougron 13997 sept. 25 2014 install-sh -rw-r--r-- 1 bougron bougron 283474 sept. 25 2014 ltmain.sh drwxr-xr-x 2 bougron bougron 4096 janv. 29 00:08 m4 -rw-r--r-- 1 bougron bougron372 janv. 28 23:14 Makefile.am -rw-r--r-- 1 bougron bougron 27136 janv. 28 23:15 Makefile.in -rwxr-xr-x 1 bougron bougron 6873 sept. 25 2014 missing -rw-r--r-- 1 bougron bougron 19892 janv. 28 23:14 NEWS -rw-r--r-- 1 bougron bougron 1147 janv. 28 18:26 README drwxr-xr-x 2 bougron bougron 4096 janv. 29 00:08 src drwxr-xr-x 2 bougron bougron 4096 janv. 29 00:08 tools * The content of README for installation say Installation To compile run: ./autogen.sh make sudo make install But there is no autogen.sh file! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1424860 Title: Unable to mount iPad: Unhandled lockdown error (-20) Status in libimobiledevice package in Ubuntu: Confirmed Bug description: My bug is not exactly like bug 1385882 My iPad is on version 8.1.3 My ubuntu version (14.04.1) use linux 3.13.0.45 So it is possible to use my iPad Because of others problems , i want to use new version of ubuntu (14.04.2) using linux version 3.16.0.30 It is not possible for me to use iPad with this message "Unable to mount iPad: Unhandled lockdown error (-20)" Perhaps another consequence: i can't use the iPad like a modem to connect on internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1424860/+subscriptions -- Mailing list: https://launchpad.net/~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 1424860] Re: Unable to mount iPad: Unhandled lockdown error (-20)
Hello http://www.libimobiledevice.org/said Packages: openSUSE openSUSE or 1-Click Install (openSUSE 13.2) Fedora Fedora (Packages in the official repositories) Debian Debian Ubuntu Ubuntu (Packages in the official repositories) My question Do you known the name of these packages? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1424860 Title: Unable to mount iPad: Unhandled lockdown error (-20) Status in libimobiledevice package in Ubuntu: New Bug description: My bug is not exactly like bug 1385882 My iPad is on version 8.1.3 My ubuntu version (14.04.1) use linux 3.13.0.45 So it is possible to use my iPad Because of others problems , i want to use new version of ubuntu (14.04.2) using linux version 3.16.0.30 It is not possible for me to use iPad with this message "Unable to mount iPad: Unhandled lockdown error (-20)" Perhaps another consequence: i can't use the iPad like a modem to connect on internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1424860/+subscriptions -- Mailing list: https://launchpad.net/~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 1425038] Re: Can't use iPad as modem ubuntu 14.04.2 (linux 3.16.0.30)
** Attachment added: "trace of syslog when i connect iPad with USB cable" https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1425038/+attachment/4326224/+files/SYSLOG1.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1425038 Title: Can't use iPad as modem ubuntu 14.04.2 (linux 3.16.0.30) Status in libimobiledevice package in Ubuntu: New Bug description: Hello When i use ubuntu 14.04.1 (linux 3.13.0.45) it is possible for me to use my iPad (8.1.3) as a modem. So i can use internet anywhere. Since a few days, i have installed ubuntu 14.04.2 (linux 3.16.0.30) but it is not possible for me to use my iPad as a modem. Why? I am not sure that it is the same reason explained in bug 1424860 NB. i connect the iPad with the usb cable to the computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1425038/+subscriptions -- Mailing list: https://launchpad.net/~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 1425038] [NEW] Can't use iPad as modem ubuntu 14.04.2 (linux 3.16.0.30)
Public bug reported: Hello When i use ubuntu 14.04.1 (linux 3.13.0.45) it is possible for me to use my iPad (8.1.3) as a modem. So i can use internet anywhere. Since a few days, i have installed ubuntu 14.04.2 (linux 3.16.0.30) but it is not possible for me to use my iPad as a modem. Why? I am not sure that it is the same reason explained in bug 1424860 NB. i connect the iPad with the usb cable to the computer. ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "trace of kern.log when i connect ipad with usb cable" https://bugs.launchpad.net/bugs/1425038/+attachment/4326223/+files/KEREN1.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1425038 Title: Can't use iPad as modem ubuntu 14.04.2 (linux 3.16.0.30) Status in libimobiledevice package in Ubuntu: New Bug description: Hello When i use ubuntu 14.04.1 (linux 3.13.0.45) it is possible for me to use my iPad (8.1.3) as a modem. So i can use internet anywhere. Since a few days, i have installed ubuntu 14.04.2 (linux 3.16.0.30) but it is not possible for me to use my iPad as a modem. Why? I am not sure that it is the same reason explained in bug 1424860 NB. i connect the iPad with the usb cable to the computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1425038/+subscriptions -- Mailing list: https://launchpad.net/~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 1424860] Re: Unable to mount iPad: Unhandled lockdown error (-20)
When i an on ubuntu 14.04.1 ( linux 3.13.0.45) The iPad connexion is good. The internet connexion via modem is good. but the iphone connexion is bad. ** Attachment added: "with old ubuntu version" https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1424860/+attachment/4325900/+files/iPad.png ** Description changed: - My bug is not exactly like bug 138882 + My bug is not exactly like bug 1385882 - My iPad is on version 8.1.3 + My iPad is on version 8.1.3 My ubuntu version (14.04.1) use linux 3.13.0.45 - So it is possible to use my iPad + So it is possible to use my iPad - Because of others probems , i want to use new version of ubuntu + Because of others problems , i want to use new version of ubuntu (14.04.2) using linux version 3.16.0.30 - It is not possible for me to use iPad with thsi message " Unable to mount iPad: Unhandled lockdown error (-20)" - Perhaps another consequence: i can't use the iPAd like a modem to connect on internet + It is not possible for me to use iPad with this message + "Unable to mount iPad: Unhandled lockdown error (-20)" + Perhaps another consequence: i can't use the iPad like a modem to connect on internet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1424860 Title: Unable to mount iPad: Unhandled lockdown error (-20) Status in libimobiledevice package in Ubuntu: New Bug description: My bug is not exactly like bug 1385882 My iPad is on version 8.1.3 My ubuntu version (14.04.1) use linux 3.13.0.45 So it is possible to use my iPad Because of others problems , i want to use new version of ubuntu (14.04.2) using linux version 3.16.0.30 It is not possible for me to use iPad with this message "Unable to mount iPad: Unhandled lockdown error (-20)" Perhaps another consequence: i can't use the iPad like a modem to connect on internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1424860/+subscriptions -- Mailing list: https://launchpad.net/~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 1424860] Re: Unable to mount iPad: Unhandled lockdown error (-20)
and for the traces of connexion ** Attachment added: "trace of impossible connexion" https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1424860/+attachment/4325890/+files/ipad.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1424860 Title: Unable to mount iPad: Unhandled lockdown error (-20) Status in libimobiledevice package in Ubuntu: New Bug description: My bug is not exactly like bug 1385882 My iPad is on version 8.1.3 My ubuntu version (14.04.1) use linux 3.13.0.45 So it is possible to use my iPad Because of others problems , i want to use new version of ubuntu (14.04.2) using linux version 3.16.0.30 It is not possible for me to use iPad with this message "Unable to mount iPad: Unhandled lockdown error (-20)" Perhaps another consequence: i can't use the iPad like a modem to connect on internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1424860/+subscriptions -- Mailing list: https://launchpad.net/~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 1424860] [NEW] Unable to mount iPad: Unhandled lockdown error (-20)
Public bug reported: My bug is not exactly like bug 138882 My iPad is on version 8.1.3 My ubuntu version (14.04.1) use linux 3.13.0.45 So it is possible to use my iPad Because of others probems , i want to use new version of ubuntu (14.04.2) using linux version 3.16.0.30 It is not possible for me to use iPad with thsi message " Unable to mount iPad: Unhandled lockdown error (-20)" Perhaps another consequence: i can't use the iPAd like a modem to connect on internet ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "first responbse" https://bugs.launchpad.net/bugs/1424860/+attachment/4325886/+files/IPAD.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1424860 Title: Unable to mount iPad: Unhandled lockdown error (-20) Status in libimobiledevice package in Ubuntu: New Bug description: My bug is not exactly like bug 138882 My iPad is on version 8.1.3 My ubuntu version (14.04.1) use linux 3.13.0.45 So it is possible to use my iPad Because of others probems , i want to use new version of ubuntu (14.04.2) using linux version 3.16.0.30 It is not possible for me to use iPad with thsi message " Unable to mount iPad: Unhandled lockdown error (-20)" Perhaps another consequence: i can't use the iPAd like a modem to connect on internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1424860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
