[Bug 1303891] Re: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method
Dimitri, I've found the issue! The installation of the libselinux1 package during the dist-upgrade from Precise to Trusty causes this issue! Here are the details from a freshly installed Ubuntu 12.04.4 amd64 VM: $ sudo apt-get update -qq && sudo apt-get dist-upgrade -qqy $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04.4 LTS" $ initctl --version initctl (upstart 1.5) $ initctl version init (upstart 1.5) $ initctl list avahi-daemon start/running, process 765 ... $ sudo sed -i 's/precise/trusty/g' /etc/apt/sources.list $ sudo apt-get update -qq $ sudo apt-get install libselinux1 -y Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: libselinux1 1 upgraded, 0 newly installed, 0 to remove and 1250 not upgraded. Need to get 58.0 kB of archives. After this operation, 2,048 B of additional disk space will be used. Get:1 http://de.archive.ubuntu.com/ubuntu/ trusty/main libselinux1 amd64 2.2.2-1 [58.0 kB] Fetched 58.0 kB in 0s (330 kB/s) (Reading database ... 174854 files and directories currently installed.) Preparing to replace libselinux1 2.1.0-4.1ubuntu1 (using .../libselinux1_2.2.2-1_amd64.deb) ... Unpacking replacement libselinux1 ... Setting up libselinux1 (2.2.2-1) ... Processing triggers for libc-bin ... ldconfig deferred processing now taking place New dmesg lines: [ 256.032898] init: Re-executing /sbin/init New syslog lines: Apr 23 14:51:40 test upstart-socket-bridge[1090]: Disconnected from Upstart Apr 23 14:51:40 test upstart-udev-bridge[595]: Disconnected from Upstart $ initctl list avahi-daemon stop/waiting ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303891 Title: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1303891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303891] Re: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method
Workaround: Before doing the dist-upgrade update the upstart package. Trusty's upstart package has no issues with Trusty's libselinux1 package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303891 Title: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1303891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312100] [NEW] dpkg "trying to overwrite '' , which is also in package " error message is not multi-arch compliant
Public bug reported: Hi everyone, On Trusty the dpkg error message "trying to overwrite '' , which is also in package " is not multi-arch compliant because it lacks the architecture of foreign packages. Current/faulty output from an amd64 install: Preparing to unpack deb-file-conflict-i386-2_1_i386.deb ... Unpacking deb-file-conflict-i386-2 (1) ... dpkg: error processing archive deb-file-conflict-i386-2_1_i386.deb (--install): trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1 1 Errors were encountered while processing: deb-file-conflict-i386-2_1_i386.deb The correct output on an amd64 install would be: Preparing to unpack deb-file-conflict-i386-2_1_i386.deb ... Unpacking deb-file-conflict-i386-2:i386 (1) ... dpkg: error processing archive deb-file-conflict-i386-2_1_i386.deb (--install): trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1:i386 1 Errors were encountered while processing: deb-file-conflict-i386-2_1_i386.deb This faulty error message makes it harder to fix conflicting file issues because the error message can be misleading. Furthermore this is a regression as the error message in Precise shows the architecture. Best, Michael ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: trusty ** Description changed: Hi everyone, On Trusty the dpkg error message "trying to overwrite '' , which is also in package " is not multi-arch compliant because it lacks the architecture of foreign packages. - Current/faulty output: + Current/faulty output from an amd64 install: Preparing to unpack deb-file-conflict-i386-2_1_i386.deb ... Unpacking deb-file-conflict-i386-2 (1) ... dpkg: error processing archive deb-file-conflict-i386-2_1_i386.deb (--install): - trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1 1 + trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1 1 Errors were encountered while processing: - deb-file-conflict-i386-2_1_i386.deb + deb-file-conflict-i386-2_1_i386.deb - The correct output would be: + The correct output on an amd64 install would be: Preparing to unpack deb-file-conflict-i386-2_1_i386.deb ... Unpacking deb-file-conflict-i386-2:i386 (1) ... dpkg: error processing archive deb-file-conflict-i386-2_1_i386.deb (--install): - trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1:i386 1 + trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1:i386 1 Errors were encountered while processing: - deb-file-conflict-i386-2_1_i386.deb + deb-file-conflict-i386-2_1_i386.deb This faulty error message makes it harder to fix conflicting file issues because the error message can be misleading. Furthermore this is a regression as the error message in Precise shows the architecture. Best, Michael ** Description changed: Hi everyone, On Trusty the dpkg error message "trying to overwrite '' , which is also in package " is not multi-arch compliant because it lacks the architecture of foreign packages. Current/faulty output from an amd64 install: Preparing to unpack deb-file-conflict-i386-2_1_i386.deb ... Unpacking deb-file-conflict-i386-2 (1) ... dpkg: error processing archive deb-file-conflict-i386-2_1_i386.deb (--install): trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1 1 Errors were encountered while processing: deb-file-conflict-i386-2_1_i386.deb The correct output on an amd64 install would be: Preparing to unpack deb-file-conflict-i386-2_1_i386.deb ... Unpacking deb-file-conflict-i386-2:i386 (1) ... dpkg: error processing archive deb-file-conflict-i386-2_1_i386.deb (--install): trying to overwrite '/var/lib/conflicting-file/conflicting-file', which is also in package deb-file-conflict-i386-1:i386 1 Errors were encountered while processing: deb-file-conflict-i386-2_1_i386.deb - This faulty error message makes it harder to fix conflicting file issues because the error message can be misleading. - Furthermore this is a regression as the error message in Precise shows the architecture. + This faulty error message makes it harder to fix conflicting file issues + because the error message can be misleading. Furthermore this is a + regression as the error message in Precise shows the architecture. Best, Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312100 Title: dpkg "trying to overwrite '' , which is also in package " error message is not multi-arch compliant To manage notificati
[Bug 1007826] Re: crash with AssertionError: file stream must be in binary mode when trying to save report to file
I'm seeing this issue when I do a dist-upgrade via python-apt from
Precise to Trusty. Can the fix be backported to Precise?
Log snippet:
2014-04-25 11:34:17 INFO: apt: Processing package kdesdk-scripts (0.2040%)
2014-04-25 11:34:17DEBUG: dpkg: Unpacking kdesdk-scripts
(4:4.13.0-0ubuntu1) over (4:4.8.5-0ubuntu0.1) ...
2014-04-25 11:34:17DEBUG: dpkg: dpkg: error processing archive
/var/cache/apt/archives/kdesdk-scripts_4%3a4.13.0-0ubuntu1_all.deb (--unpack):
2014-04-25 11:34:17DEBUG: dpkg: trying to overwrite
'/usr/bin/extractattr', which is also in package pkg-kde-tools 0.14.2ubuntu5
2014-04-25 11:34:17DEBUG: dpkg: dpkg-deb: error: subprocess paste was
killed by signal (Broken pipe)
2014-04-25 11:34:17ERROR: apt: trying to overwrite '/usr/bin/extractattr',
which is also in package pkg-kde-tools 0.14.2ubuntu5
2014-04-25 11:34:17DEBUG: dpkg: Errors were encountered while processing:
2014-04-25 11:34:17DEBUG: dpkg:
/var/cache/apt/archives/kdesdk-scripts_4%3a4.13.0-0ubuntu1_all.deb
2014-04-25 11:34:18DEBUG: dpkg: Error in function:
2014-04-25 11:34:18DEBUG: dpkg: SystemError: E:Sub-process /usr/bin/dpkg
returned an error code (1)
2014-04-25 11:34:18DEBUG: dpkg: Error in sys.excepthook:
2014-04-25 11:34:18DEBUG: dpkg: Traceback (most recent call last):
2014-04-25 11:34:18DEBUG: dpkg: File
"/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 114, in
apport_excepthook
2014-04-25 11:34:18DEBUG: dpkg: mangled_program = re.sub('/', '_',
binary)
2014-04-25 11:34:18DEBUG: dpkg: File
"/usr/lib/python2.7/dist-packages/apport/fileutils.py", line 256, in
get_recent_crashes
2014-04-25 11:34:18DEBUG: dpkg: pr.load(report, False)
2014-04-25 11:34:18DEBUG: dpkg: File
"/usr/lib/python2.7/dist-packages/problem_report.py", line 124, in load
2014-04-25 11:34:18DEBUG: dpkg: self._assert_bin_mode(file)
2014-04-25 11:34:18DEBUG: dpkg: File
"/usr/lib/python2.7/dist-packages/problem_report.py", line 631, in
_assert_bin_mode
2014-04-25 11:34:18DEBUG: dpkg: assert (type(file) == BytesIO or 'b' in
file.mode), 'file stream must be in binary mode'
2014-04-25 11:34:18DEBUG: dpkg: AssertionError: file stream must be in
binary mode
2014-04-25 11:34:18DEBUG: dpkg:
2014-04-25 11:34:18DEBUG: dpkg: Original exception was:
2014-04-25 11:34:18DEBUG: dpkg: SystemError: E:Sub-process /usr/bin/dpkg
returned an error code (1)
2014-04-25 11:34:18 INFO: apt: End of package operation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1007826
Title:
crash with AssertionError: file stream must be in binary mode when
trying to save report to file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1007826/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1312651] [NEW] trying to overwrite '/usr/bin/extractattr', which is also in package pkg-kde-tools 0.14.2ubuntu5
Public bug reported: During a dist-upgrade (via python-apt) from Precise to Trusty there is a file conflict between kdesdk-scripts and pkg-kde-tools. Log snippet: Processing package kdesdk-scripts (0.2040%) Unpacking kdesdk-scripts (4:4.13.0-0ubuntu1) over (4:4.8.5-0ubuntu0.1) ... dpkg: error processing archive /var/cache/apt/archives/kdesdk-scripts_4%3a4.13.0-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/bin/extractattr', which is also in package pkg-kde-tools 0.14.2ubuntu5 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) trying to overwrite '/usr/bin/extractattr', which is also in package pkg-kde-tools 0.14.2ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/kdesdk-scripts_4%3a4.13.0-0ubuntu1_all.deb File conflict details: Package 1: Name: kdesdk-scripts Installed version: 4:4.8.5-0ubuntu0.1 Candidate version: 4:4.13.0-0ubuntu1 Package 2: Name: pkg-kde-tools Installed version: 0.14.2ubuntu5 Candidate version: 0.15.12ubuntu1 Conflicting files: '/usr/bin/extractattr' '/usr/bin/extractrc' ** Affects: pkg-kde-tools (Ubuntu) Importance: Undecided Status: New ** Tags: precise trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1312651 Title: trying to overwrite '/usr/bin/extractattr', which is also in package pkg-kde-tools 0.14.2ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pkg-kde-tools/+bug/1312651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303891] Re: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method
Friendly ping to Dimitri. Dimitri, should I open a new bug for the new issue I've reported in comment #5 and #8? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303891 Title: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1303891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 890784] Re: Gnome-terminal continues to show outline cursor after getting focus
We would also like to see a backport to Trusty. Should we open a new bug to request this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/890784 Title: Gnome-terminal continues to show outline cursor after getting focus To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/890784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540896] Re: Always load all the nvidia modules
Alberto, is there any update on the backport to Trusty? We are particularly interested in the nvidia-340 backport as older NVIDIA hardware doesn't work with newer drivers and albeit replacements are steady we will still be stuck with that driver version for a while. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540896 Title: Always load all the nvidia modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1540896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582759] Re: Unexpected low write rate with Lexar JumpDrive P20 64GB flash drives
I'm happy to run apport-collect on a freshly installed machine if necessary. If it is needed please let me know if you want the data from a fresh Trusty, Xenial or Yaketi install. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582759 Title: Unexpected low write rate with Lexar JumpDrive P20 64GB flash drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582759] Re: Unexpected low write rate with Lexar JumpDrive P20 64GB flash drives
Sure. I'll freshly image a HP EliteBook 840 with Xenial, run apport- collect on it once all the updates are installed and then try the newest mainline kernel. ** Tags added: apport-collected ** Description changed: We are hitting an unexpected low write rate with Lexar JumpDrive P20 64GB flash drives connected via USB 3.0 on multiple machines and across multiple kernels (3.13, 4.4). Expected is a write rate of 270 MB/s and we only get 45 MB/s. Under Mac OS X and Windows we get the expected write rate of 270 MB/s. The read rate is as expected at 400 MB/s on all operating systems. Lexar JumpDrive P20 details: http://www.lexar.com/flash-drives/jumpdrive-p20 Tested machines: * HP Z440 * Lenovo ThinkPad X250 Tested kernels: * 3.13 (Trusty) * 4.4 (Xenial) lsusb details: $ lsusb -t /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M |__ Port 2: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M <-- USB 3.0 /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/11p, 480M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 8: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M $ sudo lsusb -d 05dc:a212 -vvv Bus 003 Device 002: ID 05dc:a212 Lexar Media, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x05dc Lexar Media, Inc. idProduct 0xa212 bcdDevice1.00 iManufacturer 1 Lexar iProduct2 USB Flash Drive iSerial 3 0C5E8B182D1D474C bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 224mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 3 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 3 Binary Object Store Descriptor: bLength 5 bDescriptorType15 wTotalLength 22 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType16 bDevCapabilityType 2 bmAttributes 0x0006 Link Power Management (LPM) Supported SuperSpeed USB Device Capability: bLength10 bDescriptorType16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 2 Lowest fully-functional device speed is High Speed (480Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat2047 micro seconds Device Status: 0x000c (Bus Powered) U1 Enabled U2 Enabled Write speed with kernel 4.4: $ sudo dd if=/dev/zero of=/dev/sdb bs=1M count=256 256+0 records in 256+0 records out 268435456 bytes (268 MB) copied, 5.98705 s, 44.8 MB/s Write speed under Mac OS X: $ sudo dd if=/dev/zero of=/dev/rdisk2 bs=1048576 count=256 256+0 records in 256+0 records out 268435456 bytes transferred in 0.941998 secs (284963933 bytes/sec) + --- + ApportVersion: 2.20.1-0ubuntu2
[Bug 1582759] Re: Unexpected low write rate with Lexar JumpDrive P20 64GB flash drives
Upstream bug report: http://permalink.gmane.org/gmane.linux.usb.general/142154 ** Tags added: kernel-bug-reported-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582759 Title: Unexpected low write rate with Lexar JumpDrive P20 64GB flash drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1582759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620312] [NEW] NVIDIA 367.44 on Trusty with Xenial HWE stack: VT only usable for a few seconds and then it blanks out
Public bug reported: Issue: After switching to a VT it is only usable for a few seconds and then it blanks out (goes completely black) but I can still write to it. Switching back to VT 7 (X11) and back to the VT I was using makes it usable again for a few seconds before it blanks out again. Workaround: Switching to NVIDIA driver 340.96 fixes the issue. This is hardly a long-term viable solution though. Affected/tested machines: HP z440; NVIDIA Quadro K620 Dell Precision T3500; NVIDIA Quadro 600 Notes: The nvidia-367 package for Trusty is from the Canonical-maintained "Proprietary GPU Drivers" PPA. ** Affects: nvidia-graphics-drivers-367 (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620312 Title: NVIDIA 367.44 on Trusty with Xenial HWE stack: VT only usable for a few seconds and then it blanks out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1620312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361207] [NEW] [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe
Public bug reported: nvidia-modprobe allows non-root users to load NVIDIA kernel modules and it creates the respective device entries. This is important for CUDA users as they would otherwise have to run a workaround script to load the kernel modules and create the device entries. This is documented here: http://developer.download.nvidia.com/compute/cuda/6_5/rel/docs/CUDA_Getting_Started_Linux.pdf -> 4.8 Verification Because of this newer nvidia-graphics-drivers packages (331 and newer) should at least recommend nvidia-modprobe. Furthermore the nvidia- modprobe is not available from xorg-edgers. Utopic includes an nvidia- modprobe package though. ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: [xorg-edgers] nvidia-graphics-drivers-331 and newer should recommend nvidia-modprobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361207] Re: nvidia-graphics-drivers-* should recommend nvidia-modprobe
@Alberto: Thanks. Will this also be backported to the long-term supported 340 and 352 driver series? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: nvidia-graphics-drivers-* should recommend nvidia-modprobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1361207] Re: nvidia-graphics-drivers-* should recommend nvidia-modprobe
Awesome. Thanks, Alberto. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1361207 Title: nvidia-graphics-drivers-* should recommend nvidia-modprobe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1361207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1378884] [NEW] Please update WPA supplicant to 2.2
Public bug reported: WPA supplicant version 2.2 has been released 4 months ago. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1378884 Title: Please update WPA supplicant to 2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1378884/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351977] Re: New upstream release 0.9.10.0
FYI: I've opened http:://pad.lv/1378884 to also update WPA supplicant to 2.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351977 Title: New upstream release 0.9.10.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1351977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317037] [NEW] package libticables2-6 failed to install: trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/libticables2.mo', which is also in package libticables2-2 1.3.0-0ubuntu3
Public bug reported: I've encountered this issue during a Precise to Trusty dist-upgrade if the package libticables-dev is installed. Error message: Unpacking libticables2-6:amd64 (1.3.4+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/libticables2-6_1.3.4+dfsg-3_amd64.deb (--unpack): trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/libticables2.mo', which is also in package libticables2-2 1.3.0-0ubuntu3 Reproduction instructions: 1) Install Ubuntu 12.04.4 2) sudo apt-get update 3) sudo apt-get dist-upgrade 4) sudo apt-get install libticables-dev 5) sudo reboot 6) If you use a VM take a snapshot 7) sudo sed -i s/precise/trusty/g /etc/apt/sources.list 8) sudo apt-get update 9) sudo apt-get dist-upgrade 2>&1 | tee upgrade.log The issue - the file collision - is deeply buried in the upgrade log. ** Affects: libticables (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 precise trusty ** Description changed: - I've encountered this issue during a Precise to Trusty dist-upgrade. + I've encountered this issue during a Precise to Trusty dist-upgrade if + the package libticables-dev is installed. Error message: Unpacking libticables2-6:amd64 (1.3.4+dfsg-3) ... dpkg: error processing archive /var/cache/apt/archives/libticables2-6_1.3.4+dfsg-3_amd64.deb (--unpack): - trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/libticables2.mo', which is also in package libticables2-2 1.3.0-0ubuntu3 + trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/libticables2.mo', which is also in package libticables2-2 1.3.0-0ubuntu3 Reproduction instructions: 1) Install Ubuntu 12.04.4 2) sudo apt-get update 3) sudo apt-get dist-upgrade 4) sudo apt-get install libticables-dev 5) sudo reboot 6) If you use a VM take a snapshot 7) sudo sed -i s/precise/trusty/g /etc/apt/sources.list 8) sudo apt-get update 9) sudo apt-get dist-upgrade 2>&1 | tee upgrade.log The issue - the file collision - is deeply buried in the upgrade log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317037 Title: package libticables2-6 failed to install: trying to overwrite '/usr/share/locale/fr/LC_MESSAGES/libticables2.mo', which is also in package libticables2-2 1.3.0-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libticables/+bug/1317037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301921] [NEW] package whoopsie-preferences 0.11 failed to install/upgrade: trying to overwrite '/usr/share/polkit-1/actions/com.ubuntu.whoopsiepreferences.policy', which is also in package activ
Public bug reported: package whoopsie-preferences 0.11 failed to install/upgrade: trying to overwrite '/usr/share/polkit-1/actions/com.ubuntu.whoopsiepreferences.policy', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu3.2 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: whoopsie-preferences 0.11 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 Date: Thu Apr 3 14:19:58 2014 DuplicateSignature: package:whoopsie-preferences:0.11:trying to overwrite '/usr/share/polkit-1/actions/com.ubuntu.whoopsiepreferences.policy', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu3.2 ErrorMessage: trying to overwrite '/usr/share/polkit-1/actions/com.ubuntu.whoopsiepreferences.policy', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu3.2 InstallationDate: Installed on 2014-04-02 (1 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: whoopsie-preferences Title: package whoopsie-preferences 0.11 failed to install/upgrade: trying to overwrite '/usr/share/polkit-1/actions/com.ubuntu.whoopsiepreferences.policy', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu3.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: whoopsie-preferences (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301921 Title: package whoopsie-preferences 0.11 failed to install/upgrade: trying to overwrite '/usr/share/polkit-1/actions/com.ubuntu.whoopsiepreferences.policy', which is also in package activity-log-manager-control-center 0.9.4-0ubuntu3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1301921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301919] [NEW] package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware-user.desktop', which is also in package open-vm-toolbox 201
Public bug reported: package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware- user.desktop', which is also in package open-vm-toolbox 2011.12.20-562307-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: open-vm-tools 2:9.4.0-1280544-5ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 Date: Thu Apr 3 14:14:12 2014 DuplicateSignature: package:open-vm-tools:2:9.4.0-1280544-5ubuntu5:trying to overwrite '/etc/xdg/autostart/vmware-user.desktop', which is also in package open-vm-toolbox 2011.12.20-562307-0ubuntu1 ErrorMessage: trying to overwrite '/etc/xdg/autostart/vmware-user.desktop', which is also in package open-vm-toolbox 2011.12.20-562307-0ubuntu1 InstallationDate: Installed on 2014-04-02 (1 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: open-vm-tools Title: package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware-user.desktop', which is also in package open-vm-toolbox 2011.12.20-562307-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.vmware.tools.tools.conf: mtime.conffile..etc.vmware.tools.tools.conf: 2014-04-02T14:18:56.102735 ** Affects: open-vm-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-conflict trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301919 Title: package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware- user.desktop', which is also in package open-vm-toolbox 2011.12.20-562307-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1301919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301962] [NEW] package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails
Public bug reported: During an upgrade of a vanilla Precise install to Trusty I've encountered already twice this issue: $ sudo dpkg --configure bluez Setting up bluez (4.101-0ubuntu10) ... reload: Method "Reload" with signature "" on interface "com.ubuntu.Upstart0_6.Instance" doesn't exist invoke-rc.d: initscript dbus, action "force-reload" failed. start: Job failed to start invoke-rc.d: initscript bluetooth, action "start" failed. dpkg: error processing package bluez (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: bluez ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301962 Title: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301962] Re: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails
The problematic part is in the bluez postinst script: # Automatically added by dh_installinit if [ -x "/etc/init.d/bluetooth" ] || [ -e "/etc/init/bluetooth.conf" ]; then if [ ! -e "/etc/init/bluetooth.conf" ]; then update-rc.d bluetooth defaults >/dev/null fi invoke-rc.d bluetooth start || exit $? fi $ sudo invoke-rc.d bluetooth start ; echo "exit code: $?" start: Job failed to start invoke-rc.d: initscript bluetooth, action "start" failed. exit code: 1 $ sudo /etc/init.d/bluetooth start ; echo "exit code: $?" * Starting bluetooth [ OK ] exit code: 0 $ sudo start bluetooth ; echo "exit code: $?" start: Job failed to start exit code: 1 So the Upstart job has an issue. Unfortunately after adding 'console output' to the bluetooth Upstart job configuration the job started without issues. Once I encounter this issue again I will further troubleshoot... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301962 Title: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301962] Re: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails
So it's definitely not only touching the bluetooth Upstart job configuration. 'console output' didn't give me much either. 'console log' gave me this: "Can't open RFCOMM control socket: Address family not supported by protocol" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301962 Title: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301962] Re: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails
# initctl reload-configuration # start bluetooth start: Job failed to start > A simple reload of the Upstart config isn't enough. Upstart should do this anyway as it gets notified via inotify. # find /etc/init | xargs grep bluetooth -sl /etc/init/bluetooth.conf > No Upstart jobs that use 'starting bluetooth' and that could fail # ps auxw | grep -v grep | grep bluetoothd root 622 0.0 0.0 21192 872 ?Ss Apr03 0:00 /usr/sbin/bluetoothd # killall bluetoothd # ps auxw | grep -v grep | grep bluetoothd root 24675 0.0 0.1 19296 1700 ?Ss 09:39 0:00 /usr/sbin/bluetoothd > bluetoothd is up and running and can be (re)started # ls -la /usr/sbin/hciattach -rwxr-xr-x 1 root root 100736 Dec 20 03:43 /usr/sbin/hciattach # ls -la /etc/bluetooth/uart ls: cannot access /etc/bluetooth/uart: No such file or directory > hciattach won't be called # ls -la /usr/bin/rfcomm -rwxr-xr-x 1 root root 87288 Dec 20 03:43 /usr/bin/rfcomm # ls -la /etc/bluetooth/rfcomm.conf -rw-r--r-- 1 root root 297 Mar 21 2012 /etc/bluetooth/rfcomm.conf # sh -c "/usr/bin/rfcomm -f /etc/bluetooth/rfcomm.conf bind all ; echo exit code: $?" exit code: 0 > I don't see any obvious issue with the bluetooth Upstart job configuration -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301962 Title: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301962] Re: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails
And another round. This time I can really confirm that the missing
reload of the dbus service is the issue at hand.
> Initial state:
# pidof bluetoothd
630
# dpkg --configure bluez
Setting up bluez (4.101-0ubuntu11) ...
reload: Method "Reload" with signature "" on interface
"com.ubuntu.Upstart0_6.Instance" doesn't exist
invoke-rc.d: initscript dbus, action "force-reload" failed.
start: Job failed to start
invoke-rc.d: initscript bluetooth, action "start" failed.
dpkg: error processing package bluez (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
bluez
# start bluetooth
start: Job failed to start
# pidof bluetoothd
630
> Try to trigger a reload of the dbus service via invoke-rc.d
# invoke-rc.d dbus force-reload
reload: Method "Reload" with signature "" on interface
"com.ubuntu.Upstart0_6.Instance" doesn't exist
invoke-rc.d: initscript dbus, action "force-reload" failed.
# start bluetooth
start: Job failed to start
> Try to trigger a reload of the dbus service via Upstart's initctl
# initctl reload dbus
initctl: Method "Reload" with signature "" on interface
"com.ubuntu.Upstart0_6.Instance" doesn't exist
# start bluetooth
start: Job failed to start
> Try to trigger a reload of the dbus service via SIGHUP to the dbus
system bus process
# kill -s SIGHUP $(ps ax | grep dbus | grep system | awk '{ print $1 }')
# start bluetooth
bluetooth start/post-stop, process 22101
> Success!
So the method how Upstart reloads services has changed between Precise
and Trusty. Trusty's version of initctl doesn't have backwards
compatibility with Precise's Upstart version when it comes to reloading
services and this is an issue for the dist-upgrade case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301962
Title:
package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10
(Trusty) fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301919] Re: package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware-user.desktop', which is also in package open-vm-toolbox 2011.
Hi Robie, I'm hitting this issue with a Python upgrade script that utilizes python-apt and manual apt/dpkg calls if needed. As test VM I'm using this setup: 1) Installed Ubuntu 12.04.0 (http://old-releases.ubuntu.com/releases/12.04.0/ubuntu-12.04-desktop-amd64.iso) under VMware Workstation 10 2) Installed all updates 3) Installed open-vm-toolbox and openssh-server In the upgrade script I'm doing roughly these steps: 1) Removed all sources.list and preferences entries and placed a standard sources.list for Trusty (main, restricted, universe and multiverse for trusty, trusty-security, trusty-updates and trusty-backports) 2) Places preferences file which pins repos with origin Ubuntu to 1001 to (helps a lot with upgrading on machines with many PPAs) 3) apt-get clean && apt-get update 4) Update of the core package management packages (python-apt, python-apt-common, debconf, apt, apt-utils, libapt-inst1.4, libapt-pkg4.12, dpkg) 5) apt-get upgrade 6) apt-get dist-upgrade ... So I'm not really surprised that you couldn't reproduce this out of the box. ;-) Please let me know if you need further help with this. Best, Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301919 Title: package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware- user.desktop', which is also in package open-vm-toolbox 2011.12.20-562307-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1301919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301962] Re: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails
New Upstart bug: https://bugs.launchpad.net/upstart/+bug/1303891 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301962 Title: package update of bluez 4.98-2ubuntu7 (Precise) to 4.101-0ubuntu10 (Trusty) fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1301962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1301919] Re: package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware-user.desktop', which is also in package open-vm-toolbox 2011.
Thank you, Robie. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1301919 Title: package open-vm-tools 2:9.4.0-1280544-5ubuntu5 failed to install/upgrade: trying to overwrite '/etc/xdg/autostart/vmware- user.desktop', which is also in package open-vm-toolbox 2011.12.20-562307-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1301919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313958] Re: Can't install i386 version of libltdl-dev package, Makefile.in file can't be overwrited
This also breaks dist-upgrades from Precise to Trusty if libltdl- dev:amd64 and libltdl-dev:i386 are installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313958 Title: Can't install i386 version of libltdl-dev package, Makefile.in file can't be overwrited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtool/+bug/1313958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314268] [NEW] trying to overwrite '/usr/share/man/man1/aide.1.gz', which is also in package aide-common 0.15.1-5
Public bug reported: Hi everyone, During a dist-upgrade from Precise to Trusty I'm hitting this issue: Unpacking aide (0.16~a2.git20130520-2) over (0.15.1-5) ... dpkg: error processing archive /var/cache/apt/archives/aide_0.16~a2.git20130520-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/aide.1.gz', which is also in package aide-common 0.15.1-5 Can someone please update debian/control and add a versioned Breaks statement? Reproduction instructions: 1) Install Ubuntu 12.04.4 2) sudo apt-get update 3) sudo apt-get dist-upgrade 4) sudo apt-get install aide aide-common 5) sudo reboot 6) If you use a VM take a snapshot 7) sudo sed -i s/precise/trusty/g /etc/apt/sources.list 8) sudo apt-get update 9) sudo apt-get dist-upgrade 2>&1 | tee upgrade.log 10) Wait for failure... The dist-upgrade will fail of a dependency issue. The actual issue - the file collision - is deeply buried in the upgrade log. The dependency issue should go away as soon as the file collision issue is fixed. Best, Michael ** Affects: aide (Ubuntu) Importance: Undecided Status: New ** Tags: precise trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314268 Title: trying to overwrite '/usr/share/man/man1/aide.1.gz', which is also in package aide-common 0.15.1-5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1314268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314268] Re: trying to overwrite '/usr/share/man/man1/aide.1.gz', which is also in package aide-common 0.15.1-5
apport information ** Tags added: apport-collected ** Description changed: Hi everyone, During a dist-upgrade from Precise to Trusty I'm hitting this issue: Unpacking aide (0.16~a2.git20130520-2) over (0.15.1-5) ... dpkg: error processing archive /var/cache/apt/archives/aide_0.16~a2.git20130520-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/aide.1.gz', which is also in package aide-common 0.15.1-5 Can someone please update debian/control and add a versioned Breaks statement? Reproduction instructions: 1) Install Ubuntu 12.04.4 2) sudo apt-get update 3) sudo apt-get dist-upgrade 4) sudo apt-get install aide aide-common 5) sudo reboot 6) If you use a VM take a snapshot 7) sudo sed -i s/precise/trusty/g /etc/apt/sources.list 8) sudo apt-get update 9) sudo apt-get dist-upgrade 2>&1 | tee upgrade.log 10) Wait for failure... The dist-upgrade will fail of a dependency issue. The actual issue - the file collision - is deeply buried in the upgrade log. The dependency issue should go away as soon as the file collision issue is fixed. Best, Michael + --- + ApportVersion: 2.14.1-0ubuntu3 + Architecture: amd64 + CurrentDesktop: Unity + DistroRelease: Ubuntu 14.04 + InstallationDate: Installed on 2014-04-02 (27 days ago) + InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) + Package: aide 0.16~a2.git20130520-2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 + Tags: trusty + Uname: Linux 3.13.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1314268/+attachment/4101197/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314268 Title: trying to overwrite '/usr/share/man/man1/aide.1.gz', which is also in package aide-common 0.15.1-5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1314268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314560] [NEW] package moreutils 0.50 failed to install/upgrade: trying to overwrite '/usr/bin/errno', which is also in package errno 1.3-0ubuntu1
Public bug reported: I've encountered this issue during a Precise to Trusty dist-upgrade. Error message: Unpacking moreutils (0.50) over (0.45) ... dpkg: error processing archive /var/cache/apt/archives/moreutils_0.50_amd64.deb (--unpack): trying to overwrite '/usr/bin/errno', which is also in package errno 1.3-0ubuntu1 Reproduction instructions: 1) Install Ubuntu 12.04.4 2) sudo apt-get update 3) sudo apt-get dist-upgrade 4) sudo apt-get install errno moreutils 5) sudo reboot 6) If you use a VM take a snapshot 7) sudo sed -i s/precise/trusty/g /etc/apt/sources.list 8) sudo apt-get update 9) sudo apt-get dist-upgrade 2>&1 | tee upgrade.log The issue - the file collision - is deeply buried in the upgrade log. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: moreutils 0.50 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 Date: Wed Apr 30 11:21:07 2014 ErrorMessage: trying to overwrite '/usr/bin/errno', which is also in package errno 1.3-0ubuntu1 InstallationDate: Installed on 2014-04-02 (27 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: moreutils Title: package moreutils 0.50 failed to install/upgrade: trying to overwrite '/usr/bin/errno', which is also in package errno 1.3-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: moreutils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314560 Title: package moreutils 0.50 failed to install/upgrade: trying to overwrite '/usr/bin/errno', which is also in package errno 1.3-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/moreutils/+bug/1314560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314620] [NEW] package kdesdk-scripts 4:4.13.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3
Public bug reported: A Precise to Trusty dist-upgrade fails if the packages kdesdk-scripts and subversion-tools are installed. Error: Unpacking kdesdk-scripts (4:4.13.0-0ubuntu1) over (4:4.8.5-0ubuntu0.1) ... dpkg: error processing archive /var/cache/apt/archives/kdesdk-scripts_4%3a4.13.0-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3 Reproduction instructions: 1) Install Ubuntu 12.04.4 2) sudo apt-get update 3) sudo apt-get dist-upgrade 4) sudo apt-get install kdesdk-scripts subversion-tools 5) sudo reboot 6) If you use a VM take a snapshot 7) sudo sed -i s/precise/trusty/g /etc/apt/sources.list 8) sudo apt-get update 9) sudo apt-get dist-upgrade 2>&1 | tee upgrade.log The issue - the file collision - is deeply buried in the upgrade log. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: kdesdk-scripts 4:4.13.0-0ubuntu1 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 Date: Wed Apr 30 14:21:25 2014 DuplicateSignature: package:kdesdk-scripts:4:4.13.0-0ubuntu1:trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3 ErrorMessage: trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3 InstallationDate: Installed on 2014-04-23 (7 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all SourcePackage: kde-dev-scripts Title: package kdesdk-scripts 4:4.13.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kde-dev-scripts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict precise trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314620 Title: package kdesdk-scripts 4:4.13.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-dev-scripts/+bug/1314620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1314620] Re: package kdesdk-scripts 4:4.13.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3
Details: Package: kdesdk-scripts Installed version: 4:4.8.5-0ubuntu0.1 Candidate version: 4:4.13.0-0ubuntu1 Package: subversion-tools Installed version: 1.8.8-1ubuntu3 Candidate version: 1.8.8-1ubuntu3 Conflicting files: '/usr/bin/svn-clean' So only one binary conflicts between these packages. Does kdesdk-scripts even need to ship svn-clean? If yes, how about just depending on the subversion-tools package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314620 Title: package kdesdk-scripts 4:4.13.0-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/svn-clean', which is also in package subversion-tools 1.6.17dfsg-3ubuntu3.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-dev-scripts/+bug/1314620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1358209] [NEW] Please update Network Manager version to 0.9.10.0 or 0.9.8.10
Public bug reported: Utopic uses the outdated Network Manager version 0.9.8.8. Please update the version to 0.9.10.0 or at least 0.9.8.10. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: utopic ** Package changed: network-manager-applet (Ubuntu) => network-manager (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1358209 Title: Please update Network Manager version to 0.9.10.0 or 0.9.8.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1358209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303891] Re: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method
Sorry for being impatient but when can I expect the fixed package to be available? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303891 Title: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1303891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303891] Re: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method
Then I'll test it on Monday. Thanks for fixing it so quickly. ;-) Wish you a nice weekend. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303891 Title: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1303891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303891] Re: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method
I've tested the new packages and I'm hitting a new issue: $ sudo initctl reload dbus ; echo "exit code: $?" initctl: Not running exit code: 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303891 Title: new initctl should fallback to old reload signal semantics, if pid1 doesn't export reload dbus method To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1303891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292605] [NEW] Fix wrong IP6 addresses in dispatcher script environment
Public bug reported: Hi Mathieu, Please include this upstream patch for Network Manager 0.9.8.8 in Trusty to fix wrong IP6 addresses in dispatcher script environment: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-0-9-8&id=3655e07f79c2b5fdb99fde6d4b9b185fd84cf11f The upstream bug is: https://bugzilla.gnome.org/show_bug.cgi?id=701819 Best, Michael ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292605 Title: Fix wrong IP6 addresses in dispatcher script environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1292605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257857] Re: cgroup-lite fails to install in container in precise
Workaround / Fix:
$ sudo sed -i 's|{stop|{ stop|g' /etc/init/cgroup-lite.conf
$ sudo dpkg --configure cgroup-lite
Setting up cgroup-lite (1.1.4) ...
cgroup-lite start/running
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1257857
Title:
cgroup-lite fails to install in container in precise
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1257857/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1335017] Re: Precise to Trusty dist-upgrade failure - Dependencies of Trusty's libpango1.0-0 package needs to be updated
Sorry. This one fell through my inbox cracks. Yes, the proposed package works for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1335017 Title: Precise to Trusty dist-upgrade failure - Dependencies of Trusty's libpango1.0-0 package needs to be updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1335017/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381567] [NEW] Bash returns unexpected character \001 on string operation
Public bug reported:
There has been some change between Precise and Trusty that lets this code
snippet behave differently:
Precise:
$ unset f ; f=abcd ; first_char=${f[@]:0:1} ; echo $first_char
a
Trusty
$ unset f ; f=abcd ; first_char=${f[@]:0:1} ; echo $first_char
\001
The solution is to use ${f:0:1} but nevertheless the result on Trusty seems
completely wrong. Where does the \001 even come from?!
** Affects: bash (Ubuntu)
Importance: Undecided
Status: New
** Tags: trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381567
Title:
Bash returns unexpected character \001 on string operation
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1381567/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1300638] Re: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** This bug is no longer a duplicate of private bug 1300219 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1300638 Title: compiz crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300638/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1336746] Re: [xorg-edgers] nvidia-331-uvm DKMS build error on Trusty - kernel package linux-headers-3.13.0-30-generic is not supported
Thank you, Rico. Btw... Is there some checklist you usually follow to test if a release works? If yes, where can I find it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336746 Title: [xorg-edgers] nvidia-331-uvm DKMS build error on Trusty - kernel package linux-headers-3.13.0-30-generic is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1336746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
