[Dx-packages] [Bug 1247373] Re: Empathy’s “Insert Smiley” menu doesn't display correctly
** Changed in: indicator-appmenu (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1247373 Title: Empathy’s “Insert Smiley” menu doesn't display correctly Status in “indicator-appmenu” package in Ubuntu: Confirmed Bug description: The Conversation Insert Smiley menu in Empathy is a little special: it provides images, not text, for each supported smiley, arranged on a grid to save space and showing a tooltip with the related text used for the smiley. In Ubuntu's global menu however, it's displayed as a long, empty menu, no grid, no images and no tooltips. Selecting an entry still inserts the smiley in the conversation window, but it's not really usable that way. I'm submitting this as a new report for bug #596103, as advised ba mpt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1247373/+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 1251219] Re: Calendar flickers when changing date
*** This bug is a duplicate of bug 1238626 *** https://bugs.launchpad.net/bugs/1238626 ** This bug has been marked a duplicate of bug 1238626 flickers when changing the date -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1251219 Title: Calendar flickers when changing date Status in The Date and Time Indicator: New Status in “indicator-datetime” package in Ubuntu: New Bug description: Issue: When changing the day, month or year in the calendar, after a second it flickers once. Seems like that the menu closes and reopens again very quickly. Steps to reproduce: * open calendar * e..g. change month from November to December * wait a second - datetime menu flickers This seems to be an regression as I cannot recall the indicator having this behavior in 13.04. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Nov 14 15:06:48 2013 InstallationDate: Installed on 2012-07-10 (491 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-08-26 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1251219/+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 1248760] Re: Calendar control shakes when leaving newly-selected date
*** This bug is a duplicate of bug 1238626 *** https://bugs.launchpad.net/bugs/1238626 On closer inspection, the flickering happens a fraction of a second after you choose a date, regardless of whether you leave the date area or not. So this is a duplicate of bug 1238626. ** This bug has been marked a duplicate of bug 1238626 flickers when changing the date -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1248760 Title: Calendar control shakes when leaving newly-selected date Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: Issue: If you select a date in the indicator calendar and then hovering out of the date field it has a UI bug. I can not describe it good enough so I made a short video sequence: https://www.youtube.com/watch?v=Kh4z5H9-4y0feature=youtu.be What to expect: No display issue but just a hover effect on the focused date (this does not happen). Distributor ID: Ubuntu Description: Ubuntu 13.10 Kernel: Linux hostname 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Indicator version: Version: 13.10.0+13.10.20131023.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131016.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 7 00:00:56 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-08-13 (450 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-10-22 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1248760/+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 1238626] Re: Menu flickers shortly after choosing a date
** Summary changed: - flickers when changing the date + Menu flickers shortly after choosing a date ** Description changed: - Repro steps: + indicator-datetime 13.10.0+13.10.20131011-0ubuntu1, Ubuntu 13.10 1. Click on the applet to open the drop down calendar 2. Click on any day you wish to skip to the next month 3. The entire drop down view flickers for .10 of a second . It looks like it is redrawing I have the absolute latest , including an update that just got installed, fro the indicator-datetime applet and the problem persists - ProblemType: Bug - DistroRelease: Ubuntu 13.10 - Package: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1 - ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 - Uname: Linux 3.11.0-12-generic x86_64 - ApportVersion: 2.12.5-0ubuntu1 - Architecture: amd64 - Date: Fri Oct 11 08:00:12 2013 - InstallationDate: Installed on 2013-10-10 (0 days ago) - InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007) - MarkForUpload: True - SourcePackage: indicator-datetime - UpgradeStatus: No upgrade log present (probably fresh install) + Screencast from Michael Tanner in duplicate bug 1248760: + https://www.youtube.com/watch?v=Kh4z5H9-4y0 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1238626 Title: Menu flickers shortly after choosing a date Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: indicator-datetime 13.10.0+13.10.20131011-0ubuntu1, Ubuntu 13.10 1. Click on the applet to open the drop down calendar 2. Click on any day you wish to skip to the next month 3. The entire drop down view flickers for .10 of a second . It looks like it is redrawing I have the absolute latest , including an update that just got installed, fro the indicator-datetime applet and the problem persists Screencast from Michael Tanner in duplicate bug 1248760: https://www.youtube.com/watch?v=Kh4z5H9-4y0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1238626/+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 1253810] Re: Messages in Incoming not always display the correct date and content
Weird, the indicator didn't change between 2013-10-29 and 2013-11-25 but the bug started in between ... seems like it was either there but happening less often for some reason, or it might be an issue with another component -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253810 Title: Messages in Incoming not always display the correct date and content Status in The Messaging Menu: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: Sometimes SMSes are displayed with Dec 31 as a date and the content is not displayed. This happens every once in a while, in general the notifications are displayed correctly, but as I exchanged a lot of SMSes with different numbers, this problem happened a few times. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1253810/+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 1253810] Re: Messages in Incoming not always display the correct date and content
let's add the regression tag (as it's from image 27 at least) so that we can get it in our regression list (and so fixing ASAP) ** Tags added: regression -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253810 Title: Messages in Incoming not always display the correct date and content Status in The Messaging Menu: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: Sometimes SMSes are displayed with Dec 31 as a date and the content is not displayed. This happens every once in a while, in general the notifications are displayed correctly, but as I exchanged a lot of SMSes with different numbers, this problem happened a few times. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1253810/+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 1195830] Re: mouse cursor suddenly twice as big
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1195830 Title: mouse cursor suddenly twice as big Status in “unity” package in Ubuntu: Confirmed Bug description: the mouse cursor changed to twice its size for no apparent reason. Neither decreasing its size in dconf nor with unity tweak tools reverts this. This happened after the update: Start-Date: 2013-06-28 18:44:53 Commandline: aptdaemon role='role-commit-packages' sender=':1.259' Upgrade: libegl1-mesa-drivers:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libgl1 -mesa-dri:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libgl1-mesa-dri:i386 (9.1. 3-0ubuntu0.3, 9.1.3-0ubuntu0.4), lightdm:amd64 (1.6.0-0ubuntu2.1, 1.6.0-0ubuntu3 ), libgl1-mesa-glx:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libgl1-mesa-glx:i 386 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libglapi-mesa:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libglapi-mesa:i386 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), lib openvg1-mesa:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), apport:amd64 (2.9.2-0ub untu8.1, 2.9.2-0ubuntu8.2), xserver-xorg-video-savage:amd64 (2.3.6-0ubuntu1, 2.3 .6-0ubuntu1.1), python3-problem-report:amd64 (2.9.2-0ubuntu8.1, 2.9.2-0ubuntu8.2 ), libgbm1:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libxatracker1:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libegl1-mesa:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), libgles2-mesa:amd64 (9.1.3-0ubuntu0.3, 9.1.3-0ubuntu0.4), python3-apport:amd64 (2.9.2-0ubuntu8.1, 2.9.2-0ubuntu8.2), liblightdm-gobject-1-0:amd64 (1.6.0-0ubuntu2.1, 1.6.0-0ubuntu3), upstart:amd64 (1.8-0ubuntu1, 1.8-0ubuntu1.1), apport-gtk:amd64 (2.9.2-0ubuntu8.1, 2.9.2-0ubuntu8.2) End-Date: 2013-06-28 18:45:10 Sorry for not having the patience to search for the package in question. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 7.0.0daily13.06.19~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: wl 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 313.30 Wed Mar 27 16:56:45 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jun 28 19:43:25 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2013-05-17 (41 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64+mac (20130424) MachineType: Apple Inc. MacBookPro10,1 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-26-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.9~daily13.06.19~13.04-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.43-0ubuntu1.1 version.libgl1-mesa-dri: libgl1-mesa-dri
[Dx-packages] [Bug 1253031] Re: Todays date should be marked on menu bar clock
*** This bug is a duplicate of bug 1017595 *** https://bugs.launchpad.net/bugs/1017595 ** This bug has been marked a duplicate of bug 1017595 Today's date in the calendar is unclear -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253031 Title: Todays date should be marked on menu bar clock Status in “indicator-datetime” package in Ubuntu: New Bug description: When you click the clock on the menu bar, todays date should be clearly marked. For example with white lines around it, like Google Calendar. See attached screenshots ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.307 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Wed Nov 20 10:58:21 2013 InstallationDate: Installed on 2012-08-03 (473 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1253031/+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 1253810] Re: Messages in Incoming not always display the correct date and content
So, after talking with Saviq, it's a very old bug that was always present. They have a branch proposed to fix it but never decided on the correct resolution of this. So, targetting Unity8 and attaching the branch to that bug. (and removing both version and regression tags) ** Tags removed: r27 regression ** Project changed: indicator-messages = unity8 ** Package changed: indicator-messages (Ubuntu) = unity8 (Ubuntu) ** Branch linked: lp:~nick-dedekind/unity8/StrFTimeFormatter -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253810 Title: Messages in Incoming not always display the correct date and content Status in The Unity 8 shell: New Status in “unity8” package in Ubuntu: Confirmed Bug description: Sometimes SMSes are displayed with Dec 31 as a date and the content is not displayed. This happens every once in a while, in general the notifications are displayed correctly, but as I exchanged a lot of SMSes with different numbers, this problem happened a few times. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1253810/+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 1255500] [NEW] banshee scope reports length in milliseconds for previews
Public bug reported: The banshee scope reports length in milliseconds, so the preview is pretty confused. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-lens-music 6.9.0+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 27 12:28:41 2013 SourcePackage: unity-lens-music UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-lens-music (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Screenshot 2013-11-27 12:32:52.png https://bugs.launchpad.net/bugs/1255500/+attachment/3918238/+files/Screenshot%202013-11-27%2012%3A32%3A52.png -- 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/1255500 Title: banshee scope reports length in milliseconds for previews Status in “unity-lens-music” package in Ubuntu: New Bug description: The banshee scope reports length in milliseconds, so the preview is pretty confused. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-lens-music 6.9.0+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 27 12:28:41 2013 SourcePackage: unity-lens-music UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/1255500/+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 1255514] [NEW] The spread windows functionality (super+w) does not always work
Public bug reported: Sometimes the spread functionality does not work in a login session. Login out and in again is makes it work. I think the problem always occurs in the first login session after I start my computer. expected behaviour: super+w spreads all the windows on the active workspace actual behaviour: The windows are not spread (and a w is typed in the active window if it's possible to type anything there). (I'm sorry if I indicated the wrong package, I didn't really know which to choose.) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CheckboxSubmission: 545f0c3c73676a721a0ffbc52795c2f4 CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Nov 27 12:27:20 2013 DistUpgraded: 2013-11-09 12:56:02,508 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1712] NVIDIA Corporation GF108M [GeForce GT 550M] [10de:0df6] (rev ff) (prog-if ff) InstallationDate: Installed on 2013-05-02 (208 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: ASUSTeK Computer Inc. N53SN MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=4500db2a-7566-47cc-b27b-fc416554b61b ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-11-09 (17 days ago) dmi.bios.date: 07/15/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SN.207 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SN dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SN.207:bd07/15/2011:svnASUSTeKComputerInc.:pnN53SN:pvr1.0:rvnASUSTeKComputerInc.:rnN53SN:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: N53SN dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Nov 27 12:26:20 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12620 vendor SEC xserver.version: 2:1.14.3-3ubuntu2 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu ** Description changed: Sometimes the spread functionality does not work in a login session. Login out and in again is makes it work. I think the problem always occurs in the first login session after I start my computer. expected behaviour: super+w spreads all the windows on the active workspace actual behaviour: The windows are not spread (and a w is typed in the active window if it's possible to type anything there). + (I'm sorry if I indicated the wrong package, I didn't really know which + to choose.) + ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CheckboxSubmission: 545f0c3c73676a721a0ffbc52795c2f4 CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 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 CompositorUnredirectDriverBlacklist:
[Dx-packages] [Bug 1255530] [NEW] system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock starts
Public bug reported: starting my phone set to german language the lock screen properly shows a 24h clock ... as aoon as the panel clock shows up, the lockscreen format (and all other places where the time is shown in the UI) is swithcing to AM/PM 12h time format. ** Affects: indicator-datetime (Ubuntu) Importance: Medium Status: New ** Tags: avengers ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = Medium ** Tags added: avengers -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255530 Title: system clock gets forcefully set to 12h (AM/PM) as soon as the panel clock starts Status in “indicator-datetime” package in Ubuntu: New Bug description: starting my phone set to german language the lock screen properly shows a 24h clock ... as aoon as the panel clock shows up, the lockscreen format (and all other places where the time is shown in the UI) is swithcing to AM/PM 12h time format. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1255530/+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 842693] Re: Touchpad gesture not customizable or cannot turn off all or selected gestures
Every time I reinstall Ubuntu, I have to build unity from source as per urlhttp://task3.cc/1068/os-x-like-multitouch-gestures-for-macbook-pro- running-ubuntu-12-10/#Disable_Unity_built-in_gestures/url in order to be able to use touchegg. On a laptop's touchpad, unity's built-in gestures are really inefficient. I do understand that creating new settings to enable gesture customization would be a lot of work, but would it at least be possible to make it so that the gestures are easily (I'm not even talking GUI, just some file to edit would be fine) disabled ? Right now, every unity update means taking 30 minutes to compile the whole thing again, unless I disable updates, and thus miss the bug fixes, which is what I actually do. Either way, this is obivously sub- optimal, to say the least, and judging by the number of comments on the blog post I provided, I'm really not the only one annoyed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/842693 Title: Touchpad gesture not customizable or cannot turn off all or selected gestures Status in Open Input Framework: Invalid Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: There is no way to customize or turn off touch gestures. I think we should at least have a way to disable some gestures in case user doesn't want them or wants to override the gestures using some external app like touchegg. We need a gnome-control-center tab to customize touch gesture actions. To manage notifications about this bug go to: https://bugs.launchpad.net/oif/+bug/842693/+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 1233205] Re: maximize then unmaximize of gnome-terminal shrinks window
It's not just gnome-terminal; xterm, urxvt, pterm (putty) also shrink. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1233205 Title: maximize then unmaximize of gnome-terminal shrinks window Status in “unity” package in Ubuntu: Confirmed Bug description: This sounds a lot like bug 772972, but I'm seeing it in saucy. If you maximize a gnome-temrinal and then un-maximize it, it will shrink by a full column and row. * run 'gnome-terminal' * click the maximize button (or keybinding 'maximize') * click the unmaximize button (or keybinding 'unmaximize') * notice that window has shrunk (if you do it repeatedly you'll end up with a very small window). This seems to have regressed somewhat recently in saucy for me, but Im not too sure to be honest. Related bugs: bug 772972: Horizontal/vertical-maximized window shrinks a few pixels when losing focus, upsets gnome-terminal bug 1102024: Restoring a maximized Gnome Terminal window with keybinding fails to restore the original geometry ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20130927.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 30 10:28:05 2013 DistUpgraded: 2013-05-20 08:14:41,880 DEBUG openCache() DistroCodename: saucy DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2011-10-19 (712 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 7417CTO MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-9-generic root=UUID=f9832678-e9fb-41c5-8edb-5edd5200ed0a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-05-20 (133 days ago) dmi.bios.date: 12/06/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET91WW (3.21 ) dmi.board.name: 7417CTO 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:bvr7UET91WW(3.21):bd12/06/2010:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7417CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 30 09:57:41 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16435 vendor LEN xserver.version: 2:1.14.2.901-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1233205/+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 1255076] Re: /usr/sbin/unity-greeter:*** Error in `/usr/sbin/unity-greeter': free(): invalid pointer: ADDR ***
I confirm that the bug has disappeared for me with latest updates from trusty-proposed. -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255076 Title: /usr/sbin/unity-greeter:*** Error in `/usr/sbin/unity-greeter': free(): invalid pointer: ADDR *** Status in Indicator Display Objects: Fix Committed Status in “ido” package in Ubuntu: Fix Released Status in “unity-greeter” package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-greeter. This problem was most recently seen with version 14.04.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/f182d58458c2d4d6242ca43f778cd0f42e6aec24 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ido/+bug/1255076/+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 1254728] Re: After resent package update keyboard shortcuts stopped working.
I guess nevermind. After several reboots everything works as it was before. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1254728 Title: After resent package update keyboard shortcuts stopped working. Status in “unity” package in Ubuntu: New Bug description: uname: Linux mykola-K53E 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 17:26:33 UTC 2013 i686 i686 i686 GNU/Linux What doesn't work is language switching, opening terminal window, laptop hotkeys for managing sound, brightness, etc. Alt-Tab works though. Also using hotkeys for moving windows between workspaces works only after changing workspace at least once. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mykola 2348 F pulseaudio /dev/snd/pcmC0D0p: mykola 2348 F...m pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=84a97c42-b6b4-4fe5-9cd9-95d88e43aec2 InstallationDate: Installed on 2013-01-28 (300 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: ASUSTeK Computer Inc. K53E MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=c1b9e67b-cbb4-4cf3-a17e-787e665824fc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 Tags: saucy Uname: Linux 3.11.0-13-generic i686 UpgradeStatus: Upgraded to saucy on 2013-10-18 (38 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo wireshark dmi.bios.date: 08/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K53E.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K53E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53E.214:bd08/18/2011:svnASUSTeKComputerInc.:pnK53E:pvr1.0:rvnASUSTeKComputerInc.:rnK53E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1254728/+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 1233176] Re: Alarm notifications do not appear when an alarm is triggered
** Tags added: avengers ** Also affects: ubuntu-clock-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1233176 Title: Alarm notifications do not appear when an alarm is triggered Status in The Date and Time Indicator: Fix Committed Status in Clock application for Ubuntu devices: Triaged Status in URL Dispatcher: Fix Released Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “ubuntu-clock-app” package in Ubuntu: New Status in “url-dispatcher” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Confirmed Bug description: There is no indication when an alarm goes off. This should be done by the platform which opens the clock app when an alarm is triggered. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1233176/+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 1255356] Re: gdm-session-worker crashed with SIGSEGV in malloc_consolidate()
The problem seems to go away after backporting accountsservice from quantal. ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- 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/1255356 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() Status in “accountsservice” package in Ubuntu: New Status in “gdm” package in Ubuntu: New Bug description: On an otherwise clean and up-to-date precise installation, the conditions to reproduce this gdm crash seem to be: * libnss-ldapd is installed and configured for at least passwd lookups in nsswitch. * the LDAP user being tested is not in the gdm user list. After filling in credentials and pressing Login, gdm-session-worker crashes and the login screen hangs waiting for it. For a user who is already shown in the list, whether because of being present in /etc/passwd or the wtmp history, logging in seems to work normally. I don't know whether this bug is in gdm, nss-pam-ldapd, accountsservice, or somewhere else, but gdm seems like a reasonable place to start. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Nov 26 15:46:58 2013 ExecutablePath: /usr/lib/gdm/gdm-session-worker MarkForUpload: True ProcCmdline: /usr/lib/gdm/gdm-session-worker ProcEnviron: LANG=en_CA.UTF-8 TERM=linux LANGUAGE=en_CA: PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f99dc051e08 malloc_consolidate+232: mov 0x8(%r12),%r15 PC (0x7f99dc051e08) ok source 0x8(%r12) (0x028e7388) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gdm StacktraceTop: malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4272 malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4247 _int_malloc (av=0x7f99dc38c720, bytes=1072) at malloc.c:3564 __GI___libc_malloc (bytes=1072) at malloc.c:2924 pam_modutil_getpwnam () from /lib/x86_64-linux-gnu/libpam.so.0 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1255356/+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 1255653] [NEW] Click apps nearly impossible to install.
Public bug reported: So, testing latest image 34, I decided to try installing some click apps. I started with a very simple webapp (18k download size), and this worked reasonably well. Then I tried installing SleepyTime, which is a few MBs to download. During the download, I accidentally swiped left (eg, to see the previous app, not an edge swipe). When I swiped back to SleepyTime, the download had frozen. After some seconds, the progress meter reverted to an 'Install' button, which was unresponsive. Then I thought I'd reboot to get things into a fresh state, tried to install SleepyTime again, but this time I thought ok! I won't touch anything, so it can install uninterrupted! and of course, then the screen locked while the app was downloading. When I unlocked the screen, the app detail screen was gone and I was looking at the app grid. When I clicked on SleepyTime again, the download meter was gone and there was the 'Install' button again. When I clicked on the install button, it turned into a progress meter, stayed at 0% for about 10 seconds, and then reverted to an Install button again. So basically, it seems that in order to install an app, I have to very carefully poke at the screen in order to keep it awake, without accidentally navigating away from the download screen. Leaving it alone, navigating away, etc all cause downloads to fail, and once a download has failed, all future downloads can't even start. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-lens-applications (not installed) Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu1 Architecture: armhf Date: Wed Nov 27 19:38:59 2013 InstallationDate: Installed on 2013-11-27 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131127.1) SourcePackage: unity-lens-applications UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 Importance: Critical Status: New ** Affects: unity-lens-applications (Ubuntu) Importance: Critical Status: New ** Tags: apport-bug armhf trusty ** Also affects: unity8 Importance: Undecided Status: New ** Changed in: unity-lens-applications (Ubuntu) Importance: Undecided = Critical ** Changed in: unity8 Importance: Undecided = Critical -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-applications in Ubuntu. https://bugs.launchpad.net/bugs/1255653 Title: Click apps nearly impossible to install. Status in The Unity 8 shell: New Status in “unity-lens-applications” package in Ubuntu: New Bug description: So, testing latest image 34, I decided to try installing some click apps. I started with a very simple webapp (18k download size), and this worked reasonably well. Then I tried installing SleepyTime, which is a few MBs to download. During the download, I accidentally swiped left (eg, to see the previous app, not an edge swipe). When I swiped back to SleepyTime, the download had frozen. After some seconds, the progress meter reverted to an 'Install' button, which was unresponsive. Then I thought I'd reboot to get things into a fresh state, tried to install SleepyTime again, but this time I thought ok! I won't touch anything, so it can install uninterrupted! and of course, then the screen locked while the app was downloading. When I unlocked the screen, the app detail screen was gone and I was looking at the app grid. When I clicked on SleepyTime again, the download meter was gone and there was the 'Install' button again. When I clicked on the install button, it turned into a progress meter, stayed at 0% for about 10 seconds, and then reverted to an Install button again. So basically, it seems that in order to install an app, I have to very carefully poke at the screen in order to keep it awake, without accidentally navigating away from the download screen. Leaving it alone, navigating away, etc all cause downloads to fail, and once a download has failed, all future downloads can't even start. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-lens-applications (not installed) Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu1 Architecture: armhf Date: Wed Nov 27 19:38:59 2013 InstallationDate: Installed on 2013-11-27 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20131127.1) SourcePackage: unity-lens-applications UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1255653/+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 1208204] Re: indicator-sound no longer functions with xfce4-indicator-plugin
In response to comment #90: I still observe the same issue on a fresh Xubuntu 14.04 amd64. The difference to the Saucy release is that I can't apply the fix from comment #5, because I don't have /usr/share/dbus-1/services/indicator-sound.service. Where is the file now? Is it dynamically generated, or has something in the package changed? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1208204 Title: indicator-sound no longer functions with xfce4-indicator-plugin Status in Sound Menu: New Status in Ubuntu Studio: New Status in “indicator-sound” package in Ubuntu: Triaged Bug description: *** Problems with the default Bluetooth indicator on Xfce are caused by a different, unrelated bug. See https://bugs.launchpad.net/ubuntu/+source/glipper/+bug/1203888 *** downgrading to the previous version, indicator- sound_12.10.2daily13.04.12-0ubuntu1_amd64 from Raring allows the sound indicator to function in Saucy. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-sound 12.10.2+13.10.20130731-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu2 Architecture: amd64 Date: Sun Aug 4 12:20:02 2013 InstallationDate: Installed on 2012-08-01 (367 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120801) MarkForUpload: True SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sound/+bug/1208204/+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 1255356] Re: gdm-session-worker crashed with SIGSEGV in malloc_consolidate()
Fixing the double free of user-language as per http://cgit.freedesktop.org/accountsservice/commit/?id=4399a03316bfc2b5a6f666b0606e5eece167d44a seems to be sufficient to fix this. I'll test this a few more times to convince myself of that. ** No longer affects: gdm (Ubuntu) -- 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/1255356 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() Status in “accountsservice” package in Ubuntu: New Bug description: On an otherwise clean and up-to-date precise installation, the conditions to reproduce this gdm crash seem to be: * libnss-ldapd is installed and configured for at least passwd lookups in nsswitch. * the LDAP user being tested is not in the gdm user list. After filling in credentials and pressing Login, gdm-session-worker crashes and the login screen hangs waiting for it. For a user who is already shown in the list, whether because of being present in /etc/passwd or the wtmp history, logging in seems to work normally. I don't know whether this bug is in gdm, nss-pam-ldapd, accountsservice, or somewhere else, but gdm seems like a reasonable place to start. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Nov 26 15:46:58 2013 ExecutablePath: /usr/lib/gdm/gdm-session-worker MarkForUpload: True ProcCmdline: /usr/lib/gdm/gdm-session-worker ProcEnviron: LANG=en_CA.UTF-8 TERM=linux LANGUAGE=en_CA: PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f99dc051e08 malloc_consolidate+232: mov 0x8(%r12),%r15 PC (0x7f99dc051e08) ok source 0x8(%r12) (0x028e7388) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gdm StacktraceTop: malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4272 malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4247 _int_malloc (av=0x7f99dc38c720, bytes=1072) at malloc.c:3564 __GI___libc_malloc (bytes=1072) at malloc.c:2924 pam_modutil_getpwnam () from /lib/x86_64-linux-gnu/libpam.so.0 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1255356/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
I reported bug #1255356 separately and discovered the same double free as the cause. I have verified that accountsservice from precise-proposed fixes the bug reported by Wookey and fixes the bug I reported as well. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Committed Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1067414] Re: gdm crashes if a user account is deleted or added (nslcd, ldap)
*** This bug is a duplicate of bug 1004515 *** https://bugs.launchpad.net/bugs/1004515 ** This bug has been marked a duplicate of bug 1004515 segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1067414 Title: gdm crashes if a user account is deleted or added (nslcd,ldap) Status in “accountsservice” package in Ubuntu: Confirmed Status in “gdm” package in Ubuntu: Confirmed Bug description: Scenario: * LDAP User Account (NFS Home Directory) * nslcd and gdm are used * user account information is manipulated, e.g. apt-get remove --purge tomcat7* Result: gdm session crashed Syslog: Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l This can be reproduced on 2 different machines and user accounts ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Oct 16 18:00:05 2012 SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1255716] Re: Running the click command on the desktop greeter seems wrong
I guess the click command should be used on the phone only for now... Btw the indicator logs have quite some weird warning like exiting: service couldn't acquire or lost ownership of busname, not sure if there is a timing issue with the upstart jobs -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255716 Title: Running the click command on the desktop greeter seems wrong Status in The Date and Time Indicator: New Status in “indicator-datetime” package in Ubuntu: New Bug description: Using current trusty, /var/lib/lightdm/.cache/upstart/indicator- datetime.log contains those warnings g_object_unref: assertion 'G_IS_OBJECT (object)' failed 'com.ubuntu.clock does not exist in any database for user lightdm' [Errno 2] No such file or directory: 'com.ubuntu.clock' (process:4779): Indicator-Datetime-WARNING **: indicator-datetime cannot show EDS appointments: Indicator-Datetime-Message: exiting: service couldn't acquire or lost ownership of busname Reading a bootchart confirms that the indicator runs the click command (it's installed on my desktop configuration for testing) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1255716/+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 1255716] [NEW] Running the click command on the desktop greeter seems wrong
Public bug reported: Using current trusty, /var/lib/lightdm/.cache/upstart/indicator- datetime.log contains those warnings g_object_unref: assertion 'G_IS_OBJECT (object)' failed 'com.ubuntu.clock does not exist in any database for user lightdm' [Errno 2] No such file or directory: 'com.ubuntu.clock' (process:4779): Indicator-Datetime-WARNING **: indicator-datetime cannot show EDS appointments: Indicator-Datetime-Message: exiting: service couldn't acquire or lost ownership of busname Reading a bootchart confirms that the indicator runs the click command (it's installed on my desktop configuration for testing) ** Affects: indicator-datetime Importance: High Assignee: Charles Kerr (charlesk) Status: New ** Affects: indicator-datetime (Ubuntu) Importance: High Status: New ** Also affects: indicator-datetime Importance: Undecided Status: New ** Changed in: indicator-datetime Importance: Undecided = High ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided = High ** Changed in: indicator-datetime Assignee: (unassigned) = Charles Kerr (charlesk) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255716 Title: Running the click command on the desktop greeter seems wrong Status in The Date and Time Indicator: New Status in “indicator-datetime” package in Ubuntu: New Bug description: Using current trusty, /var/lib/lightdm/.cache/upstart/indicator- datetime.log contains those warnings g_object_unref: assertion 'G_IS_OBJECT (object)' failed 'com.ubuntu.clock does not exist in any database for user lightdm' [Errno 2] No such file or directory: 'com.ubuntu.clock' (process:4779): Indicator-Datetime-WARNING **: indicator-datetime cannot show EDS appointments: Indicator-Datetime-Message: exiting: service couldn't acquire or lost ownership of busname Reading a bootchart confirms that the indicator runs the click command (it's installed on my desktop configuration for testing) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1255716/+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 1255719] [NEW] Upstart job keeps respawing indicator-sync on the greeter
Public bug reported: Using trusty, /var/lib/lightdm/.cache/upstart/indicator-sync.log indicates that upstart keeps trying spawning indicator-sync which exit with No watchers, service time out. The indicator is not supposed to be used on the greeter, the upstart job there seems like it should be smarter... ** Affects: indicator-sync Importance: High Assignee: Ted Gould (ted) Status: New ** Affects: indicator-sync (Ubuntu) Importance: High Status: New ** Changed in: indicator-sync (Ubuntu) Importance: Undecided = High ** Also affects: indicator-sync Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sync in Ubuntu. https://bugs.launchpad.net/bugs/1255719 Title: Upstart job keeps respawing indicator-sync on the greeter Status in The Sync Menu: New Status in “indicator-sync” package in Ubuntu: New Bug description: Using trusty, /var/lib/lightdm/.cache/upstart/indicator-sync.log indicates that upstart keeps trying spawning indicator-sync which exit with No watchers, service time out. The indicator is not supposed to be used on the greeter, the upstart job there seems like it should be smarter... To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sync/+bug/1255719/+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 1255719] Re: Upstart jobs keeps respawing indicator-sync on the greeter
Ted, assigning to you since you added the upstart job. That's something Lars warned about previous cycle, but we forgot about it before merging, the dbus activation was letting the indicator control if it needed to run or to exit. We profile need to make the upstart job smarter (like maybe tweak the signal to specify the session type and start e.g sync only in desktop mode) Other indicators have similar issues, but they don't keep respawning because they stopped using libindicator so they don't have the exit- when-no-listener behaviour ** Changed in: indicator-sync Importance: Undecided = High ** Changed in: indicator-sync Assignee: (unassigned) = Ted Gould (ted) ** Summary changed: - Upstart jobs keeps respawing indicator-sync on the greeter + Upstart job keeps respawing indicator-sync on the greeter -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sync in Ubuntu. https://bugs.launchpad.net/bugs/1255719 Title: Upstart job keeps respawing indicator-sync on the greeter Status in The Sync Menu: New Status in “indicator-sync” package in Ubuntu: New Bug description: Using trusty, /var/lib/lightdm/.cache/upstart/indicator-sync.log indicates that upstart keeps trying spawning indicator-sync which exit with No watchers, service time out. The indicator is not supposed to be used on the greeter, the upstart job there seems like it should be smarter... To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sync/+bug/1255719/+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 1251460] Re: crash in clock-live.c's set_detect_location_enabled()
This bug was fixed in the package indicator-datetime - 13.10.0+14.04.20131125-0ubuntu1 --- indicator-datetime (13.10.0+14.04.20131125-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Switch the build system to cmake. (LP: #1237509) * As per the spec, let users show the year in indicator-datetime. (LP: #465689) * Don't generate g_critical() messages in the log when the timezone object is clearing its value. . (LP: #1246532) * When in the desktop-greeter mode, don't allow clicking on calendar dates to launch evolution. (LP: #1246812) * Use g_icon_serialize() output when setting menuitems' icon property. * In src/clock-live.c, pass the right pointer to on_detect_location_changed(). (LP: #1251460) [ Ted Gould ] * Adding a phone_greeter profile. * Upstart Job. (LP: #1185565) [ Ubuntu daily release ] * Automatic snapshot from revision 289 -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 25 Nov 2013 03:55:52 + ** Changed in: indicator-datetime (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1251460 Title: crash in clock-live.c's set_detect_location_enabled() Status in The Date and Time Indicator: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: clock-live.c has a private function with this signature: static void on_detect_location_changed (IndicatorDatetimeClockLive * self) and indicator_datetime_clock_live_init() has this code: g_signal_connect (p-settings, changed:: SETTINGS_SHOW_DETECTED_S, G_CALLBACK(on_detect_location_changed), self); This should be _connect_swapped() s.t. self is passed to on_detect_location_changed(). To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1251460/+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 1246532] Re: warnings logged on startup: g_string_assign: assertion 'rval != NULL' failed
This bug was fixed in the package indicator-datetime - 13.10.0+14.04.20131125-0ubuntu1 --- indicator-datetime (13.10.0+14.04.20131125-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Switch the build system to cmake. (LP: #1237509) * As per the spec, let users show the year in indicator-datetime. (LP: #465689) * Don't generate g_critical() messages in the log when the timezone object is clearing its value. . (LP: #1246532) * When in the desktop-greeter mode, don't allow clicking on calendar dates to launch evolution. (LP: #1246812) * Use g_icon_serialize() output when setting menuitems' icon property. * In src/clock-live.c, pass the right pointer to on_detect_location_changed(). (LP: #1251460) [ Ted Gould ] * Adding a phone_greeter profile. * Upstart Job. (LP: #1185565) [ Ubuntu daily release ] * Automatic snapshot from revision 289 -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 25 Nov 2013 03:55:52 + ** Changed in: indicator-datetime (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246532 Title: warnings logged on startup: g_string_assign: assertion 'rval != NULL' failed Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: When starting up, indicator-datetime repeats this series of g_critical()s a half-dozen times or so: (process:5347): GLib-CRITICAL **: g_string_assign: assertion 'rval != NULL' failed (process:5347): GLib-CRITICAL **: g_string_assign: assertion 'rval != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246532/+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 1185565] Re: Indicators should have Upstart jobs
This bug was fixed in the package indicator-datetime - 13.10.0+14.04.20131125-0ubuntu1 --- indicator-datetime (13.10.0+14.04.20131125-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Switch the build system to cmake. (LP: #1237509) * As per the spec, let users show the year in indicator-datetime. (LP: #465689) * Don't generate g_critical() messages in the log when the timezone object is clearing its value. . (LP: #1246532) * When in the desktop-greeter mode, don't allow clicking on calendar dates to launch evolution. (LP: #1246812) * Use g_icon_serialize() output when setting menuitems' icon property. * In src/clock-live.c, pass the right pointer to on_detect_location_changed(). (LP: #1251460) [ Ted Gould ] * Adding a phone_greeter profile. * Upstart Job. (LP: #1185565) [ Ubuntu daily release ] * Automatic snapshot from revision 289 -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 25 Nov 2013 03:55:52 + ** Changed in: indicator-datetime (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages, dx-packages, dx-packages, dx-packages https://bugs.launchpad.net/bugs/1185565 Title: Indicators should have Upstart jobs Status in Application Indicators: Fix Committed Status in The Date and Time Indicator: Fix Committed Status in Indicator Location: Fix Committed Status in Network Menu: Fix Released Status in The Power Indicator: Fix Committed Status in The Session Menu: Fix Committed Status in Sound Menu: Fix Committed Status in The Sync Menu: Fix Committed Status in Libindicator: Confirmed Status in Unity: Fix Released Status in “indicator-application” package in Ubuntu: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-session” package in Ubuntu: Fix Released Status in “indicator-sound” package in Ubuntu: Fix Released Status in “indicator-sync” package in Ubuntu: Fix Released Status in “ubiquity” package in Ubuntu: In Progress Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: Indicators should move over to using the upstart jobs to get better logging and management of their processes. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-application/+bug/1185565/+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 1237509] Re: test coverage is far too low
This bug was fixed in the package indicator-datetime - 13.10.0+14.04.20131125-0ubuntu1 --- indicator-datetime (13.10.0+14.04.20131125-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Switch the build system to cmake. (LP: #1237509) * As per the spec, let users show the year in indicator-datetime. (LP: #465689) * Don't generate g_critical() messages in the log when the timezone object is clearing its value. . (LP: #1246532) * When in the desktop-greeter mode, don't allow clicking on calendar dates to launch evolution. (LP: #1246812) * Use g_icon_serialize() output when setting menuitems' icon property. * In src/clock-live.c, pass the right pointer to on_detect_location_changed(). (LP: #1251460) [ Ted Gould ] * Adding a phone_greeter profile. * Upstart Job. (LP: #1185565) [ Ubuntu daily release ] * Automatic snapshot from revision 289 -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 25 Nov 2013 03:55:52 + ** Changed in: indicator-datetime (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1237509 Title: test coverage is far too low Status in The Date and Time Indicator: In Progress Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: Improving test coverage is an ongoing goal across lots of our codebases, but the ratio of features to tests in datetime is just insane. I'm adding the alarm features right now on a tight schedule and it would take me days to add tests for this code because there's absolutely no framework in tests/ for unit testing features in datetime, much less features whose states change over time. So, adding this ticket as a line in the sand to remind myself to improve this in the 14.04 cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1237509/+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 465689] Re: Ubuntu Clock Won't Show Year
This bug was fixed in the package indicator-datetime - 13.10.0+14.04.20131125-0ubuntu1 --- indicator-datetime (13.10.0+14.04.20131125-0ubuntu1) trusty; urgency=low [ Charles Kerr ] * Switch the build system to cmake. (LP: #1237509) * As per the spec, let users show the year in indicator-datetime. (LP: #465689) * Don't generate g_critical() messages in the log when the timezone object is clearing its value. . (LP: #1246532) * When in the desktop-greeter mode, don't allow clicking on calendar dates to launch evolution. (LP: #1246812) * Use g_icon_serialize() output when setting menuitems' icon property. * In src/clock-live.c, pass the right pointer to on_detect_location_changed(). (LP: #1251460) [ Ted Gould ] * Adding a phone_greeter profile. * Upstart Job. (LP: #1185565) [ Ubuntu daily release ] * Automatic snapshot from revision 289 -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 25 Nov 2013 03:55:52 + ** Changed in: indicator-datetime (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/465689 Title: Ubuntu Clock Won't Show Year Status in Desktop panel for GNOME: In Progress Status in The Date and Time Indicator: Fix Committed Status in “gnome-panel” package in Ubuntu: Triaged Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: indicator-datetime, Ubuntu 12.10 The Ubuntu menu bar clock offers no setting to show year. Yes, I know what year it is, but I have very good reason for wanting it shown. For years, I've been collecting screen-shots, when I'm doing something I think is pretty cool. When I use to use windows, these screen shots (over the years) have always showed the current year. However, since April of 2007 (The date I started using Ubuntu exclusively), my screen shots have not included the year, because the Gnome clock doesn't provide this capability. https://wiki.ubuntu.com/TimeAndDate#settings: 'Year' should be both insensitive and unchecked whenever 'Date and month' is unchecked... To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/465689/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
** Changed in: accountsservice (Ubuntu) Assignee: shan (shan40) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Committed Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 649800] Re: datetime indicator won't show today's date if you've ever clicked on any others
I can confirm that. It's quite confusing. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/649800 Title: datetime indicator won't show today's date if you've ever clicked on any others Status in Ayatana Design: Confirmed Status in The Date and Time Indicator: Fix Released Status in Unity Foundations: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Natty: Fix Released Bug description: Binary package hint: indicator-datetime If you click on the date/time indicator and scroll through to any other month or day, it remains where you left it even after you click elsewhere and then back to re-open it. This means that if I browse January 1970, I can never learn from this tool what today's date is, as it will always show January 1970. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: indicator-datetime 0.0.6-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 Architecture: amd64 Date: Tue Sep 28 14:09:17 2010 EcryptfsInUse: Yes ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-datetime To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/649800/+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 1233176] Re: Alarm notifications do not appear when an alarm is triggered
** No longer affects: ubuntu-clock-app (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1233176 Title: Alarm notifications do not appear when an alarm is triggered Status in The Date and Time Indicator: Fix Committed Status in Clock application for Ubuntu devices: Triaged Status in URL Dispatcher: Fix Released Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “url-dispatcher” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Confirmed Bug description: There is no indication when an alarm goes off. This should be done by the platform which opens the clock app when an alarm is triggered. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1233176/+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
