[Dx-packages] [Bug 1015151] Re: [BNR] Compiz crash in movementWindowOnScreen (caused by fix 755842)
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: compiz (Ubuntu Precise) Status: New => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1015151 Title: [BNR] Compiz crash in movementWindowOnScreen (caused by fix 755842) Status in Compiz: Fix Released Status in Compiz Main Plugins: Fix Committed Status in compiz package in Ubuntu: Fix Released Status in compiz-plugins-main package in Ubuntu: In Progress Status in compiz source package in Precise: Won't Fix Status in compiz-plugins-main source package in Precise: Fix Released Bug description: [Impact] A crash after fix to bug #755842. [Test case] Use super+W rapidly a few times. [Regression Potential] Should be low, correct usage of the vector variable. Test wall plugin's offset movement functionality in general. TESTCASE: ctest -D ExperimentalMemCheck (this option was only added on 20 June 2012) ORIGINAL DESCRIPTION: Running compiz 1:0.9.8+bzr3249-0ubuntu1 got a crash in movementWindowOnScreen after doing super+W a few times. valgrind says: ==3648== Invalid read of size 2 ==3648==at 0x806092A: compiz::wall::movementWindowOnScreen(CompRect const&, CompRegion const&) (rect.h:178) ==3648==by 0x44BCEC7: ??? ==3648== Address 0x44bd026 is 14 bytes inside a block of size 20 free'd ==3648==at 0x402ACFC: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so) ==3648==by 0x8060965: compiz::wall::movementWindowOnScreen(CompRect const&, CompRegion const&) (new_allocator.h:98) ==3648==by 0x44BCEC7: ??? The classic case of iterating a temporary vector that goes out of scope while iterating. Annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1015151/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1212337] Re: [Partial Solved] accounts-daemon crashed with SIGSEGV in dbus_connection_send()
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: accountsservice (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1212337 Title: [Partial Solved] accounts-daemon crashed with SIGSEGV in dbus_connection_send() Status in accountsservice package in Ubuntu: Fix Released Status in accountsservice source package in Precise: Won't Fix Bug description: Hi. There appeared some problems with 'accountsservice' -- a D-Bus interface for user account query and manipulation, that honestly have occurred day-to-day. ### PROBLEM DESCRIPTION: A few weeks ago after login as a normal user, 'accountsservice' (used for querying and manipulating user account informations) crashed. On the beginning it was a random incident. After a few days, 'accountsservice' crashed each time after every user logs on. I think, that's all what I can write, to try to describe this issue, because everything seems to be okay -- no system freezing or slowdowns, no problems after packages update/upgrade etc. ### DETAILED INFORMATIONS: == * ProblemType: Crash * Uname: Linux 3.2.0-51-generic-pae i686 * Architecture: i386 * DistroRelease: Ubuntu 12.04 (Xubuntu 12.04 variant) * Package: accountsservice 0.6.15-2ubuntu9.6 * ApportVersion: 2.0.1-0ubuntu17.4 * NonfreeKernelModules: nvidia * Segfault happened at: 0xb76bb7c3: mov0x10(%eax),%eax * Executable Path (ProcCmdline): /usr/lib/accountsservice/accounts-daemon Also '/var/log/apport.log' file contain some informations about this issue. Everything is in a attached log file. ,-[ $ lsb_release -rd ] | Description:Ubuntu 12.04.3 LTS | Release:12.04 `- ### WHAT HAVE HAD AN IMPACT ON THIS ISSUE? == I have no ideas, why it started to happen. Only one thing, which I've done for a few weeks before problems with 'accountsservice' was 'conky-all' install. Nothing more, nothing less -- no serious administrative tasks were performed (except e.g. kernel or programs updates via APT utility or UpdateManager, but it seems to be obvious). ### APPENDIX: = I would like to notice, that this issue still occurs, after next point Xubuntu update -- from 12.04.2 to 12.04.3 version. So for now, kernel version is; 3.2.0-55-generic-pae. Anything related with this bug, when all of this started to happen, remains unchanged. One more, important, thing to mention is that - in my case - 'accountsservices' crashed even after a fresh Xubuntu 12.04 install. For more info, please see comment #12. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1212337/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 907640] Re: alt-backtick doesn't work properly
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: unity-2d (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/907640 Title: alt-backtick doesn't work properly Status in Ayatana Design: New Status in Metacity: Fix Released Status in metacity package in Ubuntu: Fix Released Status in unity-2d package in Ubuntu: Invalid Status in metacity source package in Precise: Invalid Status in unity-2d source package in Precise: Won't Fix Status in metacity source package in Trusty: Fix Released Status in unity-2d source package in Trusty: Invalid Bug description: In Unity (and I presume unity-2d) alt-backtick (alt-grave, alt-key- above-tab) is meant to flip between the active windows of the current application. In precise unity-2d for me it shows a switcher window with 4 icons for the four windows of my current app (chrome), but repeated presses of backtick while holding alt just flip between the focussed window and the next window, not around all four. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity-2d 4.12.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5 Uname: Linux 3.2.0-5-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Dec 22 16:23:53 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all SourcePackage: unity-2d UpgradeStatus: Upgraded to precise on 2011-12-15 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/907640/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1083605] Re: env not changed in acc. with ~/.pam_environment if /home is on nfs
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: pam (Ubuntu Precise) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/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 Released Status in pam source package in Precise: Won't Fix 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 941673] Re: performance of accounts-daemon is very poor
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: accountsservice (Ubuntu Precise) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/941673 Title: performance of accounts-daemon is very poor Status in accountsservice: Unknown Status in accountsservice package in Ubuntu: In Progress Status in accountsservice source package in Oneiric: Won't Fix Status in accountsservice source package in Precise: Won't Fix Bug description: Version 11.10 The performance of accounts-daemon is unacceptable with large password and/or group files. We have appoximately 4 users in the passwords file and 16000 lines in the group file. Having looked at the source, it appears to me the problem is that for each user is pulls from the password database (via getpwXXX) its then calls getgroups to return the users list of groups. Getgroups must make a complete pass through the group file to determine the groups for the user. When initializing this results in reading the groups file 4 times. I think a better solution is to build a inverted group file map then first time getgroups is called by reading the entire group database and building a data structure indexed by username where a users group list can by found in a single lookup. Of couse, an even better solution would be for getgroups to do that itself, but that would require much larger code changes. I tried installed nscd to see if this would make a difference but no dice. At the moment, 11.10 is unusable for us because of this problem. Hope this is all the info you need. Regards, pdg p...@uow.edu.au To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/941673/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 269904] Re: Screen refresh problems with nvidia cards
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: compiz (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released Status in Compiz Core: New Status in Compiz Core 0.9.8 series: New Status in compiz package in Ubuntu: Fix Released Status in compiz-fusion-plugins-main package in Ubuntu: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in compiz source package in Precise: Won't Fix Status in compiz-plugins-main source package in Precise: Won't Fix Status in compiz source package in Trusty: Fix Released Status in compiz-plugins-main source package in Trusty: Invalid Status in compiz source package in Intrepid: Fix Released Status in compiz-plugins-main source package in Intrepid: Won't Fix Status in compiz-fusion-plugins-main package in Debian: Fix Released Bug description: [Impact] Users of Nvidia gfx using the proprietary driver may see screen corruption during certain operations. [Test Case] * Install an Nvidia graphics adapter and the proprietary driver. * Observe the graphics corrupt. * Install the version of Compiz with this fix. * Observe corruption is gone. [Regression Potential] The patch for this was provided by Nvidia. There could be some corner cases users hit that may cause other issues. That said, enough testing has been done to confidently say that the gains provided by this fix far outweigh any corner cases. --- Original Description: == Proposed compiz-fusion-plugins-main patch == See comment 234 by Anders Kaseorg and attached compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff. == Original report == Binary package hint: compiz I'm using latest compiz on intrepid. Since jockey-gtk does not work on my box (I already filed a bug), I manually installed nvidia-glx-177 and added the "driver → nvidia" line to xorg.conf. Now I seem to be having some screen refresh problems when using compiz: parts of the screen are refreshed, but others aren't. That means nautilus doesn't show files or folders until I move the cursor over them, firefox doesn't show webpages properly until I scroll down, and so on. Please, tell me if there is any additional info I can provide to find out the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 269904] Re: Screen refresh problems with nvidia cards
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: compiz-plugins-main (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards Status in Compiz: Fix Released Status in Compiz 0.9.11 series: Fix Released Status in Compiz Core: New Status in Compiz Core 0.9.8 series: New Status in compiz package in Ubuntu: Fix Released Status in compiz-fusion-plugins-main package in Ubuntu: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in compiz source package in Precise: Won't Fix Status in compiz-plugins-main source package in Precise: Won't Fix Status in compiz source package in Trusty: Fix Released Status in compiz-plugins-main source package in Trusty: Invalid Status in compiz source package in Intrepid: Fix Released Status in compiz-plugins-main source package in Intrepid: Won't Fix Status in compiz-fusion-plugins-main package in Debian: Fix Released Bug description: [Impact] Users of Nvidia gfx using the proprietary driver may see screen corruption during certain operations. [Test Case] * Install an Nvidia graphics adapter and the proprietary driver. * Observe the graphics corrupt. * Install the version of Compiz with this fix. * Observe corruption is gone. [Regression Potential] The patch for this was provided by Nvidia. There could be some corner cases users hit that may cause other issues. That said, enough testing has been done to confidently say that the gains provided by this fix far outweigh any corner cases. --- Original Description: == Proposed compiz-fusion-plugins-main patch == See comment 234 by Anders Kaseorg and attached compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff. == Original report == Binary package hint: compiz I'm using latest compiz on intrepid. Since jockey-gtk does not work on my box (I already filed a bug), I manually installed nvidia-glx-177 and added the "driver → nvidia" line to xorg.conf. Now I seem to be having some screen refresh problems when using compiz: parts of the screen are refreshed, but others aren't. That means nautilus doesn't show files or folders until I move the cursor over them, firefox doesn't show webpages properly until I scroll down, and so on. Please, tell me if there is any additional info I can provide to find out the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 851424] Re: most genres do nothing
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: unity (Ubuntu Precise) Status: New => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/851424 Title: most genres do nothing Status in Ayatana Design: New Status in Unity: Fix Released Status in Music Lens: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Incomplete Status in unity source package in Precise: Won't Fix Status in unity-lens-music source package in Precise: Won't Fix Bug description: Test case: 1. Open the dash 2. Switch to the music lens 3. Click on different genres on the filter -> See them triaged === I apparently have 4 of the 18 listed genres. Why show genres that yield zero results? Banshee shows my more than 20 genres. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/851424/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1310232] Re: Unauthorized user can view a list of processes
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: indicator-power (Ubuntu Precise) Status: New => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1310232 Title: Unauthorized user can view a list of processes Status in indicator-power package in Ubuntu: Fix Released Status in indicator-power source package in Precise: Won't Fix Bug description: On lightdm screen click on battery indicator in top right corner. Select the first menu item. gnome-power-statistic window should be opened. Select "processor" menu item in left side. Unathorized user should not view process list. OS version: Ubuntu 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.2.3-0ubuntu2.4 ProcVersionSignature: Ubuntu 3.8.0-38.56~precise1-generic 3.8.13.19 Uname: Linux 3.8.0-38-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 20 13:21:17 2014 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1310232/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 758735] Re: unity-panel-service crashed with SIGSEGV in g_settings_backend_path_changed()
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: d-conf (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/758735 Title: unity-panel-service crashed with SIGSEGV in g_settings_backend_path_changed() Status in dconf: Expired Status in Indicator Date and Time: Invalid Status in d-conf package in Ubuntu: Triaged Status in d-conf source package in Precise: Won't Fix Bug description: Binary package hint: unity Actually I don't know what I did to produce this error. $ lsb_release -rd Description: Ubuntu Natty (development branch) Release: 11.04 ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: unity 3.8.6-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 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 Kernel Module 270.30 Fri Feb 25 14:34:41 PST 2011 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu1) Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,place,grid,imgsvg,compiztoolbox,imgjpeg,mousepoll,water,resize,commands,vpswitch,session,debugspew,imgpng,wall,move,titleinfo,regex,gnomecompat,thumbnail,staticswitcher,resizeinfo,wobbly,animation,workarounds,expo,fade,scale,unityshell] CompositorRunning: compiz CrashCounter: 1 Date: Tue Apr 12 15:49:07 2011 DistUpgraded: Log time: 2011-03-21 12:55:51.607912 DistroCodename: natty DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: nVidia Corporation G96 [GeForce 9500 GT] [10de:0640] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:82f4] InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) InstallationMedia__: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) JockeyStatus: xorg:nvidia_current - Драйвер прискореної графіки NVIDIA (Комерційний, Дозволено, Використовується) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANGUAGE=uk_UA:en LANG=uk_UA.utf8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=200ca29d-4202-40f3-8f69-80dcd1035b63 ro ProcVersionSignature_: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 ProcVersionSignature__: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Renderer: Unknown SegvAnalysis: Segfault happened at: 0xb7242c91:mov(%eax,%edx,1),%eax PC (0xb7242c91) ok source "(%eax,%edx,1)" (0x0004) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 g_settings_backend_path_changed () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/gio/modules/libdconfsettings.so g_simple_async_result_complete () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in g_settings_backend_path_changed() UpgradeStatus: Upgraded to natty on 2011-03-21 (22 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare www-data dmi.bios.date: 02/03/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: TMIBX10H.86A.0029.2010.0203.1403 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DQ57TM dmi.board.vendor: Intel Corporation dmi.board.version: AAE70931-402 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrTMIBX10H.86A.0029.2010.0203.1403:bd02/03/2010:svn:pn:pvr:rvnIntelCorporation:rnDQ57TM:rvrAAE70931-402:cvn:ct3:cvr: version.compiz: compiz 1:0.9.4+bzr20110411-0ubuntu1 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/758735/+subscriptions -- Mailing
[Dx-packages] [Bug 851424] Re: most genres do nothing
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: unity-lens-music (Ubuntu Precise) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/851424 Title: most genres do nothing Status in Ayatana Design: New Status in Unity: Fix Released Status in Music Lens: Incomplete Status in unity package in Ubuntu: Fix Released Status in unity-lens-music package in Ubuntu: Incomplete Status in unity source package in Precise: Won't Fix Status in unity-lens-music source package in Precise: Won't Fix Bug description: Test case: 1. Open the dash 2. Switch to the music lens 3. Click on different genres on the filter -> See them triaged === I apparently have 4 of the 18 listed genres. Why show genres that yield zero results? Banshee shows my more than 20 genres. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/851424/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 877358] Re: QtAccessibility causes crashes in several applications
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: qt-at-spi (Ubuntu Precise) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/877358 Title: QtAccessibility causes crashes in several applications Status in at-spi2-core package in Ubuntu: Invalid Status in unity-2d package in Ubuntu: Fix Released Status in at-spi2-core source package in Oneiric: Fix Released Status in qt-at-spi source package in Oneiric: Won't Fix Status in unity-2d source package in Oneiric: Fix Released Status in at-spi2-core source package in Precise: Invalid Status in qt-at-spi source package in Precise: Won't Fix Status in unity-2d source package in Precise: Fix Released Bug description: See backtraces, and possible further comments here: https://bugs.kde.org/buglist.cgi?long_desc_type=substring_desc=QAccessible_severity=crash_status=UNCONFIRMED If possible, please give instructions how to workaround it (e.g. by disabling QtAccessibility) until the bugs are fixed. If the crashes are caused by bugs in KDE applications itself, please file back bug reports to the KDE bug tracker. SRU Info [Impact] QtAccessibility causes crashes in several applications when enabled. This affects Qt and KDE applications started on an accessibility- enabled desktop, be it Unity or KDE. [Development Fix] Upstream is confident QtAccessibility is stable enough in Qt 4.8 that no workaround will be needed in Precise. [Stable Fix] QtAccessibility does not cause Unity 2D to crash, as crashes are caused by widgets which are not used in Unity 2D. Since the desktop must be accessible, it is important to keep QtAccessibility activated for Unity 2D, but not for other applications. Activation of QtAccessibility is controlled by the QT_ACCESSIBILITY environment variable. The fix consists of two steps: - Do not enable QtAccessibility if desktop accessibility is enabled. This is implemented in the at-spi2-core debdiff - Enable QtAccessibility at startup of Unity 2D so that the desktop remains accessible, but disable it before starting applications so that they do not suffer from the crashes. It is still possible for Qt application developers to test accessibility of their application by explicitly setting the QT_ACCESSIBILITY environment variable. [Test Case] Those crashes are difficult to reproduce, but I can reliably trigger one on my machine with Kopete. 1. Enable accessibility 2. Restart the session => the QT_ACCESSIBILITY environment variable should be set 3. Start Kopete => crash 4. Ensure unity-2d still have accessibility enabled [Regression Potential] This fix causes accessibility to be disabled for all Qt applications but Unity 2D. Users who have started to rely on QtAccessibility will not be able to use it anymore. We (upstream and I) believe that the current situation is worse and that QtAccessibility is not good enough in Oneiric anyway for users to rely on it yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/877358/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 949445] Re: HUD is silent to screen readers
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: unity (Ubuntu Precise) Status: New => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/949445 Title: HUD is silent to screen readers Status in Unity: Fix Released Status in unity-2d: Fix Released Status in unity package in Ubuntu: Confirmed Status in unity-2d package in Ubuntu: Fix Released Status in unity source package in Precise: Won't Fix Status in unity-2d source package in Precise: Fix Released Bug description: Test case: 1. Enable accessibility and the orca screen reader 2. Relog into Unity-2D 3. Open any application 4. Make the HUD appear (tap Alt) 5. Enter any search that returns some results 6. Move around the results with arrow keys -> The orca reader should read the suggestions === HUD is broken for users of orca, it does not speak the suggestions. In unity2d all the suggestions are spoken as pushbuttons but not the values of them. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/949445/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 977262] Re: Unity 2D doesn't load 24 bit icons
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: unity-2d (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/977262 Title: Unity 2D doesn't load 24 bit icons Status in unity-2d: Fix Committed Status in unity-2d package in Ubuntu: Fix Released Status in unity-2d source package in Precise: Won't Fix Bug description: [Test Case] 1. Install any application offering a 24-bit application icon (e.g. kmag) 2. Run the application -> The application icon should be visible in the launcher instead of the ? icon for the application. The icon should also have correct colors. [Regression Potential] 24-bit icons in the Launcher looking strange (modified colors or similar). Original description: Unity 2D 5.8 Precise When starting an application whose icon is 24 bits, like pendu when installed from source or kmag as installed from the repositories, the icon shown is the ? icon instead of the real application icon To manage notifications about this bug go to: https://bugs.launchpad.net/unity-2d/+bug/977262/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 915468] Re: the unity-greeter keyboard's selection doesn't respect the user config
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: unity-greeter (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/915468 Title: the unity-greeter keyboard's selection doesn't respect the user config Status in accountsservice package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Status in accountsservice source package in Precise: Fix Released Status in gnome-settings-daemon source package in Precise: Fix Released Status in lightdm source package in Precise: Fix Released Status in unity-greeter source package in Precise: Won't Fix Bug description: Using the current trunk from lightdm and unity-greeter, unity-greeter display a keyboard indicator but default to "en" where my system and user .dmrc are set to fr. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/915468/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 981053] Re: should not segfault on profile errors
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: d-conf (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/981053 Title: should not segfault on profile errors Status in dconf: Fix Released Status in d-conf package in Ubuntu: Triaged Status in d-conf source package in Precise: Won't Fix Bug description: I'm trying to create a system dconf configuration, and it's causing lightdm to crash. In /etc/dconf/profile/user I have user-db:user system-db:local system-db:site Then I create empty files /etc/dconf/db/local and /etc/dconf/db/site. On start, lightdm crashes, and x-0-greeter.log has this: /usr/lib/lightdm/lightdm-greeter-session: line 35: 5782 Trace/breakpoint trap (core dumped) exec $@ If I remove the system configs, it works fine. If I don't have the empty files in /etc/dconf/db, I get a warning that the local one can't be found, and then the crash (I don't get a warning about the site one). To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/981053/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1945969] Re: Update to 0.52.6 in impish
No need for 0-day SRU. This has been sponsored into Debian unstable and will be synced to Ubuntu. Thanks @seb128! https://tracker.debian.org/news/1266939/accepted- libunity-714190420190319-6-source-into-unstable/ ** Summary changed: - FTBFS with valac 0.52.6 in impish + Update to 0.52.6 in impish ** Description changed: - [Impact] - - * libunity FTBFS using valac 0.52.6, which makes it hard to apply any - (security) updates in a timely manner. - - [Test Plan] - - * Check the Launchpad build logs to make sure that libunity - 7.1.4+19.04.20190319-6 built successfully - * Attach build logs to this bug - - [Where problems could occur] - - * The build could still fail for some reason and we would be back to - status quo. - - [Other Info] - - * I'm hijacking this valac bug for the libunity 0-day SRU - * PPA pre-testing has been done here: https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing-archive-extra - - - === Original Bug Description === - The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1945969 Title: Update to 0.52.6 in impish Status in libunity package in Ubuntu: Fix Committed Status in vala package in Ubuntu: Fix Released Status in libunity source package in Impish: Fix Committed Status in vala source package in Impish: Fix Released Bug description: The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1945969/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1945969] Re: FTBFS with valac 0.52.6 in impish
** Summary changed: - Update to 0.52.6 in impish + FTBFS with valac 0.52.6 in impish -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1945969 Title: FTBFS with valac 0.52.6 in impish Status in libunity package in Ubuntu: Fix Committed Status in vala package in Ubuntu: Fix Released Status in libunity source package in Impish: Fix Committed Status in vala source package in Impish: Fix Released Bug description: [Impact] * libunity FTBFS using valac 0.52.6, which makes it hard to apply any (security) updates in a timely manner. [Test Plan] * Check the Launchpad build logs to make sure that libunity 7.1.4+19.04.20190319-6 built successfully * Attach build logs to this bug [Where problems could occur] * The build could still fail for some reason and we would be back to status quo. [Other Info] * I'm hijacking this valac bug for the libunity 0-day SRU * PPA pre-testing has been done here: https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing-archive-extra === Original Bug Description === The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1945969/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1945969] Re: Update to 0.52.6 in impish
** Also affects: vala (Ubuntu Impish) Importance: High Assignee: Rico Tzschichholz (ricotz) Status: Fix Released ** Also affects: libunity (Ubuntu Impish) Importance: High Assignee: Lukas Märdian (slyon) Status: Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1945969 Title: Update to 0.52.6 in impish Status in libunity package in Ubuntu: Fix Committed Status in vala package in Ubuntu: Fix Released Status in libunity source package in Impish: Fix Committed Status in vala source package in Impish: Fix Released Bug description: [Impact] * libunity FTBFS using valac 0.52.6, which makes it hard to apply any (security) updates in a timely manner. [Test Plan] * Check the Launchpad build logs to make sure that libunity 7.1.4+19.04.20190319-6 built successfully * Attach build logs to this bug [Where problems could occur] * The build could still fail for some reason and we would be back to status quo. [Other Info] * I'm hijacking this valac bug for the libunity 0-day SRU * PPA pre-testing has been done here: https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing-archive-extra === Original Bug Description === The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1945969/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1945969] Re: Update to 0.52.6 in impish
This is a FTBFS fix for libunity that could become an impish 0-day SRU. PPA pre-testing has been done here: https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing- archive-extra ** Description changed: + [Impact] + + * libunity FTBFS using valac 0.52.6, which makes it hard to apply any + (security) updates in a timely manner. + + [Test Plan] + + * Check the Launchpad build logs to make sure that libunity + 7.1.4+19.04.20190319-6 built successfully + * Attach build logs to this bug + + [Where problems could occur] + + * The build could still fail for some reason and we would be back to + status quo. + + [Other Info] + + * I'm hijacking this valac bug for the libunity 0-day SRU + * PPA pre-testing has been done here: https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing-archive-extra + + + === Original Bug Description === + The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === - * Various improvements and bug fixes: - - codegen: - + Fix property access inside opaque compact class - + Add type declaration for implicit temporary local variable - - vala: - + Warn about unsupported cast to void and drop it [#1070] - + Don't restrict element type of GLib.Array [#1227] - + Multi-dimensional params-array not allowed [#1230] - + Accept NullType as generic type argument - + Set source references of created DataType instances in OCE - - valadoc: Correctly format background of inline @link's [#1226] + * Various improvements and bug fixes: + - codegen: + + Fix property access inside opaque compact class + + Add type declaration for implicit temporary local variable + - vala: + + Warn about unsupported cast to void and drop it [#1070] + + Don't restrict element type of GLib.Array [#1227] + + Multi-dimensional params-array not allowed [#1230] + + Accept NullType as generic type argument + + Set source references of created DataType instances in OCE + - valadoc: Correctly format background of inline @link's [#1226] - * Bindings: - - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - - gio-2.0: Backport fixes from 0.54.2 - - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - - glib-2.0: Add RefString since 2.58 [#723] - - gtk4: Backport fixes from 0.54.2 + * Bindings: + - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] + - gio-2.0: Backport fixes from 0.54.2 + - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] + - glib-2.0: Add RefString since 2.58 [#723] + - gtk4: Backport fixes from 0.54.2 -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1945969 Title: Update to 0.52.6 in impish Status in libunity package in Ubuntu: Fix Committed Status in vala package in Ubuntu: Fix Released Bug description: [Impact] * libunity FTBFS using valac 0.52.6, which makes it hard to apply any (security) updates in a timely manner. [Test Plan] * Check the Launchpad build logs to make sure that libunity 7.1.4+19.04.20190319-6 built successfully * Attach build logs to this bug [Where problems could occur] * The build could still fail for some reason and we would be back to status quo. [Other Info] * I'm hijacking this valac bug for the libunity 0-day SRU * PPA pre-testing has been done here: https://launchpad.net/~slyon/+archive/ubuntu/testing/+sourcepub/12784335/+listing-archive-extra === Original Bug Description === The 0.52.x series is receiving further bug fix releases for GNOME 40.x. See https://wiki.gnome.org/Projects/Vala Upstream changes since 0.52.5: Vala 0.52.6 === * Various improvements and bug fixes: - codegen: + Fix property access inside opaque compact class + Add type declaration for implicit temporary local variable - vala: + Warn about unsupported cast to void and drop it [#1070] + Don't restrict element type of GLib.Array [#1227] + Multi-dimensional params-array not allowed [#1230] + Accept NullType as generic type argument + Set source references of created DataType instances in OCE - valadoc: Correctly format background of inline @link's [#1226] * Bindings: - gio-2.0: Unhide a few usable symbols which are marked not introspectable [#1222] - gio-2.0: Backport fixes from 0.54.2 - glib-2.0: Current constants in GLib.Math are part of glib.h [#1220] - glib-2.0: Add RefString since 2.58 [#723] - gtk4: Backport fixes from 0.54.2 To manage notifications about this bug go to:
