Downgrading unity and compiz to the previously available versions makes
the problem go away. Unfortunately I don't know if just one of them
would have been enough.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subs
The same problem has been reported as questions in AskUbuntu:
http://askubuntu.com/questions/618189/computer-logs-out-while-i-lock-screen
http://askubuntu.com/questions/611717/ubuntu-14-04-logs-me-out-when-i-try-to-lock-screen
I'll point these people here, but it seems like this is a pretty
wides
Several other people at my company have seen this issue, using Unity for
14.04. Also using nvidia.
Compiz segfaults when the lock screen is supposed to get rendered and
then the session is terminated, logging them out.
This started happening with the latest SRU, that ships:
compiz 1:0.9.11.3+14
** Description changed:
-I have a user reporting an incidence that trusty unity desktop got
+ I have a user reporting an incidence that trusty unity desktop got
unlocked on its own:
- "Well, I didn't unlock/lock the system before the auto-unlock that morning.
- What I mean is that, on t
Can this be backported to Trusty as well, please?
--
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/1302885
Title:
Media keyboard shortcuts not working
Stat
I wonder on which version of Unity is that supposed to work. Maybe it
works on Utopic, but it doesn't work on Trusty:
$ gdbus call --session --dest com.canonical.Unity --object-path
/com/canonical/Unity/Session --method com.canonical.Unity.Session.IsLocked
Error: GDBus.Error:org.freedesktop.DBus
Several users in my company were experiencing this issue, and it was
gone after installing the test packages provided by Marco. Please
backport this to Trusty ASAP.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching su
This is happening much more often since the latest Unity releases.
There were several changes done to the lockscreen and it seems that
these changes made this problem more frequent.
It seems to be particularly frequent when the machine is under heavy
load (i.e. compiling stuff), which seems to poi
Hi,
I'm able to reproduce this crash by using "Shaded windows" (that don't
work properly on Trusty anyway. See:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1322808), with the
following instructions:
1. Log into a fresh new user, running Unity
2. Press Windows key, start unity-tweak-tool
Still seeing this error on current Trusty, unity version
7.2.2+14.04.20140714-0ubuntu1.1
#0 unity::switcher::Controller::Impl::GetCurrentSelection
(this=this@entry=0x1ccc970)
at
/build/buildd/unity-7.2.2+14.04.20140714/launcher/SwitcherController.cpp:691
#1 0x7f781110e7fa in unity::swi
indicator-messages now includes an example of how this should be done.
Could you please fix gm-notify, please? Thanks.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to libindicate in Ubuntu.
https://bugs.launchpad.net/bugs/1310490
Title:
Doe
** Description changed:
- Ubuntu 14.04 login screen doesn't accept keyboard input in the password
- box after my system has resumed from a sleep (=lid opening), so I can't
- relogin anymore
+ After upgrading to Unity version 7.2.2+14.04.20140714-0ubuntu1 on
+ Trusty, the lockscreen sometimes fails
As mentioned in the duplicate bug, if you have text selected, this also
happens without suspending.
Also, I've retitled this bug since the bug is much much worse than not
taking the input, the input is actually sent to the underlying Chrome
window, so people that type their password without paying
** Summary changed:
- Password typed to unlock the screen is sent to the Chrome window that was in
focus
+ Password typed to unlock the screen is sent to the Chrome window if it had a
text selection
--
You received this bug notification because you are a member of DX
Packages, which is subscri
I downgraded unity's packages to the previous version
(7.2.1+14.04.20140513-0ubuntu2) and with that version I'm no longer able
to reproduce the problem.
The changelog of the current version (7.2.2+14.04.20140714-0ubuntu1)
includes lots of screensaver changes, including changes related to the
clipb
I'm affected as well, and I've been only able to reproduce with Chrome
35 or later. I tried several other applications and was not able to
reproduce. Including Firefox, gnome-terminal and Chrome 34.
Also, it only happens on Unity, other desktop environments are not
affected.
I tried 3 different v
*** This bug is a duplicate of bug 1345505 ***
https://bugs.launchpad.net/bugs/1345505
** This bug has been marked a duplicate of bug 1345505
lock screen leaks keystrokes to window "behind" greeter
--
You received this bug notification because you are a member of DX
Packages, which is sub
I'm affected as well, and I have more data on this issue: it only
happens with Chrome. I tried several other applications and was not
able to reproduce.
Also, it only happens on Unity, other desktop environments are not
affected.
I tried 2 different versions of compiz (the latest one and the one
As an affected user, I can also verify that this fixes the issue.
--
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/1290785
Title:
Users with UID >
Re-uploading the patch, there was a typo in the changelog.
** Patch added: "Debdiff including a patch for making high uids work again"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1343261/+attachment/4154749/+files/fix-high-uids.diff
** Patch removed: "Debdiff for the patch
This is the debdiff with the patch backported from Utopic
** Patch added: "Debdiff for the patch that fixes the issue"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1343261/+attachment/4154644/+files/fix-high-uids.diff
--
You received this bug notification because you are a
Public bug reported:
Version: 0.6.35-0ubuntu7
This bug is visible in lightdm, but it's actually a problem in Trusty's
accountsservice. The code in user-classify.c forces the user account to
be between 1000 and 6. Any accounts higher than 6 are
considered systems accounts and not shown i
This is still a problem. Seen in a machine upgraded from 12.04 to 14.04.
This bug has more than 10 duplicates and more than 200 people affected.
Can we get some traction into getting a real fix instead of recommending
a killall command?
--
You received this bug notification because you are a mem
This keeps happening over and over. Looking at the resolution of the
other bug, I expect the code that needs to be fixed is not here, but in
the handling of some element in this queue. I suspect some element is
getting deleted and the memory reused without it being removed from the
queue.
Here's
Public bug reported:
Hi, this is basically the same bug as
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1298202, but that
bug is marked as Fix Released with Unity 7.2.0, and I'm still seeing
this bug on trusty, with the latest Unity version (unity
7.2.1+14.04.20140513-0ubuntu2). I already
So, I removed the dupe. Just so that the info stays visible. The duped
bug was:
https://bugs.launchpad.net/ubuntu/+source/libindicate/+bug/1315384
(14.04 libmessaging-menu lacks an example of how to use the features that used
to be provided by python-indicate in 12.04)
--
You received this bu
This bug is duped to a bug that was related to the lack of examples. I
understand that an example was needed in order to fix this one, but it's
definitely not a dupe of that one.
** This bug is no longer a duplicate of bug 1315384
14.04 libmessaging-menu lacks an example of how to use the feat
This is very easy to reproduce, you don't even need to type your real password:
1 - Lock the screen with Ctrl-Alt-L
2 - Wait until it turns completely black (aprox. 15 seconds)
3 - Start typing, it doesn't need to be your password, you can count your chars
and see that the amount on the screen (wh
I'm having this issue as well. It's not very frequent but it has
happens once in a while.
I have a machine with an NVIDIA card, using proprietary nvidia drivers,
dual monitor display. Since it's not very often, I haven't yet been
able to correlate it with any specific event.
My pam configuratio
Hi,
Still seeing this bug, also when unlocking the screen. Unity version
7.2.0+14.04.20140423-0ubuntu1.2. Is the fix supposed to be released to
Trusty?
This is the stacktrace top from the apport crash report:
?? ()
nux::WindowThread::ComputeQueuedLayout() () from
/usr/lib/x86_64-linux-gnu/libnu
This happened to me once on a two monitor desktop.
I also have the two lock bug, and it happened after I had already
unlocked the first lock. i.e. I entered my password, had a brief glance
of my desktop and then got the lock again (normal), but the lock didn't
show the dots when I tried to type my
So, when will 7.2.1 be 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/1292451
Title:
screensaver re-locks itself after unlocking if the configur
As can be seen in http://bazaar.launchpad.net/~unity-
team/unity/5.0/changes/2425?start_revid=2425, the commit was submitted
in revision 2423, but there have been no Unity 5 releases after that.
Is there going to be a last Unity 5 release, or is 5.20 the last one?
--
You received this bug notifi
Actually, it doesn't seem to be fixed in Precise. This is the latest
changelog entry of the current Precise version:
unity (5.20.0-0ubuntu3) precise-proposed; urgency=low
* Add initial support for pointer barriers with xinput2 api. (LP: #1242633)
- Fallback to xfixes stays available.
* B
This might be a dupe of https://bugs.launchpad.net/ubuntu/+source/gnome-
screensaver/+bug/1291365. Although in that case it's described as only
happening after having left the desktop locked for a while, instead of
immediately after locking.
--
You received this bug notification because you are
35 matches
Mail list logo
