Public bug reported:
I'm doing a preseeded installation that installs some additional
package, among them the nvidia driver package that triggers dkms
compilation and after that a call to update-initramfs.
If the installer is running a different kernel than the kernel that gets
installed in the
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 Ubuntu
Touch seeded packages, which is subscribed to unity in
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
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
** 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
This bug is still affecting Trusty. Not only it affects cinnamon-
screensaver, but it also affects gnome-screensaver. Anyone running
either of these two screensavers will suffer their session getting
hijacked by someone pressing the menu key before the password box comes
up.
The patch is simple
** Description changed:
- Please see:
+ [Impact]
+ Users running gnome-screensaver or cinnamon-screensaver may get their lock
screen bypassed by users pressing the menu key before the password prompt turns
up.
+ [Testcase]
+ Start GNOME or any other desktop running gnome-screensaver. Open a
Public bug reported:
After some conditional blocks, it's possible that an infinite loop is
generated.
See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59358
This problem was fixed back in December 2013 in the 4.8 branch as well
as the trunk branch. However, the trusty package ended up without
** Bug watch added: GCC Bugzilla #59358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59358
** Also affects: gcc via
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59358
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Can this be backported to Trusty as well, please?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1302885
Title:
Media keyboard shortcuts not working
Status in Unity:
Fix
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:
I just spent two hours yesterday debugging this issue, Network Manager
was not starting because there was a static interface configured that
wasn't present.
The fix is simple and works, please apply it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
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 Ubuntu
Touch seeded packages, which is subscribed to unity in
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
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
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
** 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
*** 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 Ubuntu
Touch seeded
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
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
As an affected user, I can also verify that this fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1290785
Title:
Users with UID 6 are
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
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
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
24 matches
Mail list logo
