[Dx-packages] [Bug 1499687] Re: Bluetooth turn on automatically
*** This bug is a duplicate of bug 1488170 *** https://bugs.launchpad.net/bugs/1488170 ** This bug has been marked a duplicate of bug 1488170 Bluetooth initiated after quitting airplane mode -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1499687 Title: Bluetooth turn on automatically Status in indicator-bluetooth package in Ubuntu: New Bug description: bluetooth turn on automatically when i disable the flight mode on my bq aquaris e4.5 U.E. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1499687/+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 1512893] Re: accountservice fills up auth.log after upgrade to 15.10
*** This bug is a duplicate of bug 1488344 *** https://bugs.launchpad.net/bugs/1488344 ** Changed in: accountsservice (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1488344 dbus rejected send messages -- 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/1512893 Title: accountservice fills up auth.log after upgrade to 15.10 Status in accountsservice package in Ubuntu: New Bug description: I'm getting many errors in auth.log after upgrading to 15.10 --- Nov 3 14:17:26 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:17:51 LeosLinux dbus[1101]: message repeated 3 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")] Nov 3 14:18:43 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:19:11 LeosLinux dbus[1101]: message repeated 3 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")] Nov 3 14:22:16 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:24:32 LeosLinux dbus[1101]: message repeated 5 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")] Nov 3 14:28:24 LeosLinux sudo: pam_unix(sudo:session): session closed for user root Nov 3 14:28:51 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") As I'm running ossec, these errors generate emails, so I would like to find out what error error means and how to stop it from occurring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1512893/+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 1512893] [NEW] accountservice fills up auth.log after upgrade to 15.10
Public bug reported: I'm getting many errors in auth.log after upgrading to 15.10 --- Nov 3 14:17:26 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:17:51 LeosLinux dbus[1101]: message repeated 3 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")] Nov 3 14:18:43 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:19:11 LeosLinux dbus[1101]: message repeated 3 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")] Nov 3 14:22:16 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:24:32 LeosLinux dbus[1101]: message repeated 5 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")] Nov 3 14:28:24 LeosLinux sudo: pam_unix(sudo:session): session closed for user root Nov 3 14:28:51 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") As I'm running ossec, these errors generate emails, so I would like to find out what error error means and how to stop it from occurring. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1512893 Title: accountservice fills up auth.log after upgrade to 15.10 Status in accountsservice package in Ubuntu: New Bug description: I'm getting many errors in auth.log after upgrading to 15.10 --- Nov 3 14:17:26 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:17:51 LeosLinux dbus[1101]: message repeated 3 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic")] Nov 3 14:18:43 LeosLinux dbus[1101]: [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.65" (uid=1000 pid=2820 comm="/usr/lib/x86_64-linux-gnu/indicator-messages/indic") Nov 3 14:19:11 LeosLinux dbus[1101]: message repeated 3 times: [ [system] Rejected send message, 9 matched rules; type="method_return", sender=":1.3" (uid=0 pid=1098 comm="/usr/lib/accountsservice/accounts-daemon ") interface="(unset)" member="(unset)" error name="(unset)" reques
[Dx-packages] [Bug 1512180] Re: [datetime] Standard alarms are not work correctly for Timers, after timezone/DST change
Not sure I understand why this is not just an issue fr the timer app. Alarms want to be interpreted in local time, I am sure this is as designed. Timers are not really alarms as they reflect a duration not a time of day. For me the issue is the timer app implemented timers incorrectly. ** Changed in: canonical-devices-system-image Status: New => Incomplete -- 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/1512180 Title: [datetime] Standard alarms are not work correctly for Timers, after timezone/DST change Status in Canonical System Image: Incomplete Status in Timer: New Status in Ubuntu Clock App: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Standard alarms will not work correctly after changing timezone and during DST change. Steps to reproduce: 1. Install Timer from Store: https://uappexplorer.com/app/timer.mivoligo 2. Set timer to 5 minutes 3. Open Clock app. Look for alarm, and notice that alarm is correctly set 3. Switch to System Settings -> Time & Date -> Time zone: 4. Change Time zone to something different (eg. New York). (Or wait for DST change: https://en.wikipedia.org/wiki/Daylight_saving_time) Expected behaviour: - timer ringing as expected after timezone/DST change Current behaviour: - alarm is not ringing. (you could check active alarms in "Ubuntu Clock app) Proposal solution: - introduce new type of alarms, which is based on UTC (https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and independent from time zones. - This alatms will not be visible in applications which is using standard alarms (Ubuntu Clock, Ubuntu Calendar etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512180/+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 1303796] Re: Display scaling is not applied runtime
Attached a branch that fixes the issue I mentioned in comment #3 ** Branch linked: lp:~larsu/notify-osd/lp1303796 -- 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/1303796 Title: Display scaling is not applied runtime Status in notify-osd package in Ubuntu: Triaged Bug description: I changed my scaling to a value and back to 1, I think notify-osd got triggered at that time, and all subsequent notifications were scaled incorrectly. It looks like notify-osd doesn't update the scaling value runtime. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140213-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 13:59:10 2014 MachineType: Dell Inc. Latitude E6420 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-23-generic root=UUID=e11751da-d20f-4832-9530-c41e15f1e05c ro rootflags=subvol=@ splash quiet vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0-4ubuntu1 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 xserver-xorg-video-ati 1:7.3.0-1ubuntu3 SourcePackage: notify-osd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd07/11/2012:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1303796/+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 1478321] Re: Weird battery values bq Aquaris 4.5
I get this too with the latest update, battery goes to 0% very fast once you reach 20% charge, also I noticed the time since last charge can show way more hours than it should. -- 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/1478321 Title: Weird battery values bq Aquaris 4.5 Status in indicator-power package in Ubuntu: Confirmed Bug description: Many times it happens that the percentage of the battery shown is not the real one. Yesterday evening I had a big problem where the phone suddenly went from 20% to 0% and it shut itself down. This is shown in the battery history graph, that I attach. As you can see there are various vertical lines, clearly indicating that the value jumps from one point to the other. This is a big problem, because if one sees that the phone has still 20% of battery, one thinks that it still has 1/5 of its life span before dying. It is not the first time that this happens to me and others, and I believe that anyone experiencing this should attach a picture of it, so that eventually we might be able to resolve it, maybe with some kind of approximations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1478321/+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 1498609] Re: No notification about incomming calls on bluetooth headset
** Description changed: When I get incomming calls there is no notice on my bluetooth headset, - about these. This happened when the phone was silenced and also when it - was not. When the phone was not silenced, it at least did a little - crack. + about these. The bluetooth headset works more or less fine. Also the + phone vibrates on incomming calls but on the headset a notification + about the incomming call is missing. This happened when the phone was + silenced and also when it was not. When the phone was not silenced, it + at least did a little crack. There should be a notification in both cases. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1498609 Title: No notification about incomming calls on bluetooth headset Status in Ubuntu UX: Incomplete Status in dialer-app package in Ubuntu: New Status in indicator-bluetooth package in Ubuntu: New Status in indicator-messages package in Ubuntu: New Bug description: When I get incomming calls there is no notice on my bluetooth headset, about these. The bluetooth headset works more or less fine. Also the phone vibrates on incomming calls but on the headset a notification about the incomming call is missing. This happened when the phone was silenced and also when it was not. When the phone was not silenced, it at least did a little crack. There should be a notification in both cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1498609/+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 1512180] Re: [datetime] Standard alarms will not work correctly for Timers, after timezone/DST change
** Description changed: Standard alarms will not work correctly after changing timezone and during DST change. Steps to reproduce: 1. Install Timer from Store: https://uappexplorer.com/app/timer.mivoligo 2. Set timer to 5 minutes 3. Open Clock app. Look for alarm, and notice that alarm is correctly set 3. Switch to System Settings -> Time & Date -> Time zone: 4. Change Time zone to something different (eg. New York). (Or wait for DST change: https://en.wikipedia.org/wiki/Daylight_saving_time) Expected behaviour: - timer ringing as expected after timezone/DST change Current behaviour: - alarm is not ringing. (you could check active alarms in "Ubuntu Clock app) Proposal solution: - introduce new type of alarms, which is based on UTC (https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and independent from time zones. + - This alatms will not be visible in applications which is using standard alarms (Ubuntu Clock, Ubuntu Calendar etc.) ** Summary changed: - [datetime] Standard alarms will not work correctly for Timers, after timezone/DST change + [datetime] Standard alarms are not work correctly for Timers, after timezone/DST change ** Also affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1512180 Title: [datetime] Standard alarms are not work correctly for Timers, after timezone/DST change Status in Canonical System Image: New Status in Timer: New Status in Ubuntu Clock App: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Standard alarms will not work correctly after changing timezone and during DST change. Steps to reproduce: 1. Install Timer from Store: https://uappexplorer.com/app/timer.mivoligo 2. Set timer to 5 minutes 3. Open Clock app. Look for alarm, and notice that alarm is correctly set 3. Switch to System Settings -> Time & Date -> Time zone: 4. Change Time zone to something different (eg. New York). (Or wait for DST change: https://en.wikipedia.org/wiki/Daylight_saving_time) Expected behaviour: - timer ringing as expected after timezone/DST change Current behaviour: - alarm is not ringing. (you could check active alarms in "Ubuntu Clock app) Proposal solution: - introduce new type of alarms, which is based on UTC (https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and independent from time zones. - This alatms will not be visible in applications which is using standard alarms (Ubuntu Clock, Ubuntu Calendar etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512180/+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 1436405] Re: Duplicate menu (both unity and in-app) for Qt apps
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: appmenu-qt5 (Ubuntu) Status: New => Confirmed -- 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/1436405 Title: Duplicate menu (both unity and in-app) for Qt apps Status in One Hundred Papercuts: Confirmed Status in appmenu-qt5 package in Ubuntu: Confirmed Status in libdbusmenu-qt package in Ubuntu: Confirmed Bug description: At least konsole and khelpcenter suffers from this bug: Start the app inside the default Unity environment (not under KDE). Notice that the app's menubar appears twice. Once in the upper row of the whole desktop, as expected and as it is for every Gnome app. And also inside the application's window, wasting precious screen real estate. In Utopic, at least for konsole, I'm quite sure that the menu wasn't duplicated inside the app, it only appeared on the desktop's top Unity bar. (I'm not sure I guessed the component right; please reassign as appropriate.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 16:33:14 2015 InstallationDate: Installed on 2012-05-30 (1028 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: libdbusmenu-qt UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+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 1436405] Re: Duplicate menu (both unity and in-app) for Qt apps
I have the same issue on Ubuntu Wily, with quasselclient, a Qt5 application. The menu shows both in the global app menu and at the top of the window. When I start using "UBUNTU_MENUPROXY=0 quasselclient", the menu will only show in the window but not the global menu area. However I'd prefer the opposite, only the global menu showing. -- 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/1436405 Title: Duplicate menu (both unity and in-app) for Qt apps Status in One Hundred Papercuts: Confirmed Status in appmenu-qt5 package in Ubuntu: New Status in libdbusmenu-qt package in Ubuntu: Confirmed Bug description: At least konsole and khelpcenter suffers from this bug: Start the app inside the default Unity environment (not under KDE). Notice that the app's menubar appears twice. Once in the upper row of the whole desktop, as expected and as it is for every Gnome app. And also inside the application's window, wasting precious screen real estate. In Utopic, at least for konsole, I'm quite sure that the menu wasn't duplicated inside the app, it only appeared on the desktop's top Unity bar. (I'm not sure I guessed the component right; please reassign as appropriate.) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libdbusmenu-qt5 0.9.3+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 16:33:14 2015 InstallationDate: Installed on 2012-05-30 (1028 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: libdbusmenu-qt UpgradeStatus: Upgraded to vivid on 2015-03-17 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1436405/+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 1485493] Re: With device connected, Bluetooth indicator won't change into "Disabled" when pressing the wireless hot key
** Changed in: indicator-appmenu (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1485493 Title: With device connected, Bluetooth indicator won't change into "Disabled" when pressing the wireless hot key Status in indicator-appmenu package in Ubuntu: Confirmed Bug description: CID: 201307-14037 With a Bluetooth mouse connected, the Bluetooth indicator won't change into "Disabled" (grey out) when you press the wireless hot key to disable the wireless network and the Bluetooth. From rfkill output and the mouse itself, the Bluetooth will be disabled correctly with the hotkey, it's just the indicator. (And it works fine without device connected) Steps: 1. Install 14.04.2 + update 2. Pair and connect a BT mouse. 3. Disable the wireless with the hotkey Expected result: * Bluetooth disabled, indicator shows that it's disabled Actual result: * Bluetooth disabled, but the indicator shows that it's still connected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-appmenu 13.01.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14 Uname: Linux 3.16.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 17 03:33:03 2015 InstallationDate: Installed on 2015-08-07 (10 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: indicator-appmenu UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/1485493/+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 1512180] Re: [datetime] Standard alarms will not work correctly for Timers, after timezone/DST change
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1512180 Title: [datetime] Standard alarms will not work correctly for Timers, after timezone/DST change Status in Canonical System Image: New Status in Timer: New Status in Ubuntu Clock App: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Standard alarms will not work correctly after changing timezone and during DST change. Steps to reproduce: 1. Install Timer from Store: https://uappexplorer.com/app/timer.mivoligo 2. Set timer to 5 minutes 3. Open Clock app. Look for alarm, and notice that alarm is correctly set 3. Switch to System Settings -> Time & Date -> Time zone: 4. Change Time zone to something different (eg. New York). (Or wait for DST change: https://en.wikipedia.org/wiki/Daylight_saving_time) Expected behaviour: - timer ringing as expected after timezone/DST change Current behaviour: - alarm is not ringing. (you could check active alarms in "Ubuntu Clock app) Proposal solution: - introduce new type of alarms, which is based on UTC (https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and independent from time zones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512180/+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 1408347] Re: bump version to 1.11 in ubuntu 15.04?
I'm working on testing GLEW 1.13.0 against its 63 reverse dependencies right now and I really hope to be able to upload it to Debian unstable/sid within the end of this month. So probably Ubuntu 16.04 should ship 1.13.0 ;-) -- You received this bug notification because you are a member of DX Packages, which is subscribed to glew in Ubuntu. https://bugs.launchpad.net/bugs/1408347 Title: bump version to 1.11 in ubuntu 15.04? Status in glew package in Ubuntu: Triaged Bug description: Debian Experimental already has 1.11 which introduces support for OpenGL 4.5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glew/+bug/1408347/+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
