[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted x11proto-input into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/x11proto- input/2.3-1~precise1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: x11proto-input (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: Fix Committed Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Branch linked: lp:ubuntu/precise-proposed/x11proto-input -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: New Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: New Status in “x11proto-input” source package in Precise: Fix Committed Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Daniel, the logs look fine; can you please add a corresponding system D-BUS debug log? (https://wiki.ubuntu.com/DebuggingDBus) I need to know if the PrepareForSleep false gets sent properly. Also, you are using hybrid suspend, which hasn't been tested at all. Can you check if this bug also happens for a standard suspend for you? I. e. does the hybrid part make a difference or not? Thanks! (The remainder of this bug is far from triaged -- it's absolutely unclear what breaks on the machines that are still affected) ** Changed in: systemd-shim (Ubuntu Trusty) Status: Triaged = Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Fix Committed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1197213] Re: Heads up display does not work in 13.10
I have the same problem. HUD totally useless now. Since HUD is a critcal part of Unity this is really anoying. Please fix this asap! I am using Ubuntu 13.10 64bit and Compiz rotating cube. I have tried the Unity reset described above at Felipe, but it did not help. While you are at it: is it possible to enhance the launcher buttons management? It would be great to be able to modify properties of buttons through right clicking on them. I would like to be able to change button properties like: icon file, full path of program launched, etc. Now I modify those properties by editting the .desktop files in ~/.local/share/applications/. Right clicking on a button would be so much easier! But please fix HUD first. -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1197213 Title: Heads up display does not work in 13.10 Status in “hud” package in Ubuntu: Confirmed Bug description: The Heads up display feature does not work in ubuntu 13.10. the interface invokes on pressing the alt key. But it does nothing when the first few letters or the entire text is typed. Please fix this bug as soon as possible Thanks and Have a nice day :) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: hud 13.10.1+13.10.20130702-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic i686 ApportVersion: 2.10.2-0ubuntu3 Architecture: i386 Date: Wed Jul 3 06:46:22 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-05-21 (42 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130101) MarkForUpload: True ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SourcePackage: hud UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1197213/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1073597] Re: [quantal] [regression] Incorrect icons for USB devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1073597 Title: [quantal] [regression] Incorrect icons for USB devices Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: In 12.04, when I plug in a USB stick it is shown as a USB icon in the laucher. A media player is displayed as a media player icon. In 12.10, some USB sticks are displayed as a combined USB/floppy icon. My media player is displayed as a USB icon. The drives which show incorrect icons are all SanDisk: Cruzer Micro (0781:5406) Cruzer Micro (0781:5151) and the media player is: Sansa E260 (0781:7421) The usual dialog asking what to do when a media player is inserted is not displayed in 12.10 as it was in 12.04. The drive that is re-mounted is an old Lexar 64MB Jumpdrive (05dc:0080). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1073597/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
This bug was fixed in the package systemd-shim - 6-0ubuntu0.13.10 --- systemd-shim (6-0ubuntu0.13.10) saucy-proposed; urgency=low * New upstream bug fix release: - Write a sendsigs.omit.d file to prevent upstart from killing us during shutdown. That's the other half of preventing suspends during shutdown. (LP: #1211514) - Flush the right bus (system, not session), to address another case of PrepareForSleep signal is missing which breaks networking after resuming. (helps some people in LP: #1252121) -- Martin Pitt martin.p...@ubuntu.com Tue, 10 Dec 2013 10:59:08 +0100 ** Changed in: systemd-shim (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1211514] Re: Shutdowns fail to finish if laptop lid is closed before completely shutdown
This bug was fixed in the package systemd-shim - 6-0ubuntu0.13.10 --- systemd-shim (6-0ubuntu0.13.10) saucy-proposed; urgency=low * New upstream bug fix release: - Write a sendsigs.omit.d file to prevent upstart from killing us during shutdown. That's the other half of preventing suspends during shutdown. (LP: #1211514) - Flush the right bus (system, not session), to address another case of PrepareForSleep signal is missing which breaks networking after resuming. (helps some people in LP: #1252121) -- Martin Pitt martin.p...@ubuntu.com Tue, 10 Dec 2013 10:59:08 +0100 ** Changed in: systemd-shim (Ubuntu Saucy) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1211514 Title: Shutdowns fail to finish if laptop lid is closed before completely shutdown Status in “systemd-shim” package in Ubuntu: Fix Released Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd-shim” source package in Trusty: Fix Released Bug description: Only seen in a ubuntu (unity) session, others report gnome sessions SRU INFORMATION TEST CASE on laptop: - Shutdown machine from session indicator, close laptop lid right after selecting shutdown or reboot from pop up window. - What should happen: lid close gets ignored and machine should complete shutdown process - What does happen: machine gets suspended until the laptop lid is re-opened, then it either completes the shutdown (if the lid close happened early enough), or hangs eternally FIX: https://github.com/desrt/systemd-shim/commit/6c65a113 and https://github.com/desrt/systemd-shim/commit/b8f324dae5 (both are needed) REGRESSION POTENTIAL: A broken systemd-shim can potentially completely prevent shutdown, reboot, suspend, hibernate. This code has been tested with all scenarios, with both doing suspend/lid close during normal operation, and during shutdown (at which point lid close is now ignored). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130812.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 Uname: Linux 3.11.0-1-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Aug 12 17:01:09 2013 InstallationDate: Installed on 2013-08-07 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1211514/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Update Released
The verification of the Stable Release Update for systemd-shim has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1211514] Update Released
The verification of the Stable Release Update for systemd-shim has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1211514 Title: Shutdowns fail to finish if laptop lid is closed before completely shutdown Status in “systemd-shim” package in Ubuntu: Fix Released Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd-shim” source package in Trusty: Fix Released Bug description: Only seen in a ubuntu (unity) session, others report gnome sessions SRU INFORMATION TEST CASE on laptop: - Shutdown machine from session indicator, close laptop lid right after selecting shutdown or reboot from pop up window. - What should happen: lid close gets ignored and machine should complete shutdown process - What does happen: machine gets suspended until the laptop lid is re-opened, then it either completes the shutdown (if the lid close happened early enough), or hangs eternally FIX: https://github.com/desrt/systemd-shim/commit/6c65a113 and https://github.com/desrt/systemd-shim/commit/b8f324dae5 (both are needed) REGRESSION POTENTIAL: A broken systemd-shim can potentially completely prevent shutdown, reboot, suspend, hibernate. This code has been tested with all scenarios, with both doing suspend/lid close during normal operation, and during shutdown (at which point lid close is now ignored). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130812.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-1.4-generic 3.11.0-rc4 Uname: Linux 3.11.0-1-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon Aug 12 17:01:09 2013 InstallationDate: Installed on 2013-08-07 (4 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130803) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1211514/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
As promised, reopening the saucy task as well, for the people who are still affected. ** Changed in: systemd-shim (Ubuntu Saucy) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1262626] [NEW] fails to build with GTK+ 3.10
Public bug reported: libindicator fails to build with GTK+ 3.10: ../../../libindicator/indicator-image-helper.c: In function 'refresh_image': ../../../libindicator/indicator-image-helper.c:68:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:68:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] ../../../libindicator/indicator-image-helper.c:118:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:118:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] cc1: all warnings being treated as errors make[5]: *** [libindicator3_la-indicator-image-helper.lo] Error 1 See https://mail.gnome.org/archives/gtk-devel- list/2013-July/msg0.html - I'll prepare a patch to convert to named icons. ** Affects: libindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1262626 Title: fails to build with GTK+ 3.10 Status in “libindicator” package in Ubuntu: New Bug description: libindicator fails to build with GTK+ 3.10: ../../../libindicator/indicator-image-helper.c: In function 'refresh_image': ../../../libindicator/indicator-image-helper.c:68:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:68:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] ../../../libindicator/indicator-image-helper.c:118:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:118:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] cc1: all warnings being treated as errors make[5]: *** [libindicator3_la-indicator-image-helper.lo] Error 1 See https://mail.gnome.org/archives/gtk-devel- list/2013-July/msg0.html - I'll prepare a patch to convert to named icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1262626/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 886605] Re: Desktop, Launcher and menu bar still visible when screen locked
Code was apparently merged to fix this bug over a year ago, and the bug report is quite long. If you are still experiencing the bug, I suggest making a new report, including a reference to this one. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/886605 Title: Desktop, Launcher and menu bar still visible when screen locked Status in Compiz: Fix Released Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Fix Released Bug description: [Test Case] 1. Lock your screen - Confirm that the whole screen goes black [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: When I lock my screen, instead of the monitor going, black, the desktop background goes black, but the Unity launcher and the main bar stay visible. When I press a key or move my mouse the unlock dialog, asking me for my password pops up, centered on the black desktop background. I think the main issue here is gnome-screensaver failing to fullscreen. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 5 13:05:04 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/886605/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1262655] [NEW] libappindicator: ftbfs with GTK 3.10, and on ppc64el
Public bug reported: uploaded a quick fix to trusty to fix the build failures http://launchpadlibrarian.net/160202211/libappindicator_12.10.1%2B13.10.20130920-0ubuntu2_12.10.1%2B13.10.20130920-0ubuntu3.diff.gz ** Affects: libappindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262655 Title: libappindicator: ftbfs with GTK 3.10, and on ppc64el Status in “libappindicator” package in Ubuntu: New Bug description: uploaded a quick fix to trusty to fix the build failures http://launchpadlibrarian.net/160202211/libappindicator_12.10.1%2B13.10.20130920-0ubuntu2_12.10.1%2B13.10.20130920-0ubuntu3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1262655/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
@pitti Ok, I have setup the dbus monitor (any filter suggestions?), tee'ing to a logfile. I have then suspended and resumed (after a minute maybe), and there's no PrepareForSleep=false in the log, only: signal sender=:1.3 - dest=(null destination) serial=1076 path=/org/freedesktop/login1; interface=org.freedesktop.login1.Manager; member=PrepareForSleep boolean true The network also did not came up after resuming. Is it safe/wise to post the dbus-monitor log unfiltered puclicitly, or can I send it directly to you? I will now disable hybrid suspend and report back. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 886605] Re: Desktop, Launcher and menu bar still visible when screen locked
I am also getting this bug intermittently on a fully patched Ubuntu 12.04. Just change the status to new. The released fix apparently never worked. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/886605 Title: Desktop, Launcher and menu bar still visible when screen locked Status in Compiz: Fix Released Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Fix Released Bug description: [Test Case] 1. Lock your screen - Confirm that the whole screen goes black [Regression Potential] Visual regressions, shell drawing problems. Part of a big change, many regression potentials. Original description: When I lock my screen, instead of the monitor going, black, the desktop background goes black, but the Unity launcher and the main bar stay visible. When I press a key or move my mouse the unlock dialog, asking me for my password pops up, centered on the black desktop background. I think the main issue here is gnome-screensaver failing to fullscreen. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-screensaver 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sat Nov 5 13:05:04 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/886605/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
With the normal suspend methd, PrepareForSleep=false showed up now (and the network came up again), (together with PrepareForSleep=true): signal sender=:1.3 - dest=(null destination) serial=1094 path=/org/freedesktop/login1; interface=org.freedesktop.login1.Manager; member=PrepareForSleep boolean false However, it usually requires a suspend cycle over night to trigger this bug anyway - so I will report back tomorrow. (I was rather surprised that it was triggered in my last attempt) Where is the PrepareForSleep=false signal emitted and what is it supposed to do? Is it something NetworkManager requires to wake up again? -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Daniel Hahler [2013-12-19 13:11 -]: I have then suspended and resumed (after a minute maybe), and there's no PrepareForSleep=false in the log, only: signal sender=:1.3 - dest=(null destination) serial=1076 path=/org/freedesktop/login1; interface=org.freedesktop.login1.Manager; member=PrepareForSleep boolean true Thanks. So that's still the case even through the shim works as intended. I don't have an off-hand idea where to go from here, I need to study in detail how PrepareForSleep is handled in logind. Is it safe/wise to post the dbus-monitor log unfiltered puclicitly, or can I send it directly to you? Should usually be harmless, but the above was the main piece of information I wanted to get out of it. It would also have the logind calls/signals which might be interesting, but I can't say without looking. Thanks! -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Daniel Hahler [2013-12-19 13:24 -]: With the normal suspend methd, PrepareForSleep=false showed up now (and the network came up again), (together with PrepareForSleep=true): Interesting. To the other affected people: are you using hybrid suspend or the simple (RAM only) suspend? Where is the PrepareForSleep=false signal emitted That comes from logind, which is the component which provides the Suspend() API for the desktop. It should send PrepareForSleep true, then it will wait until apps which registered a suspend inhibitor are done with their pre-suspend actions, then do the actual suspend, and after resume send the PrepareForSleep=false signal so that clients can do their post-suspend actions. Is it something NetworkManager requires to wake up again? Exactly. NM shuts down the network on PrepareForSleep=false, and searches for networks/re-connects on PrepareForSleep=true. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1262626] Re: fails to build with GTK+ 3.10
** Changed in: libindicator (Ubuntu) Status: New = In Progress ** Changed in: libindicator (Ubuntu) Assignee: (unassigned) = Lars Uebernickel (larsu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1262626 Title: fails to build with GTK+ 3.10 Status in “libindicator” package in Ubuntu: In Progress Bug description: libindicator fails to build with GTK+ 3.10: ../../../libindicator/indicator-image-helper.c: In function 'refresh_image': ../../../libindicator/indicator-image-helper.c:68:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:68:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] ../../../libindicator/indicator-image-helper.c:118:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:118:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] cc1: all warnings being treated as errors make[5]: *** [libindicator3_la-indicator-image-helper.lo] Error 1 See https://mail.gnome.org/archives/gtk-devel- list/2013-July/msg0.html - I'll prepare a patch to convert to named icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1262626/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1262655] Re: libappindicator: ftbfs with GTK 3.10, and on ppc64el
** Branch linked: lp:~ted/libappindicator/ppc-fixes -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262655 Title: libappindicator: ftbfs with GTK 3.10, and on ppc64el Status in “libappindicator” package in Ubuntu: New Bug description: uploaded a quick fix to trusty to fix the build failures http://launchpadlibrarian.net/160202211/libappindicator_12.10.1%2B13.10.20130920-0ubuntu2_12.10.1%2B13.10.20130920-0ubuntu3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1262655/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1262626] Re: fails to build with GTK+ 3.10
** Branch linked: lp:~larsu/libindicator/lp1262626 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1262626 Title: fails to build with GTK+ 3.10 Status in “libindicator” package in Ubuntu: In Progress Bug description: libindicator fails to build with GTK+ 3.10: ../../../libindicator/indicator-image-helper.c: In function 'refresh_image': ../../../libindicator/indicator-image-helper.c:68:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:68:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] ../../../libindicator/indicator-image-helper.c:118:3: error: 'gtk_image_set_from_stock' is deprecated (declared at /usr/include/gtk-3.0/gtk/gtkimage.h:151): Use 'gtk_image_set_from_icon_name' instead [-Werror=deprecated-declarations] gtk_image_set_from_stock (image, GTK_STOCK_MISSING_IMAGE, GTK_ICON_SIZE_LARGE_TOOLBAR); ^ ../../../libindicator/indicator-image-helper.c:118:3: error: 'GtkStock' is deprecated [-Werror=deprecated-declarations] cc1: all warnings being treated as errors make[5]: *** [libindicator3_la-indicator-image-helper.lo] Error 1 See https://mail.gnome.org/archives/gtk-devel- list/2013-July/msg0.html - I'll prepare a patch to convert to named icons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1262626/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 907635] Re: lidbusmenu-GTK crash with Geany IDE using Python
Fix committed into lp:libdbusmenu at revision 464, scheduled for release in libdbusmenu, milestone Unknown ** Changed in: libdbusmenu Status: Expired = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libdbusmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/907635 Title: lidbusmenu-GTK crash with Geany IDE using Python Status in DBus Menu: Fix Committed Status in “libdbusmenu” package in Ubuntu: Expired Bug description: When I list debug msgs from the Geany Menu, i get: 22:59:03: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:00:42: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:09:48: Geany INFO : *DOC* : Python (UTF-8) 23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:11: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:14:59: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:15:13: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:14: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:46: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:17:52: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:18: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:26: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:32: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed 23:18:55: LIBDBUSMENU-GTK CRITICAL: watch_submenu: assertion `GTK_IS_MENU_SHELL(menu)' failed I have seen the same or similar postings all on Ubuntu or a derivative. Some have implied that it was a known bug with Ubuntu 11.10. Any help would be greatly appreciated. Geany 0.20, libdbusmenu-gtk4, libdbusmenu-gtk3-4, libdbusmenu-gtk-dev, libdbusmenu-gtk3-dev, Ubuntu 11.10 Someone else on the web was having the same problems using Lotus Notes, same error msg. To manage notifications about this bug go to: https://bugs.launchpad.net/libdbusmenu/+bug/907635/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1262745] [NEW] Cluttery/repeated playback controls
Public bug reported: Currently the sound indicator shows the playback controls of *each* music/media player associated with it. I think this adds too much clutter, and is possibly a waste of space. I am not sure, but in previous versions I think the controls were hidden unless I started the player clicking on its icon. (Maybe this is a regression?) I have added a screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Dec 19 12:16:24 2013 InstallationDate: Installed on 2013-11-27 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131126) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (gnome-control-center:4645): sound-cc-panel-WARNING **: active_output_update - couldn't find a stream from the supposed active output (gnome-control-center:4645): sound-cc-panel-WARNING **: The tree is empty = we have no devices so cannot set the active input ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 needs-design trusty ** Attachment added: sound indicator controls https://bugs.launchpad.net/bugs/1262745/+attachment/3932628/+files/sound-indicator-controls.png ** Description changed: Currently the sound indicator shows the playback controls of *each* - music/media player associated with it. I think this adds to much + music/media player associated with it. I think this adds too much clutter, and is possibly a waste of space. I am not sure, but in previous versions I think the controls were hidden unless I started the player clicking on its icon. (Maybe this is a regression?) I have added a screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Dec 19 12:16:24 2013 InstallationDate: Installed on 2013-11-27 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131126) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: - (gnome-control-center:4645): sound-cc-panel-WARNING **: active_output_update - couldn't find a stream from the supposed active output - - (gnome-control-center:4645): sound-cc-panel-WARNING **: The tree is empty = we have no devices so cannot set the active input + (gnome-control-center:4645): sound-cc-panel-WARNING **: active_output_update - couldn't find a stream from the supposed active output + + (gnome-control-center:4645): sound-cc-panel-WARNING **: The tree is + empty = we have no devices so cannot set the active input -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1262745 Title: Cluttery/repeated playback controls Status in “indicator-sound” package in Ubuntu: New Bug description: Currently the sound indicator shows the playback controls of *each* music/media player associated with it. I think this adds too much clutter, and is possibly a waste of space. I am not sure, but in previous versions I think the controls were hidden unless I started the player clicking on its icon. (Maybe this is a regression?) I have added a screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-sound 12.10.2+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 ApportVersion: 2.12.7-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Thu Dec 19 12:16:24 2013 InstallationDate: Installed on 2013-11-27 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131126) SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) upstart.indicator-sound.log: (gnome-control-center:4645): sound-cc-panel-WARNING **: active_output_update - couldn't find a stream from the supposed active output (gnome-control-center:4645): sound-cc-panel-WARNING **: The tree is empty = we have no devices so cannot set the active input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1262745/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
** Changed in: accountsservice (Ubuntu) Assignee: Marcus Colla Magnus O.R. (collamagnus-or) = (unassigned) ** Changed in: accountsservice (Ubuntu Precise) Assignee: Marcus Colla Magnus O.R. (collamagnus-or) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Released Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 828663] Re: Says Updates Available... when the only updates are uninstallable
This is fixed since Ubuntu 12.10 with the merger of the user menu and device menu: the menu no longer says Updates Available in any circumstance. ** Changed in: indicator-session Status: Triaged = Fix Released ** Changed in: indicator-session (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/828663 Title: Says Updates Available... when the only updates are uninstallable Status in The Session Menu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Bug description: indicator-session 0.3.1-0ubuntu2, Ubuntu Ocelot When an update is not currently installable (for example, because it has unmet dependencies), it is greyed out in Update Manager. When the *only* updates available are not currently installable, the device menu still says Updates Available This is not useful and wastes time. I've clarified the spec to cover this. https://wiki.ubuntu.com/DeviceMenuAndUserMenu?action=diffrev2=8rev1=7 I think this is different from bug 819495, because in that bug Updates Available... disappears after opening Update Manager. Here it does not. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/828663/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 942575] Re: Power-Cog should turn blue when updates are available
This is obsolete since Ubuntu 12.10 with the merger of the user menu and device menu. ** Changed in: indicator-session Status: Confirmed = Invalid ** Changed in: indicator-session (Ubuntu) Status: Triaged = Invalid ** Changed in: ayatana-design Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/942575 Title: Power-Cog should turn blue when updates are available Status in Ayatana Design: Invalid Status in The Messaging Menu: Invalid Status in The Session Menu: Invalid Status in “indicator-session” package in Ubuntu: Invalid Bug description: When new updates are available and the Power-Cog menu entry changes from Software Is Up To Date to Updates Available... two things should happen: 1.) the Power-Cog icon in the panel should change color to blue 2.) the Updates Available... entry in the power-cog menu should change color to blue Per discussion on the unity-des...@lists.launchpad.net thread, Mark wrote on 28 February 2012: Yes, this would be consistent with our design guidelines for the indicators. * the indicator can turn colour [green - affirmative, blue - informational, red - warning] * the relevant section in the indicator (in this case, software update line in the menu) goes the same colour to create a thread from the indicator to the menu action Mockups and bugs welcome. Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/942575/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1257505] Re: Create Unity Control Center so can remain on old GNOME Control Center version
I purged the PPA today and reinstalled it again because you asked for it in mailing list. Normally the translations are there for this labels in System settings... All settings Appearance but in unity-control-center I don't see the Polish labels. Also all the labels in Appearance settings still display in English language but normally they are translated. There is one label in Brightness and blocking settings still in English. The rest of the labels display properly in Polish except Text Entry and Backup (which looks different than in 13.10) but that isn't translated normally. The settings for Online Accounts and Privacy finally work but clicking on the latter results in window becoming to wide and it also crashed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1257505 Title: Create Unity Control Center so can remain on old GNOME Control Center version Status in “activity-log-manager” package in Ubuntu: In Progress Status in “chromium-browser” package in Ubuntu: Confirmed Status in “deja-dup” package in Ubuntu: In Progress Status in “empathy” package in Ubuntu: Confirmed Status in “eog” package in Ubuntu: In Progress Status in “gnome-color-manager” package in Ubuntu: In Progress Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-control-center-signon” package in Ubuntu: In Progress Status in “gnome-media” package in Ubuntu: In Progress Status in “gthumb” package in Ubuntu: In Progress Status in “indicator-bluetooth” package in Ubuntu: In Progress Status in “indicator-datetime” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: In Progress Status in “indicator-session” package in Ubuntu: In Progress Status in “indicator-sound” package in Ubuntu: In Progress Status in “landscape-client” package in Ubuntu: In Progress Status in “language-selector” package in Ubuntu: In Progress Status in “nautilus” package in Ubuntu: In Progress Status in “software-properties” package in Ubuntu: In Progress Status in “ubuntuone-control-panel” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: In Progress Status in “webaccounts-browser-extension” package in Ubuntu: In Progress Bug description: Ubuntu/Unity uses GNOME Control Center as the application to configure the Unity session. We've made a lot of changes appropriate for Ubuntu and Unity (61 patches) which makes it hard to maintain and creates a conflict for Ubuntu GNOME to use the control center. Unity 7 will be replaced by Unity 8 in the future which has a new settings interface. So we can continue to remain on the current version of GNOME Control Center but allow Ubuntu GNOME to continue to update we will create a new project lp:unity-control-center which is a copy of GNOME Control Center 3.6 but with appropriate renaming so both can be installed. A number of packages that refer to gnome-control-center need to be updated to refer to unity-control-center (see bug tasks). A PPA for testing is https://launchpad.net/~ubuntu-desktop/+archive /unity-control-center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1257505/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 904701] Re: Changes to user photo not reflected
Robert, I'm a little confused by your comment; indicator-session does still use user images...? However, I'm also unable to repeat the behavior Owais is reporting, and indicator-session has undergone extensive refactoring since this bug was reported, so I agree with the Fix Released status. :) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/904701 Title: Changes to user photo not reflected Status in The Session Menu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Bug description: Steps to reproduce. 1) Open user accounts and change the display image of the current user. 2) Click the me-menu and observe that the photo has not changed. 3) Now logout or restart unity (reload the indicators) 4) Now the change is reflected. MeMenu should reflect changes to user's photo immediately. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/904701/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1067414] Update Released
*** This bug is a duplicate of bug 1004515 *** https://bugs.launchpad.net/bugs/1004515 The verification of the Stable Release Update for accountsservice has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1067414 Title: gdm crashes if a user account is deleted or added (nslcd,ldap) Status in “accountsservice” package in Ubuntu: Fix Released Status in “gdm” package in Ubuntu: Confirmed Bug description: Scenario: * LDAP User Account (NFS Home Directory) * nslcd and gdm are used * user account information is manipulated, e.g. apt-get remove --purge tomcat7* Result: gdm session crashed Syslog: Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l This can be reproduced on 2 different machines and user accounts ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Oct 16 18:00:05 2012 SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1067414] Re: gdm crashes if a user account is deleted or added (nslcd, ldap)
*** This bug is a duplicate of bug 1004515 *** https://bugs.launchpad.net/bugs/1004515 This bug was fixed in the package accountsservice - 0.6.15-2ubuntu9.7 --- accountsservice (0.6.15-2ubuntu9.7) precise-proposed; urgency=low * debian/patches/0014-fix-double-free.patch Removes a second call to g_free (user-language) that caused a segfault. (LP: #1067414) (LP: #1004515) -- Margarita Manterola ma...@google.com Mon, 08 Jul 2013 12:43:31 +0200 ** Changed in: accountsservice (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1067414 Title: gdm crashes if a user account is deleted or added (nslcd,ldap) Status in “accountsservice” package in Ubuntu: Fix Released Status in “gdm” package in Ubuntu: Confirmed Bug description: Scenario: * LDAP User Account (NFS Home Directory) * nslcd and gdm are used * user account information is manipulated, e.g. apt-get remove --purge tomcat7* Result: gdm session crashed Syslog: Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l This can be reproduced on 2 different machines and user accounts ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Oct 16 18:00:05 2012 SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1004515] Update Released
The verification of the Stable Release Update for accountsservice has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Released Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Martin, for me this occurs in standard suspend, hybrid suspend and also hibernate. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in “systemd-shim” package in Ubuntu: Incomplete Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Incomplete Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1253693] Re: top status bar missing shutdown button, clock, sound icon and more on upgrade to 13.10
I'm getting closer. I found that unity-panel-service wasn't running. However, I can run it in a terminal window and it works. That is, I get the date, time, sound and gear icons in the top status bar. E.g. /usr/lib/unity/unity-panel-service A number of warning messages are displayed: ** (unity-panel-service:7216): WARNING **: Unable to support GtkImageType: 0 ** (unity-panel-service:7216): WARNING **: Unable to support GtkImageType: 0 (unity-panel-service:7216): IDO-WARNING **: Can't load user avatar icon: Error opening file: No such file or directory (unity-panel-service:7216): IDO-WARNING **: Can't load user avatar icon: Error opening file: No such file or directory (unity-panel-service:7216): IDO-WARNING **: Can't load user avatar icon: Error opening file: No such file or directory But if I log out and log in again, still no sound, date/time, gear icons. I have to manually re-run unity-panel-service. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1253693 Title: top status bar missing shutdown button, clock, sound icon and more on upgrade to 13.10 Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “indicator-session” package in Ubuntu: Confirmed Bug description: This bug has been split from #1239710 as the branch for which changing launcher placement to all displays does not work. Every time I login, without fail, the top status bar is missing the gear icon for shutdown, the date, the sound icon and some others. The icons do show from the login window. So if I let the session time out so that the screen locks, I the gear icon appears in the top status bar and works. I have also added a new user to see if the issue has something to do with my account. The new user also has an empty top status bar. The issue happens for both dual monitor and single monitor configurations. When the second monitor is connected, setting launcher placement to all displays does not solve the problem. Neither does mirroring the displays. Everything worked just fine with 13.04. The problem appeared immediately following upgrade to 13.10. mark@mark-desktop:~$ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1253693/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 783240] Re: disable autohide AppMenu (global menu)
*** This bug is a duplicate of bug 682788 *** https://bugs.launchpad.net/bugs/682788 I'm using EOS Luna with mate-panel. i just want to disable the autohide behaviour of the Appmenu with minimizing applications, etc.. Somebody help me pls! Thanks -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/783240 Title: disable autohide AppMenu (global menu) Status in Ayatana Design: New Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Status in Baltix GNU/Linux: New Bug description: Binary package hint: unity I know the design idea of the autohide. http://answerleaks.com/question/ubuntu/22486/why-does-unity-hide-the- menubar But now i need to use a menu entry in two steps: first move the global menu to show it and next move to the right entry. So i wish to show always the global menu (with beneath the title). Can you add this option somewhere (at least in gconfediter). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/783240/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
Hello Maarten, or anyone else affected, Accepted qt4-x11 into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/qt4-x11/4:4.8.1-0ubuntu4.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: qt4-x11 (Ubuntu Precise) Status: New = Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: Fix Committed Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: Fix Committed Status in “x11proto-input” source package in Precise: Fix Committed Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1242633] Re: unity pointer barriers sru bug
** Branch linked: lp:ubuntu/precise-proposed/unity-2d -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1242633 Title: unity pointer barriers sru bug Status in “libxfixes” package in Ubuntu: In Progress Status in “libxi” package in Ubuntu: In Progress Status in “qt4-x11” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity-2d” package in Ubuntu: In Progress Status in “x11proto-input” package in Ubuntu: In Progress Status in “libxfixes” source package in Precise: Fix Committed Status in “libxi” source package in Precise: Fix Committed Status in “qt4-x11” source package in Precise: Fix Committed Status in “unity” source package in Precise: Fix Committed Status in “unity-2d” source package in Precise: Fix Committed Status in “x11proto-input” source package in Precise: Fix Committed Bug description: x11proto-input, libxfixes, libxi, unity and unity-2d in precise needs updates to work with the new pointer barrier api from x1.14. [Impact] * Pointer barrier api has changed between 1.13 and 1.14. (xorg-server-lts-saucy) * Modifications in unity and unity-2d are required to support both api's. [Test Case] * Update all packages. * Test pointer barriers on an old xorg-server, they should continue to work. * Test pointer barriers on the new xorg-server, they should work. [Regression Potential] * Low, it enables a separate code path for pointer barriers. The code in unity is a bit different due to copying the rework from upstream unity and keeping the old paths for legacy pointer barriers. Upstream dropped the old paths. [Other Info] * It's a bit of a hack. The old pointer barrier symbols live in libxfixes, the new ones in libxi. Because of the overlap some modifications had to be made to allow both pointer barriers to be included. This works as well as it can. * Depending on the queried libxi2/libxfixes versions, old pointer barriers or new ones are used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1242633/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
