[Touch-packages] [Bug 1740008] [NEW] package python-xdg 0.25-4 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Public bug reported: error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-xdg 0.25-4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Dec 25 16:20:43 2017 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-12-24 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: pyxdg Title: package python-xdg 0.25-4 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pyxdg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyxdg in Ubuntu. https://bugs.launchpad.net/bugs/1740008 Title: package python-xdg 0.25-4 failed to install/upgrade: 子进程 已安装 post- installation 脚本 返回错误状态 1 Status in pyxdg package in Ubuntu: New Bug description: error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-xdg 0.25-4 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Mon Dec 25 16:20:43 2017 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-12-24 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: pyxdg Title: package python-xdg 0.25-4 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyxdg/+bug/1740008/+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
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 1577168] Re: Browser hangs Ubuntu 16.04
How do I get rid of this hang? My keyboard and mouse both aren't working -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1577168 Title: Browser hangs Ubuntu 16.04 Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When I activate Browser or click on Amazon button (which activates Browser), Ubuntu 16.04 hangs. This occurrence should not happen. An exception to this problem is that the mouse pointer is movable initially. In the extreme case, the mouse pointer hangs also. This problem does not occur when activating Firefox or Chromium. Occurs in a freshly installed Ubuntu 16.04 system. Description: Ubuntu 16.04 LTS Release: 16.04 N: Unable to locate package pkgname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1577168/+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 1725863] Re: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04)
Hi Daniel, wanted to share my findings for the last weeks. So I tested 16.04,16.10,17.04 and 17.10. The issue is now showing on all versions. In 17.04 I remember not seeing the issue although I might not have enough testing as am doing right now. Previously I used it for about 5 to 20 minutes in 17.04 compared to 4 to 6 hours in 17.10 and 16.04 when I tested. So it's giving the same error on all 4. What do you recommend I do now to follow up with you. Merry Christmas buddy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1725863 Title: Logitech G930 drops connection and reconnects in 17.10 (But not in 17.04) Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Every so many seconds / minutes the Wireless headset Logitech G930 simply drops connection. It always reconnects but when doing a recording, a meeting, listening to music or a movie it simply drops the connection for 1 to 3 second. This happens several times an hour. If it helps, it was not happening in 17.04 (Never happened in more than 200+ hours of using the headset). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyrex 1288 F pulseaudio /dev/snd/controlC2: cyrex 1288 F pulseaudio /dev/snd/controlC0: cyrex 1288 F pulseaudio Date: Sat Oct 21 17:55:42 2017 InstallationDate: Installed on 2017-10-19 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/30/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3504 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO ALPHA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/30/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHEROALPHA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1725863/+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 1740032] [NEW] no ubuntu wifi network connection
Public bug reported: ## wireless info START ## Report from: 25 Dec 2017 20:32 +07 +0700 Booted last: 25 Dec 2017 00:00 +07 +0700 Script from: 05 Dec 2017 03:13 UTC + # release ### Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial # kernel Linux 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Parameters: ro, quiet, splash, vt.handoff=7 # desktop ### Ubuntu # lspci # 02:00.0 Network controller [0280]: Intel Corporation Device [8086:24fb] (rev 10) Subsystem: Intel Corporation Device [8086:2110] 03:00.0 Ethernet controller [0200]: Qualcomm Atheros QCA8171 Gigabit Ethernet [1969:10a1] (rev 10) Subsystem: Micro-Star International Co., Ltd. [MSI] QCA8171 Gigabit Ethernet [1462:11c8] Kernel driver in use: alx # lsusb # Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 1770:ff00 Bus 001 Device 006: ID 09da:010e A4Tech Co., Ltd. Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 004: ID 04f2:b521 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # PCMCIA card info ## # rfkill 0: hci0: Bluetooth Soft blocked: no Hard blocked: no # lsmod # msi_wmi16384 0 sparse_keymap 16384 1 msi_wmi mxm_wmi16384 1 nouveau wmi20480 3 msi_wmi,mxm_wmi,nouveau video 40960 3 i915_bpo,msi_wmi,nouveau # interfaces auto lo iface lo inet loopback # ifconfig ## eth0 Link encap:Ethernet HWaddr inet addr:192.168.1.6 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::fe64:323:9af1:72b1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:88486 errors:0 dropped:0 overruns:0 frame:0 TX packets:66685 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:100934412 (100.9 MB) TX bytes:6835373 (6.8 MB) Interrupt:19 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:5786 errors:0 dropped:0 overruns:0 frame:0 TX packets:5786 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:823424 (823.4 KB) TX bytes:823424 (823.4 KB) # iwconfig ## lono wireless extensions. eth0 no wireless extensions. # route # Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG10000 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 10000 eth0 # resolv.conf ### nameserver 127.0.1.1 # network managers ## Installed: NetworkManager Running: root 935 1 0 19:33 ?00:00:00 /usr/sbin/NetworkManager --no-daemon # NetworkManager info ### GENERAL.DEVICE: eth0 GENERAL.TYPE: ethernet GENERAL.NM-TYPE:NMDeviceEthernet GENERAL.VENDOR: Qualcomm Atheros GENERAL.PRODUCT:QCA8171 Gigabit Ethernet GENERAL.DRIVER: alx GENERAL.DRIVER-VERSION: GENERAL.FIRMWARE-VERSION: GENERAL.HWADDR: GENERAL.MTU:1500 GENERAL.STATE: 100 (connected) GENERAL.REASON: 0 (No reason given) GENERAL.UDI: /sys/devices/pci:00/:00:1c.3/:03:00.0/net/eth0 GENERAL.IP-IFACE: eth0 GENERAL.IS-SOFTWARE:no GENERAL.NM-MANAGED: yes GENERAL.AUTOCONNECT:yes GENERAL.FIRMWARE-MISSING: no GENERAL.NM-PLUGIN-MISSING: no GENERAL.PHYS-PORT-ID: -- GENERAL.CONNECTION: Wired connection 1 GENERAL.CON-UUID: 4284f7e8-56c3-38d2-8bb0-dc7f239dfaf8 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/0 GENERAL.METERED:no (guessed) CAPABILITIES.CARRIER-DETECT:yes CAPABILITIES.SPEED: 100 Mb/s CAPABILITIES.
[Touch-packages] [Bug 1740033] [NEW] [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only
Public bug reported: I've upgraded my computer to a new one with a Realtek ALC1220 from an ASUS crosshair VI hero and on my ubuntu 17.10 my 5.1 surround left audio is busted, I've configured the system audio to 5.1 and tested all speakers one by one and the only one that isn't working correctly is the left speaker, it emits the testing sound but is disturbed and very low, I've checked alsaconf and everything is alright there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 Uname: Linux 4.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: biohazard 1481 F pulseaudio /dev/snd/controlC1: biohazard 1481 F pulseaudio CurrentDesktop: GNOME Date: Mon Dec 25 15:39:30 2017 InstallationDate: Installed on 2017-12-25 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_Type: High background noise, or volume is too low Title: [System Product Name, Realtek ALC1220, Green Line Out, Rear] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3008 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3008:bd11/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1740033 Title: [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only Status in alsa-driver package in Ubuntu: New Bug description: I've upgraded my computer to a new one with a Realtek ALC1220 from an ASUS crosshair VI hero and on my ubuntu 17.10 my 5.1 surround left audio is busted, I've configured the system audio to 5.1 and tested all speakers one by one and the only one that isn't working correctly is the left speaker, it emits the testing sound but is disturbed and very low, I've checked alsaconf and everything is alright there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 Uname: Linux 4.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: biohazard 1481 F pulseaudio /dev/snd/controlC1: biohazard 1481 F pulseaudio CurrentDesktop: GNOME Date: Mon Dec 25 15:39:30 2017 InstallationDate: Installed on 2017-12-25 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_Type: High background noise, or volume is too low Title: [System Product Name, Realtek ALC1220, Green Line Out, Rear] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3008 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3008:bd11/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.pr
[Touch-packages] [Bug 1739977] Re: [needs-upgrade] protobuf 3.5
** Summary changed: - [needs-upgrad] protobuf 3.5 + [needs-upgrade] protobuf 3.5 ** Tags added: artful bionic ** Tags removed: artful bionic ** Tags added: needs-upgrade ** Tags added: artful bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1739977 Title: [needs-upgrade] protobuf 3.5 Status in protobuf package in Ubuntu: New Bug description: Protobuf is bionic, artful, and zesty is super outdated. Please upgrade the package before the LTS is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protobuf/+bug/1739977/+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 1321045] Re: Can't unmount NFS mount point as user ("not found" error)
** Changed in: util-linux (Debian)
Status: New => Fix Released
--
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/1321045
Title:
Can't unmount NFS mount point as user ("not found" error)
Status in util-linux package in Ubuntu:
Fix Released
Status in util-linux package in Debian:
Fix Released
Bug description:
Dear fellows,
I had a strange behavior since I upgraded to 14.04 LTS about my user-
mountable NFS shares. My /etc/fstab follows:
# NFS shares from Synology Diskstation
192.168.25.107:/volume1/Documentos/mnt/Documentos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
192.168.25.107:/volume1/Downloads /mnt/Downloads nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
192.168.25.107:/volume1/Imagens /mnt/Imagensnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
192.168.25.107:/volume1/Músicas /mnt/Músicasnfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
192.168.25.107:/volume1/Vídeos/mnt/Vídeos nfs4
rw,noauto,users,rsize=32768,wsize=32768,timeo=14,intr
Notice I'm using noauto (don't try to mount at boot) and users (any user can
mount or umount).
I can mount normally as user. However, when I try to umount, the following
message appears:
$ umount /mnt/Documentos
umount.nfs4: /mnt/Documentos: not found
umount.nfs4: /mnt/Documentos: not found
(message appears 2 times, exactly)
So, if I try to issue a umount as a superuser (sudo umount
/mnt/Documentos), it works flawlessly.
Believe this is a bug that happened in the past on Debian (see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661527), and it was
solved back then. I'm afraid it would be reintroduced at some point.
Status of directory permissions at /mnt:
$ ls -l /mnt
total 20
drwxr-xr-x 2 tulio tulio 4096 Abr 12 19:57 Documentos
drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Downloads
drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Imagens
drwxr-xr-x 2 tulio tulio 4096 Mar 11 20:20 Músicas
drwxr-xr-x 2 tulio tulio 4096 Mar 12 20:59 Vídeos
Thanks in advance.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libmount1 2.20.1-5.1ubuntu20
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon May 19 20:30:47 2014
ProcEnviron:
LANGUAGE=pt_BR:pt:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: Upgraded to trusty on 2014-04-27 (22 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1321045/+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 1563305] Re: Update IBus to 1.5.11 on Trusty
If you want ibus 1.5.11, please upgrade to Ubuntu 16.04 LTS. ibus 1.5.11 looks to big too big of an upgrade to backport to 14.04 LTS to comply with the Stable Release Update guidelines. https://wiki.ubuntu.com/StableReleaseUpdates ** Also affects: ibus (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: ibus (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ibus (Ubuntu Xenial) Status: New => Fix Released ** Changed in: ibus (Ubuntu Trusty) Importance: Undecided => Wishlist ** Changed in: ibus (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released ** Tags added: trusty upgrade-software-version xenial -- 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/1563305 Title: Update IBus to 1.5.11 on Trusty Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Trusty: Won't Fix Status in ibus source package in Xenial: Fix Released Bug description: This is a copy of ( https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1512956 ) for Trusty: newest release of Intellj IDEA does shows a warning: "IBus prior to 1.5.11 may cause input problems." that's why i request for an update of ibus to that version. Version 1.5.5 distributed with Trusty is quite old and causes several problems to the users. Upgrading the package should help. It has some dependencies, and I'm not sure if they wouldn't need an update, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1563305/+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 1740058] Re: cupsd crashed with SIGSEGV in avahi_entry_group_free()
*** This bug is a duplicate of bug 1725749 *** https://bugs.launchpad.net/bugs/1725749 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1725749, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1740058/+attachment/5027126/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1740058/+attachment/5027130/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1740058/+attachment/5027141/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1740058/+attachment/5027143/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1740058/+attachment/5027144/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1740058/+attachment/5027145/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1740058/+attachment/5027146/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1725749 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1740058 Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() Status in cups package in Ubuntu: New Bug description: just booted ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 Uname: Linux 4.13.0-22-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CrashCounter: 1 Date: Tue Dec 26 01:35:10 2017 ExecutablePath: /usr/sbin/cupsd Lpstat: device for HEWLETT-PACKARD-DESKJET-990C: parallel:/dev/lp0 device for HP-LaserJet-5: socket://192.168.22.65:9100 device for PDF: cups-pdf:/ MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Papersize: a4 PpdFiles: HEWLETT-PACKARD-DESKJET-990C: HP Deskjet 990c, hpcups 3.17.7 PDF: Generic CUPS-PDF Printer HP-LaserJet-5: HP LaserJet 5 - CUPS+Gutenprint v5.2.13 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro rhgb plymouth:debug drm.debug=0xe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-22-generic root=UUID=bdd1754a-b8b4-4d5c-bdad-2275569c1c25 ro rhgb plymouth:debug drm.debug=0xe SegvAnalysis: Segfault happened at: 0x7fc64ced0954 : cmpq $0x0,(%rdi) PC (0x7fc64ced0954) ok source "$0x0" ok destination "(%rdi)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: avahi_entry_group_free () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in avahi_entry_group_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1740058/+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 1693503] Re: Remove mlx4.conf
this module is not loaded but this install also will fail it. ubuntu@ubuntu:/etc/modprobe.d$ lsmod | grep mlx4 ubuntu@ubuntu:/etc/modprobe.d$ sudo apt install rdma-core [sudo] password for ubuntu: Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: rdma-core 0 upgraded, 1 newly installed, 0 to remove and 5 not upgraded. Need to get 0 B/54.5 kB of archives. After this operation, 188 kB of additional disk space will be used. (Reading database ... 6 files and directories currently installed.) Preparing to unpack .../rdma-core_16.0-1_arm64.deb ... Unpacking rdma-core (16.0-1) ... dpkg: error processing archive /var/cache/apt/archives/rdma-core_16.0-1_arm64.deb (--unpack): trying to overwrite '/etc/modprobe.d/mlx4.conf', which is also in package kmod 24-1ubuntu2 Errors were encountered while processing: /var/cache/apt/archives/rdma-core_16.0-1_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1693503 Title: Remove mlx4.conf Status in kmod package in Ubuntu: Confirmed Bug description: Hi, we are working on debianizing rdma-core package, it will contain a rdma service that manage the mlx4.conf file, so the conf file “/etc/modprobe.d/mlx4.conf” (that comes with “kmod” package) is not needed anymore, and must be removed. This conf file conflicts with “/lib/modprobe.d/libmlx4.conf” that will come with “rdma-core” package, and prevents running a script (/sbin/mlx4-setup.sh) that configures ConnectX-3 devices port types (IB vs. ETH). thanks Talat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1693503/+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 1515728] Re: After receiving a call while playing music the sound volume is very low and can't be raised
** Changed in: pulseaudio (Ubuntu RTM) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1515728 Title: After receiving a call while playing music the sound volume is very low and can't be raised Status in Canonical System Image: New Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu RTM: Won't Fix Bug description: Sound volume very low after a received call ends. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1515728/+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 1727227] Re: error on boot
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1727227 Title: error on boot Status in xorg package in Ubuntu: Expired Bug description: have run the report ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 387.12 Thu Sep 28 20:18:48 PDT 2017 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3 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:Unity7:ubuntu Date: Wed Oct 25 09:06:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Pegatron 3rd Gen Core processor Graphics Controller [1b0a:20dd] NVIDIA Corporation GK107M [GeForce GT 650M] [10de:0fd1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Pegatron GK107M [GeForce GT 650M] [1b0a:20dd] InstallationDate: Installed on 2016-10-22 (367 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Novatech Ltd Novatech 15.6 nSpire Laptop ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=0ddc6564-07e2-4ca2-a501-4c6c4f89a96d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/03/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: A35 dmi.board.vendor: Novatech Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Novatech Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd04/03/2012:svnNovatechLtd:pnNovatech15.6nSpireLaptop:pvr1.0:rvnNovatechLtd:rnA35:rvr1.0:cvnNovatechLtd:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: Novatech 15.6 nSpire Laptop dmi.product.version: 1.0 dmi.sys.vendor: Novatech Ltd version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Oct 25 09:02:37 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1727227/+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 1718258] Re: /boot fills up over and over and over
[Expired for initramfs-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: initramfs-tools (Ubuntu) Status: Incomplete => Expired -- 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/1718258 Title: /boot fills up over and over and over Status in initramfs-tools package in Ubuntu: Expired Bug description: Recently whenever I perform a software update the /boot directory gets filled with dozens of old, worn-out kernel builds. I'm getting sick of having to remove them just to see them rebuilt each time a software update is attempted and ultimately fails due to a full partition. The /boot directory is of reasonable size. Here's df after my most recent purge: /dev/sda1 482922 113456344532 25% /boot pmeidell@eclipse:~$ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 pmeidell@eclipse:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1718258/+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 1726802] Re: battery charging not showing if plugged in during boot
[Expired for indicator-power (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-power (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1726802 Title: battery charging not showing if plugged in during boot Status in indicator-power package in Ubuntu: Expired Bug description: When I power up my device without plugging in, the indicator shows charging, but whenever I am powering up my laptop after plugging in the battery indicator is not showing charging. I am using ASUS R558U. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1726802/+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 1727589] Re: gnome-control-center crashed with SIGSEGV in GOA_IS_OAUTH_PROVIDER()
[Expired for gnome-online-accounts (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-online-accounts (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1727589 Title: gnome-control-center crashed with SIGSEGV in GOA_IS_OAUTH_PROVIDER() Status in gnome-online-accounts package in Ubuntu: Expired Bug description: it only crashed ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 25 22:30:41 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-15 (10 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcCmdline: gnome-control-center --overview SegvAnalysis: Segfault happened at: 0x7f6c47240823 : mov(%rbx),%rbp PC (0x7f6c47240823) ok source "(%rbx)" (0x3ff0) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: goa_oauth_provider_get_callback_uri () from /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in goa_oauth_provider_get_callback_uri() UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1727589/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up
** Changed in: klibc (Debian) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Released Status in klibc source package in Wily: Won't Fix Status in klibc source package in Xenial: Fix Released Status in klibc package in Debian: Fix Committed Bug description: [Impact] PXE booting users with live images or other minimal setups using klibc-utils. [Test case] Attempt to PXE boot using Ubuntu live images; see below for details. [Regression potential] This forces the yiaddr (client requested/current IP) to be set to 0 when sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, which should typically only happen when there is no IP set on the device and it is otherwise unable to receive unicast (on account of not being configured). Should there be a need to send other messages which would require setting the yiaddr value to the current configured IP address, a naive change would break. The yiaddr variable would need to be adjusted to pull value from a new location, or initialized directly by the callers to dhcp_send() where the business logic would reside. --- Attempting to PXE boot both the 12.04.3 and 14.04 Live images. PXE boot works normally (PXE Menu, select desired image, image begins loading), then the boot process hangs while IP-Config attempts to get an IP address: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 2 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 3 secs - giving up These lines appear very quickly (5 seconds has NOT elapsed), after about a minute, we get this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 4 secs - giving up Some time later, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 6 secs - giving up Until finally, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 9 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.25.11.31 IP-Config: eth0 complete (dhcp from 172.25.10.20): (snip) While watching the DHCP server logs, Ubuntu is either not sending a DHCP Discover at times, or is not replying back with a DHCPRequest during these sessions, presumably ignoring an response from the DHCP server. From the initial booting of the system via PXE, to when Ubuntu finally shows the desktop, almost 12 minutes will have elapsed. I am seeing this same behavior on both 12.04.3 and 14.04. After finding a number of similar erros via Google and no real resolution, I have opened this bug. The system experiencing this issue has multiple ethernet interfaces (actual HW, not a VM), some Google found solutions suggest hard coding DEVICE=eth0 in /etc/initramfs-tools/initramfs.conf, however this isn't acceptable as a system attempting to PXE boot may be using an alternate port for the network. I have found what looks to be a very similar bug filed for Debian, #584583, which also contains a patch for this issue (under Debian). I have no problems in PXE booting to various Windows, RedHat, Centos, or Fedora OSs. Ubuntu is the only Live OS that I'm attempting to boot at present. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.340 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Jun 6 20:22:09 2014 LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- Mailing list: https://launchpad.net/~t
