[Bug 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root
** Changed in: systemd (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891394 Title: systemd breaks upgrade with useless error if /var is not owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906110] Re: Installing fails with: ERROR (dkms apport): kernel package linux-headers-5.9.1-050901-generic is not supported
Even though that last output said a few different ways that it failed, it appears it did install and is usable. So, just the problem with failing to install when newer unrecognized kernels are installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906110 Title: Installing fails with: ERROR (dkms apport): kernel package linux- headers-5.9.1-050901-generic is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1906110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906110] Re: Installing fails with: ERROR (dkms apport): kernel package linux-headers-5.9.1-050901-generic is not supported
BTW, the kernel I've been running through all this is the default ubuntu 20.04 version: $ uname -a Linux dancer.chaosreigns.com 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux With kernel 5.8.0 removed, it looks like I'm hitting a new bug: $ sudo apt remove linux-headers-5.8.0-25 linux-headers-5.8.0-25-generic linux-modules-5.8.0-25-generic Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-5.8.0-25 linux-headers-5.8.0-25-generic linux-headers-generic linux-modules-5.8.0-25-generic 0 upgraded, 0 newly installed, 4 to remove and 3 not upgraded. 3 not fully installed or removed. After this operation, 165 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 599496 files and directories currently installed.) Removing linux-headers-generic (5.8.0.25.30) ... Removing linux-headers-5.8.0-25-generic (5.8.0-25.26) ... Removing linux-headers-5.8.0-25 (5.8.0-25.26) ... Removing linux-modules-5.8.0-25-generic (5.8.0-25.26) ... Setting up virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Removing old virtualbox-6.1.10 DKMS files... Uninstall Beginning Module: virtualbox Version: 6.1.10 Kernel: 5.4.0-54-generic (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/5.4.0-54-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/5.4.0-54-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/5.4.0-54-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. -- Deleting module version: 6.1.10 completely from the DKMS tree. -- Done. Loading new virtualbox-6.1.10 DKMS files... Building for 5.4.0-54-generic Building initial module for 5.4.0-54-generic Done. vboxdrv.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ vboxnetadp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ vboxnetflt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ depmod... DKMS: install completed. Job for virtualbox.service failed because the control process exited with error code. See "systemctl status virtualbox.service" and "journalctl -xe" for details. invoke-rc.d: initscript virtualbox, action "restart" failed. ● virtualbox.service - LSB: VirtualBox Linux kernel module Loaded: loaded (/etc/init.d/virtualbox; generated) Active: failed (Result: exit-code) since Sat 2020-11-28 11:04:04 EST; 3ms ago Docs: man:systemd-sysv-generator(8) Process: 1152416 ExecStart=/etc/init.d/virtualbox start (code=exited, status=1/FAILURE) Nov 28 11:04:04 dancer.chaosreigns.com systemd[1]: Starting LSB: VirtualBox Linux kernel module... Nov 28 11:04:04 dancer.chaosreigns.com virtualbox[1152416]: * Loading VirtualBox kernel modules... Nov 28 11:04:04 dancer.chaosreigns.com virtualbox[1152416]: * No suitable vboxpci module for running kernel found Nov 28 11:04:04 dancer.chaosreigns.com virtualbox[1152416]:...fail! Nov 28 11:04:04 dancer.chaosreigns.com systemd[1]: virtualbox.service: Control process exited, code=exited, status=1/FAILURE Nov 28 11:04:04 dancer.chaosreigns.com systemd[1]: virtualbox.service: Failed with result 'exit-code'. Nov 28 11:04:04 dancer.chaosreigns.com systemd[1]: Failed to start LSB: VirtualBox Linux kernel module. Setting up virtualbox (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Installing new version of config file /etc/init.d/virtualbox ... vboxweb.service is a disabled or a static unit not running, not starting it. Setting up virtualbox-qt (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Processing triggers for systemd (245.4-4ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-21) ... Processing triggers for menu (2.1.47ubuntu4) ... $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.
[Bug 1906110] Re: Installing fails with: ERROR (dkms apport): kernel package linux-headers-5.9.1-050901-generic is not supported
Same error for 5.8.0-25-generic. $ sudo apt remove linux-headers-5.9.1-050901-generic linux-modules-5.9.1-050901-generic [sudo] password for darxus: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-5.9.1-050901-generic linux-modules-5.9.1-050901-generic 0 upgraded, 0 newly installed, 2 to remove and 3 not upgraded. 3 not fully installed or removed. After this operation, 288 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 618879 files and directories currently installed.) Removing linux-headers-5.9.1-050901-generic (5.9.1-050901.202010170731) ... Removing linux-modules-5.9.1-050901-generic (5.9.1-050901.202010170731) ... Setting up virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Removing old virtualbox-6.1.10 DKMS files... Uninstall Beginning Module: virtualbox Version: 6.1.10 Kernel: 5.4.0-54-generic (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. vboxdrv.ko: - Uninstallation - Deleting from: /lib/modules/5.4.0-54-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetadp.ko: - Uninstallation - Deleting from: /lib/modules/5.4.0-54-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. vboxnetflt.ko: - Uninstallation - Deleting from: /lib/modules/5.4.0-54-generic/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... DKMS: uninstall completed. -- Deleting module version: 6.1.10 completely from the DKMS tree. -- Done. Loading new virtualbox-6.1.10 DKMS files... Building for 5.4.0-54-generic 5.8.0-25-generic Building initial module for 5.4.0-54-generic Done. vboxdrv.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ vboxnetadp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ vboxnetflt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 5.8.0-25-generic ERROR (dkms apport): kernel package linux-headers-5.8.0-25-generic is not supported Error! Bad return status for module build on kernel: 5.8.0-25-generic (x86_64) Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information. dpkg: error processing package virtualbox-dkms (--configure): installed virtualbox-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of virtualbox: virtualbox depends on virtualbox-dkms (>= 6.1.10-dfsg-1~ubuntu1.20.04.1) | virtualbox-source (>= 6.1.10-dfsg-1~ubuntu1.20.04.1) | virtualbox-modules; however: Package virtualbox-dkms is not configured yet. Package virtualbox-source is not installed. Package virtualbox-modules is not installed. Package virtualbox-dkms which provides virtualbox-modules is not configured yet. dpkg: error processing package virtualbox (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of virtualbox-qt: virtualbox-qt depends on virtualbox (= 6.1.10-dfsg-1~ubuntu1.20.04.1); however: Package virtualbox is not configured yet. dpkg: error processing package virtualbox-qt (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. No apport report written because the error message indicates its a followup error from a previous failure . Errors were encountered while processing: virtualbox-dkms virtualbox virtualbox-qt E: Sub-process /usr/bin/dpkg returned an error code (1) $ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906110 Title: Installing fails with: ERROR (dkms apport): kernel package linux- headers-5.9.1-050901-generic is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1906110/+subscri
[Bug 1906110] [NEW] Installing fails with: ERROR (dkms apport): kernel package linux-headers-5.9.1-050901-generic is not supported
Public bug reported: $ sudo apt install virtualbox [sudo] password for darxus: Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: dkms libgsoap-2.8.91 libvncserver1 virtualbox-dkms virtualbox-qt Suggested packages: vde2 The following NEW packages will be installed: dkms libgsoap-2.8.91 libvncserver1 virtualbox virtualbox-dkms virtualbox-qt 0 upgraded, 6 newly installed, 0 to remove and 3 not upgraded. Need to get 44.2 MB of archives. After this operation, 180 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://us.archive.ubuntu.com/ubuntu focal/main amd64 dkms all 2.8.1-5ubuntu1 [66.6 kB] Get:2 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 libgsoap-2.8.91 amd64 2.8.91-2 [231 kB] Get:3 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 libvncserver1 amd64 0.9.12+dfsg-9ubuntu0.3 [119 kB] Get:4 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 virtualbox-dkms amd64 6.1.10-dfsg-1~ubuntu1.20.04.1 [687 kB] Get:5 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 virtualbox amd64 6.1.10-dfsg-1~ubuntu1.20.04.1 [21.4 MB] Get:6 http://us.archive.ubuntu.com/ubuntu focal-updates/multiverse amd64 virtualbox-qt amd64 6.1.10-dfsg-1~ubuntu1.20.04.1 [21.7 MB] Fetched 44.2 MB in 12s (3,611 kB/s) Selecting previously unselected package dkms. (Reading database ... 618202 files and directories currently installed.) Preparing to unpack .../0-dkms_2.8.1-5ubuntu1_all.deb ... Unpacking dkms (2.8.1-5ubuntu1) ... Selecting previously unselected package libgsoap-2.8.91:amd64. Preparing to unpack .../1-libgsoap-2.8.91_2.8.91-2_amd64.deb ... Unpacking libgsoap-2.8.91:amd64 (2.8.91-2) ... Selecting previously unselected package libvncserver1:amd64. Preparing to unpack .../2-libvncserver1_0.9.12+dfsg-9ubuntu0.3_amd64.deb ... Unpacking libvncserver1:amd64 (0.9.12+dfsg-9ubuntu0.3) ... Selecting previously unselected package virtualbox-dkms. Preparing to unpack .../3-virtualbox-dkms_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb ... Unpacking virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Selecting previously unselected package virtualbox. Preparing to unpack .../4-virtualbox_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb ... Unpacking virtualbox (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Selecting previously unselected package virtualbox-qt. Preparing to unpack .../5-virtualbox-qt_6.1.10-dfsg-1~ubuntu1.20.04.1_amd64.deb ... Unpacking virtualbox-qt (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Setting up libvncserver1:amd64 (0.9.12+dfsg-9ubuntu0.3) ... Setting up dkms (2.8.1-5ubuntu1) ... Installing new version of config file /etc/dkms/template-dkms-mkdeb/debian/control ... Installing new version of config file /etc/dkms/template-dkms-mkdeb/debian/postinst ... Installing new version of config file /etc/kernel/header_postinst.d/dkms ... Installing new version of config file /etc/kernel/postinst.d/dkms ... Installing new version of config file /etc/kernel/prerm.d/dkms ... Setting up libgsoap-2.8.91:amd64 (2.8.91-2) ... Setting up virtualbox-dkms (6.1.10-dfsg-1~ubuntu1.20.04.1) ... Loading new virtualbox-6.1.10 DKMS files... Building for 5.4.0-54-generic 5.9.1-050901-generic Building initial module for 5.4.0-54-generic Done. vboxdrv.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ vboxnetadp.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ vboxnetflt.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.4.0-54-generic/updates/dkms/ depmod... DKMS: install completed. Building initial module for 5.9.1-050901-generic ERROR (dkms apport): kernel package linux-headers-5.9.1-050901-generic is not supported Error! Bad return status for module build on kernel: 5.9.1-050901-generic (x86_64) Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information. dpkg: error processing package virtualbox-dkms (--configure): installed virtualbox-dkms package post-installation script subprocess returned error exit status 10 dpkg: dependency problems prevent configuration of virtualbox: virtualbox depends on virtualbox-dkms (>= 6.1.10-dfsg-1~ubuntu1.20.04.1) | virtualbox-source (>= 6.1.10-dfsg-1~ubuntu1.20.04.1) | virtualbox-modules; however: Package virtualbox-dkms is not configured yet. Package virtualbox-source is not ins
[Bug 1905092] Re: Handles Provides/Conflicts/Replaces badly
** Description changed: I created this PPA: https://code.launchpad.net/~darxus/+archive/ubuntu /linux-firmware-daily/ It contains a linux-firmware package. This package Provides/Conflicts/Replaces amd64-microcode. Because the upstream source for this package also contains the contents of the amd64-microcode package, so I'm including it. But the ubuntu packages split those files off into the separate package because of licensing. So when you install this PPA, it upgrades to the linux-firmware package from the PPA, and uninstalls the amd64-microcode package. Nice and clean. Then I tried purging it. Which should downgrade the linux-firmware package to the version from the ubuntu archives, and reinstall the - amd64-microcode. But instead, it uninstalls the packages that depended - on it. Specifically the REMOVED section: + amd64-microcode package. But instead, it uninstalls the packages that + depended on it. Specifically the REMOVED section: # ppa-purge ppa:darxus/linux-firmware-daily Updating packages lists PPA to be removed: darxus linux-firmware-daily Package revert list generated: - linux-firmware/focal + linux-firmware/focal - Disabling darxus PPA from + Disabling darxus PPA from /etc/apt/sources.list.d/darxus-ubuntu-linux-firmware-daily-focal.list Updating packages lists Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done Selected version '1.187.4' (Ubuntu:20.04/focal-updates [all]) for 'linux-firmware' The following packages were automatically installed and are no longer required: - intel-microcode iucode-tool thermald + intel-microcode iucode-tool thermald Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: - linux-generic-hwe-20.04 linux-image-generic linux-image-generic-hwe-20.04 + linux-generic-hwe-20.04 linux-image-generic linux-image-generic-hwe-20.04 The following packages will be DOWNGRADED: - linux-firmware + linux-firmware 0 upgraded, 0 newly installed, 1 downgraded, 3 to remove and 3 not upgraded. Need to get 0 B/99.3 MB of archives. After this operation, 114 MB disk space will be freed. Do you want to continue? [Y/n] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ppa-purge 0.2.8+bzr63 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 17:01:28 2020 InstallationDate: Installed on 2016-05-28 (1637 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ppa-purge UpgradeStatus: Upgraded to focal on 2020-08-20 (91 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905092 Title: Handles Provides/Conflicts/Replaces badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1905092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905092] [NEW] Handles Provides/Conflicts/Replaces badly
Public bug reported: I created this PPA: https://code.launchpad.net/~darxus/+archive/ubuntu /linux-firmware-daily/ It contains a linux-firmware package. This package Provides/Conflicts/Replaces amd64-microcode. Because the upstream source for this package also contains the contents of the amd64-microcode package, so I'm including it. But the ubuntu packages split those files off into the separate package because of licensing. So when you install this PPA, it upgrades to the linux-firmware package from the PPA, and uninstalls the amd64-microcode package. Nice and clean. Then I tried purging it. Which should downgrade the linux-firmware package to the version from the ubuntu archives, and reinstall the amd64-microcode. But instead, it uninstalls the packages that depended on it. Specifically the REMOVED section: # ppa-purge ppa:darxus/linux-firmware-daily Updating packages lists PPA to be removed: darxus linux-firmware-daily Package revert list generated: linux-firmware/focal Disabling darxus PPA from /etc/apt/sources.list.d/darxus-ubuntu-linux-firmware-daily-focal.list Updating packages lists Reading package lists... Done Building dependency tree Reading state information... Done Selected version '1.187.4' (Ubuntu:20.04/focal-updates [all]) for 'linux-firmware' The following packages were automatically installed and are no longer required: intel-microcode iucode-tool thermald Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: linux-generic-hwe-20.04 linux-image-generic linux-image-generic-hwe-20.04 The following packages will be DOWNGRADED: linux-firmware 0 upgraded, 0 newly installed, 1 downgraded, 3 to remove and 3 not upgraded. Need to get 0 B/99.3 MB of archives. After this operation, 114 MB disk space will be freed. Do you want to continue? [Y/n] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ppa-purge 0.2.8+bzr63 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 17:01:28 2020 InstallationDate: Installed on 2016-05-28 (1637 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ppa-purge UpgradeStatus: Upgraded to focal on 2020-08-20 (91 days ago) ** Affects: ppa-purge (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905092 Title: Handles Provides/Conflicts/Replaces badly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppa-purge/+bug/1905092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576602] Re: Fancontrol relies on the module load order
Upstream bug, which would fix this: https://github.com/lm-sensors/lm- sensors/issues/227 ** Bug watch added: github.com/lm-sensors/lm-sensors/issues #227 https://github.com/lm-sensors/lm-sensors/issues/227 ** Also affects: lmsensors via https://github.com/lm-sensors/lm-sensors/issues/227 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/576602 Title: Fancontrol relies on the module load order To manage notifications about this bug go to: https://bugs.launchpad.net/lmsensors/+bug/576602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 576602] Re: Fancontrol relies on the module load order
This problem still exists in ubuntu 20.04. It looks like a good solution to this problem would be to use the contents of /sys/class/hwmon/hwmon*/name instead of the hwmon device number. fancontrol uses these name files to do the verification that results in the errors in this bug report. I used Thomas's workaround, it worked. My module order was slightly more complicated, because I had additional devices involved in the random ordering. I added softdeps for all of them: $ grep -H . /sys/class/hwmon/hwmon*/name /sys/class/hwmon/hwmon0/name:amdgpu /sys/class/hwmon/hwmon1/name:nct6798 /sys/class/hwmon/hwmon2/name:k10temp /sys/class/hwmon/hwmon3/name:hidpp_battery_0 /sys/class/hwmon/hwmon4/name:asus # cat /etc/modprobe.d/fancontrol.conf softdep nct6775 pre: amdgpu softdep k10temp pre: nct6775 softdep asus_wmi pre: k10temp softdep hid_logitech_hidpp pre: k10temp To figure out which devices it wants to have which numbers, look at: # grep DEVNAME /etc/fancontrol DEVNAME=hwmon1=nct6798 hwmon2=k10temp My motherboard is an Asus TUF X570. I am not entirely certain that I got the right modules for the asus and hidpp_battery_0 hwmon devices. fancontrol and pwmconfig are in the fancontrol package. Upstream is https://hwmon.wiki.kernel.org/lm_sensors The download link on that page is a git archive which does contain fancontrol and pwmconfig. There is an upstream mailing list and IRC channel: https://hwmon.wiki.kernel.org/feedbackandsupport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/576602 Title: Fancontrol relies on the module load order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors-3/+bug/576602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899303] Re: Mouseover doesn't show stats
Workarounds I have found are to switch to the cinnamon desktop, or the (default ubuntu) gnome shell desktop with the dash to panel extension, which has finally made me not hate gnome shell: https://extensions.gnome.org/extension/1160/dash-to-panel/ Both of these have an extremely similar thing that works, that will let you see actual numbers in text in some reasonable way. You can select the desktop when you log in. If you don't have one installed, it's just a matter of installing one of: ubuntu-desktop cinnamon-desktop-environment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899303 Title: Mouseover doesn't show stats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-system-monitor/+bug/1899303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891394] Re: systemd breaks upgrade with useless error if /var is not owned by root
Var was owned by the user I usually log in as. I don't know why, yes it's weird, I fixed it. I don't think that justifies this package's upgrade braking behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891394 Title: systemd breaks upgrade with useless error if /var is not owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899303] [NEW] Mouseover doesn't show stats
Public bug reported: When I hover my mouse over it, on the panel, it doesn't show me how much cpu / ram / etc. is being used, like it used to. Like the mate sensors applet does. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mate-system-monitor 1.24.0-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sat Oct 10 18:53:07 2020 ExecutablePath: /usr/bin/mate-system-monitor InstallationDate: Installed on 2016-05-28 (1596 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: mate-system-monitor UpgradeStatus: Upgraded to focal on 2020-08-20 (50 days ago) ** Affects: mate-system-monitor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899303 Title: Mouseover doesn't show stats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-system-monitor/+bug/1899303/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895686] Re: blkid always hangs, launched by dpkg --configure -a
** Description changed:
I noticed last night that package install fails. Then I noticed
- processes running from an automatic upgrade that ran on September 9th.
+ processes running from an automatic upgrade that ran on September first.
Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
When I run the same command manually through strace, it seems to get
hung on opening the floppy drive, which does not exist:
# strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
b6a3-888f7368c779
...
lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
access("/dev/fd0", F_OK)= 0
stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
close(4)= 0
openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
This bug was submitted by running ubuntu-bug on one of the hung
instances of blkid.
https://ubuntuforums.org/showthread.php?t=2450510
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: util-linux 2.34-0.1ubuntu9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Sep 15 10:18:23 2020
ExecutablePath: /sbin/blkid
InstallationDate: Installed on 2016-05-28 (1571 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: util-linux
UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1895686
Title:
blkid always hangs, launched by dpkg --configure -a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895686] [NEW] blkid always hangs, launched by dpkg --configure -a
Public bug reported:
I noticed last night that package install fails. Then I noticed
processes running from an automatic upgrade that ran on September first.
Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
When I run the same command manually through strace, it seems to get
hung on opening the floppy drive, which does not exist:
# strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
b6a3-888f7368c779
...
lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
access("/dev/fd0", F_OK)= 0
stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
close(4)= 0
openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
This bug was submitted by running ubuntu-bug on one of the hung
instances of blkid.
https://ubuntuforums.org/showthread.php?t=2450510
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: util-linux 2.34-0.1ubuntu9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Sep 15 10:18:23 2020
ExecutablePath: /sbin/blkid
InstallationDate: Installed on 2016-05-28 (1571 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: util-linux
UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)
** Affects: util-linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
** Description changed:
I noticed last night that package install fails. Then I noticed
processes running from an automatic upgrade that ran on September 9th.
Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
When I run the same command manually through strace, it seems to get
hung on opening the floppy drive, which does not exist:
# strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
b6a3-888f7368c779
...
lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
access("/dev/fd0", F_OK)= 0
stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
close(4)= 0
openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
+ https://ubuntuforums.org/showthread.php?t=2450510
- https://ubuntuforums.org/showthread.php?t=2450510
+ This bug was submitted by running ubuntu-bug on one of the hung
+ instances of blkid.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: util-linux 2.34-0.1ubuntu9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Sep 15 10:18:23 2020
ExecutablePath: /sbin/blkid
InstallationDate: Installed on 2016-05-28 (1571 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: util-linux
UpgradeStatus: Upgraded to focal on 2020-08-20 (25 days ago)
** Description changed:
I noticed last night that package install fails. Then I noticed
processes running from an automatic upgrade that ran on September 9th.
Whenever I run "dpkg --configure -a", it gets stuck on blkid hanging.
When I run the same command manually through strace, it seems to get
hung on opening the floppy drive, which does not exist:
# strace -o blkid.log blkid -l -t UUID=55e42e8c-9316-46bf-
b6a3-888f7368c779
...
lstat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
access("/dev/fd0", F_OK)= 0
stat("/dev/fd0", {st_mode=S_IFBLK|0660, st_rdev=makedev(0x2, 0), ...}) = 0
openat(AT_FDCWD, "/sys/dev/block/2:0", O_RDONLY|O_CLOEXEC) = 4
openat(4, "dm/uuid", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
close(4)= 0
openat(AT_FDCWD, "/dev/fd0", O_RDONLY|O_CLOEXEC
- https://ubuntuforums.org/showthread.php?t=2450510
-
This bug was submitted by running ubuntu-bug on one of the hung
instances of blkid.
+
+ https://ubuntuforums.org/showthread.php?t=2450510
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: util-linux 2.34-0.1ubuntu9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Sep 15 10:18:23
[Bug 1895686] Re: blkid always hangs, launched by dpkg --configure -a
** Attachment added: "Full output of that strace" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+attachment/5411074/+files/blkid.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895686 Title: blkid always hangs, launched by dpkg --configure -a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1895686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811580] Re: systemd fails to start sshd at reboot
I think I had the same problem. I think it was fixed with "chown root:root /var". Related to this: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394 I think it also caused screen to be unusable until it was run by root. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811580 Title: systemd fails to start sshd at reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891394] [NEW] systemd breaks upgrade with useless error if /var is not owned by root
Public bug reported: I just upgraded from 16.04 to 18.04. The upgrade broke. The error, from systemd, was: "Unsafe symlinks encountered in /var/log/journal, refusing." That directory was empty. The fix was "chmod root:root /var". Yes, it's weird that my /var wasn't owned by root, but upgrade breaking errors should say something useful. panic:~# chown darxus:darxus /var panic:~# dpkg-reconfigure systemd Unsafe symlinks encountered in /var/spool/rsyslog, refusing. Unsafe symlinks encountered in /var/lib/colord, refusing. Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Unsafe symlinks encountered in /var/cache/man, refusing. Unsafe symlinks encountered in /var/run/opendkim, refusing. Unsafe symlinks encountered in /var/lib/systemd, refusing. Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Unsafe symlinks encountered in /var/log/wtmp, refusing. Unsafe symlinks encountered in /var/log/btmp, refusing. Unsafe symlinks encountered in /var/log/lastlog, refusing. Unsafe symlinks encountered in /var/log, refusing. Unsafe symlinks encountered in /var/log/auth.log, refusing. Unsafe symlinks encountered in /var/log/mail.err, refusing. Unsafe symlinks encountered in /var/log/mail.log, refusing. Unsafe symlinks encountered in /var/log/kern.log, refusing. Unsafe symlinks encountered in /var/log/syslog, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing. Unsafe symlinks encountered in /var/log/journal/6118992be5f52430d74ed66e4cc8d590/system.journal, refusing. panic:~# chown root:root /var panic:~# dpkg-reconfigure systemd I found the fix here: https://askubuntu.com/a/1095796 Showing that I'm not the only one encountering this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.42 Uname: Linux 5.6.14-x86_64-linode135 x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: i386 Date: Wed Aug 12 15:58:33 2020 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: root=/dev/sda console=tty1 console=ttyS0 ro devtmpfs.mount=1 ProcModules: SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2020-08-12 (0 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-0-ga698c8995f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-3.1 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-0-ga698c8995f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-3.1:cvnQEMU:ct1:cvrpc-q35-3.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-3.1 dmi.sys.vendor: QEMU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891394 Title: systemd breaks upgrade with useless error if /var is not owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594003] Re: undefined reference to `g_type_class_adjust_private_offset'
My fault, had ancient stuff in my install directory. ** Changed in: libgudev (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594003 Title: undefined reference to `g_type_class_adjust_private_offset' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgudev/+bug/1594003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594003] [NEW] undefined reference to `g_type_class_adjust_private_offset'
Public bug reported: //usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0: undefined reference to `g_type_class_adjust_private_offset' Darxus: no, that means your system is broken really Darxus: somehow you've ended up with your compiled gudev referencing parts of glib which are no longer / not yet present; nothing to do with the wayland build itself I'm building wayland, mostly following https://wayland.freedesktop.org/mint17.html . I have not built glib or gudev, I'm using them both from ubuntu 16.04 packages. I got the error while running make on wayland/libinput. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgudev-1.0-0:amd64 1:230-2 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: MATE Date: Sat Jun 18 13:04:48 2016 InstallationDate: Installed on 2016-05-28 (21 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libgudev UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libgudev (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594003 Title: undefined reference to `g_type_class_adjust_private_offset' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgudev/+bug/1594003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590136] Re: gtk-window-decorator using 6.3gb resident memory
I tried the steps for reproducing bug #1050610 - not the same bug. Wns does go back down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590136 Title: gtk-window-decorator using 6.3gb resident memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1590136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1590136] [NEW] gtk-window-decorator using 6.3gb resident memory
Public bug reported: I recently did a fresh install of ubuntu 16.04, then installed mate. With only gnome terminal running, gtk-window-decorator is using 6.3 gigabytes of resident memory. $ uptime 16:10:01 up 1 day, 2:05, 4 users, load average: 1.85, 2.17, 2.36 (with firefox open, the load seems high too - Xorg, compiz, mate-session, dbus-daemon) PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 2081 darxus20 0 8392144 6.339g 18828 S 2.0 81.3 28:39.54 gtk-window-deco It's from compiz-gnome package Version: 1:0.9.12.2+16.04.20160526-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: compiz-gnome 1:0.9.12.2+16.04.20160526-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: [core,composite,opengl,decor,wobbly,cube,td,rotate] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: MATE Date: Tue Jun 7 16:07:36 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Barts XT [Radeon HD 6870] [1787:2010] InstallationDate: Installed on 2016-05-28 (10 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) LightdmDisplayLog: (II) AIGLX: Suspending AIGLX clients for VT switch LightdmLog: [+73981.26s] DEBUG: Seat seat0 changes active session to [+73984.20s] DEBUG: Seat seat0 changes active session to 25 [+73994.32s] DEBUG: Seat seat0 changes active session to [+73995.31s] DEBUG: Seat seat0 changes active session to c2 [+73995.31s] DEBUG: Session c2 is already active MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=e18f152f-ce09-4257-a6ca-13ec4b6dd630 ro quiet splash SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A79T Deluxe 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.:bvr3503:bd05/06/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A79TDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Jun 6 14:04:29 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.2 xserver.video_driver: radeon ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590136 Title: gtk-window-decorator using 6.3gb resident memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1590136/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1436558] Re: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4
I'm not certain I had the same problem, but the workaround I used was: dpkg --force-depends -r purge libldap-2.4-2:amd64 libldap-2.4-2:i386 apt-get -f install Because apt-get purge refuses due to dependencies. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1436558 Title: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1436558/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1436558] Re: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4
I'm not certain I had the same problem, but the workaround I used was: dpkg --force-depends -r purge libldap-2.4-2:amd64 libldap-2.4-2:i386 apt-get -f install Because apt-get purge refuses due to dependencies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436558 Title: package libldap-2.4-2 2.4.31-1+nmu2ubuntu8 failed to install/upgrade: trying to overwrite shared '/etc/ldap/ldap.conf', which is different from other instances of package libldap-2.4-2:amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1436558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545894] Re: notifications appear over screensaver
This bug is still present. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.04.2 LTS Release:14.04 Codename: trusty $ apt-cache policy xscreensaver xscreensaver: Installed: 5.15-3ubuntu1 ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/545894 Title: notifications appear over screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/545894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545894] Re: notifications appear over screensaver
Possibly relevant from the xscreensaver faq: https://www.jwz.org/xscreensaver/faq.html#popup-windows The window manager I'm using is metacity 1:2.34.13-0ubuntu4.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/545894 Title: notifications appear over screensaver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/545894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565364] Re: pinning a specific package does not work
Nice, that (debian) bug is 10 years old. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/565364 Title: pinning a specific package does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/565364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
To be a little clearer, the thing that was done wrong in the initial report was here: Select fan output to configure, or other action: 1) hwmon0/device/pwm3 3) Change INTERVAL 5) Save and quit 2) hwmon0/device/pwm2 4) Just quit 6) Show configuration select (1-n): 5 Instead of hitting 5 to save, you needed to hit 1 or 2 and configure one of those PWM controls. From the rest of the output, it looks like you'd want to do both. Then save. (I did this same thing, lots of times.) Honestly, I think this bug should be kept open as a UI bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
To be a little clearer, the thing that was done wrong in the initial report was here: Select fan output to configure, or other action: 1) hwmon0/device/pwm3 3) Change INTERVAL 5) Save and quit 2) hwmon0/device/pwm2 4) Just quit 6) Show configuration select (1-n): 5 Instead of hitting 5 to save, you needed to hit 1 or 2 and configure one of those PWM controls. From the rest of the output, it looks like you'd want to do both. Then save. (I did this same thing, lots of times.) Honestly, I think this bug should be kept open as a UI bug. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
I posted to the lm-sensors mailing list about it: http://lists.lm- sensors.org/pipermail/lm-sensors/2015-January/043356.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
I posted to the lm-sensors mailing list about it: http://lists.lm- sensors.org/pipermail/lm-sensors/2015-January/043356.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
Ugh, the bug here is that this program is amazingly misleading, even with step by step instructions. I went through the pwmconfig script probably for hours trying to figure out how these values are supposed to be set before I figured this out. At the end, it says: Do you want to set up its configuration file now (y)? What should be the path to your fancontrol config file (/etc/fancontrol)? Select fan output to configure, or other action: 1) hwmon0/device/pwm2 3) Change INTERVAL 5) Save and quit 2) hwmon0/device/pwm1 4) Just quit 6) Show configuration select (1-n): 2 What we've been doing wrong is failing to select a fan output to configure. In my case, I needed to type 2 and hit enter, and then accept all the defaults. Before doing this, show configuration is blank. After doing this, show configuration contains stuff as you might expect. The directions I was trying to follow the whole time are here: http://ubuntuforums.org/showthread.php?t=42737 My mistake was thinking all the automatically determined fan speed relationships were a new feature, the script was more automated, and I didn't need to follow all of the instructions on that page. I'd say there's absolutely a bug here, but it's not that the script doesn't work. It's that it's far from obvious how to use it, and it doesn't give you any hint when you skip the necessary last step. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
Ugh, the bug here is that this program is amazingly misleading, even with step by step instructions. I went through the pwmconfig script probably for hours trying to figure out how these values are supposed to be set before I figured this out. At the end, it says: Do you want to set up its configuration file now (y)? What should be the path to your fancontrol config file (/etc/fancontrol)? Select fan output to configure, or other action: 1) hwmon0/device/pwm2 3) Change INTERVAL 5) Save and quit 2) hwmon0/device/pwm1 4) Just quit 6) Show configuration select (1-n): 2 What we've been doing wrong is failing to select a fan output to configure. In my case, I needed to type 2 and hit enter, and then accept all the defaults. Before doing this, show configuration is blank. After doing this, show configuration contains stuff as you might expect. The directions I was trying to follow the whole time are here: http://ubuntuforums.org/showthread.php?t=42737 My mistake was thinking all the automatically determined fan speed relationships were a new feature, the script was more automated, and I didn't need to follow all of the instructions on that page. I'd say there's absolutely a bug here, but it's not that the script doesn't work. It's that it's far from obvious how to use it, and it doesn't give you any hint when you skip the necessary last step. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
I also found it useful to give my fain 10 seconds between each speed change, to get a more accurate reading: $ diff pwmconfig.0 pwmconfig 64c64 DELAY=5 # 3 seconds delay is too short for large fans, thus I increased it to 5 --- DELAY=10 # 3 seconds delay is too short for large fans, thus I increased it to 5 320c320,322 PDELAY=2 --- PDELAY=10 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
I also found it useful to give my fain 10 seconds between each speed change, to get a more accurate reading: $ diff pwmconfig.0 pwmconfig 64c64 DELAY=5 # 3 seconds delay is too short for large fans, thus I increased it to 5 --- DELAY=10 # 3 seconds delay is too short for large fans, thus I increased it to 5 320c320,322 PDELAY=2 --- PDELAY=10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
I tried a couple things that didn't work. I'm running Precise. I downloaded the tarball of the latest version of lm_sensors - http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.5.tar.bz2 and ran pwmconfig directly from there (sudo bash prog/pwm/pwmconfig). No same results. Then I downloaded lm-sensors from trusty: http://packages.ubuntu.com/trusty/amd64/lm-sensors/download Installing it via dpkg -i gave me an error about a dependency for the uninstalled package init-system-helpers. So I forced it (which I do not recommend): dpkg --force-depends -i lm-sensors_3.3.4-2ubuntu1_amd64.deb That didn't work either. I'm pretty curious what's broken here. I'm starting to suspect that there's some other program the pwmconfig script uses that's somehow broken or missing in a way that's not being detected. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lm-sensors in Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 485899] Re: pwmconfig generates a blank values /etc/fancontrol
I tried a couple things that didn't work. I'm running Precise. I downloaded the tarball of the latest version of lm_sensors - http://dl.lm-sensors.org/lm-sensors/releases/lm_sensors-3.3.5.tar.bz2 and ran pwmconfig directly from there (sudo bash prog/pwm/pwmconfig). No same results. Then I downloaded lm-sensors from trusty: http://packages.ubuntu.com/trusty/amd64/lm-sensors/download Installing it via dpkg -i gave me an error about a dependency for the uninstalled package init-system-helpers. So I forced it (which I do not recommend): dpkg --force-depends -i lm-sensors_3.3.4-2ubuntu1_amd64.deb That didn't work either. I'm pretty curious what's broken here. I'm starting to suspect that there's some other program the pwmconfig script uses that's somehow broken or missing in a way that's not being detected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/485899 Title: pwmconfig generates a blank values /etc/fancontrol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/485899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 766710] Re: Add ability to mix to mono
It would be even nicer if I could pick between mixing to mono, or listening to only the right or left channel in both sides of my headphones (sometimes one channel is garbage and the other is decent),. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/766710 Title: Add ability to mix to mono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/766710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346999] Re: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS
What was the cause / solution? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1346999 Title: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1346999/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1346999] Re: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS
Nice. Maybe open a bug because it didn't throw a more useful error on not being able to create /var/lib/spamassassin? I'm not sure if that would be against aptitude or spamassassin. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1346999 Title: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1346999/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1346999] Re: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS
What was the cause / solution? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346999 Title: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1346999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1346999] Re: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS
Nice. Maybe open a bug because it didn't throw a more useful error on not being able to create /var/lib/spamassassin? I'm not sure if that would be against aptitude or spamassassin. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346999 Title: spamassassin 3.4.0 post installation script error ubuntu server 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1346999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311368] [NEW] Won't install on precise (over ssh), blocking installation of ia32-libs
Public bug reported: bluez package fails to install via apt-get, which prevents me from installing ia32-libs, on precise. Running over ssh, not sure if that could be relevant. I'm not interested in using the bluez package at all, this is a server. # apt-get install bluez Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: bluez 0 upgraded, 1 newly installed, 0 to remove and 39 not upgraded. Need to get 0 B/969 kB of archives. After this operation, 2,525 kB of additional disk space will be used. Selecting previously unselected package bluez. (Reading database ... 89815 files and directories currently installed.) Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... Setting up bluez (4.98-2ubuntu7.1) ... reload: Unknown instance: invoke-rc.d: initscript dbus, action force-reload failed. start: Job failed to start invoke-rc.d: initscript bluetooth, action start failed. dpkg: error processing bluez (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: bluez E: Sub-process /usr/bin/dpkg returned an error code (1) # apt-get install ia32-libs Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: bluez bluez-alsa:i386 ia32-libs-multiarch:i386 Suggested packages: libpam-ldap:i386 libpam-winbind:i386 libnss-ldap:i386 The following NEW packages will be installed: bluez bluez-alsa:i386 ia32-libs ia32-libs-multiarch:i386 0 upgraded, 4 newly installed, 0 to remove and 39 not upgraded. Need to get 0 B/1,111 kB of archives. After this operation, 2,987 kB of additional disk space will be used. Do you want to continue [Y/n]? Selecting previously unselected package bluez. (Reading database ... 89815 files and directories currently installed.) Unpacking bluez (from .../bluez_4.98-2ubuntu7.1_amd64.deb) ... Selecting previously unselected package bluez-alsa:i386. Unpacking bluez-alsa:i386 (from .../bluez-alsa_4.98-2ubuntu7.1_i386.deb) ... Selecting previously unselected package ia32-libs-multiarch:i386. Unpacking ia32-libs-multiarch:i386 (from .../ia32-libs-multiarch_20090808ubuntu36_i386.deb) ... Selecting previously unselected package ia32-libs. Unpacking ia32-libs (from .../ia32-libs_20090808ubuntu36_amd64.deb) ... Processing triggers for man-db ... Processing triggers for ureadahead ... Setting up bluez (4.98-2ubuntu7.1) ... reload: Unknown instance: invoke-rc.d: initscript dbus, action force-reload failed. start: Job failed to start invoke-rc.d: initscript bluetooth, action start failed. dpkg: error processing bluez (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of bluez-alsa:i386: bluez-alsa:i386 depends on bluez; however: Package bluez is not configured yet. dpkg: error processing bluez-alsa:i386 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ia32-libs-multiarch:i386: ia32-libs-multiarch:i386 depends on bluez-alsa; however: Package bluez-alsa:i386 is not configured yet. dpkg: error processing ia32-libs-multiarch:i386 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of ia32-libs: ia32-libs depends on ia32-libs-multiarch; however: Package ia32-libs-multiarch is not installed. Package ia32-libs-multiarch:i386 is not configured yet. dpkg: error processing ia32-libs (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: bluez bluez-alsa:i386 ia32-libs-multiarch:i386 ia32-libs E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311368 Title: Won't install on precise (over ssh), blocking installation of ia32-libs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1311368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311368] Re: Won't install on precise (over ssh), blocking installation of ia32-libs
This workaround seems to have worked: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1032915/comments/5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311368 Title: Won't install on precise (over ssh), blocking installation of ia32-libs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1311368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1032915] Re: [quantal] dbus: upgrade fails in chroot
I had a very similar looking problem, not under chroot, but running over ssh, on a server. Is this expected to work in that situation? Bug #1311368 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1032915 Title: [quantal] dbus: upgrade fails in chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1032915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1260855] Re: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity)
** Tags added: ipv6 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1260855 Title: http://start.ubuntu.com/connectivity-check.html and other ubiquity services are not accessible over IPv6 (no internet connectivity in ubiquity) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1260855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1208667] [NEW] needs packaging for newer ubuntu releases
Public bug reported: I just succeed in building http://sourceforge.net/projects/kxstitch/files/kxstitch/0.9.2/kxstitch-0.9.2-KDE4.tar.gz/download after just installing these packages (and their dependencies) kdelibs-bin kdelibs5-dev libmagick++-dev on Precise. I imagine you'd want to package it for a newer release. It looks like it might also be useful to do http://sourceforge.net/projects/kxstitch/files/SymbolEditor/1.0.0/SymbolEditor-1.0.0-KDE4.tar.gz/download with it. Upstream source: http://sourceforge.net/apps/mediawiki/kxstitch/index.php?title=Main_Page#Download ** Affects: kxstitch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1208667 Title: needs packaging for newer ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kxstitch/+bug/1208667/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1180218] Re: Update to 1.1
How did 4 more people see and click this bug affects them in the 6 hours since it was created? Are you all actually subscribed to new bugs against the wayland package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1180218 Title: Update to 1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1180218/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054776] Re: Don't include remote searches in the home lens
Colin: Comment #167 says nothing about it defaulting to off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054776 Title: Don't include remote searches in the home lens To manage notifications about this bug go to: https://bugs.launchpad.net/unity-lens-shopping/+bug/1054776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 967149] Re: Solution to Nvidia + cairo-gl memory problem proposed by Nvidia
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Bug watch added: www.eglibc.org/issues/ #23 http://www.eglibc.org/issues/issue23 ** Also affects: eglibc via http://www.eglibc.org/issues/issue23 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/967149 Title: Solution to Nvidia + cairo-gl memory problem proposed by Nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/967149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058211]
Yup, not much to add here, that is the reason for how things work. - krh Closing wontfix. Let us know if you have better, specific ideas. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058211 Title: weston does not fallback gracefully if $XDG_RUNTIME_DIR is not set To manage notifications about this bug go to: https://bugs.launchpad.net/weston/+bug/1058211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 940640] Re: Mouse cursors should be vector graphics
Why is this being discussed on ubuntu's bug tracker, instead of wayland's, or the wayland mailing list. Or even the wayland IRC channel. You're both often in there. min2: Using scalable vector graphics just implies using a non-raster graphics format. It does not require dealing with pointer scaling different than the existing format. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/940640 Title: Mouse cursors should be vector graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmz-cursor-theme/+bug/940640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065720] Re: Default behavior of Ubuntu's primary interface is to try to sell me things
*** This bug is a duplicate of bug 1054776 *** https://bugs.launchpad.net/bugs/1054776 unimatrix9: That's great, but it sounds like the default is still to have Amazon ads enabled, which I am not okay with. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065720 Title: Default behavior of Ubuntu's primary interface is to try to sell me things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065720] Re: Default behavior of Ubuntu's primary interface is to try to sell me things
*** This bug is a duplicate of bug 1054776 *** https://bugs.launchpad.net/bugs/1054776 Vistaus: Again, I'm not interested in workarounds. I find the default behavior offensive. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065720 Title: Default behavior of Ubuntu's primary interface is to try to sell me things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1113424] Re: gedit crashed with SIGSEGV in wl_proxy_get_user_data()
Looks like this has been fixed upstream, in gtk: Darxus gedit segfault under wayland was reportd to ubuntu, seb128 says it's a wayland bug, segfault happened in wl_proxy_get_user_data: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1113424 jpetersen Darxus, should be fixed by https://bugzilla.gnome.org/show_bug.cgi?id=693338 ** Bug watch added: GNOME Bug Tracker #693338 https://bugzilla.gnome.org/show_bug.cgi?id=693338 ** Package changed: wayland (Ubuntu) = gtk+3.0 (Ubuntu) ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=693338 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1113424 Title: gedit crashed with SIGSEGV in wl_proxy_get_user_data() To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1113424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1106158] Re: Applications using D-Bus crash on Wayland
It's probably better to run weston-launch via dbus-launch (dbus-launch install/bin/weston-launch) instead of the application. And I think this only shows up when running weston outside of X (on DRM), because when you run it under X, you already have dbus launched. Also, I'm not convinced there is a bug here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1106158 Title: Applications using D-Bus crash on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1106158/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1106145] Re: Weston does not respect keyboard language setting
I'm not sure it make sense for this to be an ubuntu bug yet. I'm guessing you're talking about communicating the keyboard layout from gnome-control-center to weston. I think it would make more sense to first discuss on the wayland list how that should even happen. I believe the only way to set it now is with the weston.ini, probably with the keymap_layout setting. And I don't think there's a global default weston.ini yet that you could put it in, which maybe there should be. The weston.ini man page has at least been committed upstream: http://cgit.freedesktop.org/wayland/weston/tree/man/weston.ini.man -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1106145 Title: Weston does not respect keyboard language setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1106145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1106145] Re: Weston does not respect keyboard language setting
If there's a relevant environment variable, it seems like it should be pretty easy and reasonable to get weston to use it for the keymap, but I still think this is a conversation that would be more appropriate on the wayland mailing list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1106145 Title: Weston does not respect keyboard language setting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1106145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Great, thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
The libwayland0 MIR has been closed fix committed. So everything should be ready to enable the wayland backend in the gtk package? Iain / Benjamin? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1102597] Re: weston-launch: could not open tty0: permission denied
This is the result of a packaging decision from about a year ago, in the 0.85 changelog: * Build without setuid for weston; it's very young and experimental, so let's be cautious. I am curious when this is likely to change. I believe weston-launch tries to handle permissions cleanly, and release them as soon as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1102597 Title: weston-launch: could not open tty0: permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1102597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Looks like Timo did the libxkbcommon v0.2.0 package. So next step is a MIR for it? Benjamin? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097685] [NEW] libwayland and weston package versions in raring are incompatable
Public bug reported: libwayland is at v1.0.2: http://packages.ubuntu.com/raring/libwayland0 weston is at v0.95: http://packages.ubuntu.com/raring/weston These won't work together. I believe the last API break was at v0.99. (I have not actually tested this myself, but got verification that this isn't expected to work.) I'm thinking this should not get the automatic wishlist priority of a normal request to package a new upstream release, since what is currently in the archives isn't usable? ** Affects: weston (Ubuntu) Importance: Undecided Status: New ** Tags: raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097685 Title: libwayland and weston package versions in raring are incompatable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1097685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
I think that libxkbcommon0 description is out of date, probably written before there was a release, when the package was built from a git repo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Not particularly, thanks :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Iain, are you aware the mesa packages already depend on libwayland0? Shouldn't that make it okay for gtk to depend on libwayland0? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Yay. In case anybody else was trying to look up how libwayland0 ended up in main: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/810217 (MIR = Main Inclusion Request) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Somebody want to un-close this bug for raring? Won't let me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Iain, could you say what exactly the reasons are for not wanting the gtk package to depend on a wayland package? I posted about this problem here: http://lists.freedesktop.org/archives/wayland-devel/2013-January/006888.html A couple people have said what they think the reasons are in replies. It would be good to be sure, to help figure out a solution. It might help to say what the reason is for having wayland conflict with proprietary drivers. I recognize weston (the reference wayland implementation) won't run on those drivers. But I'm not sure why its package would conflict with them (and I'm having difficulty checking what the conflicts actually are). But you could have the weston package conflict with those proprietary drivers, but have libwayland installable, and then be able to run gtk with a dependency on libwayland? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
The GTK+ folks closed the above bug, to split the wayland backend into a dynamically loadable library, wontfix saying No. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Fred: I think you misunderstand. I don't think Iain is saying this can't be fixed. Somebody please correct me if I'm wrong, but it sounds to me like the solution which would make Iain happy, and not cause any problems for anybody else, would be if GTK+ built its Wayland backend into a separate dynamically loadable library, and loaded it at run time. So that a GTK+ package could be installed and run (at all, under X), without the absolute necessity of installing a Wayland package just to get GTK+ to run (at all, under X). Iain, can you confirm I understand this, so I can at least open a bug against GTK+ requesting it? Is there anything else that would be needed? This has been a pretty frustrating process. Thanks for trying. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 954352] Re: Enable wayland backend
Thanks. GTK+ bug opened: https://bugzilla.gnome.org/show_bug.cgi?id=690381 ** Bug watch added: GNOME Bug Tracker #690381 https://bugzilla.gnome.org/show_bug.cgi?id=690381 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/954352 Title: Enable wayland backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/954352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054776] Re: Don't include remote searches in the home lens
'What EFF Wants From Ubuntu ... Disable Include online search results by default. ' - https://www.eff.org/deeplinks/2012/10/privacy-ubuntu-1210-amazon-ads-and-data-leaks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054776 Title: Don't include remote searches in the home lens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1054776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022424] Re: Can pick wrong DRM device
CSRedRat: Are you saying this bug has been fixed upstream? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022424 Title: Can pick wrong DRM device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1022424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065720] Re: Default behavior of Ubuntu's primary interface is to try to sell me things
*** This bug is a duplicate of bug 1054776 *** https://bugs.launchpad.net/bugs/1054776 Piet: No, the problem is not that Software Center does not declare packages (although I suppose that would also be worth adding). The problem is that Ubuntu is displaying ads by default. I see this got marked a duplicate of bug 1054776. As, I suppose, it should be. I'm sorry I missed that in my initial search. I was somewhat distracted by rage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065720 Title: Default behavior of Ubuntu's primary interface is to try to sell me things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1054776] Re: Don't include remote searches in the home lens
This is a screenshot of what you get when you type something with no local hits. I was trying to get to a package manager in a fresh install of Quantal beta 2 yesterday, typed packages, and got this. A screen full of 24 ads. I did not click more suggestion. You get fewer ads if you actually have matching installed local content, in this case, for example gdebi or synaptic. But those don't come installed with Quantal beta 2. ** Attachment added: Screenshot https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1054776/+attachment/3396542/+files/unity.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1054776 Title: Don't include remote searches in the home lens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1054776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065720] [NEW] Default behavior of Ubuntu's primary interface is to try to sell me thiings
Public bug reported: I'm so furious that I've been mentioning to people for years that I prefer Ubuntu, and that they might, as a result, think that I condone this I just installed Quantal in a virtual machine, ran Unity just long enough to switch back to the Gnome Classic UI. As I was trying to pull up the package manager, I typed in packages, and got a screen full of CDs to buy. I'm told that removing the unity-lens-shopping package fixes this. In my very strong opinion, this package needs to not be installed by default. I've never seriously considered giving up on Ubuntu before, but this is so far from okay. ** Affects: unity-lens-shopping (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065720 Title: Default behavior of Ubuntu's primary interface is to try to sell me thiings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065720] Re: Default behavior of Ubuntu's primary interface is to try to sell me thiings
** Attachment added: Screenshot https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+attachment/3395472/+files/unity.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065720 Title: Default behavior of Ubuntu's primary interface is to try to sell me thiings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065720] Re: Default behavior of Ubuntu's primary interface is to try to sell me things
** Summary changed: - Default behavior of Ubuntu's primary interface is to try to sell me thiings + Default behavior of Ubuntu's primary interface is to try to sell me things -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065720 Title: Default behavior of Ubuntu's primary interface is to try to sell me things To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-shopping/+bug/1065720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064541] Re: rfc-ignorant.org will stop working soon
This was fixed upstream, as mentioned in the upstream bug this is linked to. What might not be obvious from that bug is that you get the fix by running sa-update, to get an updated set of rules, which you should be doing daily from cron anyway. So there is nothing that needs to be done to the ubuntu packaging (for any 3.3.0 or newer release). You can verify by making sure these two rules are not in the rules you're using: DNS_FROM_RFC_BOGUSMX DNS_FROM_RFC_DSN In /var/lib/spamassassin/3.004000/updates_spamassassin_org . ** Changed in: spamassassin (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1064541 Title: rfc-ignorant.org will stop working soon To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1064541/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064541] Re: rfc-ignorant.org will stop working soon
I didn't see your comment about updating the base package before my comment / status change. I have no objection to you re-opening it for that. Just seems like it would be pretty low priority. Are there people running spamassassin without running sa-update? If so, why? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1064541 Title: rfc-ignorant.org will stop working soon To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1064541/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064541] Re: rfc-ignorant.org will stop working soon
I keep lagging behind on comments just enough to be maximally annoying, sorry. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spamassassin in Ubuntu. https://bugs.launchpad.net/bugs/1064541 Title: rfc-ignorant.org will stop working soon To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1064541/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1064541] Re: rfc-ignorant.org will stop working soon
This was fixed upstream, as mentioned in the upstream bug this is linked to. What might not be obvious from that bug is that you get the fix by running sa-update, to get an updated set of rules, which you should be doing daily from cron anyway. So there is nothing that needs to be done to the ubuntu packaging (for any 3.3.0 or newer release). You can verify by making sure these two rules are not in the rules you're using: DNS_FROM_RFC_BOGUSMX DNS_FROM_RFC_DSN In /var/lib/spamassassin/3.004000/updates_spamassassin_org . ** Changed in: spamassassin (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064541 Title: rfc-ignorant.org will stop working soon To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1064541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064541] Re: rfc-ignorant.org will stop working soon
I didn't see your comment about updating the base package before my comment / status change. I have no objection to you re-opening it for that. Just seems like it would be pretty low priority. Are there people running spamassassin without running sa-update? If so, why? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064541 Title: rfc-ignorant.org will stop working soon To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1064541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1064541] Re: rfc-ignorant.org will stop working soon
I keep lagging behind on comments just enough to be maximally annoying, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1064541 Title: rfc-ignorant.org will stop working soon To manage notifications about this bug go to: https://bugs.launchpad.net/spamassassin/+bug/1064541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Woo, it made it into quantal: http://packages.ubuntu.com/quantal /sensors-applet If anybody else was curious what happens after something gets uploaded to New: https://launchpad.net/ubuntu/quantal/+queue https://wiki.ubuntu.com/ArchiveAdministration Norbert: Must is some pretty strong language for somebody expecting something for free without contributing any effort. I find it annoying, and I think you might have better results with more polite language. (And I basically agree with you.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 894391] Re: [FFe, MIR] support $XDG_RUNTIME_DIR
The ubuntu-desktop package in quantal now has a dependency on libpam- xdg-support, so everyone will get this by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/894391 Title: [FFe, MIR] support $XDG_RUNTIME_DIR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/894391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058211] Re: weston does not fallback gracefully if $XDG_RUNTIME_DIR is not set
My interest in this bug is resolved with ubuntu-desktop now having a dependency on libpam-xdg-support. Is there any real chance anybody here is going to do anything on what the summary was changed to, the lack of fallback if $XDG_RUNTIME_DIR is not set, especially now that it will be set by default for everyone due to the above, or should it be closed won't fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058211 Title: weston does not fallback gracefully if $XDG_RUNTIME_DIR is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1058211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
It's been a few days, and this package still doesn't appear to be in the archives. What needs to be done? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 969646] Re: [needs-packaging] Gtk3 perl module
Imported from Debian for Quantal: http://packages.ubuntu.com/quantal/libgtk3-perl ** Changed in: ubuntu Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/969646 Title: [needs-packaging] Gtk3 perl module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/969646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Thanks Fabrice. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1017598] Re: no --help or --version options
weston --help and --version both work with the latest weston commit: 1428b8ccf749233908436b4b480ceca5eafd18e7 ** Changed in: weston (Ubuntu) Status: Confirmed = Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1017598 Title: no --help or --version options To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/weston/+bug/1017598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Ubuntu Sponsors? Anybody (with a Quantal key) out there? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Fabrice, thanks. Changed version to 3.0.0-0.2ubuntu1 (that's what you meant, right?) Ran update-maintainer, which changed the maintainer to Ubuntu Developers. Debdiff attached. ** Patch added: debdiff https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+attachment/3362642/+files/sensors-applet_3.0.0-0.2.dsc-sensors-applet_3.0.0-0.2ubuntu1.dsc.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Daniel: I have done nothing with locales at any point in this process. Is it an upstream problem? I'm not even sure how locales are relevant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Daniel: Do you have any reason to believe this locale issue is not an upstream problem? It seems likely that it is upstream. And 39 days after feature freeze, 17 days before release, seems like a really bad time to worry about it here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
I don't suppose anybody has any idea if a diff is actually currently required from Debian's version? The patches in the last Ubuntu package, for Natty, look pretty minor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Created a ppa, without the previous differences applied: https://launchpad.net/~darxus/+archive/sensors-applet/ List of all the commands I executed to do it are in the description. Daniel, looks like the changes you're talking about are: 1) Add build-depends (in debian/control): nvidia-settings (= 173.14.09-1ubuntu2) [amd64 i386], (Does that version need to be changed?) 2) In debian/rules: # enable nvidia support confflags += --with-nvidia=yes I don't suppose anybody has a the Debian packaging for v2.2.7-2 (without Ubuntu modifications) that we could actually do a diff of? It looks (from the changelog) like Debian was planning on splitting the nvidia support out to a separate sensors-applet-nvidia package, disabled the nvidia stuff in this one, and then never created the nvidia package? So an import without a diff should work, but not support nvidia, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
There's also this, in sensors-applet/Makefile.am: -LIBS = $(GLIB_LIBS) $(GTK_LIBS) $(GNOME_LIBS) $(CAIRO_LIBS) $(LIBNOTIFY_LIBS) +LIBS = -ldl $(GLIB_LIBS) $(GTK_LIBS) $(GNOME_LIBS) $(CAIRO_LIBS) $(LIBNOTIFY_LIBS) Not sure how / if that's related. But looking over a debdiff from sensors-applet_3.0.0-0.2.dsc to sensors-applet_2.2.7-2ubuntu2.dsc, I think these three chunks are all that was changed in the debian version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
No, I meant v2.2.7-2, because that's what the latest released ubuntu package I see is based on. But that's closer than 3.0.0-0, thanks. The -ldl was not a delta from Debian. There are a few other chunks that are, I believe, just changes in the location of line breaks in pop-up messages. I'm thinking they're not worth keeping. For example: #: ../sensors-applet/sensors-applet.c:301 -Si è verificato un errore nel tentativo di salvare la configurazione corrente del sensore. +Si è verificato un errore nel tentativo di salvare la configurazione +corrente del sensore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049343] Re: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main)
Debdiff attached. Contains, I believe, all the differences from Debian in the last package, minus some whitespace changes in pop-ups. Not tested. Uploaded to PPA, still building: https://launchpad.net/~darxus/+archive/sensors-applet/ ** Patch added: debdiff https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+attachment/3359047/+files/sensors-applet_3.0.0-0.2.dsc-sensors-applet_3.0.0-0.2ubuntu2.dsc.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049343 Title: FFe: Un-blacklist and merge sensors-applet 3.0.0-0.2 (universe) from Debian testing (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sensors-applet/+bug/1049343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
