[Dx-packages] [Bug 1446848] [NEW] Ubuntu shuts down after cancelling shut down
You have been subscribed to a public bug: In the Session Management indicator, there is an option to shut down the computer. If I select that option, a pop-up is presented asking me to confirm that I want to shut down the computer. If I select Cancel, or if I click the X on the window, Ubuntu proceeds to shut down anyway. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-panel 4.11.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 21 15:28:27 2015 InstallationDate: Installed on 2014-10-27 (176 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfce4-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- Ubuntu shuts down after cancelling shut down https://bugs.launchpad.net/bugs/1446848 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. -- 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 1446848] Re: Ubuntu shuts down after cancelling shut down
** Package changed: xfce4-panel (Ubuntu) => indicator-session (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1446848 Title: Ubuntu shuts down after cancelling shut down Status in indicator-session package in Ubuntu: New Bug description: In the Session Management indicator, there is an option to shut down the computer. If I select that option, a pop-up is presented asking me to confirm that I want to shut down the computer. If I select Cancel, or if I click the X on the window, Ubuntu proceeds to shut down anyway. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-panel 4.11.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 21 15:28:27 2015 InstallationDate: Installed on 2014-10-27 (176 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfce4-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1446848/+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 1437242] Re: Event notification no text
** Changed in: ubuntu-calendar-app Status: New => Confirmed -- 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/1437242 Title: Event notification no text Status in Calendar application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: Invalid Bug description: Aquaris, build 20. An audio alert from Calendar this morning but no accompanying text notification, no events shown in Today scope and no notification in top menu or in the 'circle'. Left wondering at first what the harp sound meant. Sound was at the exact time of the appointment. Fortunately I was there on time ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437242/+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 1437880] Re: no calendar notifications
*** This bug is a duplicate of bug 1437242 *** https://bugs.launchpad.net/bugs/1437242 ** This bug is no longer a duplicate of bug 1437882 no notification at the reminder of a google calendar event ** This bug has been marked a duplicate of bug 1437242 Event notification no text -- 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/1437880 Title: no calendar notifications Status in Calendar application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New Bug description: When adding a new calendar item in google calendar, there is no notification at the time of the appointment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437880/+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 1437882] Re: no notification at the reminder of a google calendar event
*** This bug is a duplicate of bug 1437242 *** https://bugs.launchpad.net/bugs/1437242 ** This bug has been marked a duplicate of bug 1437242 Event notification no text -- 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/1437882 Title: no notification at the reminder of a google calendar event Status in Calendar application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New Bug description: When setting a reminder in an event in google calendar, the reminder does not show up at the reminder time. Example: set event at 18:00 set reminder at 15 minutes before. calendar on the phone is synced (manually) and the event is on the today scope. There is no alarm or notification at 17:45. There is an alarm at 18:00, but no notification in the home screen or notification bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437882/+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 1437242] Re: Event notification no text
*** This bug is a duplicate of bug 1440111 *** https://bugs.launchpad.net/bugs/1440111 ** This bug has been marked a duplicate of bug 1440111 Reminder notifications are not integrated into system notifications -- 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/1437242 Title: Event notification no text Status in Calendar application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: Invalid Bug description: Aquaris, build 20. An audio alert from Calendar this morning but no accompanying text notification, no events shown in Today scope and no notification in top menu or in the 'circle'. Left wondering at first what the harp sound meant. Sound was at the exact time of the appointment. Fortunately I was there on time ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437242/+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 1437880] Re: no calendar notifications
*** This bug is a duplicate of bug 1440111 *** https://bugs.launchpad.net/bugs/1440111 ** This bug is no longer a duplicate of bug 1437242 Event notification no text ** This bug has been marked a duplicate of bug 1440111 Reminder notifications are not integrated into system notifications -- 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/1437880 Title: no calendar notifications Status in Calendar application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New Bug description: When adding a new calendar item in google calendar, there is no notification at the time of the appointment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437880/+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 1437882] Re: no notification at the reminder of a google calendar event
*** This bug is a duplicate of bug 1440111 *** https://bugs.launchpad.net/bugs/1440111 ** This bug is no longer a duplicate of bug 1437242 Event notification no text ** This bug has been marked a duplicate of bug 1440111 Reminder notifications are not integrated into system notifications -- 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/1437882 Title: no notification at the reminder of a google calendar event Status in Calendar application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New Bug description: When setting a reminder in an event in google calendar, the reminder does not show up at the reminder time. Example: set event at 18:00 set reminder at 15 minutes before. calendar on the phone is synced (manually) and the event is on the today scope. There is no alarm or notification at 17:45. There is an alarm at 18:00, but no notification in the home screen or notification bar. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1437882/+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 1440111] Re: Reminder notifications are not integrated into system notifications
Also there is no text notification on what event was triggered. There just is a sound. I was wondering for a few minuten why my phone played a sound and did not show any information. ** Changed in: ubuntu-calendar-app Status: New => Confirmed -- 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/1440111 Title: Reminder notifications are not integrated into system notifications Status in Calendar application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: Invalid Bug description: The calendar app does not use the standard notification system. You can't find it in the "Notifications" area of System Settings, and it uses its own notification sound regardless of what is set in "Sound". Also, reminders are not muted when the phone is in silent mode (I guess it's related). I'm on bq Aquaris, r20 and with the latest calendar-app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1440111/+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 1372254] Re: New Event in Calendar app not scheduled for the correct time zone.
I guess this fix is already deployed? -- 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/1372254 Title: New Event in Calendar app not scheduled for the correct time zone. Status in Calendar application for Ubuntu devices: Confirmed Status in indicator-datetime package in Ubuntu: Invalid Bug description: Phone - LGE Nexus 4 OS Version - Ubuntu 14.10 (r48) Time zone - America/Los Angeles - UTC-7 Steps to reproduce: Calendar view is for the month. 1 - select 'New Event' in the calendar app 2 - enter event information, set the date as the current date (21-Sep-2014) 3 - enter a start time = 21:30 4 - enter an end time = 22:30 5 - use 'Personal' calendar 6 - save the event An event is created for 'Tomorrow at 4:30 am', not 21:30 for the current date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1372254/+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 1451613] Re: Unity/compiz crashes when locking screen
I have the same problem, dmesg shows the following: [18317.562770] compiz[2269]: segfault at 3e8 ip 03e8 sp bfac448c error 14 in compiz[8048000+3000] -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+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 1451613] Re: Unity/compiz crashes when locking screen
Would be nice to have a backtrace. -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+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 1241101]
(In reply to Cristiano Gaviao from comment #42) > (In reply to Simone Perriello from comment #41) > > Tried, and it always crash every single time. > > Have you tried this? to create a desktop configuration file and set its > command as: > > env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0 /thepathToEclipse/eclipse > > I've being using this for months with many ubuntu machines and is working > great. Do you mean creating a .desktop file? If so, where I have to put the commands in the exec, right? Can you provide a template of a .desktop file? I've always launched Eclipse from terminal. -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
Re: [Dx-packages] [Bug 1241101]
-- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1241101]
(In reply to Simone Perriello from comment #43) > Do you mean creating a .desktop file? If so, where I have to put the > commands in the exec, right? Can you provide a template of a .desktop file? > I've always launched Eclipse from terminal. Yep, its a .desktop file that I've put in /usr/share/applications. [Desktop Entry] Version=4.5 Comment=Integrated Development Environment Exec=env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0 /opt/eclipse-ide/java-mars/eclipse/eclipse Type=Application Icon=eclipse-luna.xpm Terminal=false NoDisplay=false Categories=Development;IDE;Java StartupWMClass=Eclipse Name[en_US]=Eclipse Mars Java -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1241101]
(In reply to Cristiano Gaviao from comment #42) > (In reply to Simone Perriello from comment #41) > > Tried, and it always crash every single time. > > Have you tried this? to create a desktop configuration file and set its > command as: > > env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0 /thepathToEclipse/eclipse > > I've being using this for months with many ubuntu machines and is working > great. It doesn't work anyway. I've used this .desktop file [Desktop Entry] Version=4.4.2 Name=Eclipse-jee GenericName=IDE Comment=Programming IDE MimeType= Exec=env LIBOVERLAY_SCROLLBAR=0 SWT_GTK3=0 /opt/eclipse_all/eclipse-jee/eclipse TryExec=eclipse-jee Icon=/opt/eclipse_all/eclipse-jee/icon.xpm Type=Application Terminal=false Categories=IDE;Development; Eclipsee starts well, but crashes every time I try to move the pointer on Project->Build Working Set. It also crashes other times, but I haven't identified a pattern yet. -- 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/1241101 Title: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10 Status in Eclipse: Confirmed Status in gtk+2.0 package in Ubuntu: Triaged Status in unity package in Ubuntu: Invalid Status in gtk+2.0 package in Suse: New Bug description: Running smartgit 4.6.4 on 13.10 64 bits. After registering the product, smartgit crash when trying to open a new repository. Java error log : # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fa59061f9c0, pid=12494, tid=140349308167936 # # JRE version: 7.0_25-b30 # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libglib-2.0.so.0+0x389c0] g_str_hash+0x0 I tried different version of Java (Oracle v7 and v6 jre) with same result. Also, Eclipse display blank menus so there's a general java problem with displays. To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1241101/+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 1446848] Re: Ubuntu shuts down after cancelling shut down
Package: indicator-session 12.10.5+14.04.20150404-0ubuntu1 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1446848 Title: Ubuntu shuts down after cancelling shut down Status in indicator-session package in Ubuntu: New Bug description: In the Session Management indicator, there is an option to shut down the computer. If I select that option, a pop-up is presented asking me to confirm that I want to shut down the computer. If I select Cancel, or if I click the X on the window, Ubuntu proceeds to shut down anyway. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4-panel 4.11.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.9 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Apr 21 15:28:27 2015 InstallationDate: Installed on 2014-10-27 (176 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfce4-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1446848/+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 1435348] Re: qtcreator recently used file/project submenu empty
I can confirm this bug - out of the box my menu isn't working. Little bit annoying. -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1435348 Title: qtcreator recently used file/project submenu empty Status in appmenu-qt5 package in Ubuntu: In Progress Status in qtcreator-plugin-ubuntu package in Ubuntu: Invalid Bug description: Using current vivid, with integrated menu (appmenu-qt5), the qtcreator files-> recent files/projects submenus are empty, they work fine if the qt theme env variable is empty (use local menus instead) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1435348/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
Mh, I think we should fix the problem in unity-settings-daemon, by connecting at the com.canonical.Unity.Session.Locked signal instead. Since in unity the screensaver != lockscreen, and we emit the org.gnome.ScreenSaver.ActiveChanged only when the screensaver is shown (and this generally happens after that the lockscreen has been configured). ** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Triaged ** Changed in: unity-settings-daemon (Ubuntu Trusty) Status: New => Triaged ** Changed in: unity-settings-daemon (Ubuntu Utopic) Status: New => Triaged ** Changed in: unity-settings-daemon (Ubuntu Vivid) Status: New => Triaged ** Changed in: unity (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: unity (Ubuntu Utopic) Status: New => Won't Fix -- 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in Unity: Confirmed Status in unity package in Ubuntu: Won't Fix Status in unity-settings-daemon package in Ubuntu: Triaged Status in unity source package in Trusty: Triaged Status in unity-settings-daemon source package in Trusty: Triaged Status in unity source package in Utopic: Triaged Status in unity-settings-daemon source package in Utopic: Triaged Status in unity source package in Vivid: Won't Fix Status in unity-settings-daemon source package in Vivid: Triaged Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor "type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver'" 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438870/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
** Changed in: unity-settings-daemon (Ubuntu) Importance: Undecided => High ** Changed in: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided => High ** Changed in: unity-settings-daemon (Ubuntu Utopic) Importance: Undecided => High ** Changed in: unity-settings-daemon (Ubuntu Vivid) Importance: Undecided => High ** Changed in: unity (Ubuntu) Status: New => Triaged ** Changed in: unity (Ubuntu Trusty) Status: Won't Fix => Triaged ** Changed in: unity (Ubuntu Utopic) Status: Won't Fix => Triaged ** Changed in: unity (Ubuntu Vivid) Status: New => Triaged ** Changed in: unity 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in Unity: Confirmed Status in unity package in Ubuntu: Won't Fix Status in unity-settings-daemon package in Ubuntu: Triaged Status in unity source package in Trusty: Triaged Status in unity-settings-daemon source package in Trusty: Triaged Status in unity source package in Utopic: Triaged Status in unity-settings-daemon source package in Utopic: Triaged Status in unity source package in Vivid: Won't Fix Status in unity-settings-daemon source package in Vivid: Triaged Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor "type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver'" 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438870/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
** Changed in: unity (Ubuntu Vivid) Status: Triaged => Won't Fix ** Changed in: unity (Ubuntu) Status: Triaged => Won't Fix -- 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in Unity: Confirmed Status in unity package in Ubuntu: Won't Fix Status in unity-settings-daemon package in Ubuntu: Triaged Status in unity source package in Trusty: Triaged Status in unity-settings-daemon source package in Trusty: Triaged Status in unity source package in Utopic: Triaged Status in unity-settings-daemon source package in Utopic: Triaged Status in unity source package in Vivid: Won't Fix Status in unity-settings-daemon source package in Vivid: Triaged Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor "type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver'" 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438870/+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 1443178] Re: Accounts Service always relies on language fallback if never set by the user
Hello Ricardo, or anyone else affected,
Accepted accountsservice into trusty-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.35-0ubuntu7.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: accountsservice (Ubuntu Trusty)
Status: In Progress => Fix Committed
** Tags added: verification-needed
--
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/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Trusty:
Fix Committed
Status in accountsservice source package in Vivid:
In Progress
Bug description:
trusty and vivid SRU requests
=
[Impact]
Until a user has set the language or regional formats explicitly,
accountsservice makes the system default values available. The code
for 'calculating' the system defaults is expensive, and it's triggered
frequently. The case in the original description of this bug report is
one example of bad performance for this reason. Another example is a
system with many users (see e.g. bug #1350393).
This upload adds a couple of static variables inside the function in
question, to avoid that the expensive code is executed at each
invocation. Under certain conditions this improves the performance
significantly.
[Test Case]
Hmm.. There is no easy use case to reproduce the bug. The original
description below gives a hint.
[Regression Potential]
On a multi-user system, if the system defaults in /etc/default/locale
are changed, accountsservice will keep providing the old system
default values until the system is rebooted. (Previously it took
effect instantly.) I think the advantages with the proposed change
outweigh this subtle change in behavior (which hardly anyone will
notice anyway).
Can't think of anything besides that.
[Original description]
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_stri
[Dx-packages] [Bug 1443178] Re: Accounts Service always relies on language fallback if never set by the user
Hello Ricardo, or anyone else affected,
Accepted accountsservice into vivid-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/accountsservice/0.6.37-1ubuntu10.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Your feedback will aid us getting this update
out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed. In either case, details of your testing will help
us make a better decision.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: accountsservice (Ubuntu Vivid)
Status: In Progress => Fix Committed
--
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/1443178
Title:
Accounts Service always relies on language fallback if never set by
the user
Status in the base for Ubuntu mobile products:
New
Status in accountsservice package in Ubuntu:
Fix Released
Status in accountsservice source package in Trusty:
Fix Committed
Status in accountsservice source package in Vivid:
Fix Committed
Bug description:
trusty and vivid SRU requests
=
[Impact]
Until a user has set the language or regional formats explicitly,
accountsservice makes the system default values available. The code
for 'calculating' the system defaults is expensive, and it's triggered
frequently. The case in the original description of this bug report is
one example of bad performance for this reason. Another example is a
system with many users (see e.g. bug #1350393).
This upload adds a couple of static variables inside the function in
question, to avoid that the expensive code is executed at each
invocation. Under certain conditions this improves the performance
significantly.
[Test Case]
Hmm.. There is no easy use case to reproduce the bug. The original
description below gives a hint.
[Regression Potential]
On a multi-user system, if the system defaults in /etc/default/locale
are changed, accountsservice will keep providing the old system
default values until the system is rebooted. (Previously it took
effect instantly.) I think the advantages with the proposed change
outweigh this subtle change in behavior (which hardly anyone will
notice anyway).
Can't think of anything besides that.
[Original description]
current build number: 169
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-12 20:38:14
version version: 169
version ubuntu: 20150412
version device: 20150210
version custom: 20150412
This causes a bad side effect when changing volume via indicator-
sound, as that will cause a sync to accountsservice in order to sync
the volume. Once that sync happens, it will request the user
properties, and in case the user doesn't have a valid language at
/var/lib/AccountsService/users/, it will always rely on the
fallback, which would be fine if calculating the fallback wasn't 't so
cpu or i/o intensive (and that happens multiple times).
As a test, just flash latest vivid image on mako, don't set any
language when the wizard shows up, run top and then change the volume
by pressing volume up/down. This is what I see with mako:
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
2609 phablet 20 0 499660 121220 52688 S 7.6 6.5 0:41.69 unity8
5600 phablet 20 03676 1760 1288 R 6.0 0.1 0:00.19
language-option
1312 root 20 0 211532 15572 11344 S 1.9 0.8 0:07.25
unity-system-co
1316 phablet 20 0 36532 3792 2928 S 1.3 0.2 0:01.66
accounts-daemon
And the reason why:
src/user.c
...
static void
user_get_property (GObject*object,
guint param_id,
GValue *value,
GParamSpec *pspec)
{
User *user = USER (object);
...
case PROP_LANGUAGE:
if (user->language)
g_value_set_string (value, user->language);
else
g_value_set_string (value, user_get_fallback_value
(user, "Language"));
break;
case PROP_FORMATS_LOCALE:
if (user->formats_locale)
g_value_set_string (value, user->formats_locale);
[Dx-packages] [Bug 1159249] Re: HUD does not show up over fullscreen window
Damn it! Why are you all ignoring me? I'm suffering from this "Fix" every single time I'm launching fullscreen game! Every click on "Alt" or "Super" causes multiple seconds of lost gameplay that is sometimes vital! Are you seriously backported this ugly "feature" without any possibility to restore original behavior? @azzar1 said he can add switch for this behavior, but there is no such option currently available. -- 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/1159249 Title: HUD does not show up over fullscreen window Status in Unity: Fix Released Status in Unity 7.2 series: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Bug description: [Impact] The HUD was not being rendered above fullscreen windows although it would grab the keyboard. [TEST CASE] 1. Open some site in firefox 2. Go to fullscreen mode (F11) 3. Press "Alt" once. 4 The HUD should appear and you should be able to interact with it. [REGRESSION POTENTIAL] No known regression potential. [OTHER INFO] The fix for Ubuntu 14.04 LTS was cherry picked from the Ubuntu "Vivid Vervet" dev release where it has been in production use for some time without apparent regression. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1159249/+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 1435348] Re: qtcreator recently used file/project submenu empty
** Changed in: appmenu-qt5 (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1435348 Title: qtcreator recently used file/project submenu empty Status in appmenu-qt5 package in Ubuntu: In Progress Status in qtcreator-plugin-ubuntu package in Ubuntu: Invalid Bug description: Using current vivid, with integrated menu (appmenu-qt5), the qtcreator files-> recent files/projects submenus are empty, they work fine if the qt theme env variable is empty (use local menus instead) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1435348/+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
