I have reported on this issue before and I last experienced it in 14.04.
I can confirm that my set-up is also two identical monitors; one connected via
HDMI and another via DP.
Contrary to some other affected users here, I used to have the problem in
14.04, but I do not seem to experience it afte
It appears that this is happening when one of the screens is connected
to DP or HDMI.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to compiz-plugins-main in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1295267
T
** No longer affects: unity (Ubuntu)
** Branch linked: lp:~azzar1/unity-lens-applications/lp-1582433
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity-lens-applications in Ubuntu.
https://bugs.launchpad.net/bugs/1582433
Title:
Dash doe
** Also affects: unity-lens-applications (Ubuntu)
Importance: Undecided
Status: New
** Changed in: unity-lens-applications (Ubuntu)
Status: New => In Progress
** Changed in: unity-lens-applications (Ubuntu)
Assignee: (unassigned) => Andrea Azzarone (azzar1)
** Changed in: u
This bug was fixed in the package empathy - 3.12.11-0ubuntu4
---
empathy (3.12.11-0ubuntu4) yakkety; urgency=medium
* Drop Revert-geoclue-2.0.patch and switch to geoclue-2.0 (LP: #1389336)
* Enable geoclue and map support now that empathy is in universe
* Drop 47_git_activate_wi
Matthew, I don't know, I've just suggested it as a possible workaround
or whatever it might be called.
I've reported my problem here: https://bugs.launchpad.net/bugs/1556622 which
was marked as duplicate of this bug report, and I can confirm that the problem
I've first seen with iPad is the same
confirmed no fix yet for xubuntu 16.04 this is a non starter for the
library as users must be auto logged in or the librarians have to run
around and login every machine
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu
** Package changed: unity8 (Ubuntu) => indicator-power (Ubuntu)
--
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/1583099
Title:
[phone] Brightness slider should show value set by use
You have been subscribed to a public bug:
Reproduce step #1:
1. For convenience, set screen time out to 30 seconds.
2. Pull power indicator down, then set brightness to some value above the
lowest.
3. Leave the indicator open and wait until screen dims the brightness.
Expected result: Brightness
The same problem happens with the brightness slider in System Settings.
So this is not a problem with indicator-power, it is a problem with the
shell.
I don’t think it’s healthy for the brightness slider to have to know
about, and ignore, Unity altering the system brightness for locking
purposes —
Same issue on M10 rc-proposed
--
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/1581089
Title:
Clock app opened when closing Alarms
Status in C
Opened bug #1583639 for a real API
** Changed in: canonical-developer-experience
Importance: Undecided => Medium
** Changed in: canonical-developer-experience
Assignee: (unassigned) => Alejandro J. Cura (alecu)
** No longer affects: canonical-developer-experience
--
You received this b
** Changed in: canonical-developer-experience
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/1480200
Title:
i
Sadi, which device is shown in the menu title is unrelated to this bug,
because the same icon is supposed to be shown for the device inside the
menu as well. If the problem occurs inside the menu as well, it’s
probably a missing or misreferenced icon; if it doesn’t, it’s probably
an inconsistency i
I also started experiencing this problem on 16.04, right after I had
enabled “turn screen off when inactive” in the system settings. I have
two identical Iiyama monitors, one of which is attached to the DVI port
of the integrated Intel graphics, the other to the HDMI port.
--
You received this bu
15 matches
Mail list logo
