Is there something special you need to do after these "solutions".
Because I did the gsettings thing to no avail. I tried the gnome3 thing
and again, nothing changed. Do I need to logout and back in? Do I need
to reboot?
A while ago something got flaky with X so I decided I should logout and
back
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: indicator-session (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscription
** Changed in: url-dispatcher
Status: In Progress => Fix Released
** Changed in: url-dispatcher (Ubuntu RTM)
Status: New => Triaged
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to url-dispatcher in Ubuntu.
https://bugs.launchpad
This bug was fixed in the package indicator-transfer -
0.1+15.04.20141103-0ubuntu1
---
indicator-transfer (0.1+15.04.20141103-0ubuntu1) vivid; urgency=low
[ Ted Gould ]
* Fix menu path cut-and-paste error (LP: #1358340)
-- Ubuntu daily releaseMon, 03 Nov 2014
21:08:21 +
** Branch linked: lp:~ubuntu-branches/ubuntu/vivid/indicator-transfer
/vivid-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, dx-packages, dx-packages
https://bugs.laun
This bug was fixed in the package indicator-messages -
13.10.1+15.04.20141103-0ubuntu1
---
indicator-messages (13.10.1+15.04.20141103-0ubuntu1) vivid; urgency=low
[ Ted Gould ]
* Add filtering for lock screen. (LP: #1358340)
[ Lars Uebernickel ]
* libmessaging-menu: allow num
This bug was fixed in the package indicator-messages -
13.10.1+15.04.20141103-0ubuntu1
---
indicator-messages (13.10.1+15.04.20141103-0ubuntu1) vivid; urgency=low
[ Ted Gould ]
* Add filtering for lock screen. (LP: #1358340)
[ Lars Uebernickel ]
* libmessaging-menu: allow num
This bug was fixed in the package indicator-messages -
13.10.1+15.04.20141103-0ubuntu1
---
indicator-messages (13.10.1+15.04.20141103-0ubuntu1) vivid; urgency=low
[ Ted Gould ]
* Add filtering for lock screen. (LP: #1358340)
[ Lars Uebernickel ]
* libmessaging-menu: allow num
Hello everyone,
I found this post after a google search. I'm using 14.04.1 and still
experience this issue. With workspaces enabled the overlay doesn't work.
Otherwise no problem. My screen-resolution is 1024*768
--
You received this bug notification because you are a member of DX
Packages, whic
This bug was fixed in the package indicator-session -
12.10.5+15.04.20141103-0ubuntu1
---
indicator-session (12.10.5+15.04.20141103-0ubuntu1) vivid; urgency=low
[ Sebastien Bacher ]
* update the translations template during the build (LP: #1385260)
-- Ubuntu daily releaseMon,
This bug was fixed in the package ido - 13.10.0+15.04.20141103-0ubuntu1
---
ido (13.10.0+15.04.20141103-0ubuntu1) vivid; urgency=low
[ Ted Gould ]
* Update tags for newer GObject Introsepction Scanner and disable
xorg-gtest tests (LP: #1382020)
-- Ubuntu daily releaseMon,
msp3k - I got the same thing but just ran unity --replace in a terminal
window I had left open on the desktop. I didn't check to see if could
open a terminal. But running unity --replace from the desktop (w/o dash,
launcher, panel, menu bar, etc.) resulted in getting them all back. It
was ugly - ma
** Branch linked: lp:ubuntu/vivid-proposed/indicator-session
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-session in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1385260
Title:
translation templat
Public bug reported:
Steps to reproduce:
1. Open System Settings
2. Open the Time & Date panel
3. Set 'Set the time and date:' to 'Manually'
4. Tap on the date and time label and set the date and time to something in the
future (a few months ahead)
5. Go back and wait for the time indicator to u
This bug was fixed in the package ubuntu-system-settings -
0.3+15.04.20141103-0ubuntu1
---
ubuntu-system-settings (0.3+15.04.20141103-0ubuntu1) vivid; urgency=low
[ Ken VanDine ]
* Use the SliderMenu component instead of the Slider component, it
matches the design and doesn't
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-system-settings
--
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/1289465
Title:
Brightness icons are suboptimal
Status in “indicato
** Changed in: compiz
Status: Fix Committed => Fix Released
--
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/1234624
Title:
Spread - In the spread vi
** Changed in: compiz
Status: Fix Committed => Fix Released
--
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/1204664
Title:
control+super+d works jus
** Changed in: compiz
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to compizconfig-backend-gconf in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/207065
Title:
Bad C
** Changed in: compiz
Status: Fix Committed => Fix Released
--
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/742028
Title:
compiz crashed with SIGSEG
Whoops, looks like the upower dump was attached by default. :)
--
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/1388911
Title:
wrong indicator shown for full battery
Status in “indi
Public bug reported:
Toshiba Satellite C55-A-1M7.
When my battery is fully charged, the indicator reverts to just a full
battery (no emblem inside the battery, like a small lightning bolt). I'm
given to understand the icon should be different, and believe it was
different (with an embled inside)
** Tags added: ota-1 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/1387231
Title:
[regression][clock] alarm still rings once it's been
** Branch linked: lp:ubuntu/vivid-proposed/acpid
--
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/1201180
Title:
powerbtn.sh conflicts with logind
Status in “acpid” package in Ubuntu:
** Changed in: unity (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: unity
Status: Triaged => Won't Fix
** Changed in: compiz
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubu
Confirmed, way to trigger it easily
- connect to IRC using xchat-gnome with messaging menu integration enabled
- connect with another client and a nickname including a "|"
- talk to the first client
-> segfault
Lars, could you have a look to this one?
** Changed in: unity (Ubuntu)
Importance:
When I do that, I get the desktop back, but no dash, launcher, or panel.
On 11/03/2014 08:54 AM, Erik wrote:
> unity --replace
>
> On Mon, Nov 3, 2014 at 5:38 AM, Bruce MacNaughton
> wrote:
>
>> I have this problem but can access the desktop using SSH. Is there a
>> process I can kill/restart to
I would like to know the answer to that as well. Back in the good 'ol
days the screen lock was a separate process, and "pkill -9
gnome-screensaver" would bring back the desktop. But now...? There is
a process called "/usr/lib/unity/unity-panel-service --lockscreen-mode",
but if I "kill -9" on it
unity --replace
On Mon, Nov 3, 2014 at 5:38 AM, Bruce MacNaughton
wrote:
> I have this problem but can access the desktop using SSH. Is there a
> process I can kill/restart to fix this condition?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:
Correction: I have upgraded up until 14.10 and am sure things still
worked as I was used to . Reinstalling broke things.
--
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.launchpa
** Changed in: ubuntu-ux
Assignee: James Mulholland (jamesjosephmulholland) => Paty Davila
(dizzypaty)
--
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.launchp
I want to propose reverting this change. I consider the current behavior to be
a bug. Switching is far more useful across workspaces and hardly useful inside
the current one.
I have been upgrading Ubuntu since 12.04 up until 14.04 and am quite sure the
behavior did not break then. Recently I rei
I have this problem but can access the desktop using SSH. Is there a
process I can kill/restart to fix this condition?
--
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.
Since my duplicate doesn't seem to add Ubuntu vivid to the affected
packages and the problem seems to have returned there: How do I mark the
bug as "affects ubuntu vivid" here? Or is doing so the Right Thing To
Do?
--
You received this bug notification because you are a member of DX
Packages, whi
Only to make things easier for everybody affected by the bug:
If I am right
gsettings set org.gnome.settings-daemon.plugins.cursor active false
fixes the problem.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching sub
I now have 3 clients (all up to date, 32 and 64 bit installations) for
whom it's happening on 14.04:
1) 24 inch 1920x1080 Samsung screen connected via HDMI (desktop)
2) 10 inch 1280x800 screen (netbook)
3) 15.6 inch 1920x1080 screen (laptop I mentioned previously)
Yet on my own 15.6 1920x1080 scr
36 matches
Mail list logo
