[Dx-packages] [Bug 1301125] Re: Lock screen after idle time freezes unity
Lately I seem to be hit by this issue every time the desktop idles out to the lock screen. A workaround, that is not acceptable in the long run, seems to be to lock the screen manually every time I leave the computer, to prevent the idle timeout. -- 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/1301125 Title: Lock screen after idle time freezes unity Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Hello, I recently upgrade to 14.04. My system uses fglrx provided by 14.04. When I lock manually the screen, I get no problem. I can even sleep the system without problem. However, when the screen is locked by idle time, I cannot unlock it. At this point, I can see the screen but with some kind of translucent panel over it. Mouse also works. I tried to type blink the password but I had no luck. I only get a working system by going text mode (ctrl+alt+f1) and restarting lightdm. No dmesg or Xorg logs seems to indicate any error. The only strange log was in .xsession-errors.old: init: processos unity-settings-daemon main (2495) terminados com status 1 init: processos gnome-session (Unity) main (2539) terminados com status 1 init: processos unity-panel-service main (2572) terminados com status 1 init: processos hud main (2536) terminados com status 1 init: processo indicator-powermain (2740) morto pelo sinal TERM init: processo indicator-datetimemain (2741) morto pelo sinal TERM init: processo indicator-soundmain (2747) morto pelo sinal TERM init: processo indicator-printersmain (2748) morto pelo sinal TERM init: processo indicator-sessionmain (2768) morto pelo sinal TERM init: processo indicator-syncmain (2795) morto pelo sinal TERM init: processo update-notifier-crash (/var/crash/_usr_bin_istanbul.1000.crash)main (4987) morto pelo sinal TERM init: processos unity-panel-service-lockscreen main (7447) terminados com status 1 init: Disconnected from notified D-Bus bus init: processos at-spi2-registryd main (2538) terminados com status 1 But as it has no time info, I cannot tell when they happened. At least another user faces the same problem: http://ubuntuforums.org/showthread.php?t=2214421 And this seems to be different from bug 1283938 as pm sleep/wake works as expected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Apr 2 00:01:05 2014 DistUpgraded: 2014-03-31 21:24:46,145 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.11.0-18-generic, x86_64: installed fglrx-updates, 13.350.1, 3.13.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.11.0-18-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0012] InstallationDate: Installed on 2012-10-19 (529 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) JockeyStatus: kmod:wl - Broadcom STA wireless driver (Proprietário, Desativado, Não está em uso) [auto-install] kmod:fglrx - Video driver for the AMD graphics accelerators (Proprietário, Desativado, Não está em uso) kmod:fglrx_updates - ATI Fire GL (Proprietário, Habilitado, Não está em uso) MachineType: Dell Inc. XPS 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=6633d579-d782-47ec-ad5a-22abac1412a0 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-01 (1 days ago) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2:
[Dx-packages] [Bug 1363015] Re: App icons require shaping at every callsite
** Description changed:
- Currently, showing an app icon in the correct Ubuntu shape requires
- shaping it when you are using it.
-
- For example, ensuring that iconFrame is set to True when using
ListItem.Standard{}.
+ In list items, showing an app icon in the correct Ubuntu shape requires
shaping it when you are using it: ListItem.Standard{IconFrame: True}.
http://developer.ubuntu.com/api/devel/ubuntu-13.04/qml/ui-toolkit/qml-ubuntu-components-listitems0-standard.html
That property is set to True by default, but it's not obvious why it
should be, and list items aren't the only place that app icons get used.
The result is that several times now, app updates have ended up without the
appropriate frame:
- in the System Settings Updates list (bug 1354478)
- in the Notifications screen
- in the Launcher the frame is unintentionally different (bug 1332119).
Conversely, non-app icons have ended up *with* the frame by mistake:
- Display language (bug 1288866)
- Orientation Lock (bug 1365450)
- Ubuntu updates (bug 1367136).
- On the API design quality scale, this is roughly Read the
+ In notification bubbles, the opposite applies -- you have to set a hint to
use an *unshaped* icon: notify_notification_set_hint_string(m_notification,
x-canonical-non-shaped-icon, true).
+ https://wiki.ubuntu.com/Touch/Notifications#Elements_of_a_Notification
+
+ Predictably, this has resulted in cases of icons having frames when they
shouldn't:
+ - Wi-Fi network authentication (bug 1346904)
+ - Remove Account (bug 1350282).
+
+ On the API design quality scale, both of these are roughly Read the
implementation and you'll get it right. http://sweng.the-
- davies.net/Home/rustys-api-design-manifesto
+ davies.net/Home/rustys-api-design-manifesto Worse, they have opposite
+ defaults.
I suggest that the toolkit move all the way up to It's impossible to
get wrong, by always shaping an icon when it is an app icon, and never
otherwise. Whether an icon is an app icon could (I assume) be detected
by its path.
** Also affects: notify-osd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
In list items, showing an app icon in the correct Ubuntu shape requires
shaping it when you are using it: ListItem.Standard{IconFrame: True}.
http://developer.ubuntu.com/api/devel/ubuntu-13.04/qml/ui-toolkit/qml-ubuntu-components-listitems0-standard.html
That property is set to True by default, but it's not obvious why it
should be, and list items aren't the only place that app icons get used.
The result is that several times now, app updates have ended up without the
appropriate frame:
- in the System Settings Updates list (bug 1354478)
- in the Notifications screen
- in the Launcher the frame is unintentionally different (bug 1332119).
Conversely, non-app icons have ended up *with* the frame by mistake:
- Display language (bug 1288866)
- Orientation Lock (bug 1365450)
- Ubuntu updates (bug 1367136).
In notification bubbles, the opposite applies -- you have to set a hint to
use an *unshaped* icon: notify_notification_set_hint_string(m_notification,
x-canonical-non-shaped-icon, true).
https://wiki.ubuntu.com/Touch/Notifications#Elements_of_a_Notification
Predictably, this has resulted in cases of icons having frames when they
shouldn't:
- Wi-Fi network authentication (bug 1346904)
+ - alarms (bug 1346925)
- Remove Account (bug 1350282).
On the API design quality scale, both of these are roughly Read the
implementation and you'll get it right. http://sweng.the-
davies.net/Home/rustys-api-design-manifesto Worse, they have opposite
defaults.
I suggest that the toolkit move all the way up to It's impossible to
get wrong, by always shaping an icon when it is an app icon, and never
otherwise. Whether an icon is an app icon could (I assume) be detected
by its path.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to notify-osd in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1363015
Title:
App icons require shaping at every callsite
Status in “notify-osd” package in Ubuntu:
New
Status in “ubuntu-ui-toolkit” package in Ubuntu:
New
Bug description:
In list items, showing an app icon in the correct Ubuntu shape requires
shaping it when you are using it: ListItem.Standard{IconFrame: True}.
http://developer.ubuntu.com/api/devel/ubuntu-13.04/qml/ui-toolkit/qml-ubuntu-components-listitems0-standard.html
That property is set to True by default, but it's not obvious why it
should be, and list items aren't the only place that app icons get
used.
The result is that several times now, app updates have ended up without the
appropriate frame:
- in the System Settings Updates list (bug 1354478)
- in the Notifications screen
- in the Launcher the frame is unintentionally different (bug 1332119).
[Dx-packages] [Bug 1300650] Re: Should use separate schema for launcher items
** Changed in: unity8 (Ubuntu) Status: New = In Progress ** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu) Status: New = In Progress ** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu) Status: In Progress = Won't Fix ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Michael Zanetti (mzanetti) ** Changed in: unity8 (Ubuntu) Importance: Undecided = High ** Branch linked: lp:~mzanetti/unity8/rework-launcher-backend ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~mzanetti/unity/new-key-in-launcher-schema ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Michael Zanetti (mzanetti) ** Changed in: unity (Ubuntu) Importance: Undecided = High -- 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/1300650 Title: Should use separate schema for launcher items Status in The Sevilerow project: New Status in “gsettings-ubuntu-touch-schemas” package in Ubuntu: Won't Fix Status in “unity” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: We're using the schema from unity for launcher items, but we should instead use a custom one, since unity7 will never support click packages, so they're not compatible already. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140327.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14-0ubuntu1 Architecture: armhf Date: Tue Apr 1 09:30:11 2014 InstallationDate: Installed on 2014-04-01 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140401) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/sevilerow/+bug/1300650/+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 1352656] Re: ubuntu-app-launch-invalid-appid
Ted, that's one of the most reported issues on e.u.c for utopic, maybe we should turn that off if we don't plan to work on it? that would save bandwith for users and noise -- You received this bug notification because you are a member of DX Packages, which is subscribed to url-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1352656 Title: ubuntu-app-launch-invalid-appid Status in “url-dispatcher” package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding url-dispatcher. This problem was most recently seen with version 8.00+14.10.20140731.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/50ef8ac2301b5a70acb47d40d1efff412014d40b contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/url-dispatcher/+bug/1352656/+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 1001621] Re: appmenu-qt doesn't work with 32-bit apps on 64-bit system
** Changed in: unity (Ubuntu) Status: Confirmed = Invalid ** Changed in: unity Status: Confirmed = Invalid ** Changed in: appmenu-qt Status: Triaged = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1001621 Title: appmenu-qt doesn't work with 32-bit apps on 64-bit system Status in Application menu for Qt4: Fix Released Status in Unity: Invalid Status in “appmenu-qt” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Bug description: When I run a software which it write with and build in 32bit system in a 64bit system. It can't work a global meun and the HUD. I test this in Ubuntu 12.04 64bit,and the version of unity is 5.12.0. And we can reproduce it run the little program (attachment) in 64bit sysytem which I write it with Qt and build in 32 bit system. (You may should install ia32-libs to support 32bit software in 64bit system) And this is the output information: Unable to load library icui18n Cannot load library icui18n: (libicui18n.so.48: wrong ELF class: ELFCLASS64) /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt/+bug/1001621/+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 1001621] Re: appmenu-qt doesn't work with 32-bit apps on 64-bit system
** Branch linked: lp:~ubuntu-branches/ubuntu/utopic/appmenu-qt/utopic- proposed -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1001621 Title: appmenu-qt doesn't work with 32-bit apps on 64-bit system Status in Application menu for Qt4: Fix Released Status in Unity: Invalid Status in “appmenu-qt” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Bug description: When I run a software which it write with and build in 32bit system in a 64bit system. It can't work a global meun and the HUD. I test this in Ubuntu 12.04 64bit,and the version of unity is 5.12.0. And we can reproduce it run the little program (attachment) in 64bit sysytem which I write it with Qt and build in 32 bit system. (You may should install ia32-libs to support 32bit software in 64bit system) And this is the output information: Unable to load library icui18n Cannot load library icui18n: (libicui18n.so.48: wrong ELF class: ELFCLASS64) /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt/+bug/1001621/+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 1001621] Re: appmenu-qt doesn't work with 32-bit apps on 64-bit system
This bug was fixed in the package appmenu-qt - 0.2.7+14.04.20140305-0ubuntu2 --- appmenu-qt (0.2.7+14.04.20140305-0ubuntu2) utopic; urgency=medium * Add multiarch support (LP: #1001621) -- Miklos Juhasz juhasz.miklo...@gmail.com Sat, 23 Aug 2014 17:27:24 +0200 ** Changed in: appmenu-qt (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1001621 Title: appmenu-qt doesn't work with 32-bit apps on 64-bit system Status in Application menu for Qt4: Fix Released Status in Unity: Invalid Status in “appmenu-qt” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: When I run a software which it write with and build in 32bit system in a 64bit system. It can't work a global meun and the HUD. I test this in Ubuntu 12.04 64bit,and the version of unity is 5.12.0. And we can reproduce it run the little program (attachment) in 64bit sysytem which I write it with Qt and build in 32 bit system. (You may should install ia32-libs to support 32bit software in 64bit system) And this is the output information: Unable to load library icui18n Cannot load library icui18n: (libicui18n.so.48: wrong ELF class: ELFCLASS64) /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so: wrong ELF class: ELFCLASS64 (unitytest32bit:12486): Gtk-WARNING **: Failed to load type module: /usr/lib/gtk-2.0/2.10.0/menuproxies/libappmenu.so To manage notifications about this bug go to: https://bugs.launchpad.net/appmenu-qt/+bug/1001621/+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 1354400] Re: Implement Alarm Snooze functionality
** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: New = Fix Committed -- 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/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Fix Committed Status in Ubuntu UX bugs: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+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 1255180] Re: Reading scope models sometimes produces lots of criticals
** No longer affects: unity8 -- 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/1255180 Title: Reading scope models sometimes produces lots of criticals Status in Dee: New Status in Unity: New Status in “unity” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: In some cases shell gets into a situation where the results in the dee model are not properly synchronized with the qt model, which can cause the qt wrapper to try reading (now) invalid rows. This was identified to be caused because of the way the scope results model works and how its qt wrapper deals with changesets. Basically we have a single DeeSharedModel that contains all the results for a particular search, that model gets split up by category id into multiple DeeFilterModels, which contain results for a specific category. Now the problem is that when there's a transaction (ie multiple row additions/removals) on the master shared model, the transaction is mirrored in the per-category filter models, but it introduces a problem cause we don't serialize the changes, which means that multiple filter models can have an active transaction at the same time, and when one the filter models synchronizes with the qt wrapper, a visibility change can cause a different model to be shown, and since that model is still processing the transaction, the qt wrapper won't be properly synchronized, and can ask for rows that are about to be removed. A solution to this problem is making sure that there's always just one active transaction on the filter models. To manage notifications about this bug go to: https://bugs.launchpad.net/dee/+bug/1255180/+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 1367270] [NEW] Message is lost when user replies to an SMS from the indicator without a deault SIM
Public bug reported: TEST CASE: Pre-requisite: Dual SIM device without a default SIM selected 1. Send an SMS to the device under test 2. On notification, open the message indication 3. Tap the incoming message to show the input field 4. Type an answer and send. ACTUAL RESULT: The message is not sent and is lost. EXPECTED RESULT Either the system asks which SIM to use or replying from the indicator is locked without a default SIM. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 9 14:37:03 2014 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140909-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf qa-daily-testing rtm14 third-party-packages utopic -- 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/1367270 Title: Message is lost when user replies to an SMS from the indicator without a deault SIM Status in “indicator-messages” package in Ubuntu: New Bug description: TEST CASE: Pre-requisite: Dual SIM device without a default SIM selected 1. Send an SMS to the device under test 2. On notification, open the message indication 3. Tap the incoming message to show the input field 4. Type an answer and send. ACTUAL RESULT: The message is not sent and is lost. EXPECTED RESULT Either the system asks which SIM to use or replying from the indicator is locked without a default SIM. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 9 14:37:03 2014 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140909-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367270/+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 1367270] Re: Message is lost when user replies to an SMS from the indicator without a default SIM
** Summary changed: - Message is lost when user replies to an SMS from the indicator without a deault SIM + Message is lost when user replies to an SMS from the indicator without a default SIM -- 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/1367270 Title: Message is lost when user replies to an SMS from the indicator without a default SIM Status in “indicator-messages” package in Ubuntu: New Bug description: TEST CASE: Pre-requisite: Dual SIM device without a default SIM selected 1. Send an SMS to the device under test 2. On notification, open the message indication 3. Tap the incoming message to show the input field 4. Type an answer and send. ACTUAL RESULT: The message is not sent and is lost. EXPECTED RESULT Either the system asks which SIM to use or replying from the indicator is locked without a default SIM. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140814.1-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 9 14:37:03 2014 InstallationDate: Installed on 2014-09-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140909-030205) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367270/+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 1316978] Re: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100%
** Tags added: touch-2014-09-25 -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1316978 Title: ubuntu-touch-session needs to be able to start even if the homedir is filled to 100% Status in Ubuntu CI Services: New Status in “android” package in Ubuntu: Invalid Status in “dbus” package in Ubuntu: Confirmed Status in “hud” package in Ubuntu: Confirmed Status in “ubuntu-touch-session” package in Ubuntu: Confirmed Bug description: When the ~/phablet tree has media files added to it by the user, it is possible for the storage space to be filled, and consequently for the device not to boot. From the OEM project bug: After further investigation this problem was caused by the following: 1) Files were pushed to ~phablet/ 2) The files filled the home partition completely 3) Upon a restart of the phone the upstart session job /usr/share/upstart/sessions/dbus.conf is attempted 4) Because the partition is full, the final line of the pre-start stanza fails as $HOME/.cache/upstart/dbus-session cannot be created 5) As there is no running dbus session instance unity8 fails to start Clearing space on the home partition allows unity8 to start again. Posted here, since following discussion in #ubuntu-touch it has the same underlying cause as bug #1270248, also reported on this package. Raised as a separate bug, because this was caused by user action, rather than simply the system failing to do log housekeeping. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1316978/+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] Re: Java crash in libglib-2.0 after upgrade from 13.04 to 13.10
Concerning switching the oxygen theme please consider https://bugs.launchpad.net/ubuntu/+source/java- common/+bug/1205452/comments/20. IMHO there are multiple reasons at the moment causing java applications to SIGSEGV the reported way. This link shows AFAIS one of them. -- 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 1353379] Re: VoiceMail notification pretends there are 255 messages. It is not true there are only 2
** Tags added: qa-daily-testing rtm14 -- 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/1353379 Title: VoiceMail notification pretends there are 255 messages. It is not true there are only 2 Status in “indicator-messages” package in Ubuntu: New Bug description: Mako build #175 The VoiceMail notification indicates there are 255 voice messages (cf screenshot) on voice mail while there were only 2 new messages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-messages 13.10.1+14.10.20140725-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Wed Aug 6 11:57:43 2014 InstallationDate: Installed on 2014-08-06 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140806-020204) SourcePackage: indicator-messages UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1353379/+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 1200270] Re: compiz crashed with SIGSEGV in oif::frame::Value::GetValue()
** Tags added: utopic -- 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/1200270 Title: compiz crashed with SIGSEGV in oif::frame::Value::GetValue() Status in Open Input Framework Frame Library: Triaged Status in Unity: Invalid Status in “frame” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Invalid Bug description: I havent found out every bug correspondig to this crash notification yet, but e.g. the software center is also crashing after starting it/is not working properly. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: compiz-core 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 11 16:58:52 2013 DistUpgraded: 2013-07-10 10:00:16,415 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV670 [Radeon HD 3690/3850] [1002:9505] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device [1787:2003] InstallationDate: Installed on 2013-04-02 (99 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Gigabyte Technology Co., Ltd. EP35-DS3 MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-2-generic root=UUID=0208EF1508EF068F loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f6ed62a4570:cmpl $0x9,(%rdi) PC (0x7f6ed62a4570) ok source $0x9 ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libframe.so.6 frame_device_get_property () from /usr/lib/x86_64-linux-gnu/libframe.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgrail.so.6 Title: compiz crashed with SIGSEGV in frame_device_get_property() UpgradeStatus: Upgraded to saucy on 2013-07-10 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/19/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: EP35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP35-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.45-2ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.4-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.1-0ubuntu0.8 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.1.0-0ubuntu2.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.9-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu1.1 xserver.bootTime: Thu Jul 11 16:58:29 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.1-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/frame/+bug/1200270/+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 1320880] Re: calendar alarm never stops sounding without user interaction
** Changed in: indicator-datetime (Ubuntu) Importance: Medium = High ** Tags added: rtm14 -- 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/1320880 Title: calendar alarm never stops sounding without user interaction Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: If an alarm fires, the alarm sound seemingly will persist forever. This seems like perhaps the right choice for an alarm clock, but seems inappropriate for a calendar reminder. I would expect a calendar reminder to sound for only a short period. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1320880/+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 1320880] Re: calendar alarm never stops sounding without user interaction
** Tags removed: rtm14 ** Tags added: rtm touch-2014-09-25 -- 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/1320880 Title: calendar alarm never stops sounding without user interaction Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: If an alarm fires, the alarm sound seemingly will persist forever. This seems like perhaps the right choice for an alarm clock, but seems inappropriate for a calendar reminder. I would expect a calendar reminder to sound for only a short period. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1320880/+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 1330037] Re: upower 0.99 transition
** Branch linked: lp:ubuntu/utopic-proposed/indicator-power -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Released Status in “gnome-applets” package in Ubuntu: Invalid Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: Triaged Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Released Status in “mate-power-manager” package in Ubuntu: Fix Released Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: In Progress Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1320880] Re: calendar alarm never stops sounding without user interaction
** Changed in: indicator-datetime (Ubuntu) Assignee: Charles Kerr (charlesk) = James Mulholland (jamesjosephmulholland) -- 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/1320880 Title: calendar alarm never stops sounding without user interaction Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: If an alarm fires, the alarm sound seemingly will persist forever. This seems like perhaps the right choice for an alarm clock, but seems inappropriate for a calendar reminder. I would expect a calendar reminder to sound for only a short period. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1320880/+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 1296431] Re: Phone doesn't alert user of critical power situations
** Branch linked: lp:ubuntu/utopic-proposed/indicator-power -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1296431 Title: Phone doesn't alert user of critical power situations Status in “indicator-power” package in Ubuntu: In Progress Bug description: The phone doesn't currently alert the user when the battery is critical. This leads to power loss at times and the user doesn't know it's about to happen or had happened. e.g. during a call, or while listening to music. Also if the phone is sat on the desk unplugged from power connection. https://wiki.ubuntu.com/Power#Warnings: When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 1 hour or less remaining (PC) or 20% or less remaining (phone/tablet), a notification bubble should appear ... When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 30 minutes or less remaining (PC) or 10% or less remaining (phone/tablet), an alert should appear... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1296431/+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 1350952] Re: [Indicators] replace the text Empty! with something more useful
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-transfer (Ubuntu) Status: New = Confirmed -- 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/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: New Status in Ubuntu UX bugs: Fix Committed Status in “indicator-messages” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+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 1320880] Re: calendar alarm never stops sounding without user interaction
I don't see any description of alarm-style notification for events in the TimeAndDate, nor does the Indicators UX Spec. However, the Ubuntu Phone Notifications v2.2 document lists in the Key use cases list on page 11 next to alarms, so it seems we should have *something* here. ** Changed in: indicator-datetime (Ubuntu) Status: Triaged = 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/1320880 Title: calendar alarm never stops sounding without user interaction Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: If an alarm fires, the alarm sound seemingly will persist forever. This seems like perhaps the right choice for an alarm clock, but seems inappropriate for a calendar reminder. I would expect a calendar reminder to sound for only a short period. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1320880/+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 1330037] Re: upower 0.99 transition
This bug was fixed in the package indicator-power - 12.10.6+14.10.20140909-0ubuntu1 --- indicator-power (12.10.6+14.10.20140909-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Add support for UPower 0.99. (LP: #1330037) * When the phone's battery goes down past a certain level, pop up a snap decision to warn the user. (LP: #1296431) [ Ted Gould ] * Synchronize process management across indicators -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 09 Sep 2014 04:22:52 + ** Changed in: indicator-power (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Released Status in “gnome-applets” package in Ubuntu: Invalid Status in “gnome-control-center” package in Ubuntu: In Progress Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: In Progress Status in “gnome-session” package in Ubuntu: In Progress Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “gnome-shell” package in Ubuntu: In Progress Status in “indicator-power” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Fix Released Status in “mate-applets” package in Ubuntu: Fix Released Status in “mate-power-manager” package in Ubuntu: Fix Released Status in “mate-session-manager” package in Ubuntu: Fix Released Status in “mutter” package in Ubuntu: In Progress Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: Fix Released Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: Fix Released Status in “tracker” package in Ubuntu: Fix Committed Status in “ubuntu-system-settings” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: In Progress Status in “xfce4-power-manager” package in Ubuntu: Fix Committed Status in “xfce4-session” package in Ubuntu: Fix Released Status in “xfce4-settings” package in Ubuntu: In Progress Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: Fix Released Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery and sugar will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: works fine with systemd, suspend broken with upstart mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+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 1296431] Re: Phone doesn't alert user of critical power situations
This bug was fixed in the package indicator-power - 12.10.6+14.10.20140909-0ubuntu1 --- indicator-power (12.10.6+14.10.20140909-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Add support for UPower 0.99. (LP: #1330037) * When the phone's battery goes down past a certain level, pop up a snap decision to warn the user. (LP: #1296431) [ Ted Gould ] * Synchronize process management across indicators -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 09 Sep 2014 04:22:52 + ** Changed in: indicator-power (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1296431 Title: Phone doesn't alert user of critical power situations Status in “indicator-power” package in Ubuntu: Fix Released Bug description: The phone doesn't currently alert the user when the battery is critical. This leads to power loss at times and the user doesn't know it's about to happen or had happened. e.g. during a call, or while listening to music. Also if the phone is sat on the desk unplugged from power connection. https://wiki.ubuntu.com/Power#Warnings: When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 1 hour or less remaining (PC) or 20% or less remaining (phone/tablet), a notification bubble should appear ... When the device’s battery/batteries are discharging and reach — or begin discharging and already have — 30 minutes or less remaining (PC) or 10% or less remaining (phone/tablet), an alert should appear... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1296431/+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 1260978] Re: [Greeter] should be able to control music service while greeter locked
** Changed in: media-hub Status: New = In Progress ** Changed in: media-hub Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: media-hub Importance: Undecided = High -- 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/1260978 Title: [Greeter] should be able to control music service while greeter locked Status in Media Hub: In Progress Status in Ubuntu UX bugs: Triaged Status in “indicator-sound” package in Ubuntu: Opinion Status in “ubuntu-music-app” package in Ubuntu: Opinion Status in “ubuntu-settings-components” package in Ubuntu: Opinion Status in “unity8” package in Ubuntu: Opinion Bug description: Not sure what component to file this against-- please reassign as desired. I use my phone to play music on random while I'm driving. This works great except when I want to advance or pause the song, where I have to go through the greeter first to access the player. This can either take my attention away from driving or I need to wait until the next stop light to advance the song. This is less of a concern when the greeter can just be swiped with one gesture, but is a big concern if you enable the passcode lock where you have to add the passcode to access the player. If the music is playing, the greeter should allow rudimentary manipulation of the music, eg, pause/play and forward/back. Other platforms seem to allow for this (eg android). To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1260978/+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 1320880] Re: Calendar notifications are treated the same as an alarm notification
A little background context, FWIW: the duration for alarm notifications can be set to one of [10, 20, 30, 60 minutes] in ubuntu-clock-app settings, with the default value being 30 minutes. This duration is currently used for calendar notifications too, but of course we can change it to whatever Design wants. ** Summary changed: - calendar alarm never stops sounding without user interaction + Calendar notifications are treated the same as an alarm notification -- 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/1320880 Title: Calendar notifications are treated the same as an alarm notification Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: If an alarm fires, the alarm sound seemingly will persist forever. This seems like perhaps the right choice for an alarm clock, but seems inappropriate for a calendar reminder. I would expect a calendar reminder to sound for only a short period. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1320880/+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 1353095] Re: Missing menu content in the unity top panel in LTSP enviroment
*** This bug is a duplicate of bug 1320286 *** https://bugs.launchpad.net/bugs/1320286 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/1353095 Title: Missing menu content in the unity top panel in LTSP enviroment Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: In the unity session the content of top menu (application menu, sesssion menu) is missing in a LTSP client. The top panel displays only the grey bar with the application name. Indicator applets adn session menu are totally missing. It happens in a fresh ltsp installation with ubuntu 14.04 LTS The unity version is 7.2.0+14.04.20140423-0ubuntu1.2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Aug 5 22:05:37 2014 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1353095/+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 1353095] Re: Missing menu content in the unity top panel in LTSP enviroment
*** This bug is a duplicate of bug 1320286 *** https://bugs.launchpad.net/bugs/1320286 It happened to me after I manually restarted unity because it had crashed. I have not yet launched unity-panel-service, here are the logs asked above: $ initctl list avahi-daemon start/running, process 823 mountnfs-bootclean.sh start/running nmbd start/running, process 1828 tty4 start/running, process 922 whoopsie start/running, process 1000 winbind start/running, process 1806 upstart-udev-bridge start/running, process 7608 rsyslog start/running, process 23747 udev start/running, process 7611 avahi-cups-reload stop/waiting mountall-net stop/waiting passwd stop/waiting rc stop/waiting startpar-bridge stop/waiting ureadahead-other stop/waiting smbd start/running, process 689 tty5 start/running, process 926 irqbalance start/running, process 24746 systemd-logind start/running, process 7685 apport start/running console-setup stop/waiting gpu-manager stop/waiting hwclock-save stop/waiting plymouth-log stop/waiting modemmanager start/running, process 753 mountall.sh start/running failsafe stop/waiting rfkill-store stop/waiting atd start/running, process 996 dbus start/running, process 722 resolvconf start/running failsafe-x stop/waiting mounted-var stop/waiting nvidia-prime stop/waiting plymouth-shutdown stop/waiting plymouth stop/waiting udev-fallback-graphics stop/waiting usb-modeswitch-upstart stop/waiting checkroot.sh start/running network-manager start/running, process 865 nvidia-persistenced start/running, process 1674 control-alt-delete stop/waiting hwclock stop/waiting mounted-proc stop/waiting cups-browsed start/running, process 1133 alsa-store stop/waiting setvtrgb stop/waiting shutdown stop/waiting cron start/running, process 995 mountkernfs.sh start/running alsa-restore stop/waiting gdm stop/waiting mountall stop/waiting mounted-debugfs stop/waiting lightdm stop/waiting binfmt-support start/running console stop/waiting mounted-run stop/waiting acpid start/running, process 1031 bluetooth start/running, process 762 checkfs.sh start/running checkroot-bootclean.sh start/running mountnfs.sh start/running ufw start/running kmod stop/waiting plymouth-stop stop/waiting rcS stop/waiting reload-smbd stop/waiting wait-for-state stop/waiting bootmisc.sh start/running flush-early-job-log stop/waiting friendly-recovery stop/waiting rc-sysinit stop/waiting samba-ad-dc stop/waiting upstart-socket-bridge start/running, process 23464 cups start/running, process 7768 pulseaudio stop/waiting mountdevsubfs.sh start/running tty2 start/running, process 933 upstart-file-bridge start/running, process 23465 anacron stop/waiting udevtrigger stop/waiting mtab.sh start/running tty3 start/running, process 934 container-detect stop/waiting mounted-dev stop/waiting udev-finish stop/waiting alsa-state stop/waiting hostname stop/waiting mountall-reboot stop/waiting network-interface (vboxnet0) start/running network-interface (lo) start/running network-interface (eth0) start/running tty1 start/running, process 1338 mountall-shell stop/waiting mounted-tmp stop/waiting plymouth-ready stop/waiting plymouth-splash stop/waiting plymouth-upstart-bridge stop/waiting udevmonitor stop/waiting mountall-bootclean.sh start/running network-interface-security (network-manager) start/running network-interface-security (network-interface/eth0) start/running network-interface-security (network-interface/lo) start/running network-interface-security (network-interface) start/running network-interface-security (networking) start/running networking start/running tty6 start/running, process 937 dmesg stop/waiting procps stop/waiting rfkill-restore stop/waiting console-font stop/waiting network-interface-container stop/waiting ureadahead stop/waiting -- 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/1353095 Title: Missing menu content in the unity top panel in LTSP enviroment Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: In the unity session the content of top menu (application menu, sesssion menu) is missing in a LTSP client. The top panel displays only the grey bar with the application name. Indicator applets adn session menu are totally missing. It happens in a fresh ltsp installation with ubuntu 14.04 LTS The unity version is 7.2.0+14.04.20140423-0ubuntu1.2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Aug 5 22:05:37 2014 ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage:
[Dx-packages] [Bug 1354400] Re: Implement Alarm Snooze functionality
** Changed in: ubuntu-ux Assignee: (unassigned) = Giorgio Venturi (giorgio-venturi) ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: Fix Committed = 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/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: Fix Committed Status in Ubuntu UX bugs: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+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 1184262] Re: times out too early, stuck in PrepareForSleep, causing network and other services to not resume
I'm on fully up-to-date Ubuntu 14.04 with the latest kernel 3.13.0-36-generic, and I got this error. I have a Lenovo ThinkPad W530. I use it either with the internal monitor or with an external monitor connected to displayport. I don't remember what I did today. I think I connected the display cable, closed the lid and then logged in. I do it every day, but something must have been slightly different today. I got network disabled. I clicked on Enable Networking several times, but it didn't help. There was no error message and no change in the menus shown on left-click or right-click on the nm-applet. This didn't work: # service network-manager restart stop: Unknown job: network-manager start: Unknown job: network-manager This worked: # nmcli nm RUNNING STATE WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running asleep enabled enabledenabled enabled # nmcli nm sleep false nm-applet should show the sleep state and should wake up NetworkManager if requested by the user. Ideally, it would be great not to put the network to sleep if the computer is not going to sleep. And the computer should not go to sleep if the lid is being closed but there is a display connection. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1184262 Title: times out too early, stuck in PrepareForSleep, causing network and other services to not resume Status in “systemd” package in Ubuntu: Invalid Status in “systemd-shim” package in Ubuntu: Fix Released Status in “systemd” source package in Saucy: Invalid Status in “systemd-shim” source package in Saucy: Fix Released Status in “systemd” source package in Trusty: Invalid Status in “systemd-shim” source package in Trusty: Fix Released Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. SRU INFORMATION: Reproducer: - Force suspend to take very long by adding a sleep: echo -e '#!/bin/sh\nsleep 15\nexit 1' | sudo tee /usr/lib/pm-utils/sleep.d/00break (this will also make suspend fail, which eases testing) - Suspend from the menu or with sudo gdbus call -y -d org.freedesktop.login1 -o /org/freedesktop/login1 -m org.freedesktop.login1.Manager.Suspend true - With the 13.10 final version, systemd-shim will (often) time out, and the next Suspend call from above will fail with Operation already in progress and the network does not come back up. With the fixed version, network should be back up and the Suspend() call can be issued many times. Fix: https://github.com/desrt/systemd-shim/commit/136ed1143077d13c2 https://github.com/desrt/systemd-shim/commit/16a7fdc0652ad78f4 Regression potential: Errors in this code could potentially break suspend/shutdown completely, so for verification both of these functionalities ought to be tested on real hardware. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con:
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Alternate work-around: I was able to login successfully by detaching the keyboard, and using the mouse to 'click-in' my password with the on-screen keyboard. I usually had to click on Switch Account in the 'gear' drop-down menu to get the assistive technology icon to appear to get to the on-screen keyboard, but once I did, I could enter a password and that worked to log me in. It's somewhat bizarre that this would work since the setuid work-around suggested above also worked for me. If it is some problem running unix_chkpwd, then shouldn't the on-screen keyboard have just as much difficulty with that? -- 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/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session optionalpam_gnome_keyring.so auto_start session requiredpam_env.so readenv=1 session
[Dx-packages] [Bug 1365875] Re: mail notification displayed even when phone locked
** Branch linked: lp:~ralsina/ubuntu-push/skip-on-locked -- 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/1365875 Title: mail notification displayed even when phone locked Status in Ubuntu Push Notifications: New Status in “account-polld” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: New Status in “unity8” package in Ubuntu: Opinion Bug description: I had just woken up the phone (screen was displaying the welcome greeter) but had not yet unlocked the device (I have set a pin code) when a mail notification appeared on screen that divulged the sender. This is a privacy issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-push/+bug/1365875/+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 980519] Re: Random log off in Ubuntu 12.04 LTS
I have exactly the same problem as eMKi (mkisovec), but with Ubuntu 14.04 and dual video card system (Intel Hasewell and Nvidia GEForce 840M). I use Nvidia trive 331 and Bumblebee. Used to work pretty fine. The problem appeared today, may be due to a recently updated package. Seems that I'm not the only one experiencing this: http://askubuntu.com/questions/522099/ubuntu-14-04-logs-out- every-5-minutes -- 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/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in “nvidia-graphics-drivers” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “xorg” package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+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 1365875] Re: mail notification displayed even when phone locked
A branch is being landed now so that when the screen is locked, popups are not displayed (all other notifications still work). Further refinements really need design input. ** Changed in: ubuntu-push Status: In Progress = Fix Committed -- 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/1365875 Title: mail notification displayed even when phone locked Status in Ubuntu Push Notifications: Fix Committed Status in “account-polld” package in Ubuntu: New Status in “indicator-messages” package in Ubuntu: New Status in “unity8” package in Ubuntu: Opinion Bug description: I had just woken up the phone (screen was displaying the welcome greeter) but had not yet unlocked the device (I have set a pin code) when a mail notification appeared on screen that divulged the sender. This is a privacy issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-push/+bug/1365875/+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 1367484] [NEW] Unity or X crashes out to login screen constantly
Public bug reported: I will randomly get a blank screen and then login screen. I am able to log in again but it usually happens within a few minutes of that. I started getting this after an update this morning. The output of /var/log/apt/history.log for that update is the following Start-Date: 2014-09-10 06:33:39 Commandline: aptdaemon role='role-commit-packages' sender=':1.93' Upgrade: libgl1-mesa-dev:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), foreman:amd64 (0.74.0, 0.75.0), libegl1-mesa:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), cups-core-drivers:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), cups-server-common:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), libopenvg1-mesa:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libegl1-mesa-drivers:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), nvidia-common:amd64 (0.2.91.5, 0.2.91.6), libgl1-mesa-dri:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libgl1-mesa-dri:i386 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libcups2:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), cups-daemon:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libcupsmime1:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), libgudev-1.0-0:amd64 (204-5ubuntu20.5, 204-5ubuntu20.6), cups-client:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), libcupsimage2:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), xserver-xorg-core:amd64 (1.15.1-0ubuntu2, 1.15.1-0ubuntu2.1), libglapi-mesa:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libglapi-mesa:i386 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libnss3-1d:amd64 (3.15.4-1ubuntu7, 3.15.4-1ubuntu7.1), cups:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), xserver-common:amd64 (1.15.1-0ubuntu2, 1.15.1-0ubuntu2.1), libnss3-nssdb:amd64 (3.15.4-1ubuntu7, 3.15.4-1ubuntu7.1), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.5, 204-5ubuntu20.6), libgles2-mesa:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libgl1-mesa-glx:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libgl1-mesa-glx:i386 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libxatracker2:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), cups-bsd:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), xserver-xorg-video-intel:amd64 (2.99.914+git20140829.2086965e-0ubuntu0sarvatt~trusty, 2.99.916+git20140908.30932a7b-0ubuntu0sarvatt~trusty), libnss3:amd64 (3.15.4-1ubuntu7, 3.15.4-1ubuntu7.1), libcupscgi1:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), libwayland-egl1-mesa:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libgbm1:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), libcupsppdc1:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), cups-common:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), heroku-toolbelt:amd64 (3.9.7, 3.10.5), mesa-common-dev:amd64 (10.4.0~git20140829.6cd0dbc4-0ubuntu0sarvatt~trusty, 10.4.0~git20140908.a3306f02-0ubuntu0sarvatt~trusty), heroku:amd64 (3.9.7, 3.10.5), cups-ppdc:amd64 (1.7.2-0ubuntu1.1, 1.7.2-0ubuntu1.2), irqbalance:amd64 (1.0.6-2, 1.0.6-2ubuntu0.14.04.1), xserver-xorg-video-nouveau:amd64 (1.0.10+git20140818.16c885ce-0ubuntu0sarvatt~trusty, 1.0.11+git20140904.3cd4c849-0ubuntu0sarvatt~trusty) End-Date: 2014-09-10 06:35:37 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Sep 10 10:59:17 2014 DistUpgraded: 2014-04-29 22:17:11,967 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-32-generic, x86_64:
[Dx-packages] [Bug 1240848] Re: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner
confirming same issue, only thing that made it so bad was creating a autoban script for repeat offenders, in any event this is obviously a huge bug, just 'sudo rm -rf ~/.cache/upstart' and will baby sit this bad boy. Ubuntu 14.04.1 Desktop fresh install :( -- 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/1240848 Title: ~/.cache/upstart takes up around 70GB of space due to unity and mediascanner Status in Unity: New Status in “mediascanner” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I just noticed that ~/.cache/upstart/ folder on my computer is taking up 69GB of space. Upon further investigation, I found out that mediascanner.log and unity-panel-service.log take 12GB and 54GB of space respectively. I'm not entirely sure if this is related to upstart as I had removed logrotate package because of a conflict. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1240848/+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
