[Touch-packages] [Bug 739746] Re: bluetoothd crashed with SIGSEGV in g_main_context_dispatch()
** Attachment removed: "59953E8655178583D1BA0B09AA8231F5.jpg" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/739746/+attachment/4873010/+files/59953E8655178583D1BA0B09AA8231F5.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/739746 Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch() Status in bluez package in Ubuntu: Invalid Bug description: Binary package hint: bluez Don't know what I did but latest keys I pressed were Super+6 (activate Totem from Unity panel) and then I saw this crash. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: bluez 4.89-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 NonfreeKernelModules: wl Architecture: i386 Date: Mon Mar 21 22:42:22 2011 ExecutablePath: /usr/sbin/bluetoothd InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110320) InterestingModules: rfcomm sco bnep l2cap btusb bluetooth MachineType: Hewlett-Packard Compaq 615 ProcCmdline: /usr/sbin/bluetoothd --udev ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=6e5309ba-d57c-44a5-a02a-0ba7ab026458 ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x548ff8: mov0x4(%edi),%eax PC (0x00548ff8) ok source "0x4(%edi)" (0x0004) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: bluez StacktraceTop: ?? () ?? () ?? () ?? () from /lib/libglib-2.0.so.0 g_main_context_dispatch () from /lib/libglib-2.0.so.0 Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/17/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68GVV Ver. F.04 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 308C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 27.07 dmi.chassis.asset.tag: CNU9326ML2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68GVVVer.F.04:bd07/17/2009:svnHewlett-Packard:pnCompaq615:pvrF.04:rvnHewlett-Packard:rn308C:rvrKBCVersion27.07:cvnHewlett-Packard:ct10:cvr: dmi.product.name: Compaq 615 dmi.product.version: F.04 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:24:7E:7E:99:A1 ACL MTU: 1017:8 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:657 acl:0 sco:0 events:21 errors:0 TX bytes:340 acl:0 sco:0 commands:21 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/739746/+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 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Changed in: linux-hwe (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693540 Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: Fix Committed Status in linux-hwe package in Ubuntu: Fix Committed Bug description: it show there's bug in my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 08:42:40 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-03 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+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 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Changed in: debconf (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693540 Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: Fix Committed Status in linux-hwe package in Ubuntu: Fix Committed Bug description: it show there's bug in my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 08:42:40 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-03 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+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 1428121] Re: Intel HDMI Audio not working with IOMMU enabled
Zeke Laschinski, did you test the patch yourself and confirm it fixes the problem you are experiencing? -- 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/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+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 1664748] Re: wifi connection drops, reconnects every 10 minutes
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1664748 Title: wifi connection drops, reconnects every 10 minutes Status in maas package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Expired Bug description: I recently moved my home DHCP and DNS server over to MAAS (2.1.3 from xenial-updates). Since doing so, I've noticed that my wifi connection drops and reconnects (with corresponding Unity pop-up notifications) exactly every 10 minutes. I suppose this is due to the fact that MAAS sets DHCP leases to 10 minutes by default? Has anyone else noticed this behavior? Is there a suitable workaround? Increasing the DHCP lease time? Using static addresses? Something else? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1664748/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
There are multiple variables here you need to consider... The headset socket is 4-contact to support headphones with built-in microphone. So if you plug in a 4-contact jack then you are more likely (not guaranteed) to get a clean connection (4 contacts touching 4 separate contacts). However a "clean" connection is not helpful if you've plugged in the wrong type of headset. See there are different types (too many): https://technosyndicate.files.wordpress.com/2012/12/122312_0549_common35mm11.png http://www.cablechick.com.au/blog/understanding-trrs-and-audio-jacks/ So an imperfect connection is pretty common. And an imperfect connection might touch the laptop's mic contact to something else. In fact if you get a pair of Bose Quiet Comfort QC25 then you have a choice between buying one with Apple support or Samsung/Android support (although some stores will only stock Apple). One doesn't work in the other but they both appear to be identical 4-contact 3.5mm jacks. Yes indeed this can be fixed in software to silence or reduce noise from the mic line. But remember it's a hardware problem as well as a software problem. You should try both hardware and software solutions. -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1693160] Re: software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] failed to install/upgrade: unable to make backup link of './usr/sb
Hello Seth, I am afraid that technology is beyond my expertise. I thank you for your help but I am not knowledgeable at all to carry out your instructions. I will ask for help from the person where I purchased the computer. i phoned him today and he asked me to bring the computer in. At this time I believe it is the best alternative. Your effort to help me was appreciated. On Thu, May 25, 2017 at 8:47 PM, Seth Arnold <1693...@bugs.launchpad.net> wrote: > Hello Dorothy, > > What's the output of > > namei -l /usr/sbin/sshd /usr/bin/ssh > lsattr -d /usr /usr/bin /usr/bin/ssh /usr/sbin /usr/sbin/sshd > > Thanks > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1693160 > > Title: > software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1 > [modified: usr/sbin/sshd] failed to install/upgrade: unable to make > backup link of './usr/sbin/sshd' before installing new version: > Operation not permitted > > Status in openssh package in Ubuntu: > New > > Bug description: > I am 85 years old and do not understand the technology nor proper > explanation of the problem. I simply tried to update my computer and > at the end there was a notification that there was a problem with the > system. > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] > ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 > Uname: Linux 4.4.0-78-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.6 > Architecture: amd64 > Date: Tue May 23 06:52:10 2017 > DuplicateSignature: >package:openssh-server:1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] >Unpacking openssh-server (1:7.2p2-4ubuntu2.2) over (1:7.2p2-4ubuntu2.1) > ... >dpkg: error processing archive /var/cache/apt/archives/ > openssh-server_1%3a7.2p2-4ubuntu2.2_amd64.deb (--unpack): > unable to make backup link of './usr/sbin/sshd' before installing new > version: Operation not permitted > ErrorMessage: unable to make backup link of './usr/sbin/sshd' before > installing new version: Operation not permitted > InstallationDate: Installed on 2016-04-21 (397 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.2 >apt 1.2.20 > SourcePackage: openssh > Title: package openssh-server 1:7.2p2-4ubuntu2.1 [modified: > usr/sbin/sshd] failed to install/upgrade: unable to make backup link of > './usr/sbin/sshd' before installing new version: Operation not permitted > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/ > 1693160/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1693160 Title: software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] failed to install/upgrade: unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted Status in openssh package in Ubuntu: New Bug description: I am 85 years old and do not understand the technology nor proper explanation of the problem. I simply tried to update my computer and at the end there was a notification that there was a problem with the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue May 23 06:52:10 2017 DuplicateSignature: package:openssh-server:1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] Unpacking openssh-server (1:7.2p2-4ubuntu2.2) over (1:7.2p2-4ubuntu2.1) ... dpkg: error processing archive /var/cache/apt/archives/openssh-server_1%3a7.2p2-4ubuntu2.2_amd64.deb (--unpack): unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted InstallationDate: Installed on 2016-04-21 (397 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] failed to install/upgrade: unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1693160/+subscriptions
[Touch-packages] [Bug 1693474] Re: Switches in Ambiance CSD headerbar are disproportionately big
** Summary changed: - Some switches are disproportionately big + Switches in Ambiance CSD headerbar are disproportionately big ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693474 Title: Switches in Ambiance CSD headerbar are disproportionately big Status in ubuntu-themes package in Ubuntu: New Bug description: Look at the screenshot, is it expected for the switch in the top right corner to be so large? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:36:16 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693474/+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 1693477] Re: minimise, maximise and close icons change when changing icon theme
If it is intended, as designed, then "Won't Fix" ? ** Changed in: ubuntu-themes (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693477 Title: minimise, maximise and close icons change when changing icon theme Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: When using the light themes I experienced this weird behavior: the (x)(_)([]) change their shape when changing the icon theme. Is it intended? I never experienced this with any other GTK theme so far and I'm quite surprised that changing the icon theme can change the decorations.. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:41:31 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693477/+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 1693613] Re: Ambiance headerbar has more padding on top than on bottom
Yes. Particularly noticeable is the lack of padding below the square buttons. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693613 Title: Ambiance headerbar has more padding on top than on bottom Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: If you look at the attached screenshots, Adwaita has equal padding on the top and bottom of the headerbar. Ambiance has more padding on top than on the bottom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693613/+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 1693609] Re: Please make window control buttons larger
Agreed. You read my mind. ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693609 Title: Please make window control buttons larger Status in Ubuntu UX: New Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The window control buttons ( _ X ) in Ambiance are noticeably smaller than other icon buttons in the headerbar of a "native" GNOME3 app. I think this is both a visual issue and an accessibility issue since it is harder to click the window control buttons than the other buttons. Please compare with Adwaita which has a much larger click area for the window control buttons. Commentary -- Remember that one of the major strengths of GNOME 3 is that it is usable on a touch-enabled laptop. And while there are many people that complain about Adwaita, I believe many more actually like the proportions and padding of the default GNOME theme! ubuntu-themes 16.10+17.10.20170518-0ubuntu1 Ubuntu 17.10 Alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1693609/+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 775803] ☠have you ever been there?
Hi friend! We have recently visited a great place in town, have you already been there? Here are some pics of it http://fund.thepsaproject.com See you around, john.butterworth Sent from Mail for Windows 10 ** Attachment added: "99C8C3719BDC74F36D1B70E593EC258B.jpg" https://bugs.launchpad.net/bugs/775803/+attachment/4883758/+files/99C8C3719BDC74F36D1B70E593EC258B.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/775803 Title: /usr/bin/python: error while loading shared libraries: /lib/i386 -linux-gnu/libz.so.1: invalid ELF header Status in zlib package in Ubuntu: New Bug description: Binary package hint: nvidia-common Upgrade failed to install correctly ProblemType: Package DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-9-generic 2.6.38-9.43 ProcVersionSignature: Ubuntu 2.6.35-29.51-generic 2.6.35.12 Uname: Linux 2.6.35-29-generic i686 Architecture: i386 Date: Mon May 2 19:42:26 2011 ErrorMessage: run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 127 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) SourcePackage: nvidia-common Title: package linux-image-2.6.38-9-generic 2.6.38-9.43 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/nvidia-common exited with return code 127 UpgradeStatus: Upgraded to natty on 2011-05-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/775803/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I'm on 17.04 too and suffering from this issue for a while. As I understand this issue, the problem may actually very well be in Network-Manager rather than in systemd-resolved, but the problem is indeed very visible with resolved. Here's how I experience the problem (the root of my problems are a split DNS setup, just like most other people following this ticket). This is the state of my resolved... With no VPN connected (wireless and wifi only): Link 7 (vpn0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (wlp4s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com Link 2 (enp0s31f6) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com With VPN connected: Link 7 (vpn0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.180.48 192.168.180.49 DNS Domain: example.lan Link 3 (wlp4s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com Link 2 (enp0s31f6) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com Now, I have one split DNS entry, testserver.example.net. On a public DNS, it will resolve to a public IP - On the example.lan DNS servers, it will resolve to a private IP. Doing the following a couple of times is bound to sometimes return the private IP and sometimes the public IP: systemd-resolve --flush-caches && ping -c1 testserver.example.net So for things to work in this particular example, I'd need the 192.168.8.1 DNS to either be disabled completely or only used for int.example.com. 192.168.180.48 and 49 as provided by the VPN would somehow need to be the default/active nameserver. Note that for my VPN connection in Network Manager, I've *not* enabled the "use this connection only for resources on its own network". In an attempt to work around this problem, I decided to configure network-manager for dnsmasq, which worked fine back in the 16.04 days. Basically the setup worked, but Network-Manager only added the VPN DNS servers for the VPN provided search domain example.lan. Needless to say this works even worse than the resolved solution, because now I get the wrong answer for testserver.example.net every time. It does seem to indicates that perhaps there's something fishy about how network-manager passes DNS servers to resolved. I have not found a way to force network- manager to completely replace the configured DNS servers for a VPN connection, but that might provide a usable workaround. Hopefully this can shed some light on things? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1689825] Re: gnome-keyring not unlocked on boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libgnome-keyring (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+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 1693160] Re: software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] failed to install/upgrade: unable to make backup link of './usr/sbin/s
Hello Dorothy, What's the output of namei -l /usr/sbin/sshd /usr/bin/ssh lsattr -d /usr /usr/bin /usr/bin/ssh /usr/sbin /usr/sbin/sshd Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1693160 Title: software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] failed to install/upgrade: unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted Status in openssh package in Ubuntu: New Bug description: I am 85 years old and do not understand the technology nor proper explanation of the problem. I simply tried to update my computer and at the end there was a notification that there was a problem with the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue May 23 06:52:10 2017 DuplicateSignature: package:openssh-server:1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] Unpacking openssh-server (1:7.2p2-4ubuntu2.2) over (1:7.2p2-4ubuntu2.1) ... dpkg: error processing archive /var/cache/apt/archives/openssh-server_1%3a7.2p2-4ubuntu2.2_amd64.deb (--unpack): unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted ErrorMessage: unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted InstallationDate: Installed on 2016-04-21 (397 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] failed to install/upgrade: unable to make backup link of './usr/sbin/sshd' before installing new version: Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1693160/+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 996851] Re: highlighting current line does not work
Works okay with version 3.18.3 under Ubuntu 16.04 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/996851 Title: highlighting current line does not work Status in gedit: Fix Released Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: The preference allows for the current line to be highlighted. It used to work under 11.xx, it does not work under 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 10:02:06 2012 ExecutablePath: /usr/bin/gedit InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_AU.UTF-8 LANGUAGE=en_AU:en SourcePackage: gedit UpgradeStatus: Upgraded to precise on 2012-05-01 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/996851/+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 1428121] Re: Intel HDMI Audio not working with IOMMU enabled
Ubuntu 17.04 with 4.10.0-21, libvirt 2.5.0, QEMU 2.8, and virt-manager 1.3.2. Gigabyte EX58-UD3R Rev 1.6, ICH10 (00:1b.0) audio, x5675 (Westmere). Nvidia GTX 275 for the host, GTX 1050 Ti for the VM. Added to /etc/default/grub, updated grub, rebooted, and replaced the previous entry each time: intel_iommu=igfx_off (Audio works, breaks IOMMU) intel_iommu=on,igfx_off (Breaks audio) intel_iommu=on,igfx_off snd_hda_intel.align_buffer_size=1 (Breaks audio) intel_iommu=on iommu=pt (Breaks audio) dmesg gives with intel_iommu=on: DMAR: [DMA Read] Request device [00:1b.0] fault addr b000 [fault reason 02] Present bit in context entry is clear THE FIX: Alex Williamson created a patch that was verified by Matthieu Speder https://bugzilla.kernel.org/show_bug.cgi?id=76331 https://patchwork.kernel.org/patch/4505951/ ** Bug watch added: Linux Kernel Bug Tracker #76331 https://bugzilla.kernel.org/show_bug.cgi?id=76331 -- 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/1428121 Title: Intel HDMI Audio not working with IOMMU enabled Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an Nvidia GTX 650. Host uses Intel IGD for video and HDMI audio out. When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on' HDMI audio no longer functions although the device and modules seem to load and I cannot locate any error messages. In this configuration IOMMU functions as expected and I can successfully pass the Nvidia card through to a KVM guest using VFIO. As per this (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug report and the linked bugzilla thread I attempted to use kernel flag 'intel_iommu=on,igfx_off'. This resolves the HDMI audio out but breaks IOMMU as in VGA pass through generates DMA errors. I'm running from a clean installation of 14.10 with no modifications to the kernel or kvm, qemu, libvirt or virt-manager. In either scenario above the analogue audio out continues to function, I haven't tested the optical out as I have no hardware to do so. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-31-generic 3.16.0-31.41 ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: kelvin 3468 F pulseaudio /dev/snd/controlC3: kelvin 3468 F pulseaudio /dev/snd/controlC0: kelvin 3468 F pulseaudio /dev/snd/controlC1: kelvin 3468 F pulseaudio CurrentDesktop: Unity Date: Wed Mar 4 12:53:17 2015 HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931 InstallationDate: Installed on 2015-02-26 (5 days ago) InstallationMedia: Ubuntu-Server 14.10 "Utopic Unicorn" - Release amd64 (20141022.2) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-3.16.0-31-generic N/A linux-backports-modules-3.16.0-31-generic N/A linux-firmware 1.138.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.70 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1428121/+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 1693645] [NEW] /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:nm_device_queue_activation:_internal_activate_device:_internal_activate_generic
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager. This problem was most recently seen with package version 1.4.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/b8e0244b05afe9f376ca190cbb5d6bbd0735de92 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: artful xenial yakkety zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1693645 Title: /usr/sbin/NetworkManager:6:g_assertion_message:g_assertion_message_expr:nm_device_queue_activation:_internal_activate_device:_internal_activate_generic Status in network-manager package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding network-manager. This problem was most recently seen with package version 1.4.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/b8e0244b05afe9f376ca190cbb5d6bbd0735de92 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1693645/+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 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693540 Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Bug description: it show there's bug in my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 08:42:40 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-03 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+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 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: debconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693540 Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Bug description: it show there's bug in my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 08:42:40 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-03 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+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 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693540 Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Bug description: it show there's bug in my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 08:42:40 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-03 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+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 1693499] Re: package linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1693534 *** https://bugs.launchpad.net/bugs/1693534 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 #1693534, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1693534 package linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693499 Title: package linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Bug description: not sure what's happening really ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 09:30:32 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-24 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693499/+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 1693499] Re: package linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
*** This bug is a duplicate of bug 1693534 *** https://bugs.launchpad.net/bugs/1693534 ** Also affects: debconf (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693499 Title: package linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Bug description: not sure what's happening really ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 09:30:32 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-24 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic 4.8.0-53.56~16.04.1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693499/+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 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
** Also affects: debconf (Ubuntu) Importance: Undecided Status: New ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1693540 Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in debconf package in Ubuntu: New Status in linux-hwe package in Ubuntu: New Bug description: it show there's bug in my system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.8.0-53-generic (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 08:42:40 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 InstallationDate: Installed on 2017-04-03 (51 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: linux-hwe Title: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+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 1685186] Re: [SRU] Mir needs to be updated to 0.26 in 16.04LTS
I've set this to verification-failed to prevent the accidental release of the package because these changes do not seem to exist in Artful, a requirement of the SRU process, and the version number of the package in xenial-proposed is greater than the version of the package in releases newer than Ubuntu 16.04. ** Changed in: mir (Ubuntu Xenial) Status: Fix Committed => Incomplete ** Tags removed: verification-done ** Tags added: verification-failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1685186 Title: [SRU] Mir needs to be updated to 0.26 in 16.04LTS Status in mir package in Ubuntu: In Progress Status in mir source package in Xenial: Incomplete Bug description: [Impact] Snap development using Mir has been using the "stable phone overlay" PPA which is both inconvenient and a legacy of the cancelled Unity8 project. It would greatly simplify things if Mir were updated in the Xenial archive. [Test Case] Build a Mir client snap (e.g. lp:~albaguirre/+snap/mir-client-demos) against "Primary Ubuntu Archive" and deploy as described in https://developer.ubuntu.com/en/snappy/guides/mir-snaps/ Expected: the client apps start and are visible on screen Actual: the client apps don't start and are not visible on screen [Regression Potential] Mir has two categories of dependent project: 1 Unity8 and unity-system-compositor "server" packages 2 toolkits and other "clients" of Mir "Server" packages from the archive will stop working in the LTS as they will continue using the earlier libmirserver.so.38 (from Mir 0.21) which doesn't work with the libmirclient.so.9 from Mir 0.26. This is unimportant as these packages were provided as an "early experience", not for serious use. "Client" packages are dependent only on libmirclient.so.9 which is ABI stable. The principle type of regression would be FTBFS where APIs have been deprecated in 0.26. The linked 0.26.3 release has these deprecations disabled for 16.04. The packages are available in silo: https://bileto.ubuntu.com/#/ticket/2736 notes: A recursive search or rdependencies identifies the following packages in category 1: camera-app-autopilot gallery-app-autopilot indicator-network-autopilot indicators-client qtdeclarative5-qtmir-plugin qtmir-android qtmir-desktop qtmir-tests ubuntu-desktop-mir ubuntu-experience-tests ubuntu-pocket-desktop ubuntu-push-autopilot ubuntu-touch ubuntu-touch-session unity8 unity8-autopilot unity8-desktop-session-mir unity-scope-click-autopilot unity-system-compositor unity-system-compositor-autopilot Anyone wanting these packages should switch to the "unity8-desktop- session" preview package in 17.04 where they are far more functional. [Alternatives] If we want to keep everything working in Xenial, we *could* bump the libmirclient SONAME to libmirclient.so.10. This would result in libmirclient9 being NBS, but continuing to work against the Mir servers available in 16.04[*] (until and unless they are rebuilt). However, this does not enable the desired result for IoT deployments of toolkits (GTK, Qt etc) and other clients working against servers (specifically miral-kiosk) built against the updated libraries. To work for IoT these would need to rebuilt from source - at which point they (and their dependencies) would stop working against the servers in category 1. [*] with the exception of the servers provided in mir-examples, these would only work with clients linking against libmirclient.so.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1685186/+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 1670059] Re: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot
I also have this issue. Running "alsactl restore" will allow sound to come through the headphones without rebooting, but this is suboptimal. I have attached my alsa-info output. ** Attachment added: "alsa-info.txt.vU4MuqgaEu" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+attachment/4883677/+files/alsa-info.txt.vU4MuqgaEu -- 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/1670059 Title: [Latitude 3340, Realtek ALC3234] Headphones Not Detected if Plugged in before Boot Status in alsa-driver package in Ubuntu: New Bug description: When (re)booting with headphones in, audio won't play. Once the headphones are unplugged, it will start to come through the speakers and will work with the headphones when they are plugged back in. Expected headphones to be detected automatically even if plugged in before boot. This is on latest Xenial HWE kernel (4.8.0-39-generic x86_64). ALSA Info attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1670059/+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 1639201] Re: Can not resize GEDIT windows by moving window edge
This is fixed in Ubuntu 17.10 Alpha. I don't know yet if the fixed version will be backported to older Ubuntu versions. ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntu-gnome Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1639201 Title: Can not resize GEDIT windows by moving window edge Status in Ubuntu GNOME: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: Gedit UBUNTU 16.04.1 GNOME 3-20 GEDIT 3.20.2 Please restore the previously available ability to resize the gedit window by grabbing an edge or corner of the window and moving the edge. I manipulate many text files each day and frequently have several open and visible at the same time on the same monitor. (I have multiple monitors.) The ability to quickly change the dimensions of individual windows is very important, and the "new" GNOME 3 method of: 1. Move mouse to title bar, right click 2. move the "selection" bar -DOWN- several lines, click on the word "resize" 3. --CAREFULLY-- move the mouse --ONLY-- in the direction you want to expand or reduce the window size. 4. More often then NOT, you then get to do this all over again because the computer moved the left side of the window, rather then the right side as you had intended, or the top of the window instead of the bottom, or some sort of vice-versa forcing you to now move your cursor to the top of the screen to reposition the entire window. Much easier to just grab an edge and move THAT edge. I have also noticed that the majority of the applications installed on my system also allow grabbing the window edges, even though most of them also have the "click on a non-existant icon and hope that you get a usable pulldown menu to do something useful." method of selecting options that gnome 3 seems to like. What's worse is where the "help" and "preferences" selections are - especially when you have a multi-monitor sysytem. (But I will have to say, that GNOME 3 is much better than UNITY.) Now if this method of selecting options (Resize, help, preferences, Print, etc) was done to support "Touch screens" then I have to ask, please, PLEASE, provide a user selectable option of "Desktop" or "Touch Screen" so that the user can make their own choice... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.20.2-2ubuntu1~ubuntu16.04.1 [origin: LP-PPA-gnome3-team-gnome3-staging] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 4 06:32:16 2016 InstallationDate: Installed on 2014-05-11 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1639201/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
@vanvugt I do have both cable types (with and without cable mic). In testing the Quiet Comfort 15s: Bose CQ 15 w/ normal cable - The hiss is present with 0 dB headphone mic gain, but far more reduced than the Sony earbuds. It is almost unnoticeable. If I weren't trying to hear it, I'd miss it. Bose CQ 15 w/ mic cable - I cannot detect any hiss present with 0 db gain. @esokrarkose I'm sorry I misunderstood what you were saying about your experience with the hiss. I thought you were saying it only happened while playing a sound. I too experience the constant hiss with my earbuds. I don't doubt the hiss in normal headphones. The Bose CQs do produce the hiss with one cable type. It is barely noticeable and much more subdued than the earbuds. I'm not sure what Bose does if anything with the sound signal coming from the headphone jack. Maybe it's just reduced due to higher quality speakers than say my earbuds. As I understand it the noise cancellation is meant for external sounds, but like you said, maybe it plays a role in making the hiss less audible. The noise cancellation itself does produce a level of white noise. -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1693609] [NEW] Please make window control buttons larger
Public bug reported: The window control buttons ( _ X ) in Ambiance are noticeably smaller than other icon buttons in the headerbar of a "native" GNOME3 app. I think this is both a visual issue and an accessibility issue since it is harder to click the window control buttons than the other buttons. Please compare with Adwaita which has a much larger click area for the window control buttons. Commentary -- Remember that one of the major strengths of GNOME 3 is that it is usable on a touch-enabled laptop. And while there are many people that complain about Adwaita, I believe many more actually like the proportions and padding of the default GNOME theme! ubuntu-themes 16.10+17.10.20170518-0ubuntu1 Ubuntu 17.10 Alpha ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "adwaita-windows-buttons.png" https://bugs.launchpad.net/bugs/1693609/+attachment/4883669/+files/adwaita-windows-buttons.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693609 Title: Please make window control buttons larger Status in ubuntu-themes package in Ubuntu: New Bug description: The window control buttons ( _ X ) in Ambiance are noticeably smaller than other icon buttons in the headerbar of a "native" GNOME3 app. I think this is both a visual issue and an accessibility issue since it is harder to click the window control buttons than the other buttons. Please compare with Adwaita which has a much larger click area for the window control buttons. Commentary -- Remember that one of the major strengths of GNOME 3 is that it is usable on a touch-enabled laptop. And while there are many people that complain about Adwaita, I believe many more actually like the proportions and padding of the default GNOME theme! ubuntu-themes 16.10+17.10.20170518-0ubuntu1 Ubuntu 17.10 Alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693609/+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 1693609] Re: Please make window control buttons larger
** Attachment added: "ambiance-windows-buttons.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693609/+attachment/4883670/+files/ambiance-windows-buttons.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693609 Title: Please make window control buttons larger Status in ubuntu-themes package in Ubuntu: New Bug description: The window control buttons ( _ X ) in Ambiance are noticeably smaller than other icon buttons in the headerbar of a "native" GNOME3 app. I think this is both a visual issue and an accessibility issue since it is harder to click the window control buttons than the other buttons. Please compare with Adwaita which has a much larger click area for the window control buttons. Commentary -- Remember that one of the major strengths of GNOME 3 is that it is usable on a touch-enabled laptop. And while there are many people that complain about Adwaita, I believe many more actually like the proportions and padding of the default GNOME theme! ubuntu-themes 16.10+17.10.20170518-0ubuntu1 Ubuntu 17.10 Alpha To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693609/+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 1693474] Re: Some switches are disproportionately big
Comparison screenshot with Adwaita ** Attachment added: "adwaita-gnome-tweak-tool.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693474/+attachment/4883671/+files/adwaita-gnome-tweak-tool.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693474 Title: Some switches are disproportionately big Status in ubuntu-themes package in Ubuntu: New Bug description: Look at the screenshot, is it expected for the switch in the top right corner to be so large? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:36:16 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693474/+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 1693613] Re: Ambiance headerbar has more padding on top than on bottom
** Attachment added: "ambiance-windows-buttons.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693613/+attachment/4883673/+files/ambiance-windows-buttons.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693613 Title: Ambiance headerbar has more padding on top than on bottom Status in ubuntu-themes package in Ubuntu: New Bug description: If you look at the attached screenshots, Adwaita has equal padding on the top and bottom of the headerbar. Ambiance has more padding on top than on the bottom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693613/+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 1693613] [NEW] Ambiance headerbar has more padding on top than on bottom
Public bug reported: If you look at the attached screenshots, Adwaita has equal padding on the top and bottom of the headerbar. Ambiance has more padding on top than on the bottom. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "adwaita-windows-buttons.png" https://bugs.launchpad.net/bugs/1693613/+attachment/4883672/+files/adwaita-windows-buttons.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693613 Title: Ambiance headerbar has more padding on top than on bottom Status in ubuntu-themes package in Ubuntu: New Bug description: If you look at the attached screenshots, Adwaita has equal padding on the top and bottom of the headerbar. Ambiance has more padding on top than on the bottom. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693613/+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 1693419] Re: theme elements like detail box in software updater have become small
This sounds like a duplicate of https://launchpad.net/bugs/1623856 which should have been fixed for Ubuntu 16.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693419 Title: theme elements like detail box in software updater have become small Status in ubuntu-themes package in Ubuntu: New Bug description: theme elements like detail box in software updater have become small. This appeared after the upgrade to yakkety. Occurs in all themes. there were also problems like misaligned close buttons in other themes, which got solved after I ran this: sudo apt-get autoremove --purge light-themes sudo apt-get install light-themes but didn't solve the problems like the detail box. These are small in all themes now. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: light-themes 16.10+16.10.20161024-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 25 10:44:55 2017 InstallationDate: Installed on 2016-01-10 (500 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to yakkety on 2017-02-12 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693419/+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 1693477] Re: minimise, maximise and close icons change when changing icon theme
> Is it intended? Yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693477 Title: minimise, maximise and close icons change when changing icon theme Status in ubuntu-themes package in Ubuntu: New Bug description: When using the light themes I experienced this weird behavior: the (x)(_)([]) change their shape when changing the icon theme. Is it intended? I never experienced this with any other GTK theme so far and I'm quite surprised that changing the icon theme can change the decorations.. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:41:31 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693477/+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 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
** Tags removed: verification-failed
** Tags removed: patch
** Tags removed: ua
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1674399
Title:
OpenSSL CPU detection for AMD Ryzen CPUs
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Committed
Status in openssl source package in Yakkety:
Fix Committed
Status in openssl source package in Zesty:
Fix Committed
Status in openssl source package in Artful:
Fix Released
Bug description:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
64bit only (Confirmed with AMD representative). Current OpenSSL
version in Ryzens still calls SHA for SSSE3 routine as result a number
of extensions were effectively masked on Ryzen and shows no
improvement.
[1] /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 1
model name : AMD Ryzen 5 1600 Six-Core Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni
pclmulqdq monitor ssse3 fma cx16 sse
4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
[2] - sha_ni: SHA1/SHA256 Instruction Extensions
[3] - https://en.wikipedia.org/wiki/Ryzen
...
All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES,
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
...
* Program to performs the CPUID check:
Reference :
https://software.intel.com/en-us/articles/intel-sha-extensions
... Availability of the Intel® SHA Extensions on a particular
processor can be determined by checking the SHA CPUID bit in
CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
using inline assembly, performs the CPUID check:
--
int CheckForIntelShaExtensions() {
int a, b, c, d;
// Look for CPUID.7.0.EBX[29]
// EAX = 7, ECX = 0
a = 7;
c = 0;
asm volatile ("cpuid"
:"=a"(a), "=b"(b), "=c"(c), "=d"(d)
:"a"(a), "c"(c)
);
// Intel® SHA Extensions feature bit is EBX[29]
return ((b >> 29) & 1);
}
--
On CPU with sha_ni the program return "1". Otherwise it return "0".
[Test Case]
* Reproducible with Xenial/Zesty/Artful release.
* Generated a checksum of a big file (e.g. 5GB file) with openssl
$ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
SHA256(/var/tmp/5Gfile)=
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
real 0m12.835s
user 0m12.344s
sys 0m0.484s
* Openssl speed
$ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
OpenSSL 1.0.2g 1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int)
blowfish(idx)
compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
The performance are clearly better when using the patch which take
benefit of the sha extension. (See Regression Potential section for
result with patch)
[Regression Potential]
* Note : IRC discussion with infinity :
https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8
* Note from irc discussion with apw and rbasak :
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2
* It basically allow openssl to take benefit of sha extension
potential (mostly performance-wise) now that new AMD cpu starting to
have the capability.
* The code check the CPUID bit to determine if the sha instructions
are available are
[Touch-packages] [Bug 1299838] Re: [Radiance] Selection points next to menu items disappear when highlighted
Ping! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1299838 Title: [Radiance] Selection points next to menu items disappear when highlighted Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: When using the Radiance theme, the selection points, which are next to menu items, disappear when highlighted. See the attached screen-cast which describes the bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-themes 14.04+14.04.20140327-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 30 19:05:08 2014 InstallationDate: Installed on 2014-03-08 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140304) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1299838/+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 1664818] Re: Not possible to render pre-up, pre-down, post-up, or post-down snippets
> The requirement here is, I need to know when ens1 goes up or down, so > that I can make changes to the bridge interface. The `ifmonitor` script > will monitor the link status of ens1, and then take appropriate actions, > such as restarting a DHCP client, adding or removing routes that have > been programmed via the lan0 bridge to egress on ens1, adding or > removing IP addresses from the configuration, etc. Knowing the status of the physical link so that you can take appropriate action on the bridge/bond makes sense. But it seems to me that should be handled intrinsically by networkd, not something you could or should configure with scripts. Opening a task on systemd for us to verify the behavior here. When all the physical links in a bridge/bond drop, does networkd treat that as a down / subsequent up event? When you say "egress on ens1", what do you mean? Your network config doesn't show any such routes. Why would these routes be managed externally to networkd? > In the ifupdown world, the other horrible hack I've sometimes found > necessary (although the reason why is eluding me at the moment) is when > I want an interface to be 'manual', yet behave like a 'static' > definition, in that it should configure itself automatically when it > comes online. So I might have something like: In ifupdown, I would expect to handle this as a static network without 'auto'. For netplan / networkd, this looks like it needs some further work to support, already captured in bug #1664844. ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Status: New => Triaged ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.05 ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1664818 Title: Not possible to render pre-up, pre-down, post-up, or post-down snippets Status in netplan: New Status in systemd package in Ubuntu: Triaged Bug description: Many configurations require scripts to run before or after an interface comes up or down. Example: I had a situation where I needed to render a post-up script to monitor an interface with ifupdown (and with the interface set to manual mode, because if the link was down I didn't want to require DHCP to run before the system continued booting). This is similar to what NetworkManager does in order to launch (or kill) a DHCP client. Other use cases involve setting up custom routes (such as when complex logic involving metrics or source routing is required) or anything else the designers of the netplan rendering engine didn't think of, such as invoking workarounds or special settings required for a particular NIC or environment, iptables rules that should be added or removed, etc. A follow-on issue is, it should be possible to ask that custom scripts run if the *link* is detected to come up or down. But I'll be happy if netplan first can simply replicate the custom-script-invoking behavior of ifupdown. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1664818/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
@xnox you previously mentioned that you had some systemd SRUs to prepare. Feel free to include this fix in those SRUs to address the error tracker reports. It just doesn't quite make sense to do a standalone security update of the init daemon for a low priority security issue. This bug is an interesting corner case of not being quite important enough to warrant a security update yet being enough of an annoyance that it warrants an SRU. My apologies for not noticing this fact earlier. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Confirmed Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal [Testcase] Notice the dropoff rate of the crash report on errors: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1674399] [openssl/zesty] possible regression found
As a part of the Stable Release Updates quality process a search for
Launchpad bug reports using the version of openssl from zesty-proposed
was performed and bug 1692981 was found. Please investigate this bug
report to ensure that a regression will not be created by this SRU. In
the event that this is not a regression remove the "verification-failed"
tag from this bug report and add the tag "bot-stop-nagging" to bug
1692981 (not this bug). Thanks!
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1674399
Title:
OpenSSL CPU detection for AMD Ryzen CPUs
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Committed
Status in openssl source package in Yakkety:
Fix Committed
Status in openssl source package in Zesty:
Fix Committed
Status in openssl source package in Artful:
Fix Released
Bug description:
[Impact]
* Context:
AMD added support in their processors for SHA Extensions[1] (CPU flag:
sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in
64bit only (Confirmed with AMD representative). Current OpenSSL
version in Ryzens still calls SHA for SSSE3 routine as result a number
of extensions were effectively masked on Ryzen and shows no
improvement.
[1] /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 23
model : 1
model name : AMD Ryzen 5 1600 Six-Core Processor
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm
constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni
pclmulqdq monitor ssse3 fma cx16 sse
4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm
extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce
topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall
fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho
pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
[2] - sha_ni: SHA1/SHA256 Instruction Extensions
[3] - https://en.wikipedia.org/wiki/Ryzen
...
All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES,
CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5]
...
* Program to performs the CPUID check:
Reference :
https://software.intel.com/en-us/articles/intel-sha-extensions
... Availability of the Intel® SHA Extensions on a particular
processor can be determined by checking the SHA CPUID bit in
CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function,
using inline assembly, performs the CPUID check:
--
int CheckForIntelShaExtensions() {
int a, b, c, d;
// Look for CPUID.7.0.EBX[29]
// EAX = 7, ECX = 0
a = 7;
c = 0;
asm volatile ("cpuid"
:"=a"(a), "=b"(b), "=c"(c), "=d"(d)
:"a"(a), "c"(c)
);
// Intel® SHA Extensions feature bit is EBX[29]
return ((b >> 29) & 1);
}
--
On CPU with sha_ni the program return "1". Otherwise it return "0".
[Test Case]
* Reproducible with Xenial/Zesty/Artful release.
* Generated a checksum of a big file (e.g. 5GB file) with openssl
$ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile
SHA256(/var/tmp/5Gfile)=
8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8
real 0m12.835s
user 0m12.344s
sys 0m0.484s
* Openssl speed
$ openssl speed sha1
Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s
Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s
Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s
Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s
Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s
OpenSSL 1.0.2g 1 Mar 2016
built on: reproducible build, date unspecified
options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int)
blowfish(idx)
compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT
-DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall
-DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5
-DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM
-DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55
The performance are clearly better when using the patch which take
benefit of the sha extension. (See Regression Potential section for
result with patch)
[Regression Potential]
* Note : IRC discussion with infinity :
[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
Lennart pointed out in the upstream pull request that systemd-resolved is respawned after crashing. Therefore, Ubuntu Security considers this security issue to be a low priority. To reduce the risk of regressions in security updates, our general rule is to only perform security updates that fix a medium or higher issue or wait until around five low issues have accumulated. The fix is simple and low risk but there's always inherent risk in building/publishing/installing new binaries. We'll include the fix in a future security update if there are new issues discovered in systemd. ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Yakkety) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Confirmed Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal [Testcase] Notice the dropoff rate of the crash report on errors: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
Regarding the Bose Quiet Comfort ... those are noise cancelling headphones, it is no surprise to me that those cancel the hiss. I have tested multiple normal earphones and I can reproduce the issue everytime. -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1693599] Re: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxdamage in Ubuntu. https://bugs.launchpad.net/bugs/1693599 Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxdamage package in Ubuntu: New Bug description: I was installing wine when my system came unresposive and I decided to restart it. So something about the apt still running on my system when I restarted. sudo dpkg --configure -a does not work output of this command is. Setting up libsystemd0:i386 (232-21ubuntu3) ... Setting up libjpeg-turbo8:i386 (1.5.1-0ubuntu1) ... Setting up libogg0:i386 (1.3.2-1) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up libxdmcp6:i386 (1:1.1.2-1.1) ... Setting up libsamplerate0:i386 (0.1.8-8) ... Setting up libgsm1:i386 (1.0.13-4) ... Setting up libxau6:i386 (1:1.0.8-1) ... Setting up libxcb1:i386 (1.11.1-1ubuntu1) ... Setting up libx11-6:i386 (2:1.6.4-3) ... Setting up libxrender1:i386 (1:0.9.10-1) ... dpkg: error processing package libxdamage1:i386 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Setting up libxext6:i386 (2:1.3.3-1) ... Setting up libxfixes3:i386 (1:5.0.3-1) ... Setting up libxcursor1:i386 (1:1.1.14-1) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Errors were encountered while processing: libxdamage1:i386 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libxdamage1:i386 1:1.1.4-2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.1 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 Date: Thu May 25 19:18:31 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DuplicateSignature: package:libxdamage1:i386:1:1.1.4-2 Setting up firefox-locale-en (53.0.3+build1-0ubuntu0.17.04.2) ... dpkg: error processing package libxdamage1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated Graphics Controller [10cf:15e9] InstallationDate: Installed on 2017-05-16 (9 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: FUJITSU LIFEBOOK E751 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=c917995c-00fa-4501-8c37-5fe93c98b07f ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libxdamage Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.22 dmi.board.name: FJNB223 dmi.board.vendor: FUJITSU dmi.board.version: G3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E751 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/26/2013:svnFUJITSU:pnLIFEBOOKE751:pvr10601409472:rvnFUJITSU:rnFJNB223:rvrG3:cvnFUJITSU:ct10:cvrLIFEBOOKE751: dmi.product.name: LIFEBOOK E751 dmi.product.version: 10601409472 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 xserver.bootTime: Thu May 25 19:13:26 2017 xserver.configfile: default xserver.errors:
[Touch-packages] [Bug 1693599] [NEW] package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: I was installing wine when my system came unresposive and I decided to restart it. So something about the apt still running on my system when I restarted. sudo dpkg --configure -a does not work output of this command is. Setting up libsystemd0:i386 (232-21ubuntu3) ... Setting up libjpeg-turbo8:i386 (1.5.1-0ubuntu1) ... Setting up libogg0:i386 (1.3.2-1) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up libxdmcp6:i386 (1:1.1.2-1.1) ... Setting up libsamplerate0:i386 (0.1.8-8) ... Setting up libgsm1:i386 (1.0.13-4) ... Setting up libxau6:i386 (1:1.0.8-1) ... Setting up libxcb1:i386 (1.11.1-1ubuntu1) ... Setting up libx11-6:i386 (2:1.6.4-3) ... Setting up libxrender1:i386 (1:0.9.10-1) ... dpkg: error processing package libxdamage1:i386 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Setting up libxext6:i386 (2:1.3.3-1) ... Setting up libxfixes3:i386 (1:5.0.3-1) ... Setting up libxcursor1:i386 (1:1.1.14-1) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Errors were encountered while processing: libxdamage1:i386 ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libxdamage1:i386 1:1.1.4-2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.1 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 Date: Thu May 25 19:18:31 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DuplicateSignature: package:libxdamage1:i386:1:1.1.4-2 Setting up firefox-locale-en (53.0.3+build1-0ubuntu0.17.04.2) ... dpkg: error processing package libxdamage1:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 2nd Generation Core Processor Family Integrated Graphics Controller [10cf:15e9] InstallationDate: Installed on 2017-05-16 (9 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: FUJITSU LIFEBOOK E751 PackageArchitecture: i386 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic.efi.signed root=UUID=c917995c-00fa-4501-8c37-5fe93c98b07f ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: libxdamage Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.22 dmi.board.name: FJNB223 dmi.board.vendor: FUJITSU dmi.board.version: G3 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK E751 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.22:bd04/26/2013:svnFUJITSU:pnLIFEBOOKE751:pvr10601409472:rvnFUJITSU:rnFJNB223:rvrG3:cvnFUJITSU:ct10:cvrLIFEBOOKE751: dmi.product.name: LIFEBOOK E751 dmi.product.version: 10601409472 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 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.14-0ubuntu1 xserver.bootTime: Thu May 25 19:13:26 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset ** Affects: libxdamage (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package compiz-0.9 i386 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxdamage in Ubuntu. https://bugs.launchpad.net/bugs/1693599 Title: package libxdamage1:i386 1:1.1.4-2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxdamage package
[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
@spike speigel: The tlp issue in the arch Linux wiki is unrelated. The point I was that when tlp is installed and no audio is currently playing, tlp turns off the sound card and thus the hiss disappears. The second point I was trying to say: Of course the white noise is audible when nothing is playing, but only if audio is not muted. @Kai-Heng Feng: Unfortunately I can't boot your kernel (BTRFS error: could not find root 8). Could you give me the applied patch or supply a more recent kernel build? -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1693593] [NEW] libgtk-3-0-dbg is missing in Zesty
Public bug reported: Through Yakkety there was a debug package for libgtk 3, but it's missing in Zesty: https://packages.ubuntu.com/search?keywords=libgtk-3-0-dbg=names=all=all ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1693593 Title: libgtk-3-0-dbg is missing in Zesty Status in gtk+3.0 package in Ubuntu: New Bug description: Through Yakkety there was a debug package for libgtk 3, but it's missing in Zesty: https://packages.ubuntu.com/search?keywords=libgtk-3-0-dbg=names=all=all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1693593/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Solves the problem for me (ppa:ubuntu-audio-dev/pulse-testing). I can't comment on the reliability, since I've tested the procedure only a few times, but I don't need anymore to perform the disconnection/reconnection dance. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: In Progress Bug description: [Impact] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first. A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Verify in Sound settings you have it set to A2DP mode. 3. Turn off and then on the Bluetooth device. 4. Verify the device has reconnected and if not, force it to in the Bluetooth indicator menu. 5. Open Sound settings again, select the device and verify it's reappeared in A2DP mode. 6. Click 'Test Sound'. Expected: Sound can be heard from the Bluetooth device. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1438510. Possibly others too. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) 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 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI 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.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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/bluez/+bug/1582213/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates
I tested this again today with Ubuntu 16.04, Xenial, but I installed the 16.10 version of unattended-upgrades and installed the version of systemd from xenial-updates before running the test. The results were the same and /var/log/unattended-upgrades/unattended-upgrades- shutdown.log is still empty. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Status in OEM Priority Project: In Progress Status in OEM Priority Project xenial series: New Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1693488] Re: python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed
** Tags added: unmetdeps -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693488 Title: python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed Status in click package in Ubuntu: New Bug description: On `sudo apt update ; sudo apt upgrade` I got the following error ``` Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed E: Broken packages ``` I have the -proposed repository enabled but Software Updater wasn't installing a certain update to fix bug 1672424 even before I enabled -proposed, so I'm guessing that's because this broken package blocked the update. I fixed this issue by using `apt policy` to check the two packages mentioned, that showed me that `python3-click` was not installed, I ran `sudo apt install python3-click` which removed `click` (is that an issue?!), `python3-click-package`, and installed `python3-click` and `python3-colorama`. This allowed me to run `sudo apt upgrade` successfully. Although I've resolved the issue (albeit by removing packages that maybe shouldn't be removed?), presumably users shouldn't be expected to resolve this sort of problem normally? I have some PPAs enabled (for KDE Connect Indicator, Wine, Spotify, OBS, Neofetch, get-iplayer, Yarn). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: python3-click-package (not installed) ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu May 25 12:38:42 2017 InstallationDate: Installed on 2016-11-01 (204 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: click UpgradeStatus: Upgraded to zesty on 2017-04-17 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693488/+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 1693570] Re: package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1693570 Title: package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in software-properties package in Ubuntu: New Bug description: Beetween of update the os sand this message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.20.7 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Thu May 25 19:17:33 2017 DuplicateSignature: package:software-properties-common:0.96.20.7 Setting up software-properties-common (0.96.20.7) ... Segmentation fault (core dumped) dpkg: error processing package software-properties-common (--configure): subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2016-08-08 (290 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: software-properties Title: package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1693570/+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 1693570] [NEW] package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139
Public bug reported: Beetween of update the os sand this message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.20.7 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Thu May 25 19:17:33 2017 DuplicateSignature: package:software-properties-common:0.96.20.7 Setting up software-properties-common (0.96.20.7) ... Segmentation fault (core dumped) dpkg: error processing package software-properties-common (--configure): subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2016-08-08 (290 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: software-properties Title: package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1693570 Title: package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 Status in software-properties package in Ubuntu: New Bug description: Beetween of update the os sand this message. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: software-properties-common 0.96.20.7 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 Date: Thu May 25 19:17:33 2017 DuplicateSignature: package:software-properties-common:0.96.20.7 Setting up software-properties-common (0.96.20.7) ... Segmentation fault (core dumped) dpkg: error processing package software-properties-common (--configure): subprocess installed post-installation script returned error exit status 139 ErrorMessage: subprocess installed post-installation script returned error exit status 139 InstallationDate: Installed on 2016-08-08 (290 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: software-properties Title: package software-properties-common 0.96.20.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1693570/+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 1682136] Re: dnsmasq bad hex constant with 2 mac addresses but not true
** Changed in: dnsmasq (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1682136 Title: dnsmasq bad hex constant with 2 mac addresses but not true Status in dnsmasq package in Ubuntu: Invalid Bug description: Following line of dnsmasq.conf will not allow dnsmasq to start giving error "bad hex constant at line x in /etc/dnsmasq.conf" and this despite the fact that there is no error in mac addresses. dhcp- host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi With only one of those two mac addresses, all is good, so there is no error in mac addresses. In the dnsmasq.conf they are other dhcp-host with multiple mac addresses like dhcp- host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi and they are not rejected. When copying the default configuration line in a dnsmasq-2.72-3 of Debian 8.7, no problem. Description:Ubuntu 12.04.5 LTS Release:12.04 dnsmasq: Installé : 2.59-4ubuntu0.2 Candidat : 2.59-4ubuntu0.2 Table de version : *** 2.59-4ubuntu0.2 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 Packages 100 /var/lib/dpkg/status 2.59-4 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf] ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.15 Architecture: amd64 Date: Wed Apr 12 15:25:20 2017 MarkForUpload: True PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1682136/+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 1682136] Re: dnsmasq bad hex constant with 2 mac addresses but not true
As told in the original message, there was no problem with a dnsmasq-2.72-3 version of Debian 8. I downloaded the dnsmasq source version 2.76, compile it and problem is gone. You can close this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1682136 Title: dnsmasq bad hex constant with 2 mac addresses but not true Status in dnsmasq package in Ubuntu: Incomplete Bug description: Following line of dnsmasq.conf will not allow dnsmasq to start giving error "bad hex constant at line x in /etc/dnsmasq.conf" and this despite the fact that there is no error in mac addresses. dhcp- host=a8:6b:ad:4b:83:bf,44:a8:42:fb:a2:df,172.16.30.47,w10-assist1,net:ordi,infinite,set:ordi With only one of those two mac addresses, all is good, so there is no error in mac addresses. In the dnsmasq.conf they are other dhcp-host with multiple mac addresses like dhcp- host=a8:6b:ad:4a:d9:d3,44:a8:42:fb:a2:85,00:24:9b:12:71:be,172.16.30.43,w10-pierre,net:ordi,infinite,set:ordi and they are not rejected. When copying the default configuration line in a dnsmasq-2.72-3 of Debian 8.7, no problem. Description:Ubuntu 12.04.5 LTS Release:12.04 dnsmasq: Installé : 2.59-4ubuntu0.2 Candidat : 2.59-4ubuntu0.2 Table de version : *** 2.59-4ubuntu0.2 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/universe amd64 Packages 100 /var/lib/dpkg/status 2.59-4 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dnsmasq 2.59-4ubuntu0.2 [modified: etc/dnsmasq.conf] ProcVersionSignature: Ubuntu 3.13.0-116.163~precise1-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.15 Architecture: amd64 Date: Wed Apr 12 15:25:20 2017 MarkForUpload: True PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dnsmasq.conf: 2017-04-12T12:04:33.732724 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1682136/+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 1458204] Re: removing kernels should not require a restart afterward
** Attachment added: "code to add in probably all post-installation scripts except initramfs-tools and dkms to exit them before their job in case removing linux-image-extra" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4883521/+files/addition2 ** Patch removed: "code to add before touching /var/run/reboot-required in post-installation scripts ; ver. 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4882547/+files/addition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
** Patch removed: "code to add before touching /var/run/reboot-required in post-installation scripts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4881881/+files/addition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1693160] Re: software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd] failed to install/upgrade: unable to make backup link of './usr/sb
Thank you for your message I do not use ssh (I don't know what it is).
This is the message on my computer when I was notified that the updating
could not be completed "THE PACKAGE SYSTEM IS BROKEN. Check if you are
using third-party repositories (common source of problems) Furthermore run
the following command on a terminal: sudo apt-get-install-f". I tried this
command and it did not help and I do not use third-party repositories. I
will await your instructions. It is comforting to receive this help from
you. I do not know a technician and have been wondering where to take the
computer, if you can advise me how to fix the problem (with my limited
understanding of the computer mechanics) it would very appreciated. Dorothy
On Thu, May 25, 2017 at 1:56 AM, Seth Arnold <1693...@bugs.launchpad.net>
wrote:
> Hello Dorothy,
>
> Please ask whoever takes a look at your computer to inspect this bug.
> ("ubuntu bug 1693160" should suffice.) These error messages are unusual
> and may indicate that ssh and sshd have been set immutable, or set to
> mode , or something even more surprising.
>
> If you never use ssh to connect to other computers, or allow others to
> connect to your computer with ssh, perhaps these should be removed
> entirely.
>
> Thanks
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1693160
>
> Title:
> software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1
> [modified: usr/sbin/sshd] failed to install/upgrade: unable to make
> backup link of './usr/sbin/sshd' before installing new version:
> Operation not permitted
>
> Status in openssh package in Ubuntu:
> New
>
> Bug description:
> I am 85 years old and do not understand the technology nor proper
> explanation of the problem. I simply tried to update my computer and
> at the end there was a notification that there was a problem with the
> system.
>
> ProblemType: Package
> DistroRelease: Ubuntu 16.04
> Package: openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd]
> ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
> Uname: Linux 4.4.0-78-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2.6
> Architecture: amd64
> Date: Tue May 23 06:52:10 2017
> DuplicateSignature:
>package:openssh-server:1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd]
>Unpacking openssh-server (1:7.2p2-4ubuntu2.2) over (1:7.2p2-4ubuntu2.1)
> ...
>dpkg: error processing archive /var/cache/apt/archives/
> openssh-server_1%3a7.2p2-4ubuntu2.2_amd64.deb (--unpack):
> unable to make backup link of './usr/sbin/sshd' before installing new
> version: Operation not permitted
> ErrorMessage: unable to make backup link of './usr/sbin/sshd' before
> installing new version: Operation not permitted
> InstallationDate: Installed on 2016-04-21 (397 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
> RelatedPackageVersions:
>dpkg 1.18.4ubuntu1.2
>apt 1.2.20
> SourcePackage: openssh
> Title: package openssh-server 1:7.2p2-4ubuntu2.1 [modified:
> usr/sbin/sshd] failed to install/upgrade: unable to make backup link of
> './usr/sbin/sshd' before installing new version: Operation not permitted
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/
> 1693160/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1693160
Title:
software notifies a problempackage openssh-server 1:7.2p2-4ubuntu2.1
[modified: usr/sbin/sshd] failed to install/upgrade: unable to make
backup link of './usr/sbin/sshd' before installing new version:
Operation not permitted
Status in openssh package in Ubuntu:
New
Bug description:
I am 85 years old and do not understand the technology nor proper
explanation of the problem. I simply tried to update my computer and
at the end there was a notification that there was a problem with the
system.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd]
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue May 23 06:52:10 2017
DuplicateSignature:
package:openssh-server:1:7.2p2-4ubuntu2.1 [modified: usr/sbin/sshd]
Unpacking openssh-server (1:7.2p2-4ubuntu2.2) over (1:7.2p2-4ubuntu2.1) ...
dpkg: error processing archive
/var/cache/apt/archives/openssh-server_1%3a7.2p2-4ubuntu2.2_amd64.deb
(--unpack):
unable to make backup link of './usr/sbin/sshd' before installing new
version: Operation not permitted
ErrorMessage: unable to make backup link of './usr/sbin/sshd' before
installing new version:
[Touch-packages] [Bug 1627769] Re: limits.conf not applied
On 17.04, even the workaround that Ewan posted in #5 above doesn't work for me. If I add DefaultLimitNOFILE=4 to /etc/systemd/user.conf and log out and log in again, prlimit still shows this: adam:~$ prlimit RESOURCE DESCRIPTION SOFT HARD UNITS ... NOFILE max number of open files4096 4096 files adam:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627769 Title: limits.conf not applied Status in lightdm package in Ubuntu: Confirmed Bug description: Since upgraded to 16.10 Yakkety, modifications in /etc/security/limits.conf are not taken into consideration when logging in the graphical interface. /etc/security/limits.conf: @audio - rtprio 99 @audio - memlockunlimited I tried the same settings in /etc/security/limits.d/audio.conf, to the same results. After logging in Unity, opening a console, the limits are not set: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 Reloging to my user via bash DOES apply the limits: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 blablack@ideaon:~$ su blablack Password: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) unlimited real-time priority (-r) 95 Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well. The exact same setup used to work fine on Xenial 16.04 before upgrade. If you need any more information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 26 17:27:10 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627769/+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 1693548] [NEW] somenon-ASCII password not usable again
Public bug reported: When we use the passwd, if our keyboard layout is not English same as Persian, the password is set successfully, but when we try to login after first restart the available keyboard layout for login only is English layout, And we never can login again for this bug. If in login page other layouts available it's ok. Or passwd must be don't accept any non-ASCII charterer . Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: passwd 1:4.2-3.1ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 25 20:58:24 2017 InstallationDate: Installed on 2017-02-18 (95 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1693548 Title: somenon-ASCII password not usable again Status in shadow package in Ubuntu: New Bug description: When we use the passwd, if our keyboard layout is not English same as Persian, the password is set successfully, but when we try to login after first restart the available keyboard layout for login only is English layout, And we never can login again for this bug. If in login page other layouts available it's ok. Or passwd must be don't accept any non-ASCII charterer . Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: passwd 1:4.2-3.1ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 25 20:58:24 2017 InstallationDate: Installed on 2017-02-18 (95 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1693548/+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 1627769] Re: limits.conf not applied
Apparently Fedora has wrestled with this too: https://bugzilla.redhat.com/show_bug.cgi?id=1364332 The last comment there (https://bugzilla.redhat.com/show_bug.cgi?id=1364332) seems to indicate that this has been fixed in Fedora 26, which has systemd 233. I'm running Ubuntu 17.04 Zesty with systemd 232 and am still seeing this problem. Perhaps systemd 233 will solve the problem for Ubuntu as well? ** Bug watch added: Red Hat Bugzilla #1364332 https://bugzilla.redhat.com/show_bug.cgi?id=1364332 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1627769 Title: limits.conf not applied Status in lightdm package in Ubuntu: Confirmed Bug description: Since upgraded to 16.10 Yakkety, modifications in /etc/security/limits.conf are not taken into consideration when logging in the graphical interface. /etc/security/limits.conf: @audio - rtprio 99 @audio - memlockunlimited I tried the same settings in /etc/security/limits.d/audio.conf, to the same results. After logging in Unity, opening a console, the limits are not set: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 Reloging to my user via bash DOES apply the limits: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) 64 real-time priority (-r) 0 blablack@ideaon:~$ su blablack Password: blablack@ideaon:~$ ulimit -l -r max locked memory (kbytes, -l) unlimited real-time priority (-r) 95 Switching to a console (ctrl+alt+f1) and logging in would apply the limits as well. The exact same setup used to work fine on Xenial 16.04 before upgrade. If you need any more information, please let me know. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: lightdm 1.19.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 26 17:27:10 2016 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1627769/+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 1693024] Re: can't start JACK with real-time scheduling even when in audio group
*** This bug is a duplicate of bug 1627769 *** https://bugs.launchpad.net/bugs/1627769 ** This bug has been marked a duplicate of bug 1627769 limits.conf not applied -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1693024 Title: can't start JACK with real-time scheduling even when in audio group Status in jackd2 package in Ubuntu: New Bug description: I'm running Ubuntu 17.04. I've installed jack2 and have added myself to the 'audio' group as suggested at http://jackaudio.org/faq/linux_rt_config.html But when I start JACK it reports Tue May 23 16:10:24 2017: ERROR: Cannot use real-time scheduling (RR/10)(1: Operation not permitted) Tue May 23 16:10:24 2017: ERROR: AcquireSelfRealTime error I am in the 'audio' group in /etc/group: adam:~$ grep audio /etc/group audio:x:29:pulse,adam adam:~$ (I restarted the machine after adding myself to this group.) 'ulimit' isn't showing real-time priority privileges for me: adam:~$ ulimit -a | grep real real-time priority (-r) 0 adam:~$ The file /etc/security/limits.d/audio.conf looks like this: === # Provided by the jackd package. # # Changes to this file will be preserved. # # If you want to enable/disable realtime permissions, run # #dpkg-reconfigure -p high jackd @audio - rtprio 95 @audio - memlockunlimited #@audio - nice -19 === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1693024/+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 1693541] Re: package qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1693541 Title: package qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libusermetrics package in Ubuntu: New Bug description: installing apache error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 11:55:04 2017 DuplicateSignature: package:qtdeclarative5-usermetrics0.1:1.1.1+15.10.20150915-0ubuntu1 Processing triggers for ufw (0.35-0ubuntu2) ... dpkg: error processing package qtdeclarative5-usermetrics0.1 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libusermetrics Title: package qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1693541/+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 1693541] [NEW] package qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall i
Public bug reported: installing apache error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 11:55:04 2017 DuplicateSignature: package:qtdeclarative5-usermetrics0.1:1.1.1+15.10.20150915-0ubuntu1 Processing triggers for ufw (0.35-0ubuntu2) ... dpkg: error processing package qtdeclarative5-usermetrics0.1 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libusermetrics Title: package qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libusermetrics (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 libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1693541 Title: package qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libusermetrics package in Ubuntu: New Bug description: installing apache error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu May 25 11:55:04 2017 DuplicateSignature: package:qtdeclarative5-usermetrics0.1:1.1.1+15.10.20150915-0ubuntu1 Processing triggers for ufw (0.35-0ubuntu2) ... dpkg: error processing package qtdeclarative5-usermetrics0.1 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: libusermetrics Title: package qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1693541/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports
I installed isc-dhcp-client-noddns from trusty-proposed and I don't get the two random extra high ports anymore: Before: # dpkg -l | grep isc-dhcp- ii isc-dhcp-client 4.2.4-7ubuntu12.9 amd64 ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.9 amd64 common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 716/dhclient udp0 0 0.0.0.0:42496 0.0.0.0:* 716/dhclient udp6 0 0 :::7781 :::* 716/dhclient After: # dpkg -l | grep isc-dhcp- ii isc-dhcp-client 4.2.4-7ubuntu12.10 amd64ISC DHCP client ii isc-dhcp-client-noddns 4.2.4-7ubuntu12.10 amd64Dynamic DNS (DDNS) disabled DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.10 amd64common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 13411/dhclient And if I remove the isc-dhcp-client-noddns package, I get the 2 random ports again: # dpkg -l | grep isc-dhcp- ii isc-dhcp-client 4.2.4-7ubuntu12.10 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.10 amd64common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 565/dhclient udp0 0 0.0.0.0:63510 0.0.0.0:* 565/dhclient udp6 0 0 :::44100:::* 565/dhclient Looks good to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] I did the split such that Trusty users will automatically get "isc- dhcp-client-ddns" installed but users bothered by this bug will have the option to switch to "isc-dhcp-client-noddns". Existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client: dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port With isc-dhcp-client-noddns :
[Touch-packages] [Bug 1688730] Re: click-apparmor ubuntu-app-launch url-dispatcher
This appears to be a transient error:
May 06 18:49:31 hostname update-notifier.desktop[2677]: Traceback (most recent
call last):
May 06 18:49:31 hostname update-notifier.desktop[2677]: File
"/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in
_inline_callbacks
May 06 18:49:31 hostname update-notifier.desktop[2677]: result =
gen.throw(excep)
May 06 18:49:31 hostname update-notifier.desktop[2677]: File
"/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py",
line 92, in commit
May 06 18:49:31 hostname update-notifier.desktop[2677]: _("Installing
updates…"), True)
May 06 18:49:31 hostname update-notifier.desktop[2677]: File
"/usr/lib/python3/dist-packages/defer/__init__.py", line 483, in
_inline_callbacks
May 06 18:49:31 hostname update-notifier.desktop[2677]: result =
gen.throw(excep)
May 06 18:49:31 hostname update-notifier.desktop[2677]: File
"/usr/lib/python3/dist-packages/UpdateManager/backend/InstallBackendAptdaemon.py",
line 159, in _show_transaction
May 06 18:49:31 hostname update-notifier.desktop[2677]: yield trans.run()
May 06 18:49:31 hostname update-notifier.desktop[2677]:
aptdaemon.errors.TransactionFailed: Transaction failed: The package system is
broken
May 06 18:49:31 hostname update-notifier.desktop[2677]: The following packages
have unmet dependencies:
May 06 18:49:31 hostname update-notifier.desktop[2677]: click-apparmor:
Depends: python3:any (>= 3.3~) but it is a virtual package
May 06 18:49:31 hostname update-notifier.desktop[2677]:
Depends: python3-apparmor-click (= 0.3.17) but 0.3.18 is installed
May 06 18:49:31 hostname update-notifier.desktop[2677]:
Depends: apparmor (>= 2.9.1-0ubuntu8~pre8) but 2.11.0-2ubuntu4 is installed
I am able to install click-apparmor just fine here with up to date
17.04. Please update your package cache (eg, 'sudo apt update') and try
again. Closing for now. Please reopen if you are not able to upgrade.
** Changed in: click-apparmor (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to click-apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1688730
Title:
click-apparmor ubuntu-app-launch url-dispatcher
Status in click-apparmor package in Ubuntu:
Invalid
Bug description:
Cannot start click due to a conflict with a different locally-installed
Python 'click' package. Remove it using Python packaging tools and try again.
dpkg: warning: subprocess old pre-removal script returned error exit status 1
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-21-generic 4.10.0-21.23
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: chanchal 2274 F pulseaudio
/dev/snd/controlC0: chanchal 2274 F pulseaudio
CurrentDesktop: Unity:Unity7
Date: Sat May 6 18:58:27 2017
HibernationDevice: RESUME=UUID=459f0094-1f0b-4da8-9fac-1f2e7d6e36bc
InstallationDate: Installed on 2016-02-20 (440 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Dell Inc. Inspiron 5537
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=b87f269a-0aef-4bb0-93fa-18454ad51275 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.10.0-21-generic N/A
linux-backports-modules-4.10.0-21-generic N/A
linux-firmware 1.164.1
SourcePackage: linux
UpgradeStatus: Upgraded to zesty on 2017-05-06 (0 days ago)
dmi.bios.date: 08/19/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 04NGGW
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A04
dmi.modalias:
dmi:bvnDellInc.:bvrA04:bd08/19/2013:svnDellInc.:pnInspiron5537:pvrA04:rvnDellInc.:rn04NGGW:rvrA00:cvnDellInc.:ct8:cvrA04:
dmi.product.name: Inspiron 5537
dmi.product.version: A04
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1688730/+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 1693531] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 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 #1688721, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 Packages that trigger multiple debconf prompts fail to install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1693531 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: I don`t now ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu May 25 00:48:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1693531/+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 1693531] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: I don`t now ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu May 25 00:48:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1693531 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: I don`t now ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu May 25 00:48:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-25 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1693531/+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 1586528] Re: Avahi-daemon withdraws address record
Same symptoms, same result on a headless always-on box running 16.04. Made worse by the fact that I have to hard-power off the box and hook it up to monitor for troubleshooting. Every couple weeks the machine will lose connection to the network. Last time I thought I lost the on-board NIC and went and bought/installed a new NIC card (another Realtek). Two weeks later, same result: syslog shows this: May 24 22:40:14 phaedrus avahi-daemon[857]: Withdrawing address record for 192.168.0.201 on enp4s1. May 24 22:40:14 phaedrus avahi-daemon[857]: Leaving mDNS multicast group on interface enp4s1.IPv4 with address 192.168.0.201. May 24 22:40:14 phaedrus avahi-daemon[857]: Interface enp4s1.IPv4 no longer relevant for mDNS. ## System: Host: phaedrus Kernel: 4.4.0-78-generic x86_64 (64 bit) Console: tty 9 Distro: Ubuntu 16.04 xenial ## Network: (from `inxi -F`) Card-1: Device 000c:d051 IF: N/A state: N/A speed: N/A duplex: N/A mac: N/A Card-2: Realtek RTL8169 PCI Gigabit Ethernet Controller driver: r8169 IF: enp4s1 state: up speed: 1000 Mbps duplex: full mac: 00:0a:cd:2c:93:5f Looks like it might be Realtek 8168/9 related? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1660316] Re: apparmor denial of CUPS
In the meantime, users can workaround this by adjusting /etc/apparmor.d/local/usr.sbin.cupsd to have: capability net_admin, and then reloading the profile with: $ sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.cupsd -- 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/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 comm="apparmor_parser" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: cups 2.2.0-2 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1660316] Re: apparmor denial of CUPS
@Till, see 'man 7 capabilities' for what net_admin grants. We need to understand why the access is needed before granting it. -- 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/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 comm="apparmor_parser" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: cups 2.2.0-2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm
[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
Dear Rodney, and anyone else affected, Please install "isc-dhcp-client-noddns" found in trusty-proposed and provide feedbacks by commenting the bug. Your feedbacks are paramount for the success of this SRU. Additionally, I will also do some precision testing on Trusty and re-run the release upgrade scenarios from Trusty to Xenial. Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] I did the split such that Trusty users will automatically get "isc- dhcp-client-ddns" installed but users bothered by this bug will have the option to switch to "isc-dhcp-client-noddns". Existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client: dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port With isc-dhcp-client-noddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Xenial also has both distinct dhclient binary package but in the opposite way. We have decided to use the opposite way approach for not impacting actual Trusty users by changing the nature of isc-dhcp- client itself. Caribou and I, slashd, have also tested a couple of release upgrades from Trusty to Xenial with both scenarios : 1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns" 2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns" and both scenarios worked as expected for caribou and I. (See comment #42) Results : === ** Upgrade tested with isc-dhcp-client ** # dpkg -l ii isc-dhcp-client 4.2.4-7ubuntu12.8 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.8 amd64common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:20114 0.0.0.0:* 632/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 632/dhclient udp6 0 0 :::52249:::* 632/dhclient After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2) ii isc-dhcp-client 4.3.3-5ubuntu12.7 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.3.3-5ubuntu12.7 amd64common files used by all of the isc-dhcp packages # netstat -anputa |
[Touch-packages] [Bug 1693520] [NEW] Interrupting (Ctrl-C) jpegtran causes data loss when -outfile points to input file
Public bug reported: For optimizing files in-place with jpegtran, especially from scripts and when dealing with lots of pictures, it's handy to be able to specify input file as -outfile. But there's a catch: Steps to reproduce: 0. Have a large JPEG file, or, alternatively, somewhat slow CPU 1. `jpegtran -optimize -copy all -perfect -outfile large.jpg large.jpg` 2. Hit Ctrl-C before the command finishes Result: You now have a broken large.jpg with only part, if any, of the image data remaining. What I expect to happen: To have large.jpg as it was before I invoked jpegtran. Workarounds: Obviously the traditional workaround of specifying an intermediate temporary output file, then replacing the original with the temporary file only once jpegtran has finished. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo-progs 1.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 25 17:16:16 2017 InstallationDate: Installed on 2016-10-13 (224 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: libjpeg-turbo UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1693520 Title: Interrupting (Ctrl-C) jpegtran causes data loss when -outfile points to input file Status in libjpeg-turbo package in Ubuntu: New Bug description: For optimizing files in-place with jpegtran, especially from scripts and when dealing with lots of pictures, it's handy to be able to specify input file as -outfile. But there's a catch: Steps to reproduce: 0. Have a large JPEG file, or, alternatively, somewhat slow CPU 1. `jpegtran -optimize -copy all -perfect -outfile large.jpg large.jpg` 2. Hit Ctrl-C before the command finishes Result: You now have a broken large.jpg with only part, if any, of the image data remaining. What I expect to happen: To have large.jpg as it was before I invoked jpegtran. Workarounds: Obviously the traditional workaround of specifying an intermediate temporary output file, then replacing the original with the temporary file only once jpegtran has finished. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo-progs 1.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 25 17:16:16 2017 InstallationDate: Installed on 2016-10-13 (224 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: libjpeg-turbo UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1693520/+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 1073945] Re: dconf worker segfault
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: d-conf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1073945 Title: dconf worker segfault Status in d-conf package in Ubuntu: Confirmed Bug description: Nov 1 14:10:09 Jupiter kernel: [87697.123367] dconf worker[7225]: segfault at 8 ip 7f4d3630ccea sp 7f4d1bdf38a0 error 4 in libgio-2.0.so.0.3400.0[7f4d36265000+14e000] ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: dconf-tools 0.14.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 1 14:14:58 2012 InstallationDate: Installed on 2012-03-01 (244 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) MarkForUpload: True SourcePackage: d-conf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1073945/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2017-9217 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Confirmed Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal [Testcase] Notice the dropoff rate of the crash report on errors: The Ubuntu Error Tracker has been receiving reports about a problem regarding systemd. This problem was most recently seen with package version 233-6ubuntu2, the problem page at https://errors.ubuntu.com/problem/ea90aefe098653f44b46e56d72e2cc05ff980465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1574097] Re: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1605952 *** https://bugs.launchpad.net/bugs/1605952 ** This bug has been marked a duplicate of bug 1605952 [Online-Update] delllctservice* init scripts are missing LSB headers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1574097 Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in sysvinit package in Ubuntu: Expired Bug description: Like bug installation when upgrade from 14.04 (dell factory state) to ubuntu 16.04. I think, its kernel version problem. Thanks ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initscripts 2.88dsf-59.3ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36 Uname: Linux 3.13.0-85-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 22:29:07 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: sysvinit Title: package initscripts 2.88dsf-59.3ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1574097/+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 1693507] Re: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1693334 *** https://bugs.launchpad.net/bugs/1693334 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 #1693334, 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. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1693334 package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- 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/1693507 Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: While updating langauge the install fails while there is an internetconnection. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu May 25 13:22:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1693507/+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 1693507] [NEW] package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1693334 *** https://bugs.launchpad.net/bugs/1693334 Public bug reported: While updating langauge the install fails while there is an internetconnection. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu May 25 13:22:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1693507 Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: While updating langauge the install fails while there is an internetconnection. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.8 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu May 25 13:22:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1693507/+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] [NEW] Remove mlx4.conf
Public bug reported: 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 ** Affects: kmod (Ubuntu) Importance: Undecided Status: New -- 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: New 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 1648183] Re: Crackling and popping sound when using headphones
Yep fixed for me also. That's fantastic, thanks heaps Robert!! -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 385714] Re: GRUB2 Theme for Ubuntu
** Changed in: grub2 (Ubuntu) Status: Incomplete => Triaged ** Changed in: ubuntu-themes (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/385714 Title: GRUB2 Theme for Ubuntu Status in grub2 package in Ubuntu: Triaged Status in ubuntu-themes package in Ubuntu: Triaged Bug description: Binary package hint: grub2 The binary grub-pc installs /etc/grub.d/05_debian_theme which is where grub2 finds its theme. It looks for /usr/share/images/desktop-base/moreblue-orbit-grub.png to use as the theme background, which is part of desktop-base. Of course, we don't install that by default as it contains all the Debian theming. So grub shouldn't be looking for that theme, but we also need to provide a theme ourselves. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/385714/+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 1176046] Please test proposed package
Hello Rodney, or anyone else affected, Accepted isc-dhcp into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.3.3-5ubuntu12.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] I did the split such that Trusty users will automatically get "isc- dhcp-client-ddns" installed but users bothered by this bug will have the option to switch to "isc-dhcp-client-noddns". Existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client: dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port With isc-dhcp-client-noddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Xenial also has both distinct dhclient binary package but in the opposite way. We have decided to use the opposite way approach for not impacting actual Trusty users by changing the nature of isc-dhcp- client itself. Caribou and I, slashd, have also tested a couple of release upgrades from Trusty to Xenial with both scenarios : 1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns" 2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns" and both scenarios worked as expected for caribou and I. (See comment #42) Results : === ** Upgrade tested with isc-dhcp-client ** # dpkg -l ii isc-dhcp-client 4.2.4-7ubuntu12.8 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.8 amd64common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0
[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
Hello Rodney, or anyone else affected, Accepted isc-dhcp into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/isc- dhcp/4.2.4-7ubuntu12.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: isc-dhcp (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: isc-dhcp (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] I did the split such that Trusty users will automatically get "isc- dhcp-client-ddns" installed but users bothered by this bug will have the option to switch to "isc-dhcp-client-noddns". Existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client: dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port With isc-dhcp-client-noddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Xenial also has both distinct dhclient binary package but in the opposite way. We have decided to use the opposite way approach for not impacting actual Trusty users by changing the nature of isc-dhcp- client itself. Caribou and I, slashd, have also tested a couple of release upgrades from Trusty to Xenial with both scenarios : 1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns" 2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns" and both scenarios worked as expected for caribou and I. (See comment #42) Results : === ** Upgrade tested with isc-dhcp-client ** # dpkg -l ii isc-dhcp-client 4.2.4-7ubuntu12.8 amd64ISC DHCP client
[Touch-packages] [Bug 1693288] Re: package krb5-locales 1.15-1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración.
We can't know for sure what happened then. I suspect a full disk, as you said you said in comment #3 that you had just 130MB available. I suggest for you now to run "sudo apt -f install" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1693288 Title: package krb5-locales 1.15-1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in krb5 package in Ubuntu: Incomplete Bug description: he sound doesnt work. I had desisntaled the driver with "sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils" and the response was: Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Los paquetes indicados a continuación se instalaron de forma automática y ya no son necesarios. apturl-common gnome-software-common libfftw3-single3 libgtkspell3-3-0 libsnapd-glib1 python3-software-properties python3-xkit snapd-login-service software-properties-common unattended-upgrades Utilice «sudo apt autoremove» para eliminarlos. Los siguientes paquetes se ELIMINARÁN: alsa-base* alsa-utils* apturl* gnome-software* gnome-software-plugin-snap* linux-sound-base* nautilus-share* software-properties-gtk* ubuntu-desktop* ubuntu-drivers-common* ubuntu-software* 0 actualizados, 0 nuevos se instalarán, 11 para eliminar y 14 no actualizados. 1 no instalados del todo o eliminados. Se necesita descargar 14,3 kB de archivos. Se liberarán 5.386 kB después de esta operación. ¿Desea continuar? [S/n] s Des:1 http://ar.archive.ubuntu.com/ubuntu zesty/main amd64 krb5-locales all 1.15-1 [14,3 kB] Descargados 14,3 kB en 1s (10,2 kB/s) (Leyendo la base de datos ... 215231 ficheros o directorios instalados actualmente.) Desinstalando ubuntu-desktop (1.379) ... Desinstalando alsa-base (1.0.25+dfsg-0ubuntu5) ... Desinstalando ubuntu-software (3.22.7-0ubuntu3.17.04.2) ... Desinstalando nautilus-share (0.7.3-2ubuntu2) ... Desinstalando apturl (0.5.2ubuntu12) ... Desinstalando linux-sound-base (1.0.25+dfsg-0ubuntu5) ... Desinstalando gnome-software-plugin-snap (3.22.7-0ubuntu3.17.04.2) ... Desinstalando gnome-software (3.22.7-0ubuntu3.17.04.2) ... Desinstalando software-properties-gtk (0.96.24.13) ... Desinstalando ubuntu-drivers-common (1:0.4.22) ... Desinstalando alsa-utils (1.1.3-1ubuntu1) ... Procesando disparadores para mime-support (3.60ubuntu1) ... Procesando disparadores para desktop-file-utils (0.23-1ubuntu2) ... Procesando disparadores para libglib2.0-0:amd64 (2.52.0-1) ... Procesando disparadores para bamfdaemon (0.5.3+17.04.20170406-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... dpkg: error al procesar el paquete krb5-locales (--configure): El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Procesando disparadores para man-db (2.7.6.1-2) ... Procesando disparadores para shared-mime-info (1.8-1) ... Procesando disparadores para gnome-menus (3.13.3-6ubuntu5) ... Procesando disparadores para hicolor-icon-theme (0.15-1) ... Se encontraron errores al procesar: krb5-locales E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.04 Package: krb5-locales 1.15-1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed May 24 13:01:42 2017 Dependencies: ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2017-05-18 (6 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: krb5 Title: package krb5-locales 1.15-1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1693288/+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 1692275] Re: package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1692275 Title: package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: the upgrade was interrupted without any apparent reason. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: unattended-upgrades:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 19 21:18:39 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-04-28 (22 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1692275/+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 1693488] [NEW] python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed
Public bug reported: On `sudo apt update ; sudo apt upgrade` I got the following error ``` Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed E: Broken packages ``` I have the -proposed repository enabled but Software Updater wasn't installing a certain update to fix bug 1672424 even before I enabled -proposed, so I'm guessing that's because this broken package blocked the update. I fixed this issue by using `apt policy` to check the two packages mentioned, that showed me that `python3-click` was not installed, I ran `sudo apt install python3-click` which removed `click` (is that an issue?!), `python3-click-package`, and installed `python3-click` and `python3-colorama`. This allowed me to run `sudo apt upgrade` successfully. Although I've resolved the issue (albeit by removing packages that maybe shouldn't be removed?), presumably users shouldn't be expected to resolve this sort of problem normally? I have some PPAs enabled (for KDE Connect Indicator, Wine, Spotify, OBS, Neofetch, get-iplayer, Yarn). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: python3-click-package (not installed) ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu May 25 12:38:42 2017 InstallationDate: Installed on 2016-11-01 (204 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: click UpgradeStatus: Upgraded to zesty on 2017-04-17 (38 days ago) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Description changed: - On `sudo apt update ; sudo apt upgrade' I got the following error + On `sudo apt update ; sudo apt upgrade` I got the following error ``` Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. - python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed + python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed E: Broken packages ``` I have the -proposed repository enabled but Software Updater wasn't installing a certain update to fix bug 1672424 even before I enabled -proposed, so I'm guessing that's because this broken package blocked the update. I fixed this issue by using `apt policy` to check the two packages mentioned, that showed me that `python3-click` was not installed, I ran `sudo apt install python3-click` which removed `click` (is that an issue?!), `python3-click-package`, and installed `python3-click` and `python3-colorama`. This allowed me to run `sudo apt upgrade` successfully. Although I've resolved the issue (albeit by removing packages that maybe shouldn't be removed?), presumably users shouldn't be expected to resolve this sort of problem normally? I have some PPAs enabled (for KDE Connect Indicator, Wine, Spotify, OBS, Neofetch, get-iplayer, Yarn). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: python3-click-package (not installed) ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Thu May 25 12:38:42 2017 InstallationDate: Installed on 2016-11-01 (204 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: click UpgradeStatus: Upgraded to zesty on 2017-04-17 (38 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693488 Title: python3-click-package : Conflicts: python3-click but 6.6-1 is to be installed Status in click package in Ubuntu: New Bug description: On `sudo apt update ; sudo apt upgrade` I got the following error ``` Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
Sorry, I should have been more constructive with my comment. The workaround in #10 seems to partially work. It doesn't allow the "login" password keychain to be unlocked on login, but it at least let you see the passwords in seahorse so that it can be unlocked manually - which in turn prevents applications from hanging. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: New Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+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 1458204] Re: removing kernels should not require a restart afterward
The code could be added to /etc/kernel/postinst.d/zz-update-grub, too, to avoid unnecessarily updating grub. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: 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/unattended-upgrades/+bug/1458204/+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 1589605] Re: evolution-calendar-factory uses lots of memory
Upgraded Ubuntu Gnome 16.04.2 to Gnome 3.20.4 with same issue. Except I get 4 running processes and I can find no way of disabling it. Its a bummer. I don't use calendar at all. Here is what I did to disable these services; sudo chmod -x /usr/lib/evolution/evolution-calendar-factory sudo chmod -x /usr/lib/evolution/evolution-addressbook-factory sudo chmod -x /usr/lib/evolution/evolution-source-registry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1693288] Re: package krb5-locales 1.15-1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuració
Dear Andreas, In the /var/log/apt there are only 3 files: history.log term.log eipp.log.xz history.log has in the last lines: Start-Date: 2017-05-22 19:47:46 Commandline: /usr/bin/unattended-upgrade Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-10.1ubuntu4, 1:9.10.3.dfsg.P4-10.1ubuntu5), libwbclient0:amd64 (2:4.5.4+dfsg-1ubuntu2, 2:4.5.8+dfsg-0ubuntu0.17.04.1), libicu57:amd64 (57.1-5, 57.1-5ubuntu0.1), samba-libs:amd64 (2:4.5.4+dfsg-1ubuntu2, 2:4.5.8+dfsg-0ubuntu0.17.04.1), libisc-export160:amd64 (1:9.10.3.dfsg.P4-10.1ubuntu4, 1:9.10.3.dfsg.P4-10.1ubuntu5), libsmbclient:amd64 (2:4.5.4+dfsg-1ubuntu2, 2:4.5.8+dfsg-0ubuntu0.17.04.1), libnss3:amd64 (2:3.26.2-1ubuntu1, 2:3.28.4-0ubuntu0.17.04.1), libfreetype6:amd64 (2.6.3-3ubuntu2, 2.6.3-3ubuntu2.2), libisccc140:amd64 (1:9.10.3.dfsg.P4-10.1ubuntu4, 1:9.10.3.dfsg.P4-10.1ubuntu5), libnspr4:amd64 (2:4.12-6ubuntu1, 2:4.13.1-0ubuntu0.17.04.1), libcurl3-gnutls:amd64 (7.52.1-4ubuntu1, 7.52.1-4ubuntu1.1), libxslt1.1:amd64 (1.1.29-2, 1.1.29-2ubuntu0.1) End-Date: 2017-05-22 19:48:11 Start-Date: 2017-05-22 20:24:09 Commandline: aptdaemon role='role-install-packages' sender=':1.122' Install: libgcj17:amd64 (6.3.0-12ubuntu2, automatic), gcj-6-jre-lib:amd64 (6.3.0-12ubuntu2, automatic), pdfchain:amd64 (1:0.4.4.2-1), pdftk:amd64 (2.02-4build1, automatic), libgcj-common:amd64 (1:6.3-2ubuntu1, automatic) End-Date: 2017-05-22 20:24:20 Start-Date: 2017-05-22 22:46:09 Commandline: aptdaemon role='role-upgrade-packages' sender=':1.122' Upgrade: krb5-locales:amd64 (1.15-1, 1.15-1ubuntu0.1), apport:amd64 (2.20.4-0ubuntu4, 2.20.4-0ubuntu4.1), python3-apport:amd64 (2.20.4-0ubuntu4, 2.20.4-0ubuntu4.1), apport-gtk:amd64 (2.20.4-0ubuntu4, 2.20.4-0ubuntu4.1), unattended-upgrades:amd64 (0.93.1ubuntu2.1, 0.93.1ubuntu2.2), python3-problem-report:amd64 (2.20.4-0ubuntu4, 2.20.4-0ubuntu4.1) Error: Sub-process /usr/bin/dpkg exited unexpectedly End-Date: 2017-05-22 22:46:10 Start-Date: 2017-05-24 13:01:29 Commandline: apt-get --purge remove linux-sound-base alsa-base alsa-utils Requested-By: juanca (1000) Purge: alsa-base:amd64 (1.0.25+dfsg-0ubuntu5), gnome-software-plugin-snap:amd64 (3.22.7-0ubuntu3.17.04.2), gnome-software:amd64 (3.22.7-0ubuntu3.17.04.2), linux-sound-base:amd64 (1.0.25+dfsg-0ubuntu5), ubuntu-desktop:amd64 (1.379), alsa-utils:amd64 (1.1.3-1ubuntu1), software-properties-gtk:amd64 (0.96.24.13), apturl:amd64 (0.5.2ubuntu12), nautilus-share:amd64 (0.7.3-2ubuntu2), ubuntu-drivers-common:amd64 (1:0.4.22), ubuntu-software:amd64 (3.22.7-0ubuntu3.17.04.2) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2017-05-24 13:02:07 Start-Date: 2017-05-24 13:18:05 Commandline: apt-get install linux-sound-base alsa-base alsa-utils Requested-By: juanca (1000) Install: alsa-base:amd64 (1.0.25+dfsg-0ubuntu5), linux-sound-base:amd64 (1.0.25+dfsg-0ubuntu5), alsa-utils:amd64 (1.1.3-1ubuntu1) Error: Sub-process /usr/bin/dpkg returned an error code (1) term.log: Log started: 2017-05-22 19:47:46 (Leyendo la base de datos ... 215153 ficheros o directorios instalados actualmente.) Preparando para desempaquetar .../00-samba-libs_2%3a4.5.8+dfsg-0ubuntu0.17.04.1_amd64.deb ... Desempaquetando samba-libs:amd64 (2:4.5.8+dfsg-0ubuntu0.17.04.1) sobre (2:4.5.4+dfsg-1ubuntu2) ... Preparando para desempaquetar .../01-libwbclient0_2%3a4.5.8+dfsg-0ubuntu0.17.04.1_amd64.deb ... Desempaquetando libwbclient0:amd64 (2:4.5.8+dfsg-0ubuntu0.17.04.1) sobre (2:4.5.4+dfsg-1ubuntu2) ... Preparando para desempaquetar .../02-libsmbclient_2%3a4.5.8+dfsg-0ubuntu0.17.04.1_amd64.deb ... Desempaquetando libsmbclient:amd64 (2:4.5.8+dfsg-0ubuntu0.17.04.1) sobre (2:4.5.4+dfsg-1ubuntu2) ... Preparando para desempaquetar .../03-libisc-export160_1%3a9.10.3.dfsg.P4-10.1ubuntu5_amd64.deb ... Desempaquetando libisc-export160 (1:9.10.3.dfsg.P4-10.1ubuntu5) sobre (1:9.10.3.dfsg.P4-10.1ubuntu4) ... Preparando para desempaquetar .../04-libdns-export162_1%3a9.10.3.dfsg.P4-10.1ubuntu5_amd64.deb ... Desempaquetando libdns-export162 (1:9.10.3.dfsg.P4-10.1ubuntu5) sobre (1:9.10.3.dfsg.P4-10.1ubuntu4) ... Preparando para desempaquetar .../05-libcurl3-gnutls_7.52.1-4ubuntu1.1_amd64.deb ... Desempaquetando libcurl3-gnutls:amd64 (7.52.1-4ubuntu1.1) sobre (7.52.1-4ubuntu1) ... Preparando para desempaquetar .../06-libicu57_57.1-5ubuntu0.1_amd64.deb ... Desempaquetando libicu57:amd64 (57.1-5ubuntu0.1) sobre (57.1-5) ... Preparando para desempaquetar .../07-libisccc140_1%3a9.10.3.dfsg.P4-10.1ubuntu5_amd64.deb ... Desempaquetando libisccc140:amd64 (1:9.10.3.dfsg.P4-10.1ubuntu5) sobre (1:9.10.3.dfsg.P4-10.1ubuntu4) ... Preparando para desempaquetar .../08-libfreetype6_2.6.3-3ubuntu2.2_amd64.deb ... Desempaquetando libfreetype6:amd64 (2.6.3-3ubuntu2.2) sobre (2.6.3-3ubuntu2) ... Preparando para desempaquetar .../09-libnspr4_2%3a4.13.1-0ubuntu0.17.04.1_amd64.deb ... Desempaquetando libnspr4:amd64 (2:4.13.1-0ubuntu0.17.04.1) sobre (2:4.12-6ubuntu1) ... Preparando para desempaquetar
[Touch-packages] [Bug 1693477] Re: minimise, maximise and close icons change when changing icon theme
** Attachment added: "Screenshot with appropriate decoration" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693477/+attachment/4883302/+files/Screenshot%20from%202017-05-25%2012-48-41.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693477 Title: minimise, maximise and close icons change when changing icon theme Status in ubuntu-themes package in Ubuntu: New Bug description: When using the light themes I experienced this weird behavior: the (x)(_)([]) change their shape when changing the icon theme. Is it intended? I never experienced this with any other GTK theme so far and I'm quite surprised that changing the icon theme can change the decorations.. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:41:31 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693477/+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 1693477] [NEW] minimise, maximise and close icons change when changing icon theme
Public bug reported: When using the light themes I experienced this weird behavior: the (x)(_)([]) change their shape when changing the icon theme. Is it intended? I never experienced this with any other GTK theme so far and I'm quite surprised that changing the icon theme can change the decorations.. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:41:31 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Attachment added: "Screenshot with weird decoration" https://bugs.launchpad.net/bugs/1693477/+attachment/4883297/+files/Screenshot%20from%202017-05-25%2012-47-54.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693477 Title: minimise, maximise and close icons change when changing icon theme Status in ubuntu-themes package in Ubuntu: New Bug description: When using the light themes I experienced this weird behavior: the (x)(_)([]) change their shape when changing the icon theme. Is it intended? I never experienced this with any other GTK theme so far and I'm quite surprised that changing the icon theme can change the decorations.. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:41:31 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693477/+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 1693474] [NEW] Some switches are disproportionately big
Public bug reported: Look at the screenshot, is it expected for the switch in the top right corner to be so large? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:36:16 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session ** Attachment added: "scr" https://bugs.launchpad.net/bugs/1693474/+attachment/4883291/+files/Screenshot%20from%202017-05-25%2012-35-18.png ** Summary changed: - Some swithces are disproportionately big + Some switches are disproportionately big -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1693474 Title: Some switches are disproportionately big Status in ubuntu-themes package in Ubuntu: New Bug description: Look at the screenshot, is it expected for the switch in the top right corner to be so large? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20170518-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu May 25 12:36:16 2017 InstallationDate: Installed on 2017-04-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1693474/+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 1589605] Re: evolution-calendar-factory uses lots of memory
Upgraded Ubuntu Gnome 16.04.2 to Gnome 3.20.4 with same issue. Except I get 4 running processes and I can find no way of disabling it. Its a bummer. I don't use calendar at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1589605 Title: evolution-calendar-factory uses lots of memory Status in evolution package in Ubuntu: Invalid Status in evolution-data-server package in Ubuntu: Confirmed Status in indicator-datetime package in Ubuntu: Expired Bug description: As filed under bug #1342123 (under Canonical System Image, i.e. for mobile installs) by several users, including desktop installs, evolution-calendar-factory (previsouly in 14.04) then evolution-calendar-factory-subprocess (in 16.04) run using several hundreds of megabytes of memory (~ 300 Mio in my case). This might have to do with having lots of linked calendars (Google Agenda or other). Another user on my system has much fewer Google Agendas than me and her memory usage of evolution-calendar-factory-subprocess is less, but still close to 100 Mio. There have been random crashes of the process, mostly directly upon login, always caused by addressing memory out of range. There used to be a workaround by invoking the process a second time, which caused it to exit more or less gracefully. This is not the case anymore in 16.04. Unfortunately, searching Google leads to the bug #1342123 which concerns "Canonical System Image", and several users have replied even though it does not only concern mobile installs, which is not immediately self-evident when you are not aware what "Canonical System Image" stands for… To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1589605/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1059822] Re: gnome-documents unusable with Radiance/Ambiance theme
** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntu-themes Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1059822 Title: gnome-documents unusable with Radiance/Ambiance theme Status in Ubuntu theme: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: I tried to use gnome-documents (3.6 from Quantal) but it's impossible to read the documents names. See attached screnshots. With the adwaita theme, the names are visible. With the radiance/ambiance theme, the names are white and impossible to read. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: light-themes 0.1.93 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic i686 ApportVersion: 2.6.1-0ubuntu1 Architecture: i386 Date: Mon Oct 1 22:02:02 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423.2) PackageArchitecture: all SourcePackage: light-themes UpgradeStatus: Upgraded to quantal on 2012-06-23 (100 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1059822/+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 1058098] Re: SRU - "active" checkmark style for insensitive menu entries looks odd
This bug appears to be stale. Can anyone update it? ** Changed in: ubuntu-themes (Ubuntu) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1058098 Title: SRU - "active" checkmark style for insensitive menu entries looks odd Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: IMPACT: An insensitive menu entry can have a checkmark, and at the moment, the checkmark style looks like if the entry was active. See the following screenshot: http://imagebin.org/230103 TESTCASE: See the screenshot, test with a menuitem with an enabled check insensitive REGRESSION: No regressions afaics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1058098/+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 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
Please try this kernel: http://people.canonical.com/~khfeng/lp1654448/ AAMIX is disabled, I can't verify it through my bad ear though. -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1654448/+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 1036360] Re: Normal titlebar alignment is off
Are you sure? I can still see the problem in Unity7 on xenial. ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1036360 Title: Normal titlebar alignment is off Status in Ubuntu theme: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: When using a non-maximized window, the alignment of the text is to the top of the window control buttons, leaving a gap in spacing between the bottom of the button and the bottom of the text. However, on a maximized window, the alignment is such that the text is more or less centered along the horizontal axis of the window control buttons. Will include two shots to demonstrate this issue. This is on an up-to-date Precise install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1036360/+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 1048747] Re: The button of drop-down list arrow is reversed in rtl locals.
Can anyone confirm this bug in more current Ubuntu versions? ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1048747 Title: The button of drop-down list arrow is reversed in rtl locals. Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: When I used Ubuntu 12.10, I found a problem in right to left locales. See these screenshots: 1- http://i.imgur.com/w7l8M.png 2- http://i.imgur.com/Lgo7s.png 3- http://i.imgur.com/MEUnE.png This arrow button must flipped in rtl locales. That happen with Ambiance and Radiance light themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1048747/+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 1058073] Re: The currently active button looks very much like all the inactive ones
Thank you for reporting this bug to Ubuntu. Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Summary changed: - The currently active tab looks very much like all the inactive ones + The currently active button looks very much like all the inactive ones ** Changed in: ubuntu-themes (Ubuntu) Status: Triaged => Incomplete ** Changed in: ubuntu-themes Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1058073 Title: The currently active button looks very much like all the inactive ones Status in Ubuntu theme: Incomplete Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: When using several tabs in Guake the currently active one isn't easily distinguishable at a glance from all the inactive ones. It would be nice if there was some really obvious difference (perhaps emboldened text or a different colour background to the button); I keep finding myself mis-identifying the currently-active tab and typing commands at the wrong host; the attached screenshot hopefully illustrates the confusion rather than my poor eyesight :) I seems odd that they're represented as buttons rather than tabs, too. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: guake 0.4.3-3 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Fri Sep 28 12:45:27 2012 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120910) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: guake UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1058073/+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 1047353] Re: Eclipse's Tooltip Background is Black in 12.04
Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1047353 Title: Eclipse's Tooltip Background is Black in 12.04 Status in GNOME Themes Standard: Fix Released Status in Ubuntu theme: New Status in eclipse package in Ubuntu: Confirmed Status in gnome-themes-standard package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: The following link describes the problem and gives workaround. http://askubuntu.com/questions/70599/how-to-change-tooltip-background-color-in-unity I do know there is a old similar bug but it is for 10.04. I meet this bug on Unity 3D, 12.04. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: eclipse 3.7.2-1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Fri Sep 7 08:01:35 2012 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no username) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-themes-standard/+bug/1047353/+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
