[Desktop-packages] [Bug 1294163] [NEW] Please update precise nvidia drivers to support 3.13 trusty backport kernel
Public bug reported: [Impact] * The 3.13 trusty backport kernel for 12.04 will be released fairly soon. Some people have started testing the daily builds out the the Kernel Team PPA. However the NVIDIA binary drivers in precise need patches to support the 3.13 kernel. [Test Case] * The latest Nvidia binary driver series in 12.04 should work with the upcomping 3.13 backport kernel; it currently does not. [Regression Potential] * Low. The patches enable compatibility with newer kernels but do not affect installations on older kernels. ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Triaged ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Triaged ** Tags: precise ** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1294163 Title: Please update precise nvidia drivers to support 3.13 trusty backport kernel Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Triaged Bug description: [Impact] * The 3.13 trusty backport kernel for 12.04 will be released fairly soon. Some people have started testing the daily builds out the the Kernel Team PPA. However the NVIDIA binary drivers in precise need patches to support the 3.13 kernel. [Test Case] * The latest Nvidia binary driver series in 12.04 should work with the upcomping 3.13 backport kernel; it currently does not. [Regression Potential] * Low. The patches enable compatibility with newer kernels but do not affect installations on older kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1294163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1099755] Re: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1
I think that's just a matter of timing, given that we are already past feature freeze on an LTS. There is certainly interest in getting this into Debian as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1099755 Title: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 Status in “wpa” package in Ubuntu: New Status in “wpa” package in Debian: New Bug description: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) and 2.0 (released 2013-01-12) and 2.1 (released 2014-02-04). 2.1 contains a number of bugfixes relevant to frequent disconnects some might be seeing on networks where there is a lot of roaming, some IBSS (ad-hoc) fixes, etc. http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868904] Re: Redshift fails to start with session due to geoclue failure
Here's another debdiff with a patch to add the dependency _and_ change the default provider in source from #define DEFAULT_PROVIDER "org.freedesktop.Geoclue.Providers.UbuntuGeoIP" #define DEFAULT_PROVIDER_PATH "/org/freedesktop/Geoclue/Providers/UbuntuGeoIP" to: #define DEFAULT_PROVIDER "org.freedesktop.Geoclue.Providers.Hostip" #define DEFAULT_PROVIDER_PATH "/org/freedesktop/Geoclue/Providers/Hostip" I'm not sure this proves anything but I also noticed that UbuntuGeoIP is not on Freedesktop.org's list of providers: http://www.freedesktop.org/wiki/Software/GeoClue/Providers/ Really, redshift should have some sort of dependency on a working provider regardless. geoclue-ubuntu-geoip was only there on Unity-based desktops because it happens to already be pulled in by indicator- datetime and unity-webapps-service. The dependency was always missing, it just happened to work as long as geoclue-ubuntu-geoip was there and still working. ** Patch added: "redshift.saucy.chgdefault.debdiff" https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/868904/+attachment/3879574/+files/redshift.saucy.chgdefault.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/868904 Title: Redshift fails to start with session due to geoclue failure Status in Redshift color temperature adjustment: Confirmed Status in Ubuntu GeoIP Provider: New Status in “redshift” package in Ubuntu: Fix Released Status in “ubuntu-geoip” package in Ubuntu: Confirmed Bug description: Since switching to oneiric redshift won't start. It is listed as a startup application and these lines are present in .xsession-error from it: Unable to get location from provider. Started Geoclue provider `Geoclue Master'. Using provider `geoclue'. There is also no process in a ps listing. If I start it from the command prompt then it starts just fine often with substantially similar messages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: redshift 1.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Wed Oct 5 22:39:15 2011 SourcePackage: redshift UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/redshift/+bug/868904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 868904] Re: Redshift fails to start with session due to geoclue failure
Thank you @Fred and @valent! This has been bugging me for ages. Though I lived with it by hardcoding my location, it was still really annoying when traveling. I prepared a debdiff for saucy adding a dependency on geoclue-hostip. But I also took a look for geoclue-ubuntu-geoip bugs and sure enough, I found LP bug 1239082 which seems to confirm that it is broken in general. So I'll upload this first debdiff, as adding a dependency on geoclue- hostip does solve the problem alone, and perhaps the ubuntu-geoip provider will be fixed later. ** Patch added: "redshift.saucy.debdiff" https://bugs.launchpad.net/ubuntu/+source/redshift/+bug/868904/+attachment/3879553/+files/redshift.saucy.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-geoip in Ubuntu. https://bugs.launchpad.net/bugs/868904 Title: Redshift fails to start with session due to geoclue failure Status in Redshift color temperature adjustment: Confirmed Status in Ubuntu GeoIP Provider: New Status in “redshift” package in Ubuntu: Fix Released Status in “ubuntu-geoip” package in Ubuntu: Confirmed Bug description: Since switching to oneiric redshift won't start. It is listed as a startup application and these lines are present in .xsession-error from it: Unable to get location from provider. Started Geoclue provider `Geoclue Master'. Using provider `geoclue'. There is also no process in a ps listing. If I start it from the command prompt then it starts just fine often with substantially similar messages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: redshift 1.7-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Wed Oct 5 22:39:15 2011 SourcePackage: redshift UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/redshift/+bug/868904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1203540] Re: Multiple monitors no longer working on zenbook ux31e
It's interesting, I used to suffer from LP 946311 on the same hardware. The result of that bug was that I couldn't turn on the laptop with a monitor plugged in, but hot-plugging later worked fine. Since sometime in the raring cycle (iirc) that problem was solved. It's been perfect up until just recently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1203540 Title: Multiple monitors no longer working on zenbook ux31e Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Running up-to-date Saucy. Just recently (within the last couple of days) my Asus Zenbook lost the ability to support two displays. If I boot with an external display (via mini-vga port) it will work, but the internal panel will not. If I boot without the external display, the internal panel works fine, but hot-plugging the external panel does nothing. If I check System Settings / Displays using the external monitor, I only see my external monitor, although Displays reports it as "Built- in Display". ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 21 12:37:31 2013 DistUpgraded: 2013-02-14 16:33:22,299 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1427] InstallationDate: Installed on 2012-10-20 (273 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUSTeK Computer Inc. UX31E MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-4-generic root=/dev/mapper/ubuntu-root ro splash pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 elevator=noop vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to saucy on 2013-02-14 (156 days ago) dmi.bios.date: 12/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Sun Jul 21 10:32:21 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1203540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1203540] [NEW] Multiple monitors no longer working on zenbook ux31e
Public bug reported: Running up-to-date Saucy. Just recently (within the last couple of days) my Asus Zenbook lost the ability to support two displays. If I boot with an external display (via mini-vga port) it will work, but the internal panel will not. If I boot without the external display, the internal panel works fine, but hot-plugging the external panel does nothing. If I check System Settings / Displays using the external monitor, I only see my external monitor, although Displays reports it as "Built-in Display". ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 21 12:37:31 2013 DistUpgraded: 2013-02-14 16:33:22,299 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1427] InstallationDate: Installed on 2012-10-20 (273 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: ASUSTeK Computer Inc. UX31E MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.10.0-4-generic root=/dev/mapper/ubuntu-root ro splash pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 elevator=noop vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to saucy on 2013-02-14 (156 days ago) dmi.bios.date: 12/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Sun Jul 21 10:32:21 2013 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.2-0ubuntu1 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ubuntu ** Package changed: compiz (Ubuntu) => xserver-xorg-video-intel (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1203540 Title: Multiple monitors no longer working on zenbook ux31e Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Running up-to-date Saucy. Just recently (within the last couple of days) my Asus Zenbook lost the ability to support two displays. If I boot with an external display (via mini-vga port) it will work, but the internal panel will not. If I boot without the external display, the internal panel works fine, but hot-plugging the external panel does nothing. If I check System Settings / Displays using the external monitor, I only see my external monitor, although Displays reports it as "Built- in Display". ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-4.13-generic 3.10.1 Uname: Linux 3.10.0-4-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.11-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Jul 21 12:37:31 2013 DistUpgrad
[Desktop-packages] [Bug 953392] Re: File /usr/share/gnome-pkg-tools/control.header contains one blank line to much at the end - Please remove it
Also related: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694384 ** Bug watch added: Debian Bug tracker #694384 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694384 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-pkg-tools in Ubuntu. https://bugs.launchpad.net/bugs/953392 Title: File /usr/share/gnome-pkg-tools/control.header contains one blank line to much at the end - Please remove it Status in “gnome-pkg-tools” package in Ubuntu: Fix Released Status in “gnome-pkg-tools” source package in Precise: Fix Released Status in “gnome-pkg-tools” package in Debian: New Bug description: SRU Justification: [Impact] Gnome-pkg-tools produces non-standard control files. This is fixed in quantal, and is a simple removal of a blank line, thus backported easily to precise. [Testcase] See bug below. [Regression Potential] Minimal, this is a single removal of a blank line from control.header. -- Hi everyone, I've noticed that the file /usr/share/gnome-pkg-tools/control.header contains one blank line to much at the end of the file. Please remove it because it produces non standard control files. Example from the package mutter: File debian/control.in: - Source: mutter Section: x11 - File debian/control: - # This file is autogenerated. DO NOT EDIT! # # Modifications should be made to debian/control.in instead. # This file is regenerated automatically in the clean target. Source: mutter Section: x11 ... - This extra blank line causes issues with tools like pbuilder (automatic installation of build dependencies doesn't work). Because of the blank line the Source paragraph is no longer the first paragraph in the file. The first paragraph then only consists of comments and thus pbuilder-satisfydepends can't determine the build dependencies which yields a build failure because of missing build dependencies... References: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-sourcecontrolfiles Quote: "The first paragraph of the control file contains information about the source package in general. The subsequent sets each describe a binary package that the source tree builds." https://answers.launchpad.net/launchpad/+question/151535 Quote: "The problem is the blank line in your debian/control file separating the commented out block and the initial "Source: gnome-orca" paragraph. A very strict reading of the Debian Policy Manual says this is invalid: you have an empty initial paragraph, and the Source paragraph as the second paragraph. Some tools may be more tolerant and skip the initial empty paragraph, however pbuilder-satisfydepends does not." Please fix this little issue asap because it blocks automatic builds with pbuilder for certain Gnome packages. This issue is present in all package versions from Lucid up to Precise. Please also note that not all editors show the additional blank line. You could use a hex editor to get rid of the last 0a in the file. $ xxd /usr/share/gnome-pkg-tools/control.header ... 0a0: 2074 6172 6765 742e 0a0a target... Best, Michael To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-pkg-tools/+bug/953392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126633] Re: Please mark alsa-utils Multi-Arch: foreign
** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1126633 Title: Please mark alsa-utils Multi-Arch: foreign Status in “alsa-utils” package in Ubuntu: Fix Released Status in “alsa-utils” source package in Precise: Fix Committed Status in “alsa-utils” source package in Quantal: Fix Committed Bug description: [Impact] Marking alsa-utils as M-A: foreign will allow i386 packages that depend on alsa-utils to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-utils and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1154370] Re: [precise SRU] crash due to improper handling of "/" in GSettings
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1154370
Title:
[precise SRU] crash due to improper handling of "/" in GSettings
Status in “glib2.0” package in Ubuntu:
Confirmed
Bug description:
GSettings in GLib 2.32.3 has a bug where the "changed" signal is
emitted for child settings objects as if they were keys ending with
"/".
That was fixed upstream and merged into the glib-2-32 stable branch
here:
https://git.gnome.org/browse/glib/commit/?h=glib-2-32&id=e6f659a898595ba944bd02f0509b14694d1c26e7
GLib 2.32.4 was since released and contains the fix.
This fix is needed because there exists software (muffin) that
contains code along these lines:
void
change_event_handler (GSettings *settings, const gchar *key, gpointer
user_data)
{
...
g_settings_get_value (settings, key);
...
}
and it's invalid to pass a key containing "/" to
g_settings_get_value() (causing crashes).
This only happens when entire paths are reset (such as when running
'dconf update'). That makes the issue relatively rare but it's
affecting corporate deployments (Google, specifically).
We should either do an SRU with just the patch linked to above to
(ideally) QA and SRU the entire GLib 2.32.4 release to precise.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1154370/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126633] Re: Please mark alsa-utils Multi-Arch: foreign
** Tags removed: verification-needed ** Tags added: verification-done-precise verification-done-quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1126633 Title: Please mark alsa-utils Multi-Arch: foreign Status in “alsa-utils” package in Ubuntu: Fix Released Status in “alsa-utils” source package in Precise: Fix Committed Status in “alsa-utils” source package in Quantal: Fix Committed Bug description: [Impact] Marking alsa-utils as M-A: foreign will allow i386 packages that depend on alsa-utils to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-utils and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126558] Re: Please mark alsa-base as Multi-Arch: foreign
Looks good. Tested on both P and Q. Thanks! ** Tags removed: verification-needed-precise verification-needed-quantal ** Tags added: verification-done-precise verification-done-quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1126558 Title: Please mark alsa-base as Multi-Arch: foreign Status in “alsa-driver” package in Ubuntu: Fix Released Status in “alsa-driver” source package in Precise: Fix Committed Status in “alsa-driver” source package in Quantal: Fix Committed Bug description: [Impact] Marking alsa-base as M-A: foreign will allow i386 packages that depend on alsa-base to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-base:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-base and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1126558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126633] Re: Please mark alsa-utils Multi-Arch: foreign
And for precise. ** Patch added: "alsa-utils.precise.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+attachment/3554252/+files/alsa-utils.precise.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1126633 Title: Please mark alsa-utils Multi-Arch: foreign Status in “alsa-utils” package in Ubuntu: New Bug description: [Impact] Marking alsa-utils as M-A: foreign will allow i386 packages that depend on alsa-utils to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-utils and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126633] Re: Please mark alsa-utils Multi-Arch: foreign
The change is now in raring. Here's the debdiff for quantal. Thanks! ** Patch added: "alsa-utils.quantal.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+attachment/3554251/+files/alsa-utils.quantal.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1126633 Title: Please mark alsa-utils Multi-Arch: foreign Status in “alsa-utils” package in Ubuntu: New Bug description: [Impact] Marking alsa-utils as M-A: foreign will allow i386 packages that depend on alsa-utils to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-utils and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126633] Re: Please mark alsa-utils Multi-Arch: foreign
As with the alsa-base bug, this is already changed in raring packaging branches. I will post diffs for quantal and precise. Thanks @themuso for making the change in raring! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1126633 Title: Please mark alsa-utils Multi-Arch: foreign Status in “alsa-utils” package in Ubuntu: New Bug description: [Impact] Marking alsa-utils as M-A: foreign will allow i386 packages that depend on alsa-utils to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-utils and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126633] [NEW] Please mark alsa-utils Multi-Arch: foreign
Public bug reported: [Impact] Marking alsa-utils as M-A: foreign will allow i386 packages that depend on alsa-utils to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-utils and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. ** Affects: alsa-utils (Ubuntu) Importance: Undecided Status: New ** Tags: precise quantal raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1126633 Title: Please mark alsa-utils Multi-Arch: foreign Status in “alsa-utils” package in Ubuntu: New Bug description: [Impact] Marking alsa-utils as M-A: foreign will allow i386 packages that depend on alsa-utils to install on a amd64 system. Since alsa interfaces are architecture independent, foreign seems like the correct marking. $ sudo apt-get install my-32-bit-app my-32-bit-app:i386 : PreDepends: alsa-utils:i386 but it is not installable [Test Case] Install a 32-bit package that depends or pre-depends on alsa-utils and have it properly install. [Regression Potential] Minimal as this change on affects multi-arch status only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1126633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1004775] Re: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup
I think this should be marked "Fixed Released" for Precise now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1004775 Title: NetworkManager restarts dnsmasq and adds host route on every IPv6 route lookup Status in “dnsmasq” package in Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Fix Released Status in “dnsmasq” source package in Precise: In Progress Status in “network-manager” source package in Precise: In Progress Status in “dnsmasq” source package in Quantal: Fix Released Status in “network-manager” source package in Quantal: Fix Released Bug description: NetworkManager stops and starts dnsmasq very frequently (every few minutes). During the brief window that dnsmasq is restarting, hostname resolution doesn't work. dnsmasq is getting restarted frequently enough that I see brief hostname resolution errors in Chrome several times a day during normal web browsing. This is on Precise with network-manager 0.9.4.0-0ubuntu4 and dnsmasq- base 2.59-4. The frequent restarts seem to be triggered by IPv6 route advertisements on my network. (See log snippet below.) When NetworkManager gets a route advertisement, it reconfigures everything. In the case of dnsmasq, this means stopping dnsmasq, writing a new config file, and starting dnsmasq. NetworkManager should restart dnsmasq only if it its configuration changes. I'm attaching a snippet from /var/log/daemon.log on my system that demonstrates a restart. This is with debug logging configured in /etc/NetworkManager/NetworkManager.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1004775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 995165] Re: IPv4 connectivity broken after installing from ubuntu-12.04-alternate-amd64.iso
I've verified the fix in proposed using the precise mini.iso. With IPv6 enabled on the router, I was able to duplicate the issue. Reinstalling with proposed enabled in the kernel command-line worked as expected (with IPv4 connectivity). ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/995165 Title: IPv4 connectivity broken after installing from ubuntu-12.04-alternate- amd64.iso Status in “network-manager” package in Ubuntu: Fix Released Status in “network-manager” source package in Precise: Fix Committed Bug description: [Impact] IPv6 is becoming increasingly popular and installations on IPv6-ready networks are becoming more frequent; this issue affects installations of the Desktop image from the alternate image (or using d-i in any other way) when IPv6 autoconfiguration or DHCPv6 is used. These installations will fail to recognize that the interface should be managed by NetworkManager after the installation because only the "iface X inet dhcp" line would be commented out, leaving another valid "iface X" line for "inet6" causing NetworkManager to ignore the device. The solution was to comment out all lines in /etc/network/interfaces pertaining to interface X: "auto X", "iface X inet", and "iface X inet6". [Test Case] 1a) With IPv6 autoconfiguration (for example, using radvd) or DHCPv6 available on the network: 1b) With no IPv6 available on the network: 2) Install Ubuntu from the alternate CD; or using d-i via a netboot image. 3) After the installation: a) Verify that NetworkManager properly handles all interfaces. b) Verify that the network interfaces configuration is commented out in /etc/network/interfaces. [Regression Potential] Untypical configurations may find devices that should be ignored by NetworkManager to be handled by it. Standard installations could fail to comment the necessary information from /etc/network/interfaces to allow for NetworkManager to do is job; or the file could be mangled to remove the "lo" interface, which would make unrelated services fail. --- To reproduce: - Download ubuntu-12.04-alternate-amd64.iso, sha256sum: f8d54df0afbab6a6248f6e2bcab3e68f01c04d52b0bb1f889d880ad3bc881ccb - Burn it to a USB flash drive from a completely up-to-date Ubuntu 10.04 LTS with UNetbootin - Install on a machine with both IPv4 and IPv6 connectivity - Log in to the newly installed system Current behaviour: - There is no IPv4 connectivity - NetworkManager doesn't show the wired interface in its dropdown Expected behaviour: - There is IPv4 connectivity - NetworkManager does show the wired interface in its dropdown Thoughts: I suspect this is because during the install my /etc/network/interfaces was created like so: ---BEGINS--- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp # This is an autoconfigured IPv6 interface iface eth0 inet6 auto ---ENDS--- Then network-manager-0.9.4.0/debian/ifblacklist_migrate.sh mutates the file to comment out a single line like so: #NetworkManager#iface eth0 inet dhcp i.e. the line iface eth0 inet6 auto remains intact This means that the /etc/network/interfaces file gives me IPv6 connectivity but not IPv4 connectivity. Furthermore, because there is an uncommented iface eth0 inet6 line, NetworkManager doesn't show me the interface in its dropdown. To fix: - The regular expression needs to be changed so that the iface eth0 inet6 auto line is also commented out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/995165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 890986] Re: Lotus Notes is incompatible with ayatana scrollbars
Quantal and precise verified. Looks good! Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/890986 Title: Lotus Notes is incompatible with ayatana scrollbars Status in Overlay Scrollbar: Confirmed Status in The Unico Gtk+ Theming Engine: Invalid Status in “light-themes” package in Ubuntu: Invalid Status in “overlay-scrollbar” package in Ubuntu: Fix Released Status in “light-themes” source package in Precise: Invalid Status in “overlay-scrollbar” source package in Precise: Fix Committed Status in “light-themes” source package in Quantal: Invalid Status in “overlay-scrollbar” source package in Quantal: Fix Committed Bug description: = Problem = When using Lotus notes with Unity the scrollbars do not display correctly. This uses gtk_paint_box, the theme for the scrollbar should be redrawn but is not. = Environment = * Ubuntu 11.10 (Oneiric) i386 * Unity 4.22.0-0ubuntu3 = Steps to reproduce = 1. Compile scroll.cpp: g++ -o scroll scroll.cpp `pkg-config --libs gtk+-2.0``pkg-config --cflags gtk+-2.0` 2. Launch it from a terminal 3. Click on the buttons to make the scroll bar scroll up and down [Regression Potential] Minimal; adds Notes to the list of applications that won't get overlay scrollbars and instead revert to the GTK-style scrollbars. This would also affect any other applications using the same binary name: "lnotes", "notes". = Other Information = See screenshot attached (scrollbar-1.png) To manage notifications about this bug go to: https://bugs.launchpad.net/overlay-scrollbar/+bug/890986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1071950] Re: gnome-settings-daemon dconf to gconf plugin causes settings to be lost
** Tags added: precise quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1071950 Title: gnome-settings-daemon dconf to gconf plugin causes settings to be lost Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” source package in Quantal: In Progress Bug description: Impact: Using dconf profiles can lead to gconf keys to be overwritten with wrong values, it's especially impact some desktop settings and compiz Test Case: $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false $ gconftool --get /desktop/gnome/sound/event_sounds false Then editing some file under /etc/dconf and running dconf update: $ sudo vi /etc/dconf/db/site.d/screensaver $ sudo dconf update $ gconftool --get /desktop/gnome/sound/event_sounds true Regression potential: Some of the gsettings could not be written back to gconf which could impact legacy applications which are still reading the gconf value -- This was tested in a fresh installed precise machine, with the addition of dconf and a particular dconf configuration. Settings set in gconf backend get overwritten when running 'dconf update'. This can be tested by changing any value in gconf to something different than the default: $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false $ gconftool --get /desktop/gnome/sound/event_sounds false $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy $ gconftool --get /apps/metacity/general/focus_mode sloppy Then editing some file under /etc/dconf and running dconf update: $ sudo vi /etc/dconf/db/site.d/screensaver $ sudo dconf update $ gconftool --get /desktop/gnome/sound/event_sounds true $ gconftool --get /apps/metacity/general/focus_mode click After talking about this with Ryan Lortie, he suggested disabling the gnome-settings-daemon plugin: $ gsettings set org.gnome.settings-daemon.plugins.gconf active false $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy $ sudo vi /etc/dconf/db/site.d/screensaver $ sudo dconf update $ gconftool --get /desktop/gnome/sound/event_sounds false $ gconftool --get /apps/metacity/general/focus_mode sloppy It looks like the gconf plugin is overwriting all the settings with the defaults, thus losing anything the user had customized. It's quite likely that a number of other bugs "Compiz loses my settings" are actually caused by this plugin. Also, as instructed by Ryan, I tried removing /usr/share/GConf/gsettings/wm-schemas.convert and re-enabling the plugin, and then it doesn't override any values that are related to the window manager but it does override the one in the example: $ gsettings reset org.gnome.settings-daemon.plugins.gconf active $ gsettings get org.gnome.settings-daemon.plugins.gconf active true $ gconftool --set /desktop/gnome/sound/event_sounds --type bool false $ gconftool --set /apps/metacity/general/focus_mode --type string sloppy $ sudo vi /etc/dconf/db/site.d/screensaver $ sudo dconf update $ gconftool --get /desktop/gnome/sound/event_sounds true $ gconftool --get /apps/metacity/general/focus_mode sloppy So, focus_mode didn't get overwritten while event_sounds did. One possible solution is to remove the wm-schemas so that compiz settings don't get lost. A better (but probably harder) solution would be to fix the plugin so that it doesn't overwrite what the user sets. Maybe just remove the schemas that are being modified and stored in gconf for Precise. I found out that to reproduce in a fresh installed precise machine, I had to set up some dconf files, then reboot, and then I could reproduce consistently as explained here. I'm attaching a bunch of dconf files. After unpacking, you need to run dconf update once to generate the db and then reboot. After that it should be reproducible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1071950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 890986] Re: Lotus Notes is incompatible with ayatana scrollbars
** Tags added: precise quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/890986 Title: Lotus Notes is incompatible with ayatana scrollbars Status in Ayatana Scrollbar: Confirmed Status in The Unico Gtk+ Theming Engine: Invalid Status in “light-themes” package in Ubuntu: Invalid Bug description: = Problem = When using Lotus notes with Unity the scrollbars do not display correctly. This uses gtk_paint_box, the theme for the scrollbar should be redrawn but is not. = Environment = * Ubuntu 11.10 (Oneiric) i386 * Unity 4.22.0-0ubuntu3 = Steps to reproduce = 1. Compile scroll.cpp: g++ -o scroll scroll.cpp `pkg-config --libs gtk+-2.0``pkg-config --cflags gtk+-2.0` 2. Launch it from a terminal 3. Click on the buttons to make the scroll bar scroll up and down = Other Information = See screenshot attached (scrollbar-1.png) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-scrollbar/+bug/890986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 890986] Re: Lotus Notes is incompatible with ayatana scrollbars
Any guess on when this will hit precise or at least the unapproved queue? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/890986 Title: Lotus Notes is incompatible with ayatana scrollbars Status in Ayatana Scrollbar: Confirmed Status in The Unico Gtk+ Theming Engine: Invalid Status in “light-themes” package in Ubuntu: Invalid Bug description: = Problem = When using Lotus notes with Unity the scrollbars do not display correctly. This uses gtk_paint_box, the theme for the scrollbar should be redrawn but is not. = Environment = * Ubuntu 11.10 (Oneiric) i386 * Unity 4.22.0-0ubuntu3 = Steps to reproduce = 1. Compile scroll.cpp: g++ -o scroll scroll.cpp `pkg-config --libs gtk+-2.0``pkg-config --cflags gtk+-2.0` 2. Launch it from a terminal 3. Click on the buttons to make the scroll bar scroll up and down = Other Information = See screenshot attached (scrollbar-1.png) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-scrollbar/+bug/890986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1013211] Re: [FFe] Please transition libgnomecanvas to multi-arch
Do we need user verification to move this along to quantal proper? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomecanvas in Ubuntu. https://bugs.launchpad.net/bugs/1013211 Title: [FFe] Please transition libgnomecanvas to multi-arch Status in “libgnomecanvas” package in Ubuntu: Fix Released Status in “libgnomecanvas” source package in Precise: In Progress Bug description: [Impact] Please transition libgnomecanvas to support multi-arch. This package is still required by some third party applications. [Test Case] Install i386 within amd64 environment. Verify i386 applications link proper architecture dependent library. [Regression Potential] Potential is minimal as no new code changes are present only build rules. This package is a dependency of python-gnome2 as well as several packages in universe. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgnomecanvas2-0 2.30.3-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jun 14 16:47:24 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: libgnomecanvas UpgradeStatus: Upgraded to precise on 2012-05-22 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomecanvas/+bug/1013211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054344] Re: Please mark xterm as "Multi-arch: foreign"
Thanks @didrocks and @tjaalton for the tips! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1054344 Title: Please mark xterm as "Multi-arch: foreign" Status in “xterm” package in Ubuntu: Fix Released Status in “xterm” source package in Precise: In Progress Status in “xterm” source package in Quantal: Fix Released Bug description: [Impact] Marking xterm "Multi-arch: foreign" will allow 32-bit packages to depend on xterm and install successfully on 64-bit releases of Ubuntu from 11.04 onward. Some 3rd party apps, such as Lotus Sametime, use xterm to display messages. [Test Case] Build and install i386 packages on amd64 and attempt to depend on xterm. [Regression Potential] Minimal as this packaging change only means that pulling in the 64-bit xterm can satisfy the dependency of a 32-bit application. Can we make this change for precise? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1054344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054344] Re: Please mark xterm as "Multi-arch: foreign"
debdiff for precise ** Patch added: "xterm.precise.debdiff" https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1054344/+attachment/335/+files/xterm.precise.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1054344 Title: Please mark xterm as "Multi-arch: foreign" Status in “xterm” package in Ubuntu: Confirmed Bug description: [Impact] Marking xterm "Multi-arch: foreign" will allow 32-bit packages to depend on xterm and install successfully on 64-bit releases of Ubuntu from 11.04 onward. Some 3rd party apps, such as Lotus Sametime, use xterm to display messages. [Test Case] Build and install i386 packages on amd64 and attempt to depend on xterm. [Regression Potential] Minimal as this packaging change only means that pulling in the 64-bit xterm can satisfy the dependency of a 32-bit application. Can we make this change for precise? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1054344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054344] Re: Please mark xterm as "Multi-arch: foreign"
debdiff for quantal. ** Patch added: "xterm.quantal.debdiff" https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1054344/+attachment/3349991/+files/xterm.quantal.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1054344 Title: Please mark xterm as "Multi-arch: foreign" Status in “xterm” package in Ubuntu: Confirmed Bug description: [Impact] Marking xterm "Multi-arch: foreign" will allow 32-bit packages to depend on xterm and install successfully on 64-bit releases of Ubuntu from 11.04 onward. Some 3rd party apps, such as Lotus Sametime, use xterm to display messages. [Test Case] Build and install i386 packages on amd64 and attempt to depend on xterm. [Regression Potential] Minimal as this packaging change only means that pulling in the 64-bit xterm can satisfy the dependency of a 32-bit application. Can we make this change for precise? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1054344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054344] Re: Please mark xterm as "Multi-arch: foreign"
debdiff for quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1054344 Title: Please mark xterm as "Multi-arch: foreign" Status in “xterm” package in Ubuntu: Confirmed Bug description: [Impact] Marking xterm "Multi-arch: foreign" will allow 32-bit packages to depend on xterm and install successfully on 64-bit releases of Ubuntu from 11.04 onward. Some 3rd party apps, such as Lotus Sametime, use xterm to display messages. [Test Case] Build and install i386 packages on amd64 and attempt to depend on xterm. [Regression Potential] Minimal as this packaging change only means that pulling in the 64-bit xterm can satisfy the dependency of a 32-bit application. Can we make this change for precise? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1054344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1054344] [NEW] Please mark xterm as "Multi-arch: foreign"
Public bug reported: [Impact] Marking xterm "Multi-arch: foreign" will allow 32-bit packages to depend on xterm and install successfully on 64-bit releases of Ubuntu from 11.04 onward. Some 3rd party apps, such as Lotus Sametime, use xterm to display messages. [Test Case] Build and install i386 packages on amd64 and attempt to depend on xterm. [Regression Potential] Minimal as this packaging change only means that pulling in the 64-bit xterm can satisfy the dependency of a 32-bit application. Can we make this change for precise? ** Affects: xterm (Ubuntu) Importance: Undecided Status: New ** Tags: precise quantal ** Tags added: precise quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1054344 Title: Please mark xterm as "Multi-arch: foreign" Status in “xterm” package in Ubuntu: New Bug description: [Impact] Marking xterm "Multi-arch: foreign" will allow 32-bit packages to depend on xterm and install successfully on 64-bit releases of Ubuntu from 11.04 onward. Some 3rd party apps, such as Lotus Sametime, use xterm to display messages. [Test Case] Build and install i386 packages on amd64 and attempt to depend on xterm. [Regression Potential] Minimal as this packaging change only means that pulling in the 64-bit xterm can satisfy the dependency of a 32-bit application. Can we make this change for precise? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1054344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1052637] [NEW] Please transition libgnome-desktop-2-17 to multi-arch
Public bug reported: [Impact] Libgnome-desktop-2-17 is in main and is still needed for some third-party apps such as Lotus Notes. [Test Case] Install i386 within amd64 environment. Verify i386 applications link proper architecture dependent library. ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: precise quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1052637 Title: Please transition libgnome-desktop-2-17 to multi-arch Status in “gnome-desktop” package in Ubuntu: New Bug description: [Impact] Libgnome-desktop-2-17 is in main and is still needed for some third-party apps such as Lotus Notes. [Test Case] Install i386 within amd64 environment. Verify i386 applications link proper architecture dependent library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1052637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977940] Re: Please transition gnome-vfs to multi-arch
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-vfs in Ubuntu. https://bugs.launchpad.net/bugs/977940 Title: Please transition gnome-vfs to multi-arch Status in “gnome-vfs” package in Ubuntu: Fix Released Status in “gnome-vfs” source package in Precise: Fix Committed Bug description: [Impact] Please transition gnome-vfs to support multi-arch. This package is still required by some third party applications. [Test Case] Install i386 within amd64 environment. Verify i386 applications link proper architecture dependent library. [Regression Potential] Potential is minimal as no new code changes are present only build rules. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgnomevfs2-0 1:2.24.4-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu5 Architecture: amd64 Date: Tue Apr 10 12:00:32 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120401) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-vfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-vfs/+bug/977940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1052030] [NEW] Please transition libgnomeprint to multi-arch
Public bug reported: [Impact] Though the libgnomeprint library has been deprecated for years in favor of gtkprint, it is still needed for some third-party apps such as Lotus Notes. [Test Case] Install i386 within amd64 environment. Verify i386 applications link proper architecture dependent library. ** Affects: libgnomeprint (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-vfs (Ubuntu) => libgnomeprint (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-vfs in Ubuntu. https://bugs.launchpad.net/bugs/1052030 Title: Please transition libgnomeprint to multi-arch Status in “libgnomeprint” package in Ubuntu: New Bug description: [Impact] Though the libgnomeprint library has been deprecated for years in favor of gtkprint, it is still needed for some third-party apps such as Lotus Notes. [Test Case] Install i386 within amd64 environment. Verify i386 applications link proper architecture dependent library. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomeprint/+bug/1052030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 956848] Re: pam_mkhomedir.so fails to create homedir in precise
** Tags added: css-sponsored-p -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/956848 Title: pam_mkhomedir.so fails to create homedir in precise Status in Light Display Manager: New Status in “lightdm” package in Ubuntu: Confirmed Status in “lightdm” source package in Precise: Confirmed Bug description: I am testing Ubuntu Precise and I think I found a bug related to creation of home directories with pam_mkhomedir.so. I found it initially in an LDAP-based setup, but to nail down the problem I did a fresh re-install, added: session optional pam_mkhomedir.so umask=0077 skel=/etc/skel to /etc/pam.d/common-session and I removed the home directory of the user used during installation, so the bug has nothing to do with network auth. Anyway - when I login to lightdm I am successfully authenticated and the logon screen disappears, but I am presented with a black screen and nothing happens. I can login from text mode, the homedir is created and afterwards I can login, even using the graphical interface. I tried to see if this is related to lightdm or unity, but if I select Gnome classic, I get the same problem, if I switch to GDM, the problem remains. I am attaching the logs from lightdm. The syslog says: Mar 16 10:31:45 tubuntu kernel: [99829.342230] accounts-daemon[2152]: segfault at 10 ip b76c86c3 sp bfab7640 error 4 in libdbus-1.so.3.5.8[b76a3000+47000] Mar 16 10:31:45 tubuntu kernel: [99829.342545] gdm-session-wor[29440]: segfault at 6e756279 ip b743cd4c sp bf84b250 error 4 in libc-2.15.so[b73ca000+19e000] but I cannot say if this caused the issue or was caused by the issue. I hope somebody can have a look at this. I can help to do some investigating, unfortunately I don't know where to look. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/956848/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 105900]
Hi Behdad. Anything new on this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/105900 Title: [Upstream] Bold, Italics, and Bold Italics not in English on Fonts menu Status in LibreOffice Productivity Suite: Fix Released Status in Fontconfig - Font Configuration Library: Confirmed Status in The OpenOffice.org Suite: Unknown Status in “fontconfig” package in Ubuntu: Triaged Status in “libreoffice” package in Ubuntu: Fix Released Status in “openoffice.org” package in Ubuntu: Invalid Status in “openoffice.org” package in openSUSE: New Bug description: Binary package hint: openoffice.org Using the current ooo packages for Feisty, open Writer, type a few characters, and then go to the Format --> Character menu. In the Font tab under Typeface, the options listed are: Normal cursiva Negreta Negreta cursiva The system in question is en_US. I've had Feisty on this computer for some time and do not recall seeing this before (not certain I used the Font menu though). To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/105900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 806773] Re: empathy crashed with SIGABRT in raise()
Crashed on launch. Oddly this is the first time I've had this crash and I've been running oneiric for a couple of weeks. It worked fine on the next launch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/806773 Title: empathy crashed with SIGABRT in raise() Status in “empathy” package in Ubuntu: Confirmed Bug description: Unplugged NetworkManager and crash. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: empathy 3.1.3-1ubuntu1 Uname: Linux 3.0.0-0300rc6-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Wed Jul 6 22:51:11 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110531.1) ProcCmdline: empathy ProcEnviron: LANG=es_CL.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: empathy StacktraceTop: raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 abort () at abort.c:92 g_assertion_message (domain=, file=, line=, func=0x504090 "individual_store_contact_sort", message=0x15dda80 "assertion failed: (account_a != NULL)") at /build/buildd/glib2.0-2.29.8/./glib/gtestutils.c:1425 g_assertion_message_expr (domain=0x0, file=0x503c8b "empathy-individual-store.c", line=1426, func=0x504090 "individual_store_contact_sort", expr=) at /build/buildd/glib2.0-2.29.8/./glib/gtestutils.c:1436 individual_store_contact_sort (individual_a=0x13e8d80, individual_b=0x1e0e870) at empathy-individual-store.c:1426 Title: empathy crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/806773/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
