[Dx-packages] [Bug 1629002] [NEW] Ubuntu 16.10 Setup: dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly.
Public bug reported: During the installation process of Ubuntu 16.10 beta I got several of these messages: (WebKitWebProcess:): dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. (a11y-profile-manager:12999): dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. (process:13026): dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. ** Affects: d-conf (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1629002/+attachment/4751141/+files/Bildschirmfoto%20vom%202016-09-29%2018-13-00.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1629002 Title: Ubuntu 16.10 Setup: dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. Status in d-conf package in Ubuntu: New Bug description: During the installation process of Ubuntu 16.10 beta I got several of these messages: (WebKitWebProcess:): dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. (a11y-profile-manager:12999): dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. (process:13026): dconf-CRITICAL **: unable to create directory '/run/user/0/dconf': Permission denied. dconf will not work properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1629002/+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 1588526] Re: Alarm doesn't ring when screen locked
The problem seems to be specific to Nexus 4 only. Or is it anyone with bq or Meizu phone who got this bug? -- 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/1588526 Title: Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1588526] Re: Alarm doesn't ring when screen locked
ISSUE: Alarm fails to wake phone (and user) from sleep and only triggers when power button is pressed. OS VERSION: OTA-13 on LGE Nexus 4 Build: Ubuntu 15.04 - armhf (20160913-023544) DETAILS: This problem occurs regularly but I cannot reproduce it consistently. *Seems* better when phone is plugged in and charging but still testing this. Clock vibration is on. Will test with vibration off. Bug has persisted for several years now. As a vital core app (especially from a user perspective), this must be resolved. Reference bug reports: #1187994 (2013) #1299916 (2014) #1459946 (2015) ** Changed in: ubuntu-clock-app Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1588526 Title: Alarm doesn't ring when screen locked Status in Canonical System Image: Incomplete Status in Ubuntu Clock App: Confirmed Status in indicator-datetime package in Ubuntu: Confirmed Bug description: Hello, I noticed couple of time, difficult to reproduce that the alarm does not ring at the correct time but ring as soon the screen is on. Mako Rc-proposed bq-aquaris R324. Regards Edit : to make ring the phone i just need to wake up the phone and the alarm start to ring. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1587367] Re: Brightness toggle fakes brightness changes
** Changed in: canonical-devices-system-image Status: Fix Committed => Confirmed -- 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/1587367 Title: Brightness toggle fakes brightness changes Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in indicator-power package in Ubuntu: New Bug description: When the display brightness is configured from settings -> brightness and display, while sliding the slider the user gets a preview of how it will look like the chosen value. Contrarily, when the brightness is controlled from quick settings, since the whole screen is black, the only clue is the brightness of the white text around. In Android, this is solved by making this screen transparent so the user can see the effect of using different values while sliding. Product: bq Aquaris E4.5, E5 & M10 FW version: OTA-10.1 HW version: MP STEPS TO REPRO: 1. Pull down upper quick settings and check how screen is blackened 2. Now from battery toggle change screen brightness Actual Result: User can not know in advance what their chosen setting will be like Expected Result: Screen brightness changed from upper quick settings should work the same as brightness toggle in settings To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587367/+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 1628649] Re: Date and time are too far away from each other
** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed ** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => Medium -- 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/1628649 Title: Date and time are too far away from each other Status in indicator-datetime package in Ubuntu: Confirmed Bug description: In Yakkety beta the date and time were moved farther away from each other than before. There's now an about 15px space between them on my machine, whereas the gap between all other symbols is usually 12px. Date and time are the two pieces of information that are logically the closest to each other, hence having a larger space between them than between irrelevant icons is really disturbing to my eyes. I understand that it deserves a bigger space than a simple space character (as between the day of week, month and day), but it shouldn't be bigger than the gap between let's say wifi strenght and kbd layout, or between the time and the poweroff symbol etc. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 28 20:56:44 2016 InstallationDate: Installed on 2012-05-30 (1582 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to yakkety on 2016-09-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1628649/+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