[Dx-packages] [Bug 1451613] Re: Unity/compiz crashes when locking screen
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 subscriptions: dx-packages https://bugs.launchpad.net/bugs/1451613 Title: Unity/compiz crashes when locking screen Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+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 1451613] Re: Unity/compiz crashes when locking screen
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.04.20150313-0ubuntu1 unity 7.2.4+14.04.20150316-0ubuntu1 It was not happening before. -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+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 1451613] Re: Unity/compiz crashes when locking screen
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 widespread problem. -- 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/1451613 Title: Unity/compiz crashes when locking screen Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+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 1410582] Re: [Trusty / Unity] Desktop got unlocked on its own.
** 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 that morning after coming to my desk, I started
- working on my Mac and just press the space bar on my desktop to get the
- monitors woken up. The monitors came up with the locked screen and then
- after a while it got unlocked to my surprise!
+ In the morning, after coming to my desk, I just pressed the space bar
+ on my desktop to get the monitors woken up. The monitors came up with
+ the locked screen and then after a while it got unlocked to my
+ surprise!
-There was compiz crash file on his system at that time. However, I
+ There was compiz crash file on his system at that time. However, I
don't have the right debug symbols to which file (or function) it
crashed into. Here is the top part of the stack trace when I ran apport-
retrace -s on his crash file:
---
--- stack trace ---
#0 0x7ff17ed06608 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#1 0x7ff17ed06cf3 in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#2 0x7ff17ed04e2d in ?? () from
/usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
No symbol table info available.
#3 0x7ff17f3fdd02 in g_settings_backend_read (backend=optimized out,
key=key@entry=0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen,
expected_type=0x7ff1877135a0 g_variant_type_info_basic_chars,
default_value=default_value@entry=0) at
/build/buildd/glib2.0-2.40.2/./gio/gsettingsbackend.c:701
- value = optimized out
+ value = optimized out
#4 0x7ff17f401c7b in g_settings_read_from_backend
(settings=settings@entry=0x7ff13800a570, key=key@entry=0x7fffdde9c920,
user_value_only=user_value_only@entry=0, default_value=default_value@entry=0)
at /build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1052
- value = optimized out
- fixup = optimized out
- path = 0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen
+ value = optimized out
+ fixup = optimized out
+ path = 0xab011c0 /org/gnome/desktop/lockdown/disable-lock-screen
#5 0x7ff17f402e7a in g_settings_get_value (settings=0x7ff13800a570,
key=0x2087618 disable-lock-screen) at
/build/buildd/glib2.0-2.40.2/./gio/gsettings.c:1092
- skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c
disable-lock-screen, is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0
g_variant_type_info_basic_chars, minimum = 0x0, maximum = 0x0, default_value
= 0xb9c5b30, ref_count = 0}
- value = optimized out
- __FUNCTION__ = g_settings_get_value
+ skey = {schema = 0x7ff13c017a80, name = 0x4b2fa7c
disable-lock-screen, is_flags = 0, is_enum = 0, strinfo = 0x0, strinfo_length
= 0, unparsed = 0x0, lc_char = 0 '\000', type = 0x7ff1877135a0
g_variant_type_info_basic_chars, minimum = 0x0, maximum = 0x0, default_value
= 0xb9c5b30, ref_count = 0}
+ value = optimized out
+ __FUNCTION__ = g_settings_get_value
-
-The top part of the trash file when viewed in TextEdit has the information
:
+ The top part of the trash file when viewed in TextEdit has the information
:
-
ProblemType: Crash
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Dec 12 10:16:52 2014
DistroRelease: Ubuntu 14.04
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1405349348
ProcCmdline: compiz
--
-His system is Ubuntu trusty 14.04.1 LTS. Unity installed
+ His system is Ubuntu trusty 14.04.1 LTS. Unity installed
7.2.3+14.04.20140826-0ubuntu1.0.1 .
--
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/1410582
Title:
[Trusty / Unity] Desktop got unlocked on its own.
Status in Unity:
In Progress
Status in Unity 7.2 series:
In Progress
Status in unity package in Ubuntu:
In Progress
Bug description:
I have a user reporting an incidence that trusty unity desktop got
unlocked on its own:
In the morning, after coming to my desk, I just pressed the space bar
on my desktop to get the monitors woken up. The monitors came up with
the locked screen and then after a while it got unlocked to my
surprise!
[Dx-packages] [Bug 1342152] Re: GetActive method for the screensaver reports False even when screensaver is active
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.Error.UnknownMethod: No such method
'IsLocked'
Is there any alternative for Trusty?
I understand the fact that it's not the same thing to have the screen
locked than to have the screen in blacked out. However, there have been
plenty of programs or applets written in the past that check whether the
screensaver is active or not by checking this method and this is how it
worked with Unity in Precise. This basically breaks anything that used
those checks, requiring changes specific for Unity, while gnome-
screensaver keeps behaving the same way.
--
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/1342152
Title:
GetActive method for the screensaver reports False even when
screensaver is active
Status in Unity:
Won't Fix
Status in “unity” package in Ubuntu:
Won't Fix
Bug description:
Hi!
unity version: 7.2.1+14.04.20140513-0ubuntu2 (Trusty)
I have an application that checks the state of the screen saver via
dbus. Unity implements an interface for using org.gnome.ScreenSaver,
so as far as I can see, this should work (Python example):
import dbus
session_bus = dbus.SessionBus()
session_manager = session_bus.get_object('org.gnome.ScreenSaver',
'/org/gnome/ScreenSaver')
session_manager.GetActive(dbus_interface='org.gnome.ScreenSaver')
This correctly returns False when the screensaver is not active,
however, when I lock the screen and check (using a call to
time.sleep), it also returns False.
I have checked that calling:
session_manager.SetActive(True, dbus_interface='org.gnome.ScreenSaver')
Correctly activates the screensaver, so that part seems to be working.
However, even in that case, if after activating the screensaver I call
GetActive it returns False.
From looking at the code [1], I suspect the problem is that when I
lock the screen via Ctrl-Alt-L, the internal _active member is not
being set to True, but I'm not sure what might be going on with the
variable after SetActive is called.
[1]: http://bazaar.launchpad.net/~unity-greeter-team/unity-
greeter/trunk/view/head:/src/settings-daemon.vala#L172
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1342152/+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 1311316] Re: After locking screen there is no input field to type password for unlock
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 subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1311316] Re: After locking screen there is no input field to type password for unlock
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 point to some kind of race condition that is made worse when things are going slow. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1274438] Re: compiz crashed with SIGSEGV in unity::switcher::Controller::Impl::GetCurrentSelection()
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 3. Select Window Manager/Additional settings 4. Set Title Bar Actions/Double Click to Toggle Shade 5. Start a terminal 6. In the terminal, 'pgrep compiz' to get the current PID 7. Double click on titlebar to shade it; window will become ghosted 8. Press Alt-Tab to switch windows; keep holding down Alt and press Tab until the terminal window is selected 9. Release Alt. 10. Compiz crashes and takes a while to restart. Repeat 'pgrep compiz' to see new PID for compiz -- 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/1274438 Title: compiz crashed with SIGSEGV in unity::switcher::Controller::Impl::GetCurrentSelection() Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: The switcher hung and then this crash occurred. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jan 30 09:30:55 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-12-06 (54 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f07f56b85f3 _ZNK5unity8switcher10Controller4Impl19GetCurrentSelectionEv+323: mov (%rdi),%rbp PC (0x7f07f56b85f3) ok source (%rdi) (0x) not located in a known VMA region (needed readable region)! destination %rbp ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: unity::switcher::Controller::Impl::GetCurrentSelection() const () from /usr/lib/compiz/libunityshell.so unity::switcher::Controller::Impl::Hide(bool) () from /usr/lib/compiz/libunityshell.so unity::UnityScreen::altTabTerminateCommon(CompAction*, unsigned int, std::vectorCompOption, std::allocatorCompOption ) () from /usr/lib/compiz/libunityshell.so compiz::private_screen::EventManager::triggerRelease(CompAction*, unsigned int, std::vectorCompOption, std::allocatorCompOption ) () from /usr/lib/libcompiz_core.so.ABI-20130415 PrivateScreen::triggerStateNotifyBindings(std::vectorCompOption, std::allocatorCompOption , _XkbStateNotifyEvent*, std::vectorCompOption, std::allocatorCompOption ) () from /usr/lib/libcompiz_core.so.ABI-20130415 Title: compiz crashed with SIGSEGV in unity::switcher::Controller::Impl::GetCurrentSelection() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1274438/+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 1274438] Re: compiz crashed with SIGSEGV in unity::switcher::Controller::Impl::GetCurrentSelection()
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::switcher::Controller::Impl::Hide
(this=0x1ccc970,
accept_state=optimized out)
at
/build/buildd/unity-7.2.2+14.04.20140714/launcher/SwitcherController.cpp:477
#2 0x7f781110eab6 in unity::switcher::Controller::Hide (this=optimized
out,
accept_state=accept_state@entry=true)
at
/build/buildd/unity-7.2.2+14.04.20140714/launcher/SwitcherController.cpp:118
#3 0x7f7810f6f30f in unity::UnityScreen::altTabTerminateCommon
(this=0x1707200, action=0x1690340,
state=8194, options=...)
This is the function that is affected:
Selection Controller::Impl::GetCurrentSelection() const
{
AbstractLauncherIcon::Ptr application;
Window window = 0;
if (model_)
{
application = model_-Selection();
if (application)
{
if (model_-detail_selection)
{
window = model_-DetailSelectionWindow();
}
else if (model_-SelectionIsActive())
{
window = model_-DetailXids().front(); // This is line 691
}
}
}
return {application, window};
}
--
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/1274438
Title:
compiz crashed with SIGSEGV in
unity::switcher::Controller::Impl::GetCurrentSelection()
Status in Unity:
New
Status in “unity” package in Ubuntu:
Confirmed
Bug description:
The switcher hung and then this crash occurred.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20131106.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 30 09:30:55 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2013-12-06 (54 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64
(20131016.1)
ProcCmdline: compiz
SegvAnalysis:
Segfault happened at: 0x7f07f56b85f3
_ZNK5unity8switcher10Controller4Impl19GetCurrentSelectionEv+323: mov
(%rdi),%rbp
PC (0x7f07f56b85f3) ok
source (%rdi) (0x) not located in a known VMA region (needed
readable region)!
destination %rbp ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
unity::switcher::Controller::Impl::GetCurrentSelection() const () from
/usr/lib/compiz/libunityshell.so
unity::switcher::Controller::Impl::Hide(bool) () from
/usr/lib/compiz/libunityshell.so
unity::UnityScreen::altTabTerminateCommon(CompAction*, unsigned int,
std::vectorCompOption, std::allocatorCompOption ) () from
/usr/lib/compiz/libunityshell.so
compiz::private_screen::EventManager::triggerRelease(CompAction*, unsigned
int, std::vectorCompOption, std::allocatorCompOption ) () from
/usr/lib/libcompiz_core.so.ABI-20130415
PrivateScreen::triggerStateNotifyBindings(std::vectorCompOption,
std::allocatorCompOption , _XkbStateNotifyEvent*, std::vectorCompOption,
std::allocatorCompOption ) () from /usr/lib/libcompiz_core.so.ABI-20130415
Title: compiz crashed with SIGSEGV in
unity::switcher::Controller::Impl::GetCurrentSelection()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip fuse lpadmin plugdev sambashare sbuild
sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1274438/+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 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
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: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+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 1349128] Re: Password typed to unlock the screen is sent to underlying Chrome window
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 too much attention are at risk of sending their password over hangouts or similar. ** Summary changed: - Ubuntu 14.04 lock screen doesn't accept keyboard input (until using indicators) + Password typed to unlock the screen is sent to underlying Chrome window -- 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/1349128 Title: Password typed to unlock the screen is sent to underlying Chrome window Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: After upgrading to Unity version 7.2.2+14.04.20140714-0ubuntu1 on Trusty, the lockscreen sometimes fails to take the keyboard focus away from Chrome. This might happen if there's a text selection in Chrome, and also when resuming after suspend. It doesn't always happen, as this is a race condition, but it's easy to reproduce by selecting the location bar in Chrome and then locking the screen. Workaround: click on any indicator in the upper right corner, and close the menu. After that, keyboard input is sent to the lockscreen again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+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 1349128] Re: Password typed to unlock the screen is sent to underlying Chrome window
** 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 to take the keyboard focus away + from Chrome. - Excpected behaviour: the login screen should accept keyboard input and - show them as stars in the password box. + This might happen if there's a text selection in Chrome, and also when + resuming after suspend. + + It doesn't always happen, as this is a race condition, but it's easy to + reproduce by selecting the location bar in Chrome and then locking the + screen. Workaround: click on any indicator in the upper right corner, and close - the menu. After that, keyboard input is accepted again. - - $ lsb_release -rd - Description: Ubuntu 14.04.1 LTS - Release: 14.04 - - System is fully updated. Problem started to happen one or two weeks ago, - so around mid July 2014. - - === - - A way to reproduce this is described at: - - https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1345505/comments/6 + the menu. After that, keyboard input is sent to the lockscreen again. -- 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/1349128 Title: Password typed to unlock the screen is sent to underlying Chrome window Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: After upgrading to Unity version 7.2.2+14.04.20140714-0ubuntu1 on Trusty, the lockscreen sometimes fails to take the keyboard focus away from Chrome. This might happen if there's a text selection in Chrome, and also when resuming after suspend. It doesn't always happen, as this is a race condition, but it's easy to reproduce by selecting the location bar in Chrome and then locking the screen. Workaround: click on any indicator in the upper right corner, and close the menu. After that, keyboard input is sent to the lockscreen again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349128/+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 1349953] Re: Password typed to unlock the screen is sent to the Chrome window that was in focus
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 before that) and I could reproduce with both, although the behaviour is not exactly the same. There's no need to suspend. Just locking the screen with Ctrl-Alt-L while having some text selected on the Chrome window usually triggers this bug (it's not always triggered, but something like 1 out of 3 times). ** Summary changed: - Screen locking issue + Password typed to unlock the screen is sent to the Chrome window that was in focus -- 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/1349953 Title: Password typed to unlock the screen is sent to the Chrome window that was in focus Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: After coming out of sleep mode, my keyboard cannot type to the password entry field. When I try to type to the password entry field, the computer sends my input to whatever window I had open before my computer went to sleep. This means that if I type my password and press enter, and the last window I had open was, say, a gchat, I will send my password to the person with whom I was talking. It seems like this bug only occurs when I had a text entry field selected before putting my computer to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 29 09:40:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 1800 InstallationDate: Installed on 2012-12-24 (582 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-07-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349953/+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 1349953] Re: Password typed to unlock the screen is sent to the Chrome window that was in focus
*** 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 subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1349953 Title: Password typed to unlock the screen is sent to the Chrome window that was in focus Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: After coming out of sleep mode, my keyboard cannot type to the password entry field. When I try to type to the password entry field, the computer sends my input to whatever window I had open before my computer went to sleep. This means that if I type my password and press enter, and the last window I had open was, say, a gchat, I will send my password to the person with whom I was talking. It seems like this bug only occurs when I had a text entry field selected before putting my computer to sleep. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 29 09:40:10 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 1800 InstallationDate: Installed on 2012-12-24 (582 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-07-23 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349953/+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 1345505] Re: lock screen leaks keystrokes to window behind greeter
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 versions of compiz (the latest one, the one before that and the original from trusty) and I could reproduce with all of them, although the behavior is not exactly the same. The reproduction case that I found most successful is locking the screen with Ctrl-Alt-L while having some text selected on the Chrome window, for example the location bar. So: 1) Open Chrome 35 or later (current stable is 36) 2) Ctrl-L to select the location bar 3) Ctrl-Alt-L to lock the screen After that, any characters I type while the lockscreen is dimming are sent through to Chrome. ** Summary changed: - lock screen leaks keystrokes to window behind greeter + Password typed to unlock the screen is sent to the Chrome window that was in focus -- 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/1345505 Title: Password typed to unlock the screen is sent to the Chrome window that was in focus Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When my machine comes out of suspend, I am shown the unity lockscreen. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: BugDistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1345505/+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 1345505] Re: Password typed to unlock the screen is sent to the Chrome window that was in focus
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 clipboard. Clearly, some of those changes don't interact well, at least with Chrome 35 and above, I haven't been able to reproduce with any other programs. -- 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/1345505 Title: Password typed to unlock the screen is sent to the Chrome window that was in focus Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When my machine comes out of suspend, I am shown the unity lockscreen. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: BugDistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1345505/+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 1345505] Re: Password typed to unlock the screen is sent to the Chrome window if it had a text selection
** 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 subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1345505 Title: Password typed to unlock the screen is sent to the Chrome window if it had a text selection Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When my machine comes out of suspend, I am shown the unity lockscreen. However, occasionally I am unable to enter my password since the password box is not given focus. Clicking with the mouse in the password box also doesn't help. I've found that clicking the settings cog (top right) twice allows me to regain control of the focus and enter my password. Aside from the inability to enter my password in the password box, it seems that simply typing my password (or in fact any text) results in those keystrokes being passed to the full-screen window *behind* the greeter. This should not be possible and is a security issue: imagine if my full-screen console was connected to a remote shared session, or was running an irc client, etc.). ProblemType: BugDistroRelease: Ubuntu 14.10 Package: lightdm 1.11.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 09:08:47 2014 InstallationDate: Installed on 2014-04-11 (99 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140409)SourcePackage: lightdm UpgradeStatus: Upgraded to utopic on 2014-05-08 (72 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1345505/+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 1290785] Re: Users with UID 60000 are invisible in login and Settings-User unless /etc/login.defs updated
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 6 are invisible in login and Settings-User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Fix Committed Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID UID_MIN. In 13.10 this was changed to UID UID_MIN or UID UID_MAX. [Test Case] 1. Create a user with a UID UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: big-uid is shown in the greeter. Once logged in big-uid is shown in system settings. Observed result: big-uid is not shown in the greeter (14.04 LTS, 14.10) big-uid is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+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 1343261] [NEW] User accounts with id higher than 60000 are not shown in Trusty
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 in lightdm. In Utopic this is fixed by modifying the code to not take into account any maximum, but rather use the minimum and then filter nobody and nobodynfs. Editing login.defs is possible but is not enough, because in that case, nobody isn't filtered. The patch is quite small and can be backported to Trusty without much issue. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- 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/1343261 Title: User accounts with id higher than 6 are not shown in Trusty Status in “accountsservice” package in Ubuntu: New Bug description: 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 in lightdm. In Utopic this is fixed by modifying the code to not take into account any maximum, but rather use the minimum and then filter nobody and nobodynfs. Editing login.defs is possible but is not enough, because in that case, nobody isn't filtered. The patch is quite small and can be backported to Trusty without much issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1343261/+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 1343261] Re: User accounts with id higher than 60000 are not shown in Trusty
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 member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1343261 Title: User accounts with id higher than 6 are not shown in Trusty Status in “accountsservice” package in Ubuntu: New Bug description: 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 in lightdm. In Utopic this is fixed by modifying the code to not take into account any maximum, but rather use the minimum and then filter nobody and nobodynfs. Editing login.defs is possible but is not enough, because in that case, nobody isn't filtered. The patch is quite small and can be backported to Trusty without much issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1343261/+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 1343261] Re: User accounts with id higher than 60000 are not shown in Trusty
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 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 member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1343261 Title: User accounts with id higher than 6 are not shown in Trusty Status in “accountsservice” package in Ubuntu: New Bug description: 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 in lightdm. In Utopic this is fixed by modifying the code to not take into account any maximum, but rather use the minimum and then filter nobody and nobodynfs. Editing login.defs is possible but is not enough, because in that case, nobody isn't filtered. The patch is quite small and can be backported to Trusty without much issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1343261/+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 1244285] Re: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04)
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 member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1244285 Title: Date/time sometimes doesn’t appear in menu bar, settings greyed out (Ubuntu 13.10, 14.04) Status in One Hundred Papercuts: Triaged Status in The Date and Time Indicator: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: it does not happen often, and when it happens, just a log out and re- log in is enough to restore it. http://askubuntu.com/questions/357266/how-to-show-time-in- ubuntu-13-10/357280 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1244285/+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 1337244] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
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 the latest stacktrace: #0 0x in ?? () #1 0x7fdd0a32c75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x2319f40) at ./WindowThread.cpp:318 #2 0x7fdd0a32db28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x2319f40, clip=...) at ./WindowThread.cpp:1627 #3 0x7fdd0ba61389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fdd0ba61748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fdd1b3da272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fdd1b3daed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fdd203e144f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fdd203e4af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fdd2cc6b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fdd2cc6b5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fdd2cc6ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fdd2b15735f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fdd2ac49ce5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fdd2ac4a048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fdd2ac4a30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fdd2cc260eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () -- 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/1337244 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in “unity” package in Ubuntu: New Bug description: 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 mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) ()
[Dx-packages] [Bug 1337244] [NEW] compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
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 mentioned in that bug that I was still seeing it quite a while ago, but got no reply to that. Crashes are being experienced in multiple machines, while unlocking the screen. The stacktraces vary, but they always fail in the same function and same line. First stacktrace: #0 0x0410 in ?? () #1 0x7fd4bf4eb75d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x22c1990) at ./WindowThread.cpp:318 #2 0x7fd4bf4ecb28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x22c1990, clip=...) at ./WindowThread.cpp:1627 #3 0x7fd4c0c20389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd4c0c20748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd4d4f2e272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd4d4f2eed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd4d556944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd4d556caf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd4e12c053d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd4e12c05ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd4e12bfb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd4df7ac35f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd4df29ece5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd4df29f048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd4df29f30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd4e127b0eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Second stacktrace (different machine): #0 0x7f0058407ed0 in nux_area_accessible_check_pending_notification () from /usr/lib/compiz/libunityshell.so #1 0x7f0056cb175d in nux::WindowThread::ComputeQueuedLayout (this=this@entry=0x1d530e0) at ./WindowThread.cpp:318 #2 0x7f0056cb2b28 in nux::WindowThread::RenderInterfaceFromForeignCmd (this=0x1d530e0, clip=...) at ./WindowThread.cpp:1627 #3 0x7f00583e6389 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7f00583e6748 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7f00705e2272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7f00705e2ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7f0070c1d44f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7f0070c20af2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7f007879b53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7f007879b5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7f007879ab4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7f0076c8735f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7f0076779ce5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f007677a048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f007677a30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7f00787560eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () I have more, but I don't know how useful it is to add them all. All stacktraces have
[Dx-packages] [Bug 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
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 features that used to be provided by python-indicate in 12.04 -- 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: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+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 1310490] Re: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS
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 bug notification because you are a member of DX Packages, which is subscribed to libindicate in Ubuntu. https://bugs.launchpad.net/bugs/1310490 Title: Doesn't register to use the messaging menu (indicator-messages) on 14.04 LTS Status in Highly Ubuntu integrated GMail Notifier: Confirmed Status in Libindicate: Confirmed Status in “gm-notify” package in Ubuntu: Confirmed Status in “libindicate” package in Ubuntu: Confirmed Bug description: I've recently upgraded from Ubuntu 12.04.4 LTS to 14.04 LTS. I've noticed, that the mail icon (indicator-messages) is hidden (I don't use Thunderbird, so it is not installed.) I know, that it is hidden, because I'm using GMail Notifier, which displays itself if new mail has arrived, and it works. Package info: gm-notify: Installed: 0.10.3-0ubuntu3 Candidate: 0.10.3-0ubuntu3 Version table: *** 0.10.3-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status indicator-messages: Installed: 13.10.1+14.04.20140410-0ubuntu1 Candidate: 13.10.1+14.04.20140410-0ubuntu1 Version table: *** 13.10.1+14.04.20140410-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-indicate: Installed: 12.10.1-0ubuntu3 Candidate: 12.10.1-0ubuntu3 Version table: *** 12.10.1-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status $ gsettings get com.canonical.indicator.messages applications @as [] Please fix this issue! To manage notifications about this bug go to: https://bugs.launchpad.net/gm-notify/+bug/1310490/+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 1308265] Re: First password letter not registered in lockscreen if screen off
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 (when it wakes up) doesn't match. e.g. I tried typing 1234 and only three stars appeared. Although this is not a security concern, it's a pretty annoying regression, so I hope the fix gets backported to trusty. Thanks! -- 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/1308265 Title: First password letter not registered in lockscreen if screen off Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: With the new lockscreen, if my screen is off, I just start typing, every time my password is too short. It looks like the first key only triggers the screen on and does not go to the input field. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140414.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 23:59:08 2014 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308265/+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 1311316] Re: After locking screen there is no input field to type password for unlock
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 configuration is customized, but I don't believe it's related at all, since most of the time it works fine. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+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 1298202] Re: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout()
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/libnux-4.0.so.0 nux::WindowThread::RenderInterfaceFromForeignCmd(nux::Rect const) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0 unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so And the full stack trace: #1 0x7fd95322e75d in nux::WindowThread::ComputeQueuedLayout() () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0 #2 0x7fd95322fb28 in nux::WindowThread::RenderInterfaceFromForeignCmd(nux::Rect const) () from /usr/lib/x86_64-linux-gnu/libnux-4.0.so.0 #3 0x7fd95496e0a9 in unity::UnityScreen::paintDisplay() () from /usr/lib/compiz/libunityshell.so #4 0x7fd95496e468 in unity::UnityScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so #5 0x7fd9688b1272 in GLScreen::glPaintOutput(GLScreenPaintAttrib const, GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so #6 0x7fd9688b1ed4 in PrivateGLScreen::paintOutputs(std::listCompOutput*, std::allocatorCompOutput* , unsigned int, CompRegion const) () from /usr/lib/compiz/libopengl.so #7 0x7fd968ce944f in CompositeScreen::paint(std::listCompOutput*, std::allocatorCompOutput* , unsigned int) () from /usr/lib/compiz/libcomposite.so #8 0x7fd968cecaf2 in CompositeScreen::handlePaintTimeout() () from /usr/lib/compiz/libcomposite.so #9 0x7fd975d8d53d in CompTimer::triggerCallback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #10 0x7fd975d8d5ef in CompTimeoutSource::callback() () from /usr/lib/libcompiz_core.so.ABI-20140123 #11 0x7fd975d8cb4d in CompTimeoutSource::dispatch(sigc::slot_base*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #12 0x7fd97427935f in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/x86_64-linux-gnu/libglibmm-2.4.so.1 #13 0x7fd973d6bce5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7fd973d6c048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fd973d6c30a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fd975d480eb in compiz::private_screen::EventManager::startEventLoop(_XDisplay*) () from /usr/lib/libcompiz_core.so.ABI-20140123 #17 0x00401971 in main () Please let me know if you want more information. -- 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/1298202 Title: compiz crashed with SIGSEGV in nux::WindowThread::ComputeQueuedLayout() Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: no further informations To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1298202/+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 1292451] Re: screensaver re-locks itself after unlocking if the configured screen-off timer goes off while screen is locked
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 configured screen- off timer goes off while screen is locked Status in Unity: Fix Committed Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Set screen-off timeout to 1 minute 2. Configure screen to lock immediately when screen goes off. 3. Lock screen manually (Ctrl+Alt+L) 4. Wait for 1 minute 5. Notice that screen doesn't turn off 6. Unlock screen 7. Wait a couple of seconds (~10 or so) 8. Notice that screen re-locks itself. 9. Repeat steps 6-7 and notice that the screen doesn't re-lock itself this time. There are two bugs described here: 1. Screen does not shut off if the screen is locked manually before the idle timer (see step 5). 2. Screen re-locks itself after unlocking if the idle timer goes off while the screen is locked (see step 7). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu11 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 14 18:19:26 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-03-03 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292451/+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 1292217] Re: screen lock has triggered but keyboard is still connected to the main session
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 password. Today I had a related instance of the prompt on the left not taking the input but the prompt on the right taking it. -- 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/1292217 Title: screen lock has triggered but keyboard is still connected to the main session Status in “unity” package in Ubuntu: Confirmed Bug description: I have a laptop which has screensaved naturally due to timeout (most likely) and it is sitting there showing the lock screen but keyboard is still connected to the session, I can alt-tab to applications and via IRC i was able to send myself messages (blind) so clearly the keyboard is really operational. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 13 20:56:10 2014 EcryptfsInUse: Yes SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-01-17 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1292217/+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 1051921] Re: lens-bar-keynavigation periodically writes to /tmp/wut.png
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 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/1051921 Title: lens-bar-keynavigation periodically writes to /tmp/wut.png Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Triaged Bug description: [Impact] * Style::SquareButton writes a small png to /tmp/wut.png * If a user creates /tmp/wut.png as a symlink to some file on the system writeable by the owner of the unity process, then he/she can destroy that file. [Test Case] * log out * log in with the upgraded package * open the terminal application using control-alt-T, ensure the terminal is focused * invoke the HUD by pressing the Alt key and typing f (the HUD menu selection 'drop down' must appear to trigger the png file write) * check for presence of /tmp/wut.png [Regression Potential] * n/a [Other Info] * Marc Deslauriers from the security team said it isn't a problem on Ubuntu because we have symlink restrictions (in this case part of the Yama LSM [1]). * We believe, not everyone is necessarily running Yama LSM. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1051921/+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 1051921] Re: lens-bar-keynavigation periodically writes to /tmp/wut.png
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. * Bump dependencies to compile with both pointer barriers implementations. -- Maarten Lankhorst maarten.lankho...@ubuntu.com Thu, 05 Sep 2013 11:58:32 +0200 It's 0ubuntu3 as the one in the proposed patch, but it's actually a completely different entry, referencing a different bug. -- 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/1051921 Title: lens-bar-keynavigation periodically writes to /tmp/wut.png Status in Unity: Fix Released Status in Unity 5.0 series: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Precise: Fix Released Bug description: [Impact] * Style::SquareButton writes a small png to /tmp/wut.png * If a user creates /tmp/wut.png as a symlink to some file on the system writeable by the owner of the unity process, then he/she can destroy that file. [Test Case] * log out * log in with the upgraded package * open the terminal application using control-alt-T, ensure the terminal is focused * invoke the HUD by pressing the Alt key and typing f (the HUD menu selection 'drop down' must appear to trigger the png file write) * check for presence of /tmp/wut.png [Regression Potential] * n/a [Other Info] * Marc Deslauriers from the security team said it isn't a problem on Ubuntu because we have symlink restrictions (in this case part of the Yama LSM [1]). * We believe, not everyone is necessarily running Yama LSM. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1051921/+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 1293659] Re: Unity locks screen after unlocking
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 a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293659 Title: Unity locks screen after unlocking Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: After locking the computer I wanted to unlock the computer again. Once entering the desktop the screen gets locked without doing anything after several seconds. Unlocking for the second time gives no problem. However, when locking the screen again, the same problem occurs again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu6) .tmp.unity.support.test.0: ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 17 17:26:30 2014 DistUpgraded: 2014-03-14 17:04:08,335 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-17-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-17-generic, x86_64: installed virtualbox, 4.3.6, 3.11.0-18-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-17-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GF108GLM [Quadro 1000M] [10de:0dfa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1631] InstallationDate: Installed on 2013-06-15 (275 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) JockeyStatus: kmod:nvidia_304_updates - NVIDIA legacy binary driver - version 304.117 (Proprietary, Disabled, Not in use) kmod:nvidia_331 - NVIDIA binary driver - version 331.38 (Proprietary, Disabled, Not in use) kmod:nvidia_331_updates - nvidia_331_updates (Proprietary, Enabled, Not in use) kmod:nvidia_304 - NVIDIA legacy binary driver - version 304.117 (Proprietary, Disabled, Not in use) MachineType: Hewlett-Packard HP EliteBook 8560w ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=4e34beb2-745f-4a18-8d61-eff5a31a069d ro quiet splash pcie_aspm=force SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-14 (3 days ago) dmi.bios.date: 07/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.03 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.03:bd07/25/2011:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140310-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Mar 17 12:44:06 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1293659/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help :
