[Desktop-packages] [Bug 1278437] Update Released
The verification of the Stable Release Update for nautilus 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1278437 Title: can't move link type .desktop files around on desktop Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: * Impact links can't be moved on the desktop * Test case Save the following as e.g. test.desktop in your ~/Desktop folder and try to move it around on the desktop: [Desktop Entry] Version=1.0 Type=Link Name=test URL=https://launchpad.net/index.html * Regression potential Dnd should keep working -- If I have a .desktop file with Type=Link on my desktop and try to move it around it doesn't stay where I drop it but goes back where it was before and tries to download the URL it is referring to instead. Save the following as e.g. test.desktop in your ~/Desktop folder and try to move it around on the desktop: [Desktop Entry] Version=1.0 Type=Link Name=test URL=https://launchpad.net/index.html This affects at least 13.10 and 14.04. In 13.10 Nautilus crashes if the URL as a file:// URL referring to a file on your desktop. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1 Uname: Linux 3.13.0-7-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Mon Feb 10 14:06:24 2014 GsettingsChanges: InstallationDate: Installed on 2013-10-11 (122 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/zsh SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2013-12-07 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1278437/+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
Re: [Desktop-packages] [Bug 1435764] Re: FFe UI exception for LibreOffice Breeze Icons
On Tuesday, March 24, 2015 05:59:08 PM you wrote: > The Kubuntu Docs Team approve this 1000 times yes. Still waiting to hear from the LO maintainer. -- 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/1435764 Title: FFe UI exception for LibreOffice Breeze Icons Status in libreoffice package in Ubuntu: New Bug description: The Kubuntu team would like to include Breeze icons with Libreoffice. This is something we've been working with upstream Libreoffice on since last year. Screenshot: http://starsky.19inch.net/~jr/tmp/libreoffice.png Kubuntu todo item: https://trello.com/c/pXZdfAL4/18-port-libreoffice-themeing-to-kf5 This involves taking a patch which I wrote which is now in upstream master and a tar of the breeze icons Patch: http://starsky.19inch.net/~jr/tmp/kubuntu_breeze-icons.diff complete package is in my PPA https://launchpad.net/~jr/+archive/ubuntu/ppa/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1435764/+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 1435764] Re: FFe UI exception for LibreOffice Breeze Icons
Great. FFe approved. -- 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/1435764 Title: FFe UI exception for LibreOffice Breeze Icons Status in libreoffice package in Ubuntu: In Progress Bug description: The Kubuntu team would like to include Breeze icons with Libreoffice. This is something we've been working with upstream Libreoffice on since last year. Screenshot: http://starsky.19inch.net/~jr/tmp/libreoffice.png Kubuntu todo item: https://trello.com/c/pXZdfAL4/18-port-libreoffice-themeing-to-kf5 This involves taking a patch which I wrote which is now in upstream master and a tar of the breeze icons Patch: http://starsky.19inch.net/~jr/tmp/kubuntu_breeze-icons.diff complete package is in my PPA https://launchpad.net/~jr/+archive/ubuntu/ppa/+packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1435764/+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 1447654] Re: installing policykit-1 hangs under systemd
Hello Nathan, or anyone else affected, Accepted into vivid-proposed. The package will build now and be available in a few hours 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: policykit-1 (Ubuntu Vivid) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Fix Committed Status in policykit-1 source package in Vivid: Fix Committed Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU INFORMATION === Test case: - Boot a minimal VM and purge "apport policykit-1", or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails in vivid final. It should succeed fine with this update. Regression potential: Very low: polkitd does not keep state, so one can restart it fine. The postinst shell modification is simple and obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+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 1447654] Update Released
The verification of the Stable Release Update for policykit-1 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1447654 Title: installing policykit-1 hangs under systemd Status in policykit-1 package in Ubuntu: Fix Released Status in policykit-1 source package in Vivid: Fix Released Bug description: I've installed 15.04 using the current amd64 netboot.tar.gz (MD5 = 6566065bf73a9c81feeddf5520dda122). It installs fine, but I'm getting errors installing packages (such as lubuntu-core). Last few lines from apt-get: Processing triggers for systemd (219-7ubuntu3) ... Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24) Failed to execute operation: Connection timed out dpkg: error processing package systemd (--unpack): subprocess installed post-installation script returned error exit status 1 Processing triggers for libglib2.0-0:amd64 (2.44.0-1ubuntu3) ... Processing triggers for shared-mime-info (1.3-1) ... Processing triggers for mime-support (3.58ubuntu1) ... Processing triggers for udev (219-7ubuntu3) ... Processing triggers for dbus (1.8.12-1ubuntu5) ... Errors were encountered while processing: systemd E: Sub-process /usr/bin/dpkg returned an error code (1) I've done a second install using the server iso and lubuntu-core installs fine on that. The only thing different was my install media. SRU INFORMATION === Test case: - Boot a minimal VM and purge "apport policykit-1", or do the above netboot installation. - sudo apt-get install policykit-1 apport - The above hangs on the systemd triggers and eventually fails in vivid final. It should succeed fine with this update. Regression potential: Very low: polkitd does not keep state, so one can restart it fine. The postinst shell modification is simple and obvious. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1447654/+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 517021] Update Released
The verification of the Stable Release Update for gvfs 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/517021 Title: gvfsd-metadata causes 100% CPU usage Status in GVFS: Unknown Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Precise: Fix Released Status in gvfs source package in Trusty: Fix Committed Status in gvfs source package in Utopic: Fix Committed Status in gvfs source package in Vivid: Fix Released Status in gvfs package in Debian: Fix Released Bug description: Binary package hint: gvfs Failure to write metadata results in an infinite loop that keeps trying to write, thousands of times per second. Steps to reproduce: 1. Open Firefox 2. Save a data: URL (URL that contains the content, with several thousands bytes, often generated by webapps or extensions) as file (There are other ways to run into this problem, e.g. disk full or other error situations. data: URLs are just the easiest way to reproduce.) Actual result: - File is saved - 100% CPU - Extremely high number of file operations by gvfs - billions - Never stops Expected result: Failure to write metadata should just fail, not try again Fix: Patch available and accepted by GNOME https://bugzilla.gnome.org/show_bug.cgi?id=637095 --- Original description --- After installing 9.10 Ubuntu 64bit browsing and opening folder in nautilus or Gnome-commander take several minutes when there are many files in it e.g. 10.000. Interestingly Midnight-commander does not have this problem. Opening such folders does not hang with MC. Using "top" i can see that "gvfsd-metadata" is using 100% CPU and when i kill it the computer stops "hanging". I am using the 32bit version of Karmic too and there is no such Problem (although tested on a different computer). Please fix this because it is highly annyoing. Right now i am killing it every 20s with the watch command to be able to work at all. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/517021/+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 1430694] Update Released
The verification of the Stable Release Update for account-plugins 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1430694 Title: Update Facebook permissions to 2.0 API Status in Online Accounts: Account plugins: In Progress Status in the base for Ubuntu mobile products: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in account-plugins source package in Utopic: Fix Committed Status in account-plugins package in Ubuntu RTM: Fix Released Bug description: The 1.0 API is being deprecated on April 30, 2015. [Impact] Depending on how facebook decides to handle the deprecation, there's the possibility that creating facebook accounts from Ubuntu Online Accounts will just stop working, if our OAuth request (which uses deprecated parameters) gets declined. [Test case] Until the deprecation actually takes place, we won't be able to reproduce the bug. According to the Facebook official documentation, the v1.0 API will stop working on April 30th, 2015: https://developers.facebook.com/docs/apps/changelog [Regression potential] Very low: the new Facebook v2.0 API is already active, and we've been using it in Vivid without issues. A quick smoke test (just create a Facebook account from the System Settings -> Online Accounts pane) is anyway advised, to be absolutely sure. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1430694/+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 1432613] Update Released
The verification of the Stable Release Update for empathy 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 regressions. -- 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/1432613 Title: Facebook and MSN messengers shutting down (third-party client access) Status in Online Accounts: Account plugins: In Progress Status in Webapps Team Task Tracking Project: In Progress Status in account-plugins package in Ubuntu: Fix Committed Status in empathy package in Ubuntu: Fix Committed Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in account-plugins source package in Trusty: Fix Released Status in empathy source package in Trusty: Fix Released Status in ubuntu-system-settings-online-accounts source package in Trusty: Won't Fix Status in account-plugins source package in Utopic: Fix Committed Status in empathy source package in Utopic: Fix Committed Status in ubuntu-system-settings-online-accounts source package in Utopic: Won't Fix Status in account-plugins source package in Vivid: Fix Released Status in empathy source package in Vivid: Fix Released Status in ubuntu-system-settings-online-accounts source package in Vivid: Won't Fix Bug description: [ Description ] Facebook messenger and Windows Live messenger don't work any more because Facebook & Microsoft removed third-party support for them. [ Fix & QA ] Stop supporting IM accounts for these clients. For both creation & continued use. Verify that if you add a WLM or FB account in online accounts, empathy doesn't try to connect to it. account-plugins-windows-live shouldn't be pulled in by default any more (check a trusty daily which is built with proposed). [ Regression potential ] This is a regression, in that we stop supporting some account types. We don't have a choice about this. [ Original description ] The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services & SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+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 1411610] Update Released
The verification of the Stable Release Update for gnome-system-tools 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-tools in Ubuntu. https://bugs.launchpad.net/bugs/1411610 Title: don't ignore OobsResult in a callback function Status in gnome-system-tools package in Ubuntu: Fix Released Status in gnome-system-tools source package in Trusty: Fix Committed Status in gnome-system-tools source package in Utopic: Fix Released Status in gnome-system-tools package in Debian: Fix Released Bug description: [Impact] Users don't receive any info about the errors in the backends (liboobs and system-tools-backends) when they run users-admin tool (unless they run it from the terminal). It's already fixed in Debian and Ubuntu 15.04, but the package remains unpatched in 14.04 and 14.10. The attached patch makes users-admin show the message dialog with the description of the error that happened. [Test Case] You'll need unpatched versions of liboobs (3.0.0-1) and system-tools-backends (2.10.2-1ubuntu1) installed. Run users-admin from the terminal. You'll see a warning message in the terminal: Liboobs-WARNING **: There was an unknown error communicating asynchronously with the backends: Launch helper exited with unknown return code 255 But the users-admin GUI won't show this message - that's the bug. [Regression Potential] I consider the regression risk to be low here. The patch has been already tested by me and gnome-system-tools maintainer in Debian (see the corresponding Debian bug report). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-tools/+bug/1411610/+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 1411577] Update Released
The verification of the Stable Release Update for system-tools-backends 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-tools-backends in Ubuntu. https://bugs.launchpad.net/bugs/1411577 Title: fix current user's info retrieval Status in system-tools-backends package in Ubuntu: Fix Released Status in system-tools-backends source package in Trusty: Fix Committed Status in system-tools-backends source package in Utopic: Fix Released Status in system-tools-backends package in Debian: Fix Released Bug description: [Impact] When a user tries to change his full name via users-admin or mate-users-admin, an error in system-tools-backends prevents him from doing that, and the name remains unchanged (see [Other Info]). The problem is already fixed in Debian and Ubuntu 15.04, but system- tools-backends remains unpatched in 14.04 and 14.10. The attached patch fixes the issue and allows user to change the full name without any warnings or errors appearing. [Test Case] Run users-admin or mate-users-admin from the terminal. Click on the button for changing your full name, change the name to something else and click "OK". You'll see a warning message in the terminal: Liboobs-WARNING **: There was an unknown error communicating with the backends: Launch helper exited with unknown return code 255 The full name won't be changed (see [Other Info]). [Regression Potential] I consider the regression risk to be low here. The patch has been already tested by me and system-tools-backends maintainer in Debian (see the corresponding Debian bug report). [Other Info] If https://bugs.launchpad.net/bugs/1411584 isn't fixed, the new name will appear in the GUI, but it really won't be changed. You can see that for yourself by simply restarting users-admin or mate-users-admin - it will show the old name then. If that bug is fixed, an error message dialog will appear, and the name in the GUI won't be changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-tools-backends/+bug/1411577/+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 1401788] Update Released
The verification of the Stable Release Update for xserver-xorg-video- intel 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 regressions. -- 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/1401788 Title: backport BDW/CHV sna BLT fix Status in X.org xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Trusty: Fix Committed Status in xserver-xorg-video-intel source package in Utopic: Fix Released Status in xserver-xorg-video-intel source package in Vivid: Fix Released Bug description: [Impact] xserver crash on intel gen8 gfx with a test case [Test case] run 'rendercheck -o src,over,overreverse,xor -t dcoords' from i-g-t on gen8 [Regression potential] slim, limited to gen8 [Other info] needs three commits from upstream git To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1401788/+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 1410238] Update Released
The verification of the Stable Release Update for xserver-xorg-video- intel 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 regressions. -- 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/1410238 Title: Rotating external display with optimus results in corruption Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Trusty: Fix Committed Status in xserver-xorg-video-intel source package in Utopic: Fix Released Bug description: [Impact] * Black screen when attempting to rotating external display in affected configurations. [Test Case] * Run a system with a internal nvidia card, and 2 displays on the intel card. (Usually LCD screen + external VGA/DVI screen.) * Run xrandr --output --rotate left * Expect a normal, rotated screen. * Bad behavior is a black screen. [Regression Potential] * Low, only affects the transformed case in optimus mode, but it will be tested against !optimus config too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1410238/+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 1411584] Update Released
The verification of the Stable Release Update for liboobs 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liboobs in Ubuntu. https://bugs.launchpad.net/bugs/1411584 Title: correctly return error and emit warning Status in liboobs package in Ubuntu: Fix Released Status in liboobs source package in Trusty: Fix Committed Status in liboobs source package in Utopic: Fix Released Status in liboobs package in Debian: Fix Released Bug description: [Impact] When a user tries to change his full name via users-admin or mate- users-admin, and some error happens in the backends (either liboobs or system-tools-backends), the error message isn't shown in the GUI. Moreover, the new full name will appear in the GUI, as if it has been successfully changed (when it's not so). The issues are already fixed in Debian and Ubuntu 15.04, but the package remains unpatched in 14.04 and 14.10. The attached patches make users-admin (and mate-users-admin) show the error message dialog when the mentioned error happens, and also show the unchanged full name in this case. [Test Case] You'll need the unpatched version of system-tools-backends (2.10.2-1ubuntu1) installed. Run users-admin or mate-users-admin from the terminal. Click on the button for changing your full name, change the name to something else and click "OK". You'll see a warning message in the terminal: Liboobs-WARNING **: There was an unknown error communicating with the backends: Launch helper exited with unknown return code 255 No error message dialog will appear though. Also the full name in the GUI will be changed to the name you entered. This is not correct because some error happened in the backends, and the name hasn't been actually changed. You can see that for yourself by simply restarting users-admin or mate-users-admin - it will show the old name then. [Regression Potential] I consider the regression risk to be low here. The patches have been already tested by me and liboobs maintainer in Debian (see the corresponding Debian bug report). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liboobs/+bug/1411584/+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 1401784] Update Released
The verification of the Stable Release Update for xserver-xorg-video- intel 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 regressions. -- 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/1401784 Title: Disable DRI3 Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Utopic: Fix Released Status in xserver-xorg-video-intel source package in Vivid: Fix Released Bug description: [Impact] from the upstream commit: "The external libraries, both in git, and especially shipping already enabled in distributions, are buggy and lead to server crashes and lockups. Caveat emptor." so disable it by default in vivid and utopic. [Test case] grep DRI3 /var/log/Xorg.0.log should not return anything [Regression potential] none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1401784/+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 1400730] Update Released
The verification of the Stable Release Update for libxext 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxext in Ubuntu. https://bugs.launchpad.net/bugs/1400730 Title: libxext fills up .xsession-errors log files Status in libxext package in Ubuntu: Fix Released Status in libxext source package in Utopic: Fix Released Status in libxext source package in Vivid: Fix Released Bug description: libxext can write debug output, and it can write so much of it that it fills up .xsession-errors t be several GB and fill up the hard disk (or the equivalent file with lightdm). error is "_xgeWireToEvent: Unknown extension 148, this should never happen" [TEST CASE] Install Plasma 5 on utopic Use it for a while Notice that ~/.xsession-errors is filling up saying "_xgeWireToEvent: Unknown extension 148, this should never happen" with the new packages this will not happen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxext/+bug/1400730/+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 1040259] Re: FFE: libmessaging-menu transitions for quantal
** Also affects: quassel (Ubuntu) Importance: Undecided Status: New ** Also affects: libdbusmenu-qt (Ubuntu) Importance: Undecided Status: New ** Also affects: kdepim (Ubuntu) Importance: Undecided Status: New ** Also affects: kdenetwork (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1040259 Title: FFE: libmessaging-menu transitions for quantal Status in Gmail Watcher: Triaged Status in Lightread: New Status in Quassel Irc Client: New Status in Skype-wrapper: In Progress Status in “evolution-indicator” package in Ubuntu: Triaged Status in “gm-notify” package in Ubuntu: Triaged Status in “gwibber” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “kdenetwork” package in Ubuntu: New Status in “kdepim” package in Ubuntu: New Status in “libdbusmenu-qt” package in Ubuntu: New Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “liferea” package in Ubuntu: Triaged Status in “pidgin” package in Ubuntu: Confirmed Status in “pidgin-libnotify” package in Ubuntu: Triaged Status in “quassel” package in Ubuntu: New Status in “smuxi” package in Ubuntu: Fix Released Status in “telepathy-indicator” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: Fix Released Status in “unity-mail” package in Ubuntu: Fix Released Status in “xchat-indicator” package in Ubuntu: Fix Released Status in “gm-notify” source package in Quantal: Triaged Status in “gwibber” source package in Quantal: Fix Released Status in “indicator-messages” source package in Quantal: Fix Released Status in “kdenetwork” source package in Quantal: New Status in “kdepim” source package in Quantal: New Status in “libdbusmenu-qt” source package in Quantal: New Status in “libunity-webapps” source package in Quantal: Fix Released Status in “liferea” source package in Quantal: Triaged Status in “pidgin” source package in Quantal: Confirmed Status in “pidgin-libnotify” source package in Quantal: In Progress Status in “quassel” source package in Quantal: New Status in “smuxi” source package in Quantal: Fix Released Status in “telepathy-indicator” source package in Quantal: Fix Released Status in “thunderbird” source package in Quantal: Fix Released Status in “unity-mail” source package in Quantal: Fix Released Status in “xchat-indicator” source package in Quantal: Fix Released Bug description: indicator-messages got updated, introducing a new libmessaging-menu api (deprecating the old libindicate library) which should make application developper's life easier. The indicator work is done and the library is ready and we started porting applications The current stack is being tested in https://launchpad.net/~ubuntu- desktop/+archive/ppa/ It includes - indicator-messages - gwibber - indicator-telepathy - thunderbird (soon, work is being finished) which is what we consider the minimal set for landing the feature for quantal we will add those soon: - pidgin - xchat-indicator - evolution-indicator To manage notifications about this bug go to: https://bugs.launchpad.net/gmailwatcher/+bug/1040259/+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 1057000] Re: [Ubuntu 12.04.1/12.10] nVidia drivers 304.51 prevent autohidden Unity launcher from revealing
nvidia-graphics-drivers-experimental-310 nvidia-settings- experimental-310 are released to quantal-updates for people wanting to try that instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1057000 Title: [Ubuntu 12.04.1/12.10] nVidia drivers 304.51 prevent autohidden Unity launcher from revealing Status in NVIDIA Drivers Ubuntu: Fix Released Status in Unity: Invalid Status in “nvidia-graphics-drivers” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-updates” package in Ubuntu: Triaged Status in “xorg-server” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers” source package in Precise: Fix Released Status in “nvidia-graphics-drivers-updates” source package in Precise: Invalid Status in “xorg-server” source package in Precise: Won't Fix Status in “nvidia-graphics-drivers” source package in Quantal: Fix Released Status in “nvidia-graphics-drivers-updates” source package in Quantal: Triaged Status in “xorg-server” source package in Quantal: Won't Fix Bug description: The bug is as described in the title. Reverting to drivers 304.43 solves the problem. This report is intended primarily for those suffering from this bug and not knowing how to solve it. Today I also reported it to nVidia, but it will take time for them to respond and fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1057000/+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 1067856] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1067856 Title: "Open a new window" quicklist menu entry translations are not loaded Status in WebApps: libunity: Fix Released Status in Ubuntu Translations: Triaged Status in “libunity-webapps” package in Ubuntu: Fix Released Bug description: [Test Case] 1) Login to the desktop using a language other than english 2) launch the amazon app from the launcher 3) after the page loads, right click on the amazon launcher and verify the quick lists are not translated 4) install the unity-webapps-service package from -proposed. 5) logout and log back in. 6) launch the amazon app again 7) after the page loads, right click on the amazon launcher and verify the quick lists are translated [Regression potential] None; previous version simply wasn't binding to the GETTEXT_DOMAIN, this fixes that. [Impact] When shown in the Dash, each webapp icon has got a Unity quicklist with several entries, which are (pending an upload that will implement this) all localized. However, there is one particular quicklist menu entry for all webapps whose translations are not loaded, and thus always appear in English: "Open a new window". See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1067856/+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 1067461] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1067461 Title: Update Amazon affiliates code for webapps runner target url Status in WebApps: libunity: Fix Committed Status in “libunity-webapps” package in Ubuntu: Fix Released Bug description: In the case of Amazon, libunity-webapps runner selects the landing page following a launcher webapp click using geolocation. Each landing page is "decorated" by affiliates code for Amazon if any is available. Those affiliates codes should be extended for es, it, cn and jp. To manage notifications about this bug go to: https://bugs.launchpad.net/libunity-webapps/+bug/1067461/+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] Update Released
The verification of this Stable Release Update 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 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: Fix Released 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 1070771] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1070771 Title: 3.6.1 stable update Status in “gedit” package in Ubuntu: Fix Released Status in “gedit” source package in Quantal: Fix Released Bug description: There is a new bugfix version: === gedit 3.6.1 === New Features and Fixes == - File Browser side panel improvements (Ignacio Casal Quinteiro) - Fix print preview in landscape mode (Adrian Johnson) - Misc bugfixes Impact: The new version fixes some bugs and has updated translations. GNOME has a MRE so the update should qualify for SRU Test Case: Check that gedit keeps working, testing the print preview in lanscape mode should be easy to verify that fix Regression Potential: Limited, watch for the print previews To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1070771/+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 1070629] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1070629 Title: Update epiphany-browser to 3.6.1 Status in “epiphany-browser” package in Ubuntu: In Progress Status in “epiphany-browser” source package in Quantal: Fix Released Bug description: [IMPACT] GNOME bug fix update http://git.gnome.org/browse/epiphany/tree/NEWS?h=gnome-3-6 - Do not replace environment when spawning ephy-profile-migrator (#683538) - Merge the app menu into the gear menu when the system does not support global application menus (#673054) - Add F10 as accel for the gear menu (#673878) - Make sure windows are properly closed when using the 'Quit' option in the app menu (#679844) - Do not automatically download embedded objects (#683635) - Translation updates. [TESTCASE] * This is covered by the GNOME MRE. No explicit test case required, only aging for regression testing. [Regression Potential] * This is shipped by default in the Ubuntu GNOME Remix ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: epiphany-browser 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 Date: Tue Oct 23 20:45:59 2012 MarkForUpload: True SourcePackage: epiphany-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1070629/+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 1078772] Re: SRU : Fix typo in amarok Recommmends
Hello Rohan, or anyone else affected, Accepted into quantal-proposed. The package will build now and be available in a few hours 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 change the bug tag from verification-needed to verification-done. If it does not, 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: amarok (Ubuntu Quantal) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to amarok in Ubuntu. https://bugs.launchpad.net/bugs/1078772 Title: SRU : Fix typo in amarok Recommmends Status in “amarok” package in Ubuntu: Fix Released Status in “amarok” source package in Quantal: Fix Committed Status in “amarok” source package in Raring: Fix Released Bug description: Amarok has a typo in the Recommends field which would cause media- player-info not to be pulled in when installing amarok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1078772/+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 1068565] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1068565 Title: Update to 3.6.1 Status in “gnome-keyring” package in Ubuntu: Fix Released Status in “gnome-keyring” source package in Quantal: Fix Released Bug description: There are some good fixes in 3.6.1 that we should have in Q: Changes in version 3.6.1 are: * Fix regressions with keyring master password changing * Load schema for secret items correctly, prevents storing multiple times for items stored via libsecret * Setup translations properly when daemon starts * Fix memory leak in PKCS#11 module Under the GNOME MRE, we are allowed to assume that the individual bugs have been fixed, so just give gnome-keyring a good workout to regression test it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1068565/+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 1049210] Re: Gnome-shell notification from empathy doesn't contain any text
Domen: What did you do to verify this fix? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-logger in Ubuntu. https://bugs.launchpad.net/bugs/1049210 Title: Gnome-shell notification from empathy doesn't contain any text Status in GNOME Shell: Unknown Status in “telepathy-logger” package in Ubuntu: Fix Released Status in “telepathy-logger” source package in Quantal: Fix Committed Bug description: [IMPACT] * Empathy chat message notification popup is not displayed. * notification in the messagetray is missing message contents/text. This is due to an incorrect introspection annotation, that has been fixed upstream and in debian package telepathy-logger 0.4.0-2. [TESTCASE] 1. setup empathy with an IM account 2. get someone to message you Notice that no popup notifaction appears, additionally the empathy notification in the message tray is missing the text from the message. Apply the fix and repeat step 2 (make sure there are no existing notifications in the tray) Now you will be correctly notified by a popup, and the notification in the message tray will contain the message text. [Regression Potential] I believe the gobject introspection interface for telepathy logger is only used by gnome-shell, so its very unlikely to cause problems with any other packages. === Original Bug Report === Ubuntu 12.10 beta 1 The problem occures with the combination of gnome-shell and empathy but I had to choose only one package... When I receive a message from someone through empathy (connected to google talk) and the window for chatting with that person is not opened yet, the notification trai contains an icon for that person but the text content is missing and empathy's chat window doesn't open but if you open it manually the text is there. After replying in gnome-shell notification window you get all the new messages that the person writes afterwards without any problems but you never get the old messages. How to reproduce: Open empathy chat window (google talk). Say something to someone. When that person replies write him something back in gnome-shell notification window and then close the empathy chat window on desktop (or if the window isn't opened yet just double click on gnome-shell notification window and close empathy window then after replying). When that person replies back you will only get the notification icon without the text. Also the notification window won't pop up from notification tray and empathy chat window won't open. If the person writes something else the notification window will pop up as normal containing the text that that person wrote next (without the text that was written first). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1049210/+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 1064962] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1064962 Title: [SRU] Global menubar items do not work when opening a document directly from nautilus with no LibreOffice instance running Status in BAMF Application Matching Framework: Won't Fix Status in LibreOffice Productivity Suite: Won't Fix Status in The Application Menu: Confirmed Status in “bamf” package in Ubuntu: Confirmed Status in “indicator-appmenu” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Fix Committed Status in “bamf” source package in Quantal: Confirmed Status in “indicator-appmenu” source package in Quantal: Confirmed Status in “libreoffice” source package in Quantal: Fix Released Bug description: [IMPACT] * there is no menu available in some scenarios of opening LibreOffice * makes LibreOffice essentially unusable when opening a docuemnt directly [TESTCASE] * open a existing file from nautilus -> no menu in a unity session [Regression Potential] * changes are to the menu code integration, possible regressions will be there * package has been available for user testing https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-quantaltest-20120601 since 2012-10-26 without any reported regressions * see comment 74 for realworld enduser testing --- pre-SRU description details: 1) Have no instance of LibreOffice running 2) open a document by double-clicking it in nautilus 3) new window has no menu 4) unfocusing/refocusing (e.g. by pressing F7 to bring up the spelling dialog) makes the menu appear WORKAROUND: minimize and restore the LibreOffice window (more permanent workaround, disable the global menu by removing the package "libreoffice-gtk"). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-gtk 1:3.6.2~rc2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 Date: Wed Oct 10 11:48:20 2012 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-09-30 (9 days ago) original description: In writer, none of the menubar items appear to work. Example: * Open new document in Writer * Type some text and highlight it * Try Edit->Cut >> Nothing happens * Try Format->Change chase->UPPERCASE >> Nothing happens! workaround: restart your session after update To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1064962/+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 959084] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to adium-theme-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/959084 Title: empathy-chat consistently uses 9-10 % CPU Status in Ubuntu Adium Theme: Fix Released Status in Chat app, and Telepathy user interface: Unknown Status in “adium-theme-ubuntu” package in Ubuntu: Fix Released Status in “empathy” package in Ubuntu: Invalid Status in “webkit” package in Ubuntu: Invalid Status in “adium-theme-ubuntu” source package in Quantal: Fix Released Status in “empathy” source package in Quantal: Invalid Status in “webkit” source package in Quantal: Invalid Bug description: [Test Case] Verification is simple, open a chat window with someone where the history doesn't fill the chat window and leave it sit idle. While it is open, check the load created by the empathy-chat process. [Regression potential] Low, this really just slows down how aggressive the javascript is in detecting how close it is to the bottom of the window. This may have started since I upgraded my system to 12.04, it was certainly a recent development at around that time. I am using empathy for IRC only, connected to four channels on two servers, though even disabling all accounts does not change this. The empathy-chat process is very consistently at 9% CPU, with spikes at 10% or higher from time to time. I have tested this on mobile broadband, wifi and ethernet. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: empathy 3.3.91-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 09:28:49 2012 ExecutablePath: /usr/lib/empathy/empathy-chatInstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8SourcePackage: empathy UpgradeStatus: Upgraded to precise on 2012-03-12 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adium-theme-ubuntu/+bug/959084/+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 1049210] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to telepathy-logger in Ubuntu. https://bugs.launchpad.net/bugs/1049210 Title: Gnome-shell notification from empathy doesn't contain any text Status in GNOME Shell: Unknown Status in “telepathy-logger” package in Ubuntu: Fix Released Status in “telepathy-logger” source package in Quantal: Fix Released Bug description: [IMPACT] * Empathy chat message notification popup is not displayed. * notification in the messagetray is missing message contents/text. This is due to an incorrect introspection annotation, that has been fixed upstream and in debian package telepathy-logger 0.4.0-2. [TESTCASE] 1. setup empathy with an IM account 2. get someone to message you Notice that no popup notifaction appears, additionally the empathy notification in the message tray is missing the text from the message. Apply the fix and repeat step 2 (make sure there are no existing notifications in the tray) Now you will be correctly notified by a popup, and the notification in the message tray will contain the message text. [Regression Potential] I believe the gobject introspection interface for telepathy logger is only used by gnome-shell, so its very unlikely to cause problems with any other packages. === Original Bug Report === Ubuntu 12.10 beta 1 The problem occures with the combination of gnome-shell and empathy but I had to choose only one package... When I receive a message from someone through empathy (connected to google talk) and the window for chatting with that person is not opened yet, the notification trai contains an icon for that person but the text content is missing and empathy's chat window doesn't open but if you open it manually the text is there. After replying in gnome-shell notification window you get all the new messages that the person writes afterwards without any problems but you never get the old messages. How to reproduce: Open empathy chat window (google talk). Say something to someone. When that person replies write him something back in gnome-shell notification window and then close the empathy chat window on desktop (or if the window isn't opened yet just double click on gnome-shell notification window and close empathy window then after replying). When that person replies back you will only get the notification icon without the text. Also the notification window won't pop up from notification tray and empathy chat window won't open. If the person writes something else the notification window will pop up as normal containing the text that that person wrote next (without the text that was written first). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1049210/+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 1071956] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/1071956 Title: [GNOME Classic+Compiz] Wrong background color for icon of selected window under Ambiance Status in “light-themes” package in Ubuntu: Fix Released Status in “light-themes” source package in Precise: Fix Released Bug description: System: Ubuntu 12.04 LTS with GNOME Classic (using Compiz) The selected window in the window list has a visual bug: The transparent parts of the application icon is filled with the incorrect color (it's lighter than it should be). The left gnome-terminal is selected in the attached screenshot. You can see a lighter stripe above that gnome-terminal icon. [Test Case] 1) sudo apt-get install gnome-panel 2) Close your current session and start Gnome-Classic Session in LightDM. 3) Select Ambiance as theme. 4) Open a gnome-terminal. 5) There should be no lighter stripe above the icon of the selected gnome-terminal window (in the window list). [Regression Potential] The fix can lead to a regression in the visual appearance of the GNOME panel in the Classic session. Other sessions could not be affected because these changes apply to a CSS file only used by gnome-panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1071956/+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 1157678] Re: [ffe] unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it.
I just accepted xserver-xorg-video-intel, but put a britney block in place for it. It looks like a good, but not essential for release fix. If there's no opportunity to copy it in, then it can be an SRU. -- 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/1157678 Title: [ffe] unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it. Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Committed Bug description: [Impact] With updated 13.04 beta, unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it. A screen capture looks normal (not like what the display is showing!). Plugging an external monitor in does not produce any similar problem. [Test Case] 1. On affected hardware, boot with an external monitor connected 2. Unplug the external monitor Expected behavior: Normal screen Actual behavior: Screen corruption [Development Fix] The fix for this issue is a cherrypick of an upstream patch with a minor change to make it apply to raring. (See comment #56) The upstream patch is rather large (~228 lines), but half of that is simple code refactoring (moving some common code into functions, moving some functions earlier in their files so they can be referenced in other routines, etc.) For review purposes, a cleaned up (uncleaned up?) version of the patch is available in comment #59, which shows just the functional changes to the code. [Regression Potential] The patch originates from an upstream change that has not been part of a release yet, but has gone through upstream review and testing. This patch primarily *adds* code, and most of that is cleanup code to clear graphics memory and free pointers, which should be quite safe. However, cleanup code can sometimes expose pre-existing bugs (e.g. freeing invalid pointers that otherwise would have been ignored). We don't expect that to happen, though. A few while loops are added. It does not look like the code could get stuck in those loops, though. Types of symptoms to look for include X server crashes, gpu lockups, and screen corruption, particularly associated with screen initialization, destruction, or resizing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-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: Wed Mar 20 07:45:34 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c1] InstallationDate: Installed on 2013-03-18 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) MachineType: LENOVO 2901CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=fcf8343d-2c1d-4f25-ab52-876891045ee9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET69WW (1.49 ) dmi.board.name: 2901CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET69WW(1.49):bd04/25/2012:svnLENOVO:pn2901CTO:pvrThinkPadT410s:rvnLENOVO:rn2901CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2901CTO dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1 version.xserver-xorg-video-nouveau: xserver
[Desktop-packages] [Bug 1157678] Re: [ffe] unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it.
Now that the package is built in raring-proposed, could someone who is experiencing the problem verify that the update solves the problem (like we would do for an SRU)? -- 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/1157678 Title: [ffe] unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it. Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Committed Bug description: [Impact] With updated 13.04 beta, unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it. A screen capture looks normal (not like what the display is showing!). Plugging an external monitor in does not produce any similar problem. [Test Case] 1. On affected hardware, boot with an external monitor connected 2. Unplug the external monitor Expected behavior: Normal screen Actual behavior: Screen corruption [Development Fix] The fix for this issue is a cherrypick of an upstream patch with a minor change to make it apply to raring. (See comment #56) The upstream patch is rather large (~228 lines), but half of that is simple code refactoring (moving some common code into functions, moving some functions earlier in their files so they can be referenced in other routines, etc.) For review purposes, a cleaned up (uncleaned up?) version of the patch is available in comment #59, which shows just the functional changes to the code. [Regression Potential] The patch originates from an upstream change that has not been part of a release yet, but has gone through upstream review and testing. This patch primarily *adds* code, and most of that is cleanup code to clear graphics memory and free pointers, which should be quite safe. However, cleanup code can sometimes expose pre-existing bugs (e.g. freeing invalid pointers that otherwise would have been ignored). We don't expect that to happen, though. A few while loops are added. It does not look like the code could get stuck in those loops, though. Types of symptoms to look for include X server crashes, gpu lockups, and screen corruption, particularly associated with screen initialization, destruction, or resizing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-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: Wed Mar 20 07:45:34 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c1] InstallationDate: Installed on 2013-03-18 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) MachineType: LENOVO 2901CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=fcf8343d-2c1d-4f25-ab52-876891045ee9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET69WW (1.49 ) dmi.board.name: 2901CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET69WW(1.49):bd04/25/2012:svnLENOVO:pn2901CTO:pvrThinkPadT410s:rvnLENOVO:rn2901CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2901CTO dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu
Re: [Desktop-packages] [Bug 1157678] Re: [ffe] unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it.
Thanks for verifying. I've unblocked it so it will go into raring. -- 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/1157678 Title: [ffe] unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it. Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Committed Bug description: [Impact] With updated 13.04 beta, unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it. A screen capture looks normal (not like what the display is showing!). Plugging an external monitor in does not produce any similar problem. [Test Case] 1. On affected hardware, boot with an external monitor connected 2. Unplug the external monitor Expected behavior: Normal screen Actual behavior: Screen corruption [Development Fix] The fix for this issue is a cherrypick of an upstream patch with a minor change to make it apply to raring. (See comment #56) The upstream patch is rather large (~228 lines), but half of that is simple code refactoring (moving some common code into functions, moving some functions earlier in their files so they can be referenced in other routines, etc.) For review purposes, a cleaned up (uncleaned up?) version of the patch is available in comment #59, which shows just the functional changes to the code. [Regression Potential] The patch originates from an upstream change that has not been part of a release yet, but has gone through upstream review and testing. This patch primarily *adds* code, and most of that is cleanup code to clear graphics memory and free pointers, which should be quite safe. However, cleanup code can sometimes expose pre-existing bugs (e.g. freeing invalid pointers that otherwise would have been ignored). We don't expect that to happen, though. A few while loops are added. It does not look like the code could get stuck in those loops, though. Types of symptoms to look for include X server crashes, gpu lockups, and screen corruption, particularly associated with screen initialization, destruction, or resizing. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-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: Wed Mar 20 07:45:34 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.8, 3.8.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21c1] InstallationDate: Installed on 2013-03-18 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130318) MachineType: LENOVO 2901CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=fcf8343d-2c1d-4f25-ab52-876891045ee9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET69WW (1.49 ) dmi.board.name: 2901CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET69WW(1.49):bd04/25/2012:svnLENOVO:pn2901CTO:pvrThinkPadT410s:rvnLENOVO:rn2901CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2901CTO dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.42-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1 xserver.bootTime: Wed Mar 20 07:41:30 2013 xserver.configfile: default xserver.logfile: /va
[Desktop-packages] [Bug 1171048] [NEW] Segfault during Broadcom STA wireless driver install in Kubuntu live session
Public bug reported: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
** Attachment added: "live session dmesg.0" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+attachment/3649511/+files/dmesg.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
** Attachment added: "live session jockey log" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+attachment/3649509/+files/jockey.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
** Attachment added: "live session dmesg" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+attachment/3649510/+files/dmesg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
Traceback is at 00:58:12. ** Attachment added: "live session kern.log" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+attachment/3649513/+files/kern.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Status in “jockey” source package in Raring: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
** Attachment added: "live session syslog" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+attachment/3649514/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Status in “jockey” source package in Raring: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
Since fixing this would only be useful on the installation media, it'd be nice to get this looked into before release. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Status in “jockey” source package in Raring: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
When trying to install in the live session, I got automatically switched to a vt showing this. The same text shows up in the kern log and syslog I previously attached. ** Attachment added: "Screen shot" https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+attachment/3649515/+files/20130420_210041.jpg ** Also affects: jockey (Ubuntu Raring) Importance: Undecided Status: New ** Changed in: jockey (Ubuntu Raring) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Status in “jockey” source package in Raring: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
** Changed in: jockey (Ubuntu Raring) Milestone: None => ubuntu-13.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “jockey” package in Ubuntu: New Status in “jockey” source package in Raring: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1171048/+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 1171048] Re: Segfault during Broadcom STA wireless driver install in Kubuntu live session
I followed through the steps on the attached jockey log and everything is fine up to the unbind/rebind. What is the command for that? Now the fun part is since I was stepping through this manually, so I could see where things were at a given time. Once I installed bcmwl- kernel-source and it's DKMS build/install had completed, I had wifi. I'm glad to continue troubleshooting the specific issue with the unbind/rebind, but for jockey, could it just be dropped for this driver? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1171048 Title: Segfault during Broadcom STA wireless driver install in Kubuntu live session Status in “bcmwl” package in Ubuntu: New Status in “jockey” package in Ubuntu: New Status in “bcmwl” source package in Raring: New Status in “jockey” source package in Raring: New Bug description: As the subject says, install of the wifi driver at least partly fails. It looks like it's installing and wifi becomes selectable as an option in network manager, but it's not working. It installs and works fine when installed during a regular install. The automatically attached files will be from the installed system. I'll attach files from /var/log of the live session separately. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: jockey-kde 0.9.7-0ubuntu12 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CurrentDmesg: [ 13.665319] init: plymouth-stop pre-start process (1175) terminated with status 1 [ 89.757527] ERROR @wl_cfg80211_get_station : Could not get rate (-1) [ 89.757543] ERROR @wl_cfg80211_get_station : Could not get rssi (-1) Date: Sat Apr 20 21:45:24 2013 InstallationDate: Installed on 2013-04-20 (0 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release i386 (20130420) MachineType: Dell Inc. Inspiron 1011 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=bcb28f3f-1ac9-4ebc-9d7f-a1ddf2f6d5ac ro SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: CN0Y53 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A00 dmi.modalias: dmi:bvnDellInc.:bvrA00:bd03/20/2009:svnDellInc.:pnInspiron1011:pvrA00:rvnDellInc.:rnCN0Y53:rvrA00:cvnDellInc.:ct8:cvrA00: dmi.product.name: Inspiron 1011 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1171048/+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 1156670] Re: Cannot chose language with home on nfs export
Gunnar: No, that's not actually sufficient. We need verification done with the packages actually going in the archive, not a predecessor package from a PPA. ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1156670 Title: Cannot chose language with home on nfs export Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Committed Bug description: [Impact] Accountsservice incorrectly prevents you from changing the user language if HOME is on NFS. [Test Case] Can be reproduced anytime on Precise when logged in as a user whose HOME is on NFS. [Regression Potential] Minimal. [Original description] There is no possibility to choose language in an interactive way in Ubuntu 12.04, neither with XFCE4 nor with Gnome, neither with lightdm nor with GDM3 when home dirs aren't on local drive. Error message: gdm-session-worker[2009]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved That's a bummer, I have users from all over the world, they need to be able to choose their own language. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9.4 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Mon Mar 18 16:21:13 2013 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1156670/+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 1083605] Re: env not changed in acc. with ~/.pam_environment if /home is on nfs
Verification needs to be done on the packages in proposed, not from a PPA. ** Tags removed: verification-done ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1083605 Title: env not changed in acc. with ~/.pam_environment if /home is on nfs Status in “accountsservice” package in Ubuntu: Fix Released Status in “pam” package in Ubuntu: Incomplete Status in “accountsservice” source package in Precise: Fix Committed Status in “pam” source package in Precise: Incomplete Status in “accountsservice” source package in Quantal: Won't Fix Status in “pam” source package in Quantal: Won't Fix Bug description: When using localization setup from the login screen, the choice doesn't work because of a permission error, if the user's home directory is mounted with nfs. The problem happens because this is done by root, usually not able to write over nfs shares. The problem disappears if home directories are exported with no_root_squash option. So, something is making access as root, instead as user. I'm using Precise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1083605/+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 997470] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/997470 Title: apport-gpu-error-intel.py keep crashing for 4-5 times on every reboot Status in “xdiagnose” package in Ubuntu: Won't Fix Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xdiagnose” source package in Precise: Fix Released Status in “xserver-xorg-video-intel” source package in Precise: Fix Released Status in “xdiagnose” source package in Quantal: Fix Released Status in “xserver-xorg-video-intel” source package in Quantal: Fix Committed Status in “xdiagnose” source package in Raring: Won't Fix Status in “xserver-xorg-video-intel” source package in Raring: Fix Released Bug description: [Impact] Apport is disabled in the release itself, so this hook should not be getting triggered at all. However, for some users it does. This wouldn't be a big deal, except it also gets triggered in cases where no GPU lockup was experienced (aka False GPU lockups - bug #983640), which gives poor user experience. [Development Fix] Since we want any and all GPU lockup reports in the development release, we leave things as they are, and focus on getting a targeted fix to just #983640. [Stable Fix] Since we don't intend for the GPU lockup hook to be run at all, whether or not Apport is enabled, in the stable release we forcefully disable the udev hook entirely. If someone does specifically want this enabled, they'd need to also manually enable apport and so forth, in addition to re-enabling this udev rule. But I think it'd probably be easier for these people to just manually collect the gpu dump and dmesg directly, so don't expect anyone to need the script. A duplicate udev rule calling the gpu lockup apport hook has been installed by xserver-xorg-video-intel. Since the hook has been moved to xdiagnose, this extra rule is redundant and should be dropped from the package. Indeed, I believe this second hook is the cause of the false gpu lockup reports (the hook in xdiagnose was already fixed to not file these.) [Test Case] The issues have been strange corner case problems that seem to be highly hardware-specific, and not synthetically reproducible. 1. To verify the apport hook has been properly changed, do: grep apport-gpu-error /lib/udev/rules.d/* Expected Behavior: A single, commented-out line is printed Broken Behavior: Multiple lines printed, or the line is not commented out. 2. On affected hardware, boot into a regular user session normally Expected Behavior: No apport popups about GPU lockups Broken Behavior: Apport pops up dialog about a GPU lockup bug, when nothing of the sort had actually happened. [Regression Potential] None really, as this is just disabling functionality we don't need enabled in the release. The class of regressions to watch for with this would be udev-related problems, or odd apport behaviors. But I don't think anything untoward is remotely likely to happen. [Original Report] I installed ubuntu 12.04 recently on a DELL inspiron 1440 notebook. I think the chipset is GM45 something. I am quite fresh on linux operation system. I do not know how could I solve this problem. It seems not only me have this problem. I install ubuntu 12.04 64bit and windows 7 64bit on my notebook. Every time I enter the ubuntu, I will notify me this problem for 4-5 times. It say "sorry, Ubuntu 12.04 has experienced an internal error". the detail are as follows: ExecutablePath /usr/share/apport/apport-gpu-error-intel.py Package xserver-xorg-xideo-intel2:2.17.0-1ubuntu4 ProblemType Crash Title [gm45] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 ApportVerion 2.0.1-0ubuntu7 Architecture amd64 . ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xdiagnose 2.5 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 139.311070] init: plymouth-stop pre-start process (3041) terminated with status 1 Date: Thu M
[Desktop-packages] [Bug 997470] Re: apport-gpu-error-intel.py keep crashing for 4-5 times on every reboot
Set back to verification needed for quantal as it doesn't seem to have been verified there. ** Tags removed: verification-done ** Tags added: verification-needed -- 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/997470 Title: apport-gpu-error-intel.py keep crashing for 4-5 times on every reboot Status in “xdiagnose” package in Ubuntu: Won't Fix Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xdiagnose” source package in Precise: Fix Released Status in “xserver-xorg-video-intel” source package in Precise: Fix Released Status in “xdiagnose” source package in Quantal: Fix Released Status in “xserver-xorg-video-intel” source package in Quantal: Fix Committed Status in “xdiagnose” source package in Raring: Won't Fix Status in “xserver-xorg-video-intel” source package in Raring: Fix Released Bug description: [Impact] Apport is disabled in the release itself, so this hook should not be getting triggered at all. However, for some users it does. This wouldn't be a big deal, except it also gets triggered in cases where no GPU lockup was experienced (aka False GPU lockups - bug #983640), which gives poor user experience. [Development Fix] Since we want any and all GPU lockup reports in the development release, we leave things as they are, and focus on getting a targeted fix to just #983640. [Stable Fix] Since we don't intend for the GPU lockup hook to be run at all, whether or not Apport is enabled, in the stable release we forcefully disable the udev hook entirely. If someone does specifically want this enabled, they'd need to also manually enable apport and so forth, in addition to re-enabling this udev rule. But I think it'd probably be easier for these people to just manually collect the gpu dump and dmesg directly, so don't expect anyone to need the script. A duplicate udev rule calling the gpu lockup apport hook has been installed by xserver-xorg-video-intel. Since the hook has been moved to xdiagnose, this extra rule is redundant and should be dropped from the package. Indeed, I believe this second hook is the cause of the false gpu lockup reports (the hook in xdiagnose was already fixed to not file these.) [Test Case] The issues have been strange corner case problems that seem to be highly hardware-specific, and not synthetically reproducible. 1. To verify the apport hook has been properly changed, do: grep apport-gpu-error /lib/udev/rules.d/* Expected Behavior: A single, commented-out line is printed Broken Behavior: Multiple lines printed, or the line is not commented out. 2. On affected hardware, boot into a regular user session normally Expected Behavior: No apport popups about GPU lockups Broken Behavior: Apport pops up dialog about a GPU lockup bug, when nothing of the sort had actually happened. [Regression Potential] None really, as this is just disabling functionality we don't need enabled in the release. The class of regressions to watch for with this would be udev-related problems, or odd apport behaviors. But I don't think anything untoward is remotely likely to happen. [Original Report] I installed ubuntu 12.04 recently on a DELL inspiron 1440 notebook. I think the chipset is GM45 something. I am quite fresh on linux operation system. I do not know how could I solve this problem. It seems not only me have this problem. I install ubuntu 12.04 64bit and windows 7 64bit on my notebook. Every time I enter the ubuntu, I will notify me this problem for 4-5 times. It say "sorry, Ubuntu 12.04 has experienced an internal error". the detail are as follows: ExecutablePath /usr/share/apport/apport-gpu-error-intel.py Package xserver-xorg-xideo-intel2:2.17.0-1ubuntu4 ProblemType Crash Title [gm45] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 ApportVerion 2.0.1-0ubuntu7 Architecture amd64 . ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xdiagnose 2.5 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 139.311070] init: plymouth-stop pre-start process (3041) terminated with status 1 Date: Thu May 10 14:30:41 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02cf] S
Re: [Desktop-packages] [Bug 997470] Re: apport-gpu-error-intel.py keep crashing for 4-5 times on every reboot
Thanks for clarifying. Released. -- 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/997470 Title: apport-gpu-error-intel.py keep crashing for 4-5 times on every reboot Status in “xdiagnose” package in Ubuntu: Won't Fix Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Status in “xdiagnose” source package in Precise: Fix Released Status in “xserver-xorg-video-intel” source package in Precise: Fix Released Status in “xdiagnose” source package in Quantal: Fix Released Status in “xserver-xorg-video-intel” source package in Quantal: Fix Released Status in “xdiagnose” source package in Raring: Won't Fix Status in “xserver-xorg-video-intel” source package in Raring: Fix Released Bug description: [Impact] Apport is disabled in the release itself, so this hook should not be getting triggered at all. However, for some users it does. This wouldn't be a big deal, except it also gets triggered in cases where no GPU lockup was experienced (aka False GPU lockups - bug #983640), which gives poor user experience. [Development Fix] Since we want any and all GPU lockup reports in the development release, we leave things as they are, and focus on getting a targeted fix to just #983640. [Stable Fix] Since we don't intend for the GPU lockup hook to be run at all, whether or not Apport is enabled, in the stable release we forcefully disable the udev hook entirely. If someone does specifically want this enabled, they'd need to also manually enable apport and so forth, in addition to re-enabling this udev rule. But I think it'd probably be easier for these people to just manually collect the gpu dump and dmesg directly, so don't expect anyone to need the script. A duplicate udev rule calling the gpu lockup apport hook has been installed by xserver-xorg-video-intel. Since the hook has been moved to xdiagnose, this extra rule is redundant and should be dropped from the package. Indeed, I believe this second hook is the cause of the false gpu lockup reports (the hook in xdiagnose was already fixed to not file these.) [Test Case] The issues have been strange corner case problems that seem to be highly hardware-specific, and not synthetically reproducible. 1. To verify the apport hook has been properly changed, do: grep apport-gpu-error /lib/udev/rules.d/* Expected Behavior: A single, commented-out line is printed Broken Behavior: Multiple lines printed, or the line is not commented out. 2. On affected hardware, boot into a regular user session normally Expected Behavior: No apport popups about GPU lockups Broken Behavior: Apport pops up dialog about a GPU lockup bug, when nothing of the sort had actually happened. [Regression Potential] None really, as this is just disabling functionality we don't need enabled in the release. The class of regressions to watch for with this would be udev-related problems, or odd apport behaviors. But I don't think anything untoward is remotely likely to happen. [Original Report] I installed ubuntu 12.04 recently on a DELL inspiron 1440 notebook. I think the chipset is GM45 something. I am quite fresh on linux operation system. I do not know how could I solve this problem. It seems not only me have this problem. I install ubuntu 12.04 64bit and windows 7 64bit on my notebook. Every time I enter the ubuntu, I will notify me this problem for 4-5 times. It say "sorry, Ubuntu 12.04 has experienced an internal error". the detail are as follows: ExecutablePath /usr/share/apport/apport-gpu-error-intel.py Package xserver-xorg-xideo-intel2:2.17.0-1ubuntu4 ProblemType Crash Title [gm45] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0010 ApportVerion 2.0.1-0ubuntu7 Architecture amd64 . ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xdiagnose 2.5 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CurrentDmesg: [ 139.311070] init: plymouth-stop pre-start process (3041) terminated with status 1 Date: Thu May 10 14:30:41 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02cf] Subsystem: Dell Device [1028:02cf] InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineTy
[Desktop-packages] [Bug 1108056] Re: fetching URLs freezes pidgin
Robert Hooker: Please add the required elements for an SRU bug. I'm going to accept it into -proposed, but leave it there so it can be verified early. http://wiki.ubuntu.com/StableReleaseUpdates -- 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/1108056 Title: fetching URLs freezes pidgin Status in Pidgin: Unknown Status in “glib2.0” package in Ubuntu: Confirmed Status in “pidgin” package in Ubuntu: Confirmed Bug description: after about two weeks with Pidgin freezing on two different laptops, I made a brand new clean profile and this is what i get $ pidgin -nm (16:52:37) prefs: Reading /home/fernando/.purple/prefs.xml (16:52:37) prefs: Reading /etc/purple/prefs.xml (16:52:37) prefs: /pidgin/browsers/manual_command changed, scheduling save. (16:52:37) prefs: removing pref /pidgin/browsers/command (16:52:37) dbus: okkk (16:52:37) plugins: probing /usr/lib/pidgin/ticker.so (16:52:37) plugins: probing /usr/lib/pidgin/switchspell.so (16:52:37) plugins: probing /usr/lib/pidgin/mystatusbox.so (16:52:37) plugins: probing /usr/lib/pidgin/gestures.so (16:52:37) plugins: probing /usr/lib/pidgin/convcolors.so (16:52:37) plugins: probing /usr/lib/pidgin/listlog.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppconsole.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp_format.so (16:52:37) plugins: probing /usr/lib/pidgin/cap.so (16:52:37) plugins: probing /usr/lib/pidgin/history.so (16:52:37) plugins: probing /usr/lib/pidgin/xmppdisco.so (16:52:37) plugins: probing /usr/lib/pidgin/vvconfig.so (16:52:37) plugins: probing /usr/lib/pidgin/markerline.so (16:52:37) plugins: probing /usr/lib/pidgin/libpidgin_pp.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-twitter.so (16:52:37) plugins: probing /usr/lib/pidgin/irssi.so (16:52:37) plugins: probing /usr/lib/pidgin/pidginrc.so (16:52:37) plugins: probing /usr/lib/pidgin/themeedit.so (16:52:37) plugins: probing /usr/lib/pidgin/enhancedhist.so (16:52:37) plugins: probing /usr/lib/pidgin/notify.so (16:52:37) plugins: probing /usr/lib/pidgin/expand.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-otr.so (16:52:37) plugins: probing /usr/lib/pidgin/musicmessaging.so (16:52:37) plugins: probing /usr/lib/pidgin/icon_override.so (16:52:37) plugins: probing /usr/lib/pidgin/timelog.so (16:52:37) plugins: probing /usr/lib/pidgin/extplacement.so (16:52:37) plugins: probing /usr/lib/pidgin/iconaway.so (16:52:37) plugins: probing /usr/lib/pidgin/difftopic.so (16:52:37) plugins: probing /usr/lib/pidgin/plonkers.so (16:52:37) plugins: probing /usr/lib/pidgin/xchat-chats.so (16:52:37) plugins: probing /usr/lib/pidgin/nicksaid.so (16:52:37) plugins: probing /usr/lib/pidgin/sepandtab.so (16:52:37) plugins: probing /usr/lib/pidgin/pidgin-schedule.so (16:52:37) plugins: probing /usr/lib/pidgin/album.so (16:52:37) plugins: probing /usr/lib/pidgin/lastseen.so (16:52:37) plugins: probing /usr/lib/pidgin/gtkbuddynote.so (16:52:37) plugins: probing /usr/lib/pidgin/blistops.so (16:52:37) plugins: probing /usr/lib/pidgin/gRIM.so (16:52:37) plugins: probing /usr/lib/pidgin/spellchk.so (16:52:37) plugins: probing /usr/lib/pidgin/convbadger.so (16:52:37) plugins: probing /usr/lib/pidgin/sendbutton.so (16:52:37) plugins: probing /usr/lib/pidgin/infopane.so (16:52:37) plugins: probing /usr/lib/pidgin/timestamp.so (16:52:37) plugins: probing /usr/lib/purple-2/groupmsg.so (16:52:37) plugins: probing /usr/lib/purple-2/idle.so (16:52:37) plugins: probing /usr/lib/purple-2/liboldtwitter.so (16:52:37) plugins: probing /usr/lib/purple-2/buddynote.so (16:52:37) plugins: probing /usr/lib/purple-2/libirc.so (16:52:37) plugins: probing /usr/lib/purple-2/libjabber.so (16:52:37) plugins: /usr/lib/purple-2/libjabber.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro? (16:52:37) plugins: probing /usr/lib/purple-2/libxmpp.so (16:52:37) plugins: probing /usr/lib/purple-2/libgg.so (16:52:37) plugins: probing /usr/lib/purple-2/listhandler.so (16:52:37) plugins: probing /usr/lib/purple-2/libbonjour.so (16:52:37) plugins: probing /usr/lib/purple-2/google.so (16:52:37) plugins: probing /usr/lib/purple-2/capsnot.so (16:52:37) plugins: probing /usr/lib/purple-2/libicq.so (16:52:37) plugins: probing /usr/lib/purple-2/dice.so (16:52:37) plugins: probing /usr/lib/purple-2/dewysiwygification.so (16:52:37) plugins: probing /usr/lib/purple-2/simfix.so (16:52:37) plugins: probing /usr/lib/purple-2/libstatusnet.so (16:52:37) twitterim: plugin_init (16:52:37) twitterim: plugin = 0x7f658884bd30 (16:52:37) plugins: probing /usr/lib/purple-2/oldlogger.so (16:52:37) plugins: probing /usr/lib/purple-2/autoprofile.so (16:52:37) autoprofile: general: Initializing AutoProfi
[Desktop-packages] [Bug 1067565] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1067565 Title: Update to 3.7.0.94. Status in “gnome-orca” package in Ubuntu: In Progress Status in “gnome-orca” source package in Quantal: Fix Released Bug description: [Impact] This update is covered by the MicroReleaseException for GNOME. [Test case] ? GNOME upstream has released a new version of orca. For GNOME 3.6, the version is 3.6.1, but Orca upstrea have maintained a python 3 branch of orca at the same time during 3.6 development, hense the 3.7.0.x version number, since 3.8 is likely going to move to python 3. Please consider this update for quantal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/1067565/+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 875435] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/875435 Title: iBus indicator does not show on the panel Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Release Notes for Ubuntu: Invalid Status in “ibus” package in Ubuntu: Invalid Status in “im-switch” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Invalid Status in “ibus” source package in Oneiric: Invalid Status in “im-switch” source package in Oneiric: Fix Released Status in “ibus” source package in Precise: Invalid Status in “im-switch” source package in Precise: Fix Committed Status in “ibus” source package in Quantal: Invalid Status in “im-switch” source package in Quantal: Fix Committed Bug description: IBus icon does not show at Unity panel in some environments, we are discovering the real culprit now. [Impact] Impacts all users of CJK languages or any other user depending on IBUS for character composition. This is a rather large user base and the prority of this bug has been updated as to reflect the impact on users. The missing indicator on session start disables users from having a visual cue of the current state of the ibus support for their session, as well as the current ibus input method in use, which may change during the course of a session. Furthermore, since the underlying issue appears to be related to ibus-daemon startup, this may render ibus input unusable until the daemon is restarted. [Release note for P] see https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/875435/comments/23 [Development Fix] (TBD) [Stable Fix] (TBD) [Workaround] We have some workarounds, but they are not root fix. The root cause is not identified. A) gsettings approach: see comment 8, comment 23 B) exec: ibus-daemon -rxd RESTARTing ibus-daemon can fix the one-time solution. If user met this problem, executing `ibus-daemon -rxd`. This command restart ibus-daemon, and fix for current login sessions. But that is not root fix, if user restart the session (or reboot system), problem are back-in. Notes: If user exec the Ibus icon on Dash, that is not functional. Because ibus-daemon are already running by /etc/X11/Xsession.d/80im- switch. B') .desktop approach (with user initiated ibus restart) Workaround is as discussed in this bug report, to apply the debdiff provided by Ikuya Awashiro. This change modifies the parameters passed to ibus-daemon's .desktop file, that used in a Unity Dash. That provide more better B) approach. the session manager on a new session; and makes ibus-daemon replace any previously running ibus daemon for the user. [Test Case] 1) Start a Unity session with a CJK language (Chinese, Japanese, Korean, Vietnamese) or any other language depending on ibus to compose characters. 2) Verify that the ibus indicator is shown in the Unity panel, and that ibus input can be used. The indicator should be visible in all cases. Since this bug is akin to a race condition, it may need a few startups to trigger the bug. [Regression Potential] Minimal, this only affects the ibus daemon on session startup in the way that it gets spawned by the session manager: it will replace any other running ibus daemon at the time, though none should be running before ibus-daemon gets spawned regardless. A different (or the same) ibus daemon can still be started manually. Possible issues could include the ibus daemon failing to start altogether with the session, in which case the ibus input methods would be unavailable, and can be started manually by users (using a terminal). [Background] (guess by Ikuya AWASHIRO, Fumihito YOSHIDA) In Ubuntu/Unity environments, ibus-daemon are initiated by /etc/X11/Xsession.d/80im-switch scripts. That invoked at early state on system start-up, so too early invoking bring up the race between Unity-panel and indicator-ibus. If indicator-ibus are start-up at too fast phase, the Unity-panel are not started, that cause "no icon" running. -- iBus still run but doesn't show off in the panel, in every way. The only thing to make it right is do ibus-deamon -rxd ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: ibus 1.3.99.20110419-1ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic
[Desktop-packages] [Bug 1069207] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1069207 Title: Alacarte ignores XDG_MENU_PREFIX Status in Alacarte Menu Editor: Fix Released Status in “alacarte” package in Ubuntu: Fix Released Status in “alacarte” source package in Quantal: Fix Released Status in “alacarte” source package in Raring: Fix Released Bug description: [Impact] * Inability to edit a menu when its filename is "$XDG_MENU_PREFIX"applications.menu instead of only applications.menu. [Test case] * Start your Xubuntu session. * Open Alacarte (Settings > Main menu). * Try to unhide a desktop file, e.g. check GParted in System. * Close Alacarte, check your menu, nothing changed. * Install alacarte from -proposed * Repeat the steps above. * The changes are now applied, e.g. GParted should now appear in the System submenu. [Regression Potential] * On systems where XDG_MENU_PREFIX is set but applications.menu is used, alacarte won't write to the correct menu file (this case shouldn't happen naturally, even gnome-menus supports this envvar). On a fresh install of XUbuntu 64bit I am unable to add items to the main menu. All the buttons seem to work but when you hit "New Item" or "New Menu", type in your settins and click "create" nothing happens. Also attempted to disable some menu items and while the menu editor shows the changes there are no changes to the actual menu, even after restarting X. Let me know if you need anything else, Westin Shafer ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xubuntu-default-settings 12.10.7 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Sat Oct 20 15:42:51 2012 InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) PackageArchitecture: all SourcePackage: xubuntu-default-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/alacarte/+bug/1069207/+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 1067554] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1067554 Title: Update to 2.6.1. Status in “at-spi2-atk” package in Ubuntu: In Progress Status in “at-spi2-core” package in Ubuntu: Fix Released Status in “at-spi2-atk” source package in Quantal: In Progress Status in “at-spi2-core” source package in Quantal: Fix Released Bug description: GNOME upstream has released new bugfix releases of the at-spi2 stack, version 2.6.1, affecting at-spi2-atk and at-spi2-core. Please consider these updates for quantal. This update shoudl be considered under the GNOME micro release exception. Test case: Make sure that at-spi2-core v2.6.1 continues to work as expected. Regression potential: The chances of regression are extremely low, as this release is a bugfix release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1067554/+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 853137] Re: The page 'gkr-keyring' was not found in the document 'ghelpseahorse'.
--- Releasing seahorse --- Proposed: 3.2.2-0ubuntu2.1 Release: 3.2.2-0ubuntu2 Copied to precise-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/853137 Title: The page 'gkr-keyring' was not found in the document 'ghelpseahorse'. Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in Seahorse: New Status in “seahorse” package in Ubuntu: Fix Released Status in “seahorse” source package in Precise: Fix Released Status in “seahorse” source package in Quantal: Fix Released Bug description: Impact: One of the "help" button is leading to an error page Testcase: precise: seahorse > (Passsword and Keyss) > [tab] Passwords > Passwors: default> [right-click] Properties > "Passwords:default" > (dialog window "Passwords:default") > Keyring > Name:=default, Created:=(empty) > Help > (Help) > "PageNotFound": > The page 'gkr-keyring' was not found in the document 'ghelpseahorse'. quantal: right click on a keyring in the left side of the main ui, properties, help -> error Regression Potential: the button can keep not working... To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/853137/+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 1017125] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1017125 Title: [SRU quantal] boost::unordered_multimap<>::erase(iterator, iterator) broken in boost1.49 Status in Boost C++ Libraries: New Status in LibreOffice Productivity Suite: Won't Fix Status in “boost-mpi-source1.49” package in Ubuntu: Fix Released Status in “boost1.49” package in Ubuntu: Fix Released Status in “gcc-4.7” package in Ubuntu: Invalid Status in “libreoffice” package in Ubuntu: Fix Released Status in “boost-mpi-source1.49” source package in Quantal: Fix Released Status in “boost1.49” source package in Quantal: Fix Released Status in “gcc-4.7” source package in Quantal: Invalid Status in “libreoffice” source package in Quantal: New Status in “boost1.49” package in Debian: New Status in “boost1.49” package in Fedora: Unknown Status in “boost1.49” package in Gentoo Linux: New Bug description: [Impact] * possible root cause of bug 1067907 and essentially ever other client using boost::unordered * bug 1067907 alone has ~50 reported crashes per day [Test Case] * compile and run the attached testcase [Regression Potential] * miminal patch provided as a patch by upstream -- has been fixed in later boost versions [Other Info] These was the original symptoms in LibreOffice causing the bug hunt -- it has been evaded (without fixing the root cause in boost up to now) by not using the broken boost method in LibreOffice with http://cgit.freedesktop.org/libreoffice/core/commit/?id=861e55bd889d9f5f5b37724b3615e9355e2d5c15&g=libreoffice-3-6 : subsequentcheck sometimes crashes in xmloff.Impress.XMLContentImporter::com::sun::star::document::XImporter Testcode: http://opengrok.libreoffice.org/xref/core/qadevOOo/tests/java/ifc/document/_XImporter.java against service: http://opengrok.libreoffice.org/xref/core/qadevOOo/tests/java/mod/_xmloff/Impress/XMLContentImporter.java steps to reproduce: cd xmloff echo "-o xmloff.Impress.XMLContentImporter" > qa/unoapi/xmloff.sce echo > qa/unoapi/knownissues.xcl << EOF xmloff.Impress.XMLContentImporter::com::sun::star::lang::XInitialization xmloff.Impress.XMLContentImporter::com::sun::star::document::XFilter xmloff.Impress.XMLContentImporter::com::sun::star::container::XNamed EOF R=T; while test "$R" = "T"; do make subsequentcheck || R=F; done expected result: test passes without a crash actual result: crash To manage notifications about this bug go to: https://bugs.launchpad.net/boost/+bug/1017125/+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 1017125] Re: [SRU quantal] boost::unordered_multimap<>::erase(iterator, iterator) broken in boost1.49
SRU released to updates. -- 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/1017125 Title: [SRU quantal] boost::unordered_multimap<>::erase(iterator, iterator) broken in boost1.49 Status in Boost C++ Libraries: New Status in LibreOffice Productivity Suite: Won't Fix Status in “boost-mpi-source1.49” package in Ubuntu: Fix Released Status in “boost1.49” package in Ubuntu: Fix Released Status in “gcc-4.7” package in Ubuntu: Invalid Status in “libreoffice” package in Ubuntu: Fix Released Status in “boost-mpi-source1.49” source package in Quantal: Fix Released Status in “boost1.49” source package in Quantal: Fix Released Status in “gcc-4.7” source package in Quantal: Invalid Status in “libreoffice” source package in Quantal: New Status in “boost1.49” package in Debian: New Status in “boost1.49” package in Fedora: Unknown Status in “boost1.49” package in Gentoo Linux: New Bug description: [Impact] * possible root cause of bug 1067907 and essentially ever other client using boost::unordered * bug 1067907 alone has ~50 reported crashes per day [Test Case] * compile and run the attached testcase [Regression Potential] * miminal patch provided as a patch by upstream -- has been fixed in later boost versions [Other Info] These was the original symptoms in LibreOffice causing the bug hunt -- it has been evaded (without fixing the root cause in boost up to now) by not using the broken boost method in LibreOffice with http://cgit.freedesktop.org/libreoffice/core/commit/?id=861e55bd889d9f5f5b37724b3615e9355e2d5c15&g=libreoffice-3-6 : subsequentcheck sometimes crashes in xmloff.Impress.XMLContentImporter::com::sun::star::document::XImporter Testcode: http://opengrok.libreoffice.org/xref/core/qadevOOo/tests/java/ifc/document/_XImporter.java against service: http://opengrok.libreoffice.org/xref/core/qadevOOo/tests/java/mod/_xmloff/Impress/XMLContentImporter.java steps to reproduce: cd xmloff echo "-o xmloff.Impress.XMLContentImporter" > qa/unoapi/xmloff.sce echo > qa/unoapi/knownissues.xcl << EOF xmloff.Impress.XMLContentImporter::com::sun::star::lang::XInitialization xmloff.Impress.XMLContentImporter::com::sun::star::document::XFilter xmloff.Impress.XMLContentImporter::com::sun::star::container::XNamed EOF R=T; while test "$R" = "T"; do make subsequentcheck || R=F; done expected result: test passes without a crash actual result: crash To manage notifications about this bug go to: https://bugs.launchpad.net/boost/+bug/1017125/+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 771661] Re: Allow .xsession-errors to be a symlink
Correcting source package for kdm. ** Package changed: kdebase (Ubuntu) => kde-workspace (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/771661 Title: Allow .xsession-errors to be a symlink Status in GDM: The Gnome Display Manager: Fix Released Status in Lucid Backports: Fix Released Status in “gdm” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: New Status in “gdm” source package in Lucid: Fix Released Bug description: Binary package hint: gdm Bug 60448 discusses the problem about ~/.xsession-errors growing unbearably large when there are buggy programs spamming it. One remedy is to allow ~/.xsession-errors to be a symlink to e. g. /dev/null or a local file, so that you can at least avoid network contention if ~ is on NFS. scm sent a first patch for this (https://launchpadlibrarian.net/70203386/gdm-session-worker.c.diff). This should be cleaned up to use g_file_test() and reported upstream. SRU TEST CASE: * Remove ~/.xsession-errors and ~/.xsession-errors.old * ln -s /tmp/xe ~/.xsession-errors * Reboot and log back in. -> Current behavior: the ~/.xsession-errors symlink gets rotated to ~/.xsession-errors.old, and a new ~/.xsession-errors is created as a regular file. -> Desired behaviour: ~/.xsession-errors remains a symlink, and the target file /tmp/xe is truncated for the new session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/771661/+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 956438] Re: qjackctl unable to stop jackd2
It should be fixed released when it's fixed in the development release (which it is). Tasks for specific releases shouldn't be marked fixed released until it's in updates for that release. Fixing. ** Changed in: jackd2 (Ubuntu) Status: New => Fix Released ** Also affects: jackd2 (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: jackd2 (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: jackd2 (Ubuntu) Milestone: precise-updates => None -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/956438 Title: qjackctl unable to stop jackd2 Status in “jackd2” package in Ubuntu: Fix Released Status in “jackd2” source package in Precise: New Status in “jackd2” source package in Quantal: New Bug description: [Impact] This bug makes jackdbus often freeze when commanding it to stop. It is not possible to kill it from the system monitor, so users often reboot in order to be able start jackdbus again. [Test Case] - Start qjackctl - Select an audio device in: Setup/Interface - Click "Start" and "Stop" a few times to make jackdbus freeze. [Regression Potential] No apparent one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/956438/+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 1066372] Re: X crash when doing nothing in particular
OK. This still happens. Is there a way I can get that information? ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Incomplete => New -- 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/1066372 Title: X crash when doing nothing in particular Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: Twice today X has completely crashed on me (I ended up back at lightdm ready to login again). Once while I was away from the computer and once while I was using it. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Sat Oct 13 15:10:40 2012 EcryptfsInUse: Yes InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330) ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to quantal on 2012-10-06 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1066372/+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 1026678] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gst-plugins-base0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1026678 Title: Playback stops when going from an ogg to a flac Status in GStreamer Plugins (Base): Fix Released Status in “gst-plugins-base0.10” package in Ubuntu: Fix Released Status in “gst-plugins-base0.10” source package in Quantal: Fix Released Status in “gst-plugins-base0.10” package in Debian: Fix Released Bug description: Impact: the audio playing with stop sometimes on ogg to flac transitions Test Case: Test in rhythmbox or try the upstream bug case: "- play ogg vorbis file - seek near to the end - wait for about-to-finish - set new uri property (flac file) - playbin2 hangs when the transition should happen - a position query returns always the same value - state is still playing Testcase: http://pastie.org/pastes/4283968/text (edit the uris..)" Regression potential: limited, check that playback and transitions from files to files works as it should See upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=680252 This is probably related to, but was NOT fixed along with, https://bugs.launchpad.net/ubuntu/+source/gst-plugins- base0.10/+bug/921071 Steps to reproduce: * Deactivate crossfade in Rhythmbox * Make a playlist from two files, first one an ogg, second one a flac * Start playing this playlist, skip towards the end of the first (ogg) piece if you like * Playback stops after reaching the end of the ogg file, Rhythmbox displays the title of the second file but the timer does not move over the 0:00 mark I've attached the output of GST_DEBUG=:5 rhythmbox --debug &> debug.log while performing the above steps. To manage notifications about this bug go to: https://bugs.launchpad.net/gst-plugins-base/+bug/1026678/+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 1054495] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1054495 Title: AirPrint doesn't work on iOS 6 device Status in “cups” package in Ubuntu: Fix Released Status in “cups” source package in Precise: Fix Released Bug description: After iOS 6 update on my iPad2 device Airprin doesn't work on my ubuntu 12,04 "precise" machine. On my iPhone with iOS 5.1.1 still works fine. I dont know if any attachement is required for this issue. Sorry... [IMPACT] Everyone with iOS 6 on his iPhone/iPad/iPod Touch, independent whether iOS 6 was installed from the beginning or by an update, is not able to print from his iOS device any more, as there are changes in the AirPrint implementation. Due to Apple's updates this affects Apple hardware of the last three years. [TESTCASE] Print from an Appler iOS device with iOS 6 or newer. The print queues of your shared printers on your Precise machine do not appear. After applying the fixed package the queues will appear and printing will work. [Regression Potential] The changes are very simple (see attached debdiff) and so there are no regressions expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1054495/+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] Update Released
The verification of this Stable Release Update 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 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 Released Status in “light-themes” source package in Quantal: Invalid Status in “overlay-scrollbar” source package in Quantal: Fix Released 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 1020162] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1020162 Title: some characters not displayed in a PDF file Status in Poppler: Fix Released Status in “poppler” package in Ubuntu: Fix Released Status in “poppler” source package in Precise: Fix Released Status in “poppler” source package in Quantal: In Progress Bug description: Impact: Some part of the text is not displayed in some pdf documents Test Case: open https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1020162/+attachment/3210969/+files/Bug.pdf in evince, see if the text is fully displayed Regression potential: Check that other pdfs still render fine To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1020162/+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 1086868] [NEW] No global menu in Plasma (KDE) session in Raring
Public bug reported: Under a Plasma (KDE) session in raring there is no global menu (plasma- widget-menubar). This does work in 12.10, so it's a regression. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1086868 Title: No global menu in Plasma (KDE) session in Raring Status in “libreoffice” package in Ubuntu: New Bug description: Under a Plasma (KDE) session in raring there is no global menu (plasma-widget-menubar). This does work in 12.10, so it's a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086868/+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 1086868] Re: No global menu in Plasma (KDE) session in Raring
It was not installed, but after installing it (and restarting the system, just to be sure), the global menu is still not there. -- 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/1086868 Title: No global menu in Plasma (KDE) session in Raring Status in “libreoffice” package in Ubuntu: New Bug description: Under a Plasma (KDE) session in raring there is no global menu (plasma-widget-menubar). This does work in 12.10, so it's a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086868/+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 1086868] Re: No global menu in Plasma (KDE) session in Raring
Actually, I take it back. It doesn't work on 12.10 either. -- 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/1086868 Title: No global menu in Plasma (KDE) session in Raring Status in “libreoffice” package in Ubuntu: New Bug description: Under a Plasma (KDE) session in raring there is no global menu (plasma-widget-menubar). This does work in 12.10, so it's a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086868/+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 1086868] Re: No global menu in Plasma (KDE) session in Raring
Gimp manages to work with the plasma menubar. In theory anything that's using the Unity menubar stuff should just work since it's done via DBus. Is there some way we can separate out the menubar aspects of the gtk plugin from the rest? -- 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/1086868 Title: No global menu in Plasma (KDE) session in Raring Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Under a Plasma (KDE) session in raring there is no global menu (plasma-widget-menubar). This does work in 12.10, so it's a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086868/+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
Re: [Desktop-packages] [Bug 1086868] Re: No global menu in Plasma (KDE) session in Raring
OK. Thanks. -- 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/1086868 Title: No global menu in Plasma (KDE) session in Raring Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Under a Plasma (KDE) session in raring there is no global menu (plasma-widget-menubar). This does work in 12.10, so it's a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1086868/+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 1041369] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1041369 Title: System Settings -> Details doesn't match lsb_release -a Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: Fix Released Bug description: Impact: I'm on 12.04.1, but System Settings -> Details shows 12.04. This is confusing for users. Test Case: Open system settings, details, look at the version displayed Regression potential: That's an image updated, it could looks wrong or break dialog alignments To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1041369/+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 986692] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/986692 Title: [soundnua] Unmutting sound effects using the slider doesn't work Status in GNOME Control Center: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Fix Committed Status in OEM Priority Project quantal series: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: Fix Released Status in “gnome-control-center” source package in Quantal: Triaged Bug description: [IMPACT] When users unckeck the "Mute" checkbox on "Alert volume" you reset the slider and the checkbox is automatically unchecked. However, the "Alert volume" is not actually unmuted. This is a significat design issue for obvious reasons, but also has the side effect that if the the user does not know that he's not getting audio alerts (s)he may miss some important work. When [TESTCASE] After poking with it a bit, I think I just isolated it: it only happens when instead of unckecking the "Mute" checkbox on "Alert volume" you reset the slider and the checkbox is automatically unchecked. Visually the end result is the same (non-zero volume leve and unckecked box) but how you get there has different effect. By the way the "Output volume" slider doesn't have this problem, only the "Alert volume". [Regression Potential] Small. The code has been merged upstream and has been tested in both upstream and ubuntu. The diff is only one additional line of code. [Original Report] Sound--> Tab "Sound Effects" After bringing alert volume to the minimum none of the selected alert was working. Everything else is ok. Sound in other places is perfect. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.3.92-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Sat Apr 21 21:10:21 2012 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/986692/+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 416825] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/416825 Title: gnome-keyring passwd should be changed on system password change Status in GNOME Control Center: Fix Released Status in GNOME keyring services: Invalid Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-control-center” source package in Precise: Fix Released Status in Baltix GNU/Linux: New Bug description: Impact: Leads to have login and desktop passwords out of sync which triggers confusing password prompts for users (need to enter their old login password) Test Case: 1. Install a fresh Ubuntu 2. Log in and connect to a password protected WLAN (and thus save a password in the Gnome keyring) 3. Log in again and change the password of the user using System > User info > Change password 4. Log in again. Now the Gnome keyring complains that it was unable to open. The computer is not connected to the protected WLAN and the user is asked both the Gnome keyring password and the WLAN password. Regression potention: Check that the keyring password is correctly updated Better description and fresh follow-up in report https://bugs.launchpad.net/ubuntu/precise/+source/gnome-control- center/+bug/911426 Original description: The default Gnome keyring manger in Ubuntu 9.04 (Seahorse 26.6.1?) asks the user to unlock his/her keyring in order to save the Ubuntu One token _if_ the user has changed his/her password after initial installation/login of Ubuntu 9.04. The actual problem seems to be that the default password for the keyring is initially and automatically set to the same password the user uses to log in into Ubuntu (GDM). The user does not know anything about the keyring, because it works automatically (and that's fine). However if the user ever changes his/her password for Ubuntu (Linux username) the password protecting the keyring is not changed. So later if the user needs to unlock the keyring, he/she needs to rembember what was his/her password when he/she started using Ubuntu in the beginning. The solution would be to set some kind of flag in the Gnome keyring (Sea Horse?) that the password has been taken automatically from the username/login. So if ever the user does change his username/login password, the Gnome keyring would know to automatically also change the password that protects the keyring. This bug does not effect new users of Ubuntu, but most likely everybody who has been using Ubuntu for a longer time (and thus has changed their login password at some time, which brakes the keyring automatics). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/416825/+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 1066046] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to webkit in Ubuntu. https://bugs.launchpad.net/bugs/1066046 Title: pvr driver crashes when ubiquity-slideshow starts Status in Webkit Direct Port: New Status in “livecd-rootfs” package in Ubuntu: Fix Released Status in “pvr-omap4” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Invalid Status in “webkit” package in Ubuntu: Fix Released Status in “livecd-rootfs” source package in Quantal: Fix Released Status in “pvr-omap4” source package in Quantal: Confirmed Status in “ubiquity” source package in Quantal: Invalid Status in “webkit” source package in Quantal: Fix Released Bug description: [ Description ] I think this happened on any page which uses JS. An upstream bug (linked from here) in the JS JIT results in segfaults. [ Test case ] On an armhf machine, try /usr/lib/webkitgtk-3.0-0/libexec/GtkLauncher "http://news.bbc.co.uk/"; it should briefly open a window and then segfault before the fix, and successfully load the webpage after. Also try the slideshow that prompted this bug report in the first place bzr branch lp:ubiquity-slideshow-ubuntu cd ubiquity-slideshow-ubuntu ./Slideshow.py --path=build/ubuntu --controls again you should see a segfault (coming from webkit) before, and a lovely slideshow after. [ Regression Potential ] This might make webkit a bit slower on armel/hf. It shouldn't be too bad, but perhaps exercise a bit by browsing around in epiphany-browser to see. [ Original Description ] On panda, I'm hitting this crash on the 20121012.2 image for quantal. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: ubiquity 2.12.10 ProcVersionSignature: Ubuntu 3.5.0-213.20-omap4 3.5.5 Uname: Linux 3.5.0-213-omap4 armv7l ApportVersion: 2.6.1-0ubuntu3 Architecture: armhf CasperVersion: 1.328 Date: Fri Oct 12 11:26:13 2012 InstallCmdLine: fixrtc quiet splash -- boot=casper only-ubiquity LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Release armhf+omap4 (20121012.2) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/1066046/+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 1088393] Re: New bug fix releases: 9.1.7, 8.4.15, 8.3.22
Hello Martin, or anyone else affected, Accepted into quantal-proposed. The package will build now and be available in a few hours 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 change the bug tag from verification-needed to verification-done. If it does not, 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: postgresql-9.1 (Ubuntu Quantal) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1088393 Title: New bug fix releases: 9.1.7, 8.4.15, 8.3.22 Status in “postgresql-8.3” package in Ubuntu: Invalid Status in “postgresql-8.4” package in Ubuntu: Invalid Status in “postgresql-9.1” package in Ubuntu: Fix Released Status in “postgresql-8.4” source package in Lucid: In Progress Status in “postgresql-9.1” source package in Oneiric: In Progress Status in “postgresql-8.4” source package in Precise: In Progress Status in “postgresql-9.1” source package in Precise: In Progress Status in “postgresql-9.1” source package in Quantal: Fix Committed Status in “postgresql-9.1” source package in Raring: Fix Released Status in “postgresql-8.3” source package in Hardy: In Progress Bug description: PostgreSQL announced new microreleases some days ago: http://www.postgresql.org/about/news/1430/ As per the standing SRU microrelease exception I would like to update our stable releases with the new versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1088393/+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 1088393] Please test proposed package
Hello Martin, or anyone else affected, Accepted into quantal-proposed. The package will build now and be available in a few hours 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 change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1088393 Title: New bug fix releases: 9.1.7, 8.4.15, 8.3.22 Status in “postgresql-8.3” package in Ubuntu: Invalid Status in “postgresql-8.4” package in Ubuntu: Invalid Status in “postgresql-9.1” package in Ubuntu: Fix Released Status in “postgresql-8.4” source package in Lucid: In Progress Status in “postgresql-9.1” source package in Oneiric: In Progress Status in “postgresql-8.4” source package in Precise: In Progress Status in “postgresql-9.1” source package in Precise: In Progress Status in “postgresql-9.1” source package in Quantal: Fix Committed Status in “postgresql-9.1” source package in Raring: Fix Released Status in “postgresql-8.3” source package in Hardy: In Progress Bug description: PostgreSQL announced new microreleases some days ago: http://www.postgresql.org/about/news/1430/ As per the standing SRU microrelease exception I would like to update our stable releases with the new versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1088393/+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 1088393] Please test proposed package
Hello Martin, or anyone else affected, Accepted into quantal-proposed. The package will build now and be available in a few hours 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 change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1088393 Title: New bug fix releases: 9.1.7, 8.4.15, 8.3.22 Status in “postgresql-8.3” package in Ubuntu: Invalid Status in “postgresql-8.4” package in Ubuntu: Invalid Status in “postgresql-9.1” package in Ubuntu: Fix Released Status in “postgresql-8.4” source package in Lucid: In Progress Status in “postgresql-9.1” source package in Oneiric: In Progress Status in “postgresql-8.4” source package in Precise: In Progress Status in “postgresql-9.1” source package in Precise: In Progress Status in “postgresql-9.1” source package in Quantal: Fix Committed Status in “postgresql-9.1” source package in Raring: Fix Released Status in “postgresql-8.3” source package in Hardy: In Progress Bug description: PostgreSQL announced new microreleases some days ago: http://www.postgresql.org/about/news/1430/ As per the standing SRU microrelease exception I would like to update our stable releases with the new versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1088393/+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 1088393] Please test proposed package
Hello Martin, or anyone else affected, Accepted into quantal-proposed. The package will build now and be available in a few hours 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 change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to postgresql-9.1 in Ubuntu. https://bugs.launchpad.net/bugs/1088393 Title: New bug fix releases: 9.1.7, 8.4.15, 8.3.22 Status in “postgresql-8.3” package in Ubuntu: Invalid Status in “postgresql-8.4” package in Ubuntu: Invalid Status in “postgresql-9.1” package in Ubuntu: Fix Released Status in “postgresql-8.4” source package in Lucid: In Progress Status in “postgresql-9.1” source package in Oneiric: In Progress Status in “postgresql-8.4” source package in Precise: In Progress Status in “postgresql-9.1” source package in Precise: In Progress Status in “postgresql-9.1” source package in Quantal: Fix Committed Status in “postgresql-9.1” source package in Raring: Fix Released Status in “postgresql-8.3” source package in Hardy: In Progress Bug description: PostgreSQL announced new microreleases some days ago: http://www.postgresql.org/about/news/1430/ As per the standing SRU microrelease exception I would like to update our stable releases with the new versions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/1088393/+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 1058672] Re: Can't add my Facebook account
Please file a new bug for the follow on issue (after checking that there isn't one already). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1058672 Title: Can't add my Facebook account Status in Gwibber: Fix Released Status in “gwibber” package in Ubuntu: Invalid Status in “gwibber” source package in Precise: Fix Released Bug description: Steps to reproduce: 1. Open gwibber 2. Open the accounts window 3. Select and add new Facebook account 4. Authorize using password What should happen: Facebook account is added to the accounts list What happens: Message appears: "Success" Ubuntu version: 12.04.1 LTS Gwibber version: 3.4.2 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gwibber 3.4.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sat Sep 29 10:37:49 2012 ExecutablePath: /usr/bin/gwibber InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64+mac (20120823.1) SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/1058672/+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 1058672] Update Released
The verification of this Stable Release Update 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 Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1058672 Title: Can't add my Facebook account Status in Gwibber: Fix Released Status in “gwibber” package in Ubuntu: Invalid Status in “gwibber” source package in Precise: Fix Released Bug description: Steps to reproduce: 1. Open gwibber 2. Open the accounts window 3. Select and add new Facebook account 4. Authorize using password What should happen: Facebook account is added to the accounts list What happens: Message appears: "Success" Ubuntu version: 12.04.1 LTS Gwibber version: 3.4.2 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gwibber 3.4.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 Date: Sat Sep 29 10:37:49 2012 ExecutablePath: /usr/bin/gwibber InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64+mac (20120823.1) SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/1058672/+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 1319338] Re: Default boost v1.54 has broken asio while available 1.55 is fixed
** Package changed: boost-defaults (Ubuntu) => boost1.54 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to boost-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1319338 Title: Default boost v1.54 has broken asio while available 1.55 is fixed Status in Boost C++ Libraries: Fix Released Status in “boost1.54” package in Ubuntu: Fix Released Status in “boost1.54” source package in Trusty: In Progress Bug description: [Test Case] 1) g++ chat_client.cpp -std=gnu++11 -lboost_system -lpthread -o chat_client You will need the header chat I will attach in the following comment in order to make it to compile. Bug in current boost Trusty libraries, while trying to connect to non existing server. * Bug: ./chat_client localhost 2423424 Success * Expected: ./chat_client localhost 2423424 Connection refused Original Description Release: 14.04 LTS Version: 1.54.0.1ubuntu1 Expected: Depend on working version of boost Happened: Depends on boost 1.54 Here is a bug that was fixed in boost 7 months ago: https://svn.boost.org/trac/boost/ticket/8795 Due to that, working with boost/asio seems impossible. The bug is still present in boost1.54 but fixed in boost1.55. Therefore I consider it a bug to use version 1.54 as default, as other libraries' dev-packages depend on boost-default and hence cannot be installed together with libboost1.55-dev without being rebuild. Of course, other possibilities would be to ask upstream if version 1.54 could be patched or add this patch to boost1.54. But there might be more benefits in boost1.55 and as both versions are not perfect I see no reason to stick with the older one. To manage notifications about this bug go to: https://bugs.launchpad.net/boost/+bug/1319338/+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 1311697] Update Released
The verification of the Stable Release Update for hplip 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1311697 Title: HP Officejet Pro K550 should use hpijs by default Status in “hplip” package in Ubuntu: Fix Released Status in “hplip” source package in Trusty: Fix Released Bug description: When an HP Officejet Pro K550 is connected, by default CUPS picks hpcups as a driver. Unfortunately, hpcups is broken for this printer, and it has been for a long time. https://bugs.launchpad.net/hplip/+bug/981473 It was first broken in 11.04 and has been broken since. It has been reported since 2011 and no progress has been made on the bug report. This printer is also considered to be "End of Support" by the HPLIP project, and it is likely no resources will ever be committed to fix the real bug: http://hplipopensource.com/hplip-web/models/officejet/officejet_pro_k550.html "The HP product has reached the end of support life, meaning the HPLIP solution is considered “As-is”. No further HPLIP code changes will be implemented by HP. While monitoring of Launchpad posts by HP personnel will continue, follow-up by HP personnel on these products will be extremely limited. Community members are encouraged to assist others with issues on these printers." The very simple workaround is to pick hpijs instead of hpcups. This should be done by default, as it is very hard to find this bug report googling around (I thought I had a broken printer, and only after several hours spent debugging, wasting ink and paper did I find the bug report). It doesn't help that this is not a linux-only issue, as there are many people on windows having this issue so googling gets filled with bogus windows info. Thank you. [Impact] Users of the HP Officejet Pro K550 are not able to print with the automatic printer setup in Ubuntu. [Test Case] Plug an HP Officejet Pro K550 to the USB and wait for a print queue getting auto-generated. If you have an HP Officejet Pro K550 on the network, open system-config-printer, click on "new Printer", and select the HP Officejet Pro K550 under the printers discovered in the network. Follow the steps of the wizard to complete the setup. With the current version of HPLIP you will get a non-working queue with the hpcups driver, due to a bug in the driver which HP does not fix any more as the printer is too old. To get it working with the proposed fix, after installing it, remove your queue(s) for the HP Officejet Pro K550 and create a new queue for it. Now the queue will use the hpijs driver which makes this printer correctly working. [Regression Potential] Very low, as there is nothing more done than removing the hpcups support for the HP Officejet Pro K550. All other printers should work exactly as before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1311697/+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 1327205] Update Released
The verification of the Stable Release Update for gnome-sudoku 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1327205 Title: Doesn't use correct translations domain Status in GNOME Sudoku: Confirmed Status in “gnome-sudoku” package in Ubuntu: Fix Released Status in “gnome-sudoku” source package in Trusty: Fix Released Bug description: * Impact the UI displays mostly in english * Test case run gnome-sudoku under a non english locale * Regression potential look at the UI strings, they should be translated To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-sudoku/+bug/1327205/+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 1316243] Update Released
The verification of the Stable Release Update for libreoffice 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 regressions. -- 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/1316243 Title: [SRU] Prevent DoS via OOXML Status in “libreoffice” package in Ubuntu: Fix Released Status in “libreoffice” source package in Precise: Fix Released Bug description: LibreOffice 3.5.x allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted element in an OOXML document file. SRU data: [Impact] * DoS/application termination upon opening crafted file [Test Case] * none [Regression Potential] * patch affects only OOXML filters for Writer * change is in all upstream LibreOffice releases since 3.6.7/4.0.4, so regression potential is low * patch has been considered fine by the security team [Other Info] * none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1316243/+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 1308515] Update Released
The verification of the Stable Release Update for xorg-server-lts-saucy 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1308515 Title: black screen when enabling rotation on a gpu screen Status in HWE Next Project: Triaged Status in OEM Priority Project: In Progress Status in X.Org X server: New Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server-lts-saucy” package in Ubuntu: Invalid Status in “xorg-server-lts-saucy” source package in Precise: Fix Released Status in “xorg-server” source package in Saucy: Fix Committed Status in “xorg-server” source package in Trusty: Fix Released Bug description: Running with the proprietary nvidia drivers in an optimus config works, but enabling reflection or rotation on the intel screen causes a black screen to appear. [Impact] * Causes a black screen if rotation or reflection is enabled. [Test Case] * Run xrandr --output SOMEOUTPUT --rotation left - Expected: Screen should rotate, or the call should fail. - Bad behavior: Succeeds, but causes a black screen. [Regression Potential] * The affected codepaths have reflection and rotation disabled for gpu screens. Another fix could be fixing reflection/rotation, but that will be more involved and likely require driver fixes. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1308515/+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 1280743] Update Released
The verification of the Stable Release Update for xorg-server-lts-saucy 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1280743 Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Saucy: Fix Committed Bug description: 1) Ubuntu Trusty Tahr 14.04 2) nvidia-prime 0.5.5 3) after installing and restarting the system the above error apeared. In this moment I don't see any other issues but I will report if something else is appearing. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-15ubuntu3) .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu4 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 Feb 16 11:48:18 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-8-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-8-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04ca] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04ca] InstallationDate: Installed on 2014-02-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140215) MachineType: Dell Inc. Inspiron N5110 ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=d4b2ed66-3f0a-415c-b5d3-b252d06d0bc4 ro quiet splash Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: RRCrtcDetachScanoutPixmap () ?? () ?? () FreeClientResources () FreeAllResources () Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/22/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0HVRTT dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd03/22/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0HVRTT:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1280743/+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 1277014] Update Released
The verification of the Stable Release Update for xorg-server-lts-saucy 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1277014 Title: Xorg assert failure: X: ../../dix/dispatch.c:3920: DetachUnboundGPU: Assertion `slave->isGPU' failed. Status in “xorg-server” package in Ubuntu: Fix Released Status in “xorg-server” source package in Saucy: Fix Committed Bug description: This error occurred when I started my notebook without connecting to power source. This probably happened because I'm using the beta driver from nvidia optimus. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AssertionMessage: X: ../../dix/dispatch.c:3920: DetachUnboundGPU: Assertion `slave->isGPU' failed. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 6 08:46:47 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-6-generic, x86_64: installed bbswitch, 0.7, 3.13.0-7-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-6-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-7-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0d1] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev ff) (prog-if ff) InstallationDate: Installed on 2014-01-28 (8 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140128) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550P5C/550P7C ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed root=UUID=a3adce6a-3b61-48e0-82d6-ac3ec5a24dcb ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __assert_fail_base (fmt=0x7f18ee23cbe0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f18f075ad57 "slave->isGPU", file=file@entry=0x7f18f075ad22 "../../dix/dispatch.c", line=line@entry=3920, function=function@entry=0x7f18f075ade0 "DetachUnboundGPU") at assert.c:92 __GI___assert_fail (assertion=0x7f18f075ad57 "slave->isGPU", file=0x7f18f075ad22 "../../dix/dispatch.c", line=3920, function=0x7f18f075ade0 "DetachUnboundGPU") at assert.c:101 DetachUnboundGPU () ?? () ProcRRSetProviderOutputSource () Title: Xorg assert failure: X: ../../dix/dispatch.c:3920: DetachUnboundGPU: Assertion `slave->isGPU' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ABI.016.130917.dg dmi.board.asset.tag: No Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ABI.016.130917.dg:bd09/17/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn550P5C/550P7C:pvrP05ABI:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 550P5C/550P7C dmi.product.version: P05ABI dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-vid
[Desktop-packages] [Bug 1200277] Update Released
The verification of the Stable Release Update for libreoffice 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 regressions. -- 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/1200277 Title: [LibreOffice] - libreoffice-writer.desktop when drag/drop to desktop, 100% broken. Status in Desktop panel for GNOME: Invalid Status in “libreoffice” package in Ubuntu: Fix Released Status in “libreoffice” source package in Precise: Fix Released Bug description: [Impact] Attempting to drag and drop within Unity (to create a desktop shortcut) creates a broken link. [Test Case] 1. Login to gnome fallback session http://askubuntu.com/questions/58172/how-to-revert-to-gnome-classic-desktop 2. Ensure nautilus is used for managing desktop http://askubuntu.com/questions/43246/how-to-configure-gnome-3-to-show-icons-on-desktop 2. Drag and drop libreoffice (writer) icon to desktop Actual Results: Broken Shortcut ( dangling symlink ) Expected Results: Shortcut to be created Alternatively, $ file /usr/share/applications/libreoffice-writer.desktop /usr/share/applications/libreoffice-writer.desktop: symbolic link to `/usr/lib/libreoffice/share/xdg/writer.desktop' [Regression Potential] none [Other Info] patch attached to copy the .desktop file, rather than create a symlink as seen with other distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1200277/+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 1242678] Update Released
The verification of the Stable Release Update for libspectre 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 regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1242678 Title: evince cannot render some EPS files Status in Evince document viewer: New Status in GS-GPL - GPL Ghostscript: Unknown Status in libspectre: Confirmed Status in “evince” package in Ubuntu: Triaged Status in “libspectre” package in Ubuntu: Fix Released Status in “evince” source package in Trusty: Triaged Status in “libspectre” source package in Trusty: Fix Released Bug description: I upgraded to Ubuntu Saucy, evince cannot render EPS files generated by gnuplot. (Just show an empty page.) [how to reproduce] 1. Generate an EPS file using gnuplot by executing the following command. $ gnuplot -e "set terminal postscript; set output 'test.eps'; plot x;" 2. Open the file "test.eps" just created. $ evince "test.eps" The following are what evince writes to the terminal. (evince:24176): EvinceDocument-CRITICAL **: ev_document_get_n_pages: assertion 'EV_IS_DOCUMENT (document)' failed (evince:24176): Gtk-WARNING **: drawing failure for widget `EvView': invalid matrix (not invertible) (evince:24176): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface: assertion 'width > 0 && height > 0' failed (evince:24176): Gdk-CRITICAL **: gdk_pixbuf_get_from_surface: assertion 'width > 0 && height > 0' failed 3. Then evince just shows an empty (white) page. === If i rotate 90 or -90 degree by pressing Ctrl+Left or Ctrl+Right key, evince can show this file correctly. === Okular, GIMP, inkscape and gs can show this EPS file. (may be rotated 90 degree, however) [Impact] With the default viewer for PostrScript and EPS files, many files do not display and produce errors/warnings. Users usually do not know that they can visualize these files by rotating the page and rotated it is also not in a very useful orientation. [Test Case] Display the attached EPS file with evince or follow the steps under "how to reproduce" above. Rotate the page via Ctrl+Left or Ctrl+Right and the image is only visible for two of the four orientations. Withe the proposed package the problem get solved. The image is visible in all the four orientations. [Regression Potential] Low, as tested with various files and reviewed by several upstream developers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: evince 3.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 21 21:23:15 2013 InstallationDate: Installed on 2013-09-07 (44 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: evince UpgradeStatus: Upgraded to saucy on 2013-10-04 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1242678/+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 1253009] Re: [FFe] Please sync latest upstream release (0.9x) from Debian unstable - Pitivi developers recommends to use 0.92 or later
Seems well tested and a significant update to get in. Approved. Get it done quickly though and make sure someone from Studio is subscribed to bugs. ** Changed in: pitivi (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pitivi in Ubuntu. https://bugs.launchpad.net/bugs/1253009 Title: [FFe] Please sync latest upstream release (0.9x) from Debian unstable - Pitivi developers recommends to use 0.92 or later Status in “pitivi” package in Ubuntu: Triaged Status in “pitivi” package in Baltix: Triaged Bug description: Ubuntu Trusty still has old and outdated Pitivi version - 0.15, while Pitivi developers recommends to use 0.92 or later, see download page on http://pitivi.org : Various Linux distributions provide Pitivi in their repositories, but the version provided may be too old. For an optimal experience, make sure you are using Pitivi 0.92 Please sync latest upstream Pitivi release (0.9x) from Debian experimental - AFAIK we have enough time until 14.04 import freeze to find if latest Pitivi release series is good enough for including into LTS release. Pitivi Wiki also contains info, that 0.15 release is lower quality than 0.92: That said, one month after 0.91, with the feedback we have received so far, we are pretty confident that the new release series is of much higher quality than the 0.15 series and older. See http://wiki.pitivi.org/wiki/0.93 and http://wiki.pitivi.org/wiki/0.92 Addendum/Mirv: pitivi 0.15 end user experience as it is currently on Ubuntu makes most people to back away from it - it requires specific settings to not crash or hang, for example (I've found webm container to usually work, but the last time I tried that didn't work either which may be some bitrotting happening) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pitivi/+bug/1253009/+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
Re: [Desktop-packages] [Bug 1305307] Re: FFe for pam-kwallet integration
lightdm changes should be ack'ed by upstream before upload (as disucssed on IRC). -- 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/1305307 Title: FFe for pam-kwallet integration Status in “kde-workspace” package in Ubuntu: New Status in “kubuntu-meta” package in Ubuntu: New Status in “lightdm” package in Ubuntu: New Status in “pam-kwallet” package in Ubuntu: New Bug description: pam-kwallet enables unlocking of kwallet's secret data storage without having to enter a password on session start. To get things rolling we'll need to ship a new version of pam-kwallet (that unlike the present version actually works), add a trivial change to kde-workspace to hand the startkde envrionment over to the helper, and last but not least actually add the pam-kwallet helper to the lightdm pam configs. Including pam-kwallet will bring a significantly improved user experience, even if a bit on a short notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1305307/+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 1305307] Re: FFe for pam-kwallet integration
It's in Ubuntu too. ** Changed in: pam-kwallet (Ubuntu) Status: New => Fix Committed ** Changed in: pam-kwallet (Ubuntu) Importance: Undecided => High ** Changed in: kubuntu-meta (Ubuntu) Importance: Undecided => High ** Changed in: kde-workspace (Ubuntu) Importance: Undecided => High ** Changed in: kde-workspace (Ubuntu) Assignee: (unassigned) => Harald Sitter (apachelogger) ** Changed in: kubuntu-meta (Ubuntu) Assignee: (unassigned) => Harald Sitter (apachelogger) ** Changed in: kde-workspace (Ubuntu) Milestone: None => ubuntu-14.04 ** Changed in: kubuntu-meta (Ubuntu) Milestone: None => ubuntu-14.04 -- 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/1305307 Title: FFe for pam-kwallet integration Status in “kde-workspace” package in Ubuntu: New Status in “kubuntu-meta” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Fix Committed Status in “pam-kwallet” package in Ubuntu: Fix Committed Bug description: pam-kwallet enables unlocking of kwallet's secret data storage without having to enter a password on session start. To get things rolling we'll need to ship a new version of pam-kwallet (that unlike the present version actually works), add a trivial change to kde-workspace to hand the startkde envrionment over to the helper, and last but not least actually add the pam-kwallet helper to the lightdm pam configs. Including pam-kwallet will bring a significantly improved user experience, even if a bit on a short notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1305307/+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 1305307] Re: FFe for pam-kwallet integration
** Changed in: lightdm (Ubuntu) Assignee: (unassigned) => Harald Sitter (apachelogger) ** Changed in: pam-kwallet (Ubuntu) Assignee: (unassigned) => Harald Sitter (apachelogger) ** Changed in: lightdm (Ubuntu) Importance: Undecided => High ** Changed in: lightdm (Ubuntu) Milestone: None => ubuntu-14.04 ** Changed in: pam-kwallet (Ubuntu) Milestone: None => ubuntu-14.04 -- 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/1305307 Title: FFe for pam-kwallet integration Status in “kde-workspace” package in Ubuntu: New Status in “kubuntu-meta” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Fix Committed Status in “pam-kwallet” package in Ubuntu: Fix Committed Bug description: pam-kwallet enables unlocking of kwallet's secret data storage without having to enter a password on session start. To get things rolling we'll need to ship a new version of pam-kwallet (that unlike the present version actually works), add a trivial change to kde-workspace to hand the startkde envrionment over to the helper, and last but not least actually add the pam-kwallet helper to the lightdm pam configs. Including pam-kwallet will bring a significantly improved user experience, even if a bit on a short notice. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/1305307/+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 1310158] Re: package libxml2 2.7.8.dfsg-5.1ubuntu4.4 [modified: usr/share/doc/libxml2/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: libxml2:amd64 2.7.8.dfsg-5.1
The current version in 12.04 is 2.7.8.dfsg-5.1ubuntu4.6, which is not either of the ones reported in the logs. I would remove libxml2:i386, upgrade and then reinstall it and whatever other packages you have that needed it. I don't think this is an actual package bug, but some kind of local configuration error. ** Changed in: libxml2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1310158 Title: package libxml2 2.7.8.dfsg-5.1ubuntu4.4 [modified: usr/share/doc/libxml2/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: libxml2:amd64 2.7.8.dfsg-5.1ubuntu4.4 cannot be configured because libxml2 Status in “libxml2” package in Ubuntu: Incomplete Bug description: This problem has stopped me from installing software for sometime. I decided to upgrade to latest 12.04. but the message "libxml2: could not be configured" appeared during the upgrade. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libxml2 2.7.8.dfsg-5.1ubuntu4.4 [modified: usr/share/doc/libxml2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51 Uname: Linux 3.2.0-56-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sat Apr 19 19:55:28 2014 ErrorMessage: ErrorMessage: libxml2:amd64 2.7.8.dfsg-5.1ubuntu4.4 cannot be configured because libxml2 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MarkForUpload: True SourcePackage: libxml2 Title: package libxml2 2.7.8.dfsg-5.1ubuntu4.4 [modified: usr/share/doc/libxml2/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: libxml2:amd64 2.7.8.dfsg-5.1ubuntu4.4 cannot be configured because libxml2 UpgradeStatus: Upgraded to precise on 2014-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1310158/+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 1290717] Re: akonadi 1.11.80 fails to start
Hello Bruno, or anyone else affected, Accepted into trusty-proposed. The package will build now and be available in a few hours 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: akonadi (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1290717 Title: akonadi 1.11.80 fails to start Status in Akonadi - The PIM Storage Service: Fix Released Status in “akonadi” package in Ubuntu: Triaged Status in “akonadi” source package in Trusty: Fix Committed Status in “akonadi” source package in Utopic: Fix Committed Bug description: [Impact] installations that used to be trusty and went through akonadi 1.11.80 (early beta upgrades to 14.04) have a broken database adding a fix for these broken setups as per upstream request. [Test Case] * have a broken akonadi and upgrade OR * install 14.04 alpha * login and setup mails * upgrade akonadi to [1] * logout and login again, observe akonadi being broken * upgrade to final+proposed * akonadi should be repaired [1] https://launchpad.net/ubuntu/+source/akonadi/1.11.80-0ubuntu3 [Regression Potential] N/A [Other Info] N/A -- akonadi fails to start since the update from 1.11.0 to 1.11.80 Full description in upstream bug report: https://bugs.kde.org/show_bug.cgi?id=331867 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1290717/+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 1290717] Update Released
The verification of the Stable Release Update for akonadi 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 Desktop Packages, which is subscribed to akonadi in Ubuntu. https://bugs.launchpad.net/bugs/1290717 Title: akonadi 1.11.80 fails to start Status in Akonadi - The PIM Storage Service: Fix Released Status in “akonadi” package in Ubuntu: Triaged Status in “akonadi” source package in Trusty: Fix Released Status in “akonadi” source package in Utopic: Fix Committed Bug description: [Impact] installations that used to be trusty and went through akonadi 1.11.80 (early beta upgrades to 14.04) have a broken database adding a fix for these broken setups as per upstream request. [Test Case] * have a broken akonadi and upgrade OR * install 14.04 alpha * login and setup mails * upgrade akonadi to [1] * logout and login again, observe akonadi being broken * upgrade to final+proposed * akonadi should be repaired [1] https://launchpad.net/ubuntu/+source/akonadi/1.11.80-0ubuntu3 [Regression Potential] N/A [Other Info] N/A -- akonadi fails to start since the update from 1.11.0 to 1.11.80 Full description in upstream bug report: https://bugs.kde.org/show_bug.cgi?id=331867 To manage notifications about this bug go to: https://bugs.launchpad.net/akonadi/+bug/1290717/+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 1311895] Update Released
The verification of the Stable Release Update for gettext 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 Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1311895 Title: 0.18.3.1 can fail when tracing due to missing files Status in “gettext” package in Ubuntu: Fix Released Status in “gettext” source package in Trusty: Fix Released Status in “gettext” package in Debian: Fix Released Bug description: This is fixed in the 0.18.3.2 release. For example when bootstrapping coreutils we get: > ./bootstrap: autopoint --force > sh: build-aux/git-version-gen: No such file or directory > /usr/bin/m4:configure.ac:444: cannot open `m4/cu-progs.m4': \ > No such file or directory > autom4te: /usr/bin/m4 failed with exit status: 1 Please rebase the trusty version to 0.18.3.2 to avoid this and other issues. thanks, Pádraig. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1311895/+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 1304866] Update Released
The verification of the Stable Release Update for unity-greeter 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 Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1304866 Title: Notice of expiring password in greeter not really visible Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: Fix Committed Status in “unity-greeter” source package in Trusty: Fix Released Bug description: [Impact] Messages that are shown after authentication is complete are not seen as the greeter immediately closes and the session starts. Examples of messages are warnings that the user password will expire soon. [Test Case] 1. Make new user 2. Make user account set to expiring with chage tool. (pick yesterday for the date here) $ sudo chage -d 2014/04/29 -M 2 3. Log into this user from the greeter Expected result: User is informed that their password is about to expire. Observed result: Message displayed briefly before greeter closes and session starts. (On fast systems may not be visible at all) [Regression Potential] Since this is a behaviour change in how the UI presents authentication prompts there is a risk that other authentication cases might be adversely affected. Tested manually using the unity-greeter test mode which simulates many of these cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1304866/+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 1304798] Update Released
The verification of the Stable Release Update for account-plugins 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 Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1304798 Title: Unable to access Facebook online account Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: Account plugins 12.10 series: New Status in Online Accounts: Account plugins 13.04 series: New Status in Online Accounts: Account plugins 13.10 series: New Status in “account-plugins” package in Ubuntu: Fix Released Status in “empathy” package in Ubuntu: Confirmed Status in “friends-app” package in Ubuntu: Confirmed Status in “account-plugins” source package in Saucy: Fix Released Status in “empathy” source package in Saucy: Invalid Status in “friends-app” source package in Saucy: Invalid Status in “account-plugins” source package in Trusty: Fix Released Status in “empathy” source package in Trusty: Confirmed Status in “friends-app” source package in Trusty: Confirmed Bug description: [Impact] * Facebook integration has failed due to API token becoming invalidated. * No Saucy users are able to integrate Facebook in either Empathy or Friends. [Test Case] * Open Ubuntu Online Accounts, attempt to register a Facebook account. Facebook gives an error message saying your app is either deleted or invalid. [Regression Potential] * Zero, stable release is already broken. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1304798/+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 1301839] Update Released
The verification of the Stable Release Update for xserver-xorg-video-ati 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 Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1301839 Title: AMD Radeon HD 8670A/8670M/8690M[1002:6660] Low-graphic mode with Trusty Status in X.org XServer - ATI gfx chipset driver: Fix Released Status in “xserver-xorg-video-ati” package in Ubuntu: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Invalid Status in “xserver-xorg-video-ati” source package in Trusty: Fix Released Status in “xserver-xorg-video-intel” source package in Trusty: Invalid Bug description: [Impact] * An explanation of the effects of the bug on users and * justification for backporting the fix to the stable release. * In addition, it is helpful, but not required, to include an explanation of how the upload fixes this bug. [Test Case] * Try to boot to the desktop with 14.04 - Working: Desktop works fine - Bad behavior: You will be ask to run on low-graphic mode, or you will need to add "nomodeset" parameter into grub to boot normally. [Regression Potential] * Low, patches have been taken from upstream. Most likely manifests itself with crash and/or hangs. [Other info] Commits c84230d686c078aac1dc98d82153f8b02521b2e1 and cadb6b493942a84bfeb298751dce0dee39257a06 upstream. [Original bug report] CID: 201305-13624 - AMD Radeon HD 8670A/8670M/8690M[1002:6660] CID: 201309-14197 - AMD Radeon HD 8570A/8570M[1002:6663] This system cannot boot to desktop by "Try Ubuntu" option with liveUSB, it will ask you to run on low-graphic mode. Steps: 1. Try to boot to the desktop with 14.04 Expected result * Desktop works fine Actual result: * You will be ask to run on low-graphic mode, or you will need to add "nomodeset" parameter into grub to boot normally. This bug exists in 12.04.4, and it's fixed in Trusty dailylive 11-Mar-2014 07:51, also the Trusty beta 2 image, but it's now broken again. You can refer to bug 1290745 0a:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] [1002:6660] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14-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 CurrentDesktop: Unity Date: Thu Apr 3 05:44:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2162] Subsystem: Hewlett-Packard Company Device [103c:2162] InstallationDate: Installed on 2014-04-03 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140401) MachineType: Hewlett-Packard HP Pavilion TS 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=8fdb7584-0c55-43ae-923f-b24b1286a592 ro rootdelay=60 quiet splash nomodeset initcall_debug Renderer: Software SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2013 dmi.bios.vendor: Insyde dmi.bios.version: B.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2162 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.0A dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.09:bd05/27/2013:svnHewlett-Packard:pnHPPavilionTS14NotebookPC:pvr089C101630100:rvnHewlett-Packard:rn2162:rvr29.0A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion TS 14 Notebook PC dmi.product.version: 089C101630100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 v
[Desktop-packages] [Bug 1296276] Update Released
The verification of the Stable Release Update for lightdm 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 Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1296276 Title: Unlocking with greeter fails to properly renew kerberos tickets with pam-krb5 Status in Light Display Manager: Fix Released Status in Light Display Manager 1.10 series: Fix Released Status in “lightdm” package in Ubuntu: Fix Released Status in “lightdm” source package in Trusty: Fix Released Bug description: [Impact] Aborted PAM authentications may leave artifacts behind. This is due to LightDM not correctly calling pam_end on these. Authenticating via a LightDM greeter does not refresh PAM credentials. [Test Case] 1. Lock screen using LightDM greeter 2. Enter password to return to session Expected result: Screen is unlocked, credentials are refreshed. Observed result: Screen is unlocked, artifacts are left behind from PAM authentication, credentials not refreshed. [Regression Potential] Since this change affects the PAM handling other PAM modules might potentially have a change in behaviour. This seems low risk as both changes are correct behaviour over the previously incorrect behaviour. I am using the pam-krb5 module to log into a Kerberos realm using lightdm. This works the initial time I log in, when I come in through lightdm. However, once I am logged in, and I lock the screen using light-locker, when I unlock the screen I no longer get renewed tickets. The problem seems to be this: -rw--- 1 me me 504 Mar 23 08:37 krb5cc_1000_sjkfhagfg -rw--- 1 root root504 Mar 23 08:38 krb5cc_pam_lsdkjhfsdk So what is happening is that on the initial login, I get a valid ticket cache, owned by my logging-in user, and showing my UID in the file name. This ticket works fine. However, once I lock the screen and then unlock it, I get a ticket cache owned by root, with "_pam_" in the filename, and of course I can't use it because I am not logged in as root. This problem did not occur in 12.04 LTS, probably because it did not use light-locker. The pam-krb5 module works in all other cases in my installations, so I do not believe this is any kind of problem with the pam_krb5 module. Thanks, Brian ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: light-locker 1.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Sun Mar 23 08:40:38 2014 InstallationDate: Installed on 2014-03-22 (0 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140320) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1296276/+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 1220826] Update Released
The verification of the Stable Release Update for simple-scan 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 Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1220826 Title: PDFs of scanned documents are incompatible with Adobe Reader Status in Simple Scan: Fix Released Status in Simple Scan 3.10 series: Fix Released Status in Simple Scan 3.12 series: Fix Released Status in Simple Scan 3.4 series: Fix Released Status in Simple Scan 3.6 series: Fix Released Status in “simple-scan” package in Ubuntu: Fix Released Status in “simple-scan” source package in Precise: Fix Released Status in “simple-scan” source package in Trusty: Fix Released Bug description: [Impact] PDF files generated by simple-scan are not readable from Acrobat reader due to incorrectly formatted PDF trailers. Other PDF readers ignore these errors. [Test Case] 1. Open Simple Scan 2. Scan a document 3. Save as a PDF file 4. Open with Acrobat reader Expected result: PDF file opens and show scanned contents Observed results: PDF file fails to open due to error [Regression Potential] PDF files are generated slightly differently and other readers could potentially read them differently. This seems low as the current generation is clearly not spec compliant, online compliant checkers pick up the errors and now don't complain. Evince continues to open both the broken and fixed PDF files. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1220826/+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 1074797] Re: [SRU] thousands separator and decimal separator wrong in es_GT
Hello Gonzalo, or anyone else affected, Accepted langpack-locales into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/langpack- locales/2.13+git20120306-12.1 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: langpack-locales (Ubuntu Trusty) Status: Triaged => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to langpack-locales in Ubuntu. https://bugs.launchpad.net/bugs/1074797 Title: [SRU] thousands separator and decimal separator wrong in es_GT Status in “langpack-locales” package in Ubuntu: Fix Released Status in “langpack-locales” source package in Trusty: Fix Committed Bug description: trusty SRU request == Please add a trusty task on both this bug report and bug #997248. [Impact] The LC_NUMERIC formats are imported from the es_ES locale to several Latin American locales with other conventions for thousands_sep and decimal_point, which results in incorrect number formating. Quoting from bug #997248: "This problem is seen when I try to use the calculator, or other gnome program that involves math, it's confusing." [Test Case] Before the fix: $ LC_NUMERIC=es_GT.UTF-8 printf "%'.2f\n" 12345,67 12.345,67 After the fix: $ LC_NUMERIC=es_GT.UTF-8 printf "%'.2f\n" 12345.67 12,345.67 [Regression Potential] There might exist scripts that adapts to the current incorrect behavior. Given that 14.04 was recently released, fixing the bug ought to carry greater weight. [Original description] In Guatemala the thousands separator is a comma and the decimal separator is a dot. Had to change in /usr/share/i18n/locales/es_GT: from: LC_NUMERIC copy "es_ES" END LC_NUMERIC to: LC_NUMERIC decimal_point "" thousands_sep "" grouping 3;3 END LC_NUMERIC then sudo dpkg-reconfigure locales lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/langpack-locales/+bug/1074797/+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
