[Dx-packages] [Bug 2024182] Re: GHSL-2023-139: use-after-free in user.c
** Information type changed from Private Security to Public Security
--
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/2024182
Title:
GHSL-2023-139: use-after-free in user.c
Status in accountsservice package in Ubuntu:
In Progress
Status in accountsservice source package in Focal:
Fix Released
Status in accountsservice source package in Jammy:
Fix Released
Status in accountsservice source package in Kinetic:
Fix Released
Status in accountsservice source package in Lunar:
Fix Released
Status in accountsservice source package in Mantic:
In Progress
Bug description:
# GitHub Security Lab (GHSL) Vulnerability Report, accountsservice:
`GHSL-2023-139`
The [GitHub Security Lab](https://securitylab.github.com) team has
identified a potential security vulnerability in
[accountsservice](https://code.launchpad.net/ubuntu/+source/accountsservice).
We are committed to working with you to help resolve this issue. In
this report you will find everything you need to effectively
coordinate a resolution of this issue with the GHSL team.
If at any point you have concerns or questions about this process,
please do not hesitate to reach out to us at `security...@github.com`
(please include `GHSL-2023-139` as a reference).
If you are _NOT_ the correct point of contact for this report, please
let us know!
## Summary
An unprivileged local attacker can trigger a use-after-free
vulnerability in accountsservice by sending a D-Bus message to the
accounts-daemon process.
## Product
accountsservice
## Tested Version
[22.08.8-1ubuntu7](https://launchpad.net/ubuntu/+source/accountsservice/22.08.8-1ubuntu7)
The bug is easier to observe on Ubuntu 23.04 than on Ubuntu 22.04 LTS,
but it is present on both.
## Details
### Use-after-free when `throw_error` is called (`GHSL-2023-139`)
After receiving a D-Bus [method
call](https://dbus.freedesktop.org/doc/dbus-
specification.html#message-protocol-types), a D-Bus server is expected
to send either a `METHOD_RETURN` or a `ERROR` message back to the
client, _but not both_. This is done incorrectly in several places in
accountsservice. For example, in
[`user_change_language_authorized_cb`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010-set-
language.patch?h=import/22.08.8-1ubuntu7#n427):
```c
static void
user_change_language_authorized_cb (Daemon*daemon,
User *user,
GDBusMethodInvocation *context,
gpointer data)
{
const gchar *language = data;
if (!user_HOME_available (user)) {
/* SetLanguage was probably called from a login greeter,
and HOME not mounted and/or not decrypted.
Hence don't save anything, or else accountsservice
and ~/.pam_environment would become out of sync. */
throw_error (context, ERROR_FAILED, "not access to HOME yet
so language not saved"); <= 1
goto out;
}
out:
accounts_user_complete_set_language (ACCOUNTS_USER (user), context);
<= 2
}
```
If `user_HOME_available` returns an error, then `throw_error` is
called at 1 to send an `ERROR` message, but a regular `METHOD_RETURN`
is also sent at 2. This is incorrect D-Bus protocol, but the more
serious problem is that it causes a use-after-free because both
`throw_error` and `accounts_user_complete_set_language` decrease the
reference count on `context`. In other words, `context` is freed by
`throw_error` and a UAF occurs in
`accounts_user_complete_set_language`.
An attacker can trigger the bug above by causing `user_HOME_available`
to fail, which they can do by deleting all the files from their home
directory. But there are other incorrect uses of `throw_error` in
`user.c` which are less inconvenient to trigger. For example, this
command triggers a call to `throw_error` in `user_update_environment`
due to the invalid characters in the string.
```bash
dbus-send --system --print-reply --dest=org.freedesktop.Accounts
/org/freedesktop/Accounts/User`id -u` org.freedesktop.Accounts.User.SetLanguage
string:'**'
```
On Ubuntu 23.04, the above command causes `accounts-daemon` to crash
with a `SIGSEGV`. But on Ubuntu 22.04 LTS it doesn't cause any visible
harm. The difference is due to a recent [change in
GLib's](https://gitlab.gnome.org/GNOME/glib/-/commit/69e9ba80e2f4d2061a1a68d72bae1c32c1e4f8fa)
memory allocation: older versions of GLib used the "slice" allocator,
but newer version uses the system allocator. The system allocator
trashes the memory when it's
[Dx-packages] [Bug 1974250] Re: ~/.pam_environment gets created as owned by root
** Information type changed from Private Security to Public Security ** Also affects: accountsservice (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: accountsservice (Ubuntu Kinetic) Importance: High Status: Fix Released ** Changed in: accountsservice (Ubuntu Jammy) Status: New => Fix Released ** Changed in: accountsservice (Ubuntu Kinetic) Status: Fix Released => Confirmed -- 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/1974250 Title: ~/.pam_environment gets created as owned by root Status in accountsservice package in Ubuntu: Confirmed Status in accountsservice source package in Jammy: Fix Released Status in accountsservice source package in Kinetic: Confirmed Bug description: Something has happened lately with accountsservice, which makes it act as root instead of the current user when creating ~/.pam_environment. The very old bug #904395 comes to mind, and this smells a security issue. The function which is supposed to prevent this behavior is here: https://salsa.debian.org/freedesktop- team/accountsservice/-/blob/ubuntu/debian/patches/0010-set- language.patch#L75 Haven't investigated further yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+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 1900255] Re: accountsservice drop privileges denial of service (GHSL-2020-187, GHSL-2020-188)
** Information type changed from Private Security to Public Security
--
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/1900255
Title:
accountsservice drop privileges denial of service (GHSL-2020-187,
GHSL-2020-188)
Status in accountsservice package in Ubuntu:
Fix Released
Bug description:
# GitHub Security Lab (GHSL) Vulnerability Report: `GHSL-2020-187`,
`GHSL-2020-188`
The [GitHub Security Lab](https://securitylab.github.com) team has
identified potential security vulnerabilities in
[accountsservice](https://git.launchpad.net/ubuntu/+source/accountsservice/).
We are committed to working with you to help resolve these issues. In
this report you will find everything you need to effectively
coordinate a resolution of these issues with the GHSL team.
If at any point you have concerns or questions about this process,
please do not hesitate to reach out to us at `security...@github.com`
(please include `GHSL-2020-187` or `GHSL-2020-188` as a reference).
If you are _NOT_ the correct point of contact for this report, please
let us know!
## Summary
The accountsservice daemon drops privileges to perform certain
operations. For example while performing the
`org.freedesktop.Accounts.User.SetLanguage` D-Bus method, which can be
triggered by an unprivileged user, accounts-daemon temporarily drops
privileges to the same UID as the user, to avoid being tricked into
opening a file which the unprivileged user should not be able to
access. Unfortunately, by changing its
[RUID](https://en.wikipedia.org/wiki/User_identifier#Real_user_ID) it
has given the user permission to send it signals. This means that the
unprivileged user can send accounts-daemon a `SIGSTOP` signal, which
stops the process and causes a denial of service.
## Product
[accountsservice](https://git.launchpad.net/ubuntu/+source/accountsservice/)
## Tested Version
* accountsservice, version 0.6.55-0ubuntu12~20.04.1
* Tested on Ubuntu 20.04.1 LTS
Note: I believe these issues only exist in Ubuntu's version of
accountsservice. I couldn't find the vulnerable functions in the git
repos maintained by
[freedesktop](https://gitlab.freedesktop.org/accountsservice/accountsservice)
or [debian](https://salsa.debian.org/freedesktop-
team/accountsservice). I originally discovered the vulnerable code in
the version of the code that I had obtained by running `apt-get source
accountsservice`, but I struggled to figure out where it came from
when I started searching the official repositories. I eventually
tracked it down to this patch file: [0010-set-
language.patch](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates=e0347185d4c5554b026c13ccca691577c239afd5).
## Details
### Issue 1: accountsservice drop privileges `SIGSTOP` denial of
service (`GHSL-2020-187`)
A [source code
patch](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates=e0347185d4c5554b026c13ccca691577c239afd5) that (as far as I
know) only exists in Ubuntu's version of accountsservice, adds a
function named
[`user_drop_privileges_to_user`](https://git.launchpad.net/ubuntu/+source/accountsservice/tree/debian/patches/0010
-set-language.patch?h=ubuntu/focal-
updates=e0347185d4c5554b026c13ccca691577c239afd5#n66):
```c
static gboolean
user_drop_privileges_to_user (User *user)
{
if (setresgid (user->gid, user->gid, -1) != 0) {
g_warning ("setresgid() failed");
return FALSE;
}
if (setresuid (accounts_user_get_uid (ACCOUNTS_USER (user)),
accounts_user_get_uid (ACCOUNTS_USER (user)), -1) != 0) {
g_warning ("setresuid() failed");
return FALSE;
}
return TRUE;
}
```
This function is used to drop privileges while doing operations on
behalf of an unprivileged user. Dropping the
[EUID](https://en.wikipedia.org/wiki/User_identifier#Effective_user_ID)
is a sensible precaution, which prevents accountsservice from
accessing a file which the unprivileged user cannot access themselves.
Unfortunately, dropping the
[RUID](https://en.wikipedia.org/wiki/User_identifier#Real_user_ID) has
the opposite effect of making security worse, because it enables the
unprivileged user to send signals to accountsservice. For example,
they can send a `SIGSTOP` which stops the accountsservice daemon and
causes a denial of service.
The vulnerability can be triggered via multiple different D-Bus
methods. Many of them involve precise timing to send the `SIGSTOP`
signal at just the right moment. But there is a much simpler and more
reliable way to reproduce the
[Dx-packages] [Bug 1886770] Re: Computer is not locked after suspend
** Package changed: indicator-session (Ubuntu) => mate-screensaver (Ubuntu) ** Changed in: mate-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1886770 Title: Computer is not locked after suspend Status in mate-screensaver package in Ubuntu: Confirmed Bug description: Prerequisites: 1. Set up a password. Steps to reproduce: 1. Click the gear wheel icon. 2. In the indicator menu, click "Suspend" item. Expected behavior: 1. Computer goes to sleep mode. 2. After wake up, it is required to type the password to log in. Actual behavior: 1. Computer goes to sleep mode. 2. After wake up, screen is not locked, it is possible to use session without the password. Notes: 1. If a user suspend the system via shut down dialog box, the password is prompted. 2. The same vulnerability is present for hibernation mode if it is enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: indicator-session 17.3.20+19.10.20190921-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-390/nvidia-kernel-source-390_390.132-0ubuntu2_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: MATE Date: Wed Jul 8 05:46:24 2020 LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash LANG=C.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-screensaver/+bug/1886770/+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 1771603] [NEW] Does not honour UID_MAX
Public bug reported: accountsservice doesn't honour the UID_MAX settings in /etc/login.defs, resulting in system users being displayed at the login screen and in the users control panel. See attached screenshot to see that the "libvirt-qemu" user is being displayed when it shouldn't. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 16 11:03:09 2018 InstallationDate: Installed on 2017-12-12 (155 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: accountsservice UpgradeStatus: Upgraded to bionic on 2018-05-09 (7 days ago) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "screenshot of issue" https://bugs.launchpad.net/bugs/1771603/+attachment/5140372/+files/Screenshot%20from%202018-05-16%2011-05-30.png -- 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/1771603 Title: Does not honour UID_MAX Status in accountsservice package in Ubuntu: New Bug description: accountsservice doesn't honour the UID_MAX settings in /etc/login.defs, resulting in system users being displayed at the login screen and in the users control panel. See attached screenshot to see that the "libvirt-qemu" user is being displayed when it shouldn't. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 16 11:03:09 2018 InstallationDate: Installed on 2017-12-12 (155 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: accountsservice UpgradeStatus: Upgraded to bionic on 2018-05-09 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1771603/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
I tested the 2018-04-21 daily image, and the permissions on ~/.config and ~/.local are OK now. -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Fix Released Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Released Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Hi daniel, I wasn't able to reproduce with 16.04. Did you install the regular Ubuntu desktop, or a specific flavour? -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Committed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Bionic) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: xorg-server (Ubuntu Bionic) Importance: Undecided => High ** Changed in: xorg-server (Ubuntu Bionic) Status: New => In Progress ** Changed in: xorg-server (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Committed Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Fix Committed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Here's another: https://cgit.freedesktop.org/xorg/xserver/tree/hw/xfree86/common/xf86Helper.c#n1136 -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Is there anything left to land here? I just installed the 2018-04-13 desktop iso, and while ~/.config has correct permissions, ~/.local does not. -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Fix Released Status in d-conf package in Ubuntu: Fix Released Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in session-migration package in Ubuntu: Fix Released Status in d-conf source package in Bionic: Fix Released Status in dconf source package in Bionic: Triaged Status in gnome-session source package in Bionic: Fix Released Status in session-migration source package in Bionic: Fix Released Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Any further progress on these issues? -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Confirmed Status in d-conf package in Ubuntu: Triaged Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Triaged Status in session-migration package in Ubuntu: Fix Released Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Related bug in ubuntu-mate-welcome: bug 1745929 -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in dconf: Confirmed Status in gnome-session: Confirmed Status in d-conf package in Ubuntu: Triaged Status in dconf package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Triaged Status in session-migration package in Ubuntu: Fix Released Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
and another: https://git.gnome.org/browse/gnome-session/tree/gnome-session/gsm-util.c?h=gnome-3-26#n99 ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in d-conf package in Ubuntu: New Status in gnome-session package in Ubuntu: New Status in session-migration package in Ubuntu: Confirmed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1735929/+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 1735929] Re: security problems with incorrect permissions for ubuntu 17.10
Here's another: https://git.gnome.org/browse/dconf/tree/service/dconf-gvdb-utils.c#n177 https://git.gnome.org/browse/dconf/tree/service/dconf-keyfile-writer.c#n210 ** Also affects: d-conf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to d-conf in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1735929 Title: security problems with incorrect permissions for ubuntu 17.10 Status in d-conf package in Ubuntu: New Status in session-migration package in Ubuntu: Confirmed Bug description: The release of Ubuntu you are using (lsb_release -rd): Description: Ubuntu 17.10 Release: 17.10 This is a fresh installation of Ubuntu 17.10 from the mini.iso. I select only default options + [Ubuntu Desktop] installation. What you expected to happen: My home folder contains the following folders with correct and safe permissions after the first login: drwx-- 11 user user 4096 Dec 2 17:40 .config drwx-- 3 user user 4096 Dec 2 17:39 .local What happened instead: I received these folders after the first login: drwxr-xr-x 11 user user 4096 Dec 2 17:40 .config drwxr-xr-x 3 user user 4096 Dec 2 17:39 .local It is not safe. Any user can access to my .config folders and read for example my mail databases I'm trying to create a new user...: sudo useradd -m user2 sudo passwd user2 ... and login then. It has the same problem: drwxr-xr-x 10 user2 user2 4096 Dec 2 19:44 .config drwxr-xr-x 3 user2 user2 4096 Dec 2 19:44 .local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1735929/+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 1721804] [NEW] About this computer doesn't open the about tab
Public bug reported: Selecting "About this computer" from the power indicator doesn't actually show the about tab. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: indicator-session 17.3.20+17.10.20170717.1-0ubuntu3 ProcVersionSignature: User Name 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:37:14 2017 InstallationDate: Installed on 2017-07-18 (80 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1721804 Title: About this computer doesn't open the about tab Status in indicator-session package in Ubuntu: New Bug description: Selecting "About this computer" from the power indicator doesn't actually show the about tab. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: indicator-session 17.3.20+17.10.20170717.1-0ubuntu3 ProcVersionSignature: User Name 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 11:37:14 2017 InstallationDate: Installed on 2017-07-18 (80 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170716) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1721804/+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 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
I can't think of any reason why having a session would be important in this case, so I think changing allow_any to yes should be fine. -- 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/1512002 Title: Annoying dialog "Authentication is required to change your own user data" Status in accountsservice: Confirmed Status in accountsservice package in Ubuntu: Triaged Status in indicator-messages package in Ubuntu: Confirmed Status in policykit-1-gnome package in Ubuntu: Confirmed Bug description: Every few days a dialog pops up saying "Authentication is required to change your own user data" with an entry field for a password. If I type my user's password the dialog will reappear with an empty entry field. If I click on the cross to close the window many times it will be gone, but reappear a few days later. I don't know what this window is for and it makes no difference whether I close it or leave it. I don't use the gnome keyring. This started with Ubuntu 15.04 or maybe with an earlier release, and is still there in Ubuntu 15.10, also on machines I did a fresh install. To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1512002/+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 1565917] Re: package unity-lens-music 6.9.0+14.04.20151120.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-lens-music in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1565917 Title: package unity-lens-music 6.9.0+14.04.20151120.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in unity-lens-music package in Ubuntu: New Bug description: ok ProblemType: Package DistroRelease: Ubuntu 14.04 Package: unity-lens-music 6.9.0+14.04.20151120.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Mon Apr 4 20:49:02 2016 DuplicateSignature: package:unity-lens-music:6.9.0+14.04.20151120.2-0ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-09-26 (556 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: unity-lens-music Title: package unity-lens-music 6.9.0+14.04.20151120.2-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-lens-music/+bug/1565917/+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 1175691] Re: Rate limit in libunity-webapps can be abused to make Firefox collect C callbacks that are still in use
We no longer ship this package: http://www.ubuntu.com/usn/usn-2743-3/ ** Changed in: unity-firefox-extension (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libunity-webapps (Ubuntu) Status: Confirmed => Invalid ** Changed in: unity-firefox-extension Status: New => Confirmed ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1175691 Title: Rate limit in libunity-webapps can be abused to make Firefox collect C callbacks that are still in use Status in WebApps: unity-firefox-extension: Confirmed Status in libunity-webapps package in Ubuntu: Invalid Status in unity-firefox-extension package in Ubuntu: Fix Released Bug description: PoC is attached. What happens when you click the button (and accept integration) is that it adds an action to the launcher and then repeatedly updates it with a new callback. However, at some point it will hit the rate limit inside libunity-webapps (in unity_webapps_launcher_add_action), at which point it no longer updates the actual C callback. Because this failure is not propagated out of libunity-webapps, unity-firefox- extension stores a reference to the new (and unused) callback thus dropping its reference to the old (and still in use) callback, which will now be collected by the garbage collector. Give it a few seconds for the garbage collector to free the old callback and then click on the action in the launcher icon. Firefox will crash with a trace that looks a bit like this: #0 js::ctypes::CClosure::ClosureStub (cif=0x617320, result=0x7fffb5d0, args=0x7fffb440, userData=0x6c8) at /home/chr1s/src/firefox/mozilla-central/js/src/ctypes/CTypes.cpp:6116 #1 0x74020dab in ffi_closure_unix64_inner (closure=0x7fffe040b940, rvalue=0x7fffb5d0, reg_args=0x7fffb520, argp=0x7fffb5f0 "") at /home/chr1s/src/firefox/mozilla-central/js/src/ctypes/libffi/src/x86/ffi64.c:621 #2 0x740212c4 in ffi_closure_unix64 () at /home/chr1s/src/firefox/mozilla-central/js/src/ctypes/libffi/src/x86/unix64.S:228 #3 0x7402115c in ffi_call_unix64 () at /home/chr1s/src/firefox/mozilla-central/js/src/ctypes/libffi/src/x86/unix64.S:75 #4 0x7402084e in ffi_call (cif=0x7fffb7f0, fn=0x7fffc84eccf0 <_launcher_context_action_invoked>, rvalue=0x7fffb750, avalue=0x7fffb6f0) at /home/chr1s/src/firefox/mozilla-central/js/src/ctypes/libffi/src/x86/ffi64.c:485 #5 0x70fc6f7b in g_cclosure_marshal_generic (closure=0x7fff54009a00, return_gvalue=0x0, n_param_values=, param_values=, invocation_hint=, marshal_data=0x7fffc84eccf0 <_launcher_context_action_invoked>) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1454 #6 0x70fc6620 in g_closure_invoke (closure=0x7fff54009a00, return_value=0x0, n_param_values=3, param_values=0x32fc920, invocation_hint=0x7fffb9d0) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:777 #7 0x70fd7f00 in signal_emit_unlocked_R (node=node@entry=0x7fff5400d050, detail=detail@entry=0, instance=instance@entry=0x7fff5400f8e0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x32fc920) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3584 #8 0x70fdee3b in g_signal_emitv (instance_and_params=instance_and_params@entry=0x32fc920, signal_id=, detail=detail@entry=0, return_value=return_value@entry=0x0) at /build/buildd/glib2.0-2.36.0/./gobject/gsignal.c:3059 #9 0x7fffc84e61c3 in unity_webapps_gen_launcher_proxy_g_signal (proxy=, sender_name=, signal_name=, parameters=) at ../unity-webapps-gen-launcher.c:2079 #10 0x7402115c in ffi_call_unix64 () at /home/chr1s/src/firefox/mozilla-central/js/src/ctypes/libffi/src/x86/unix64.S:75 #11 0x7402084e in ffi_call (cif=0x7fffbdb0, fn=0x7fffc84e60b0 , rvalue=0x7fffbd10, avalue=0x7fffbc90) at /home/chr1s/src/firefox/mozilla-central/js/src/ctypes/libffi/src/x86/ffi64.c:485 #12 0x70fc6f7b in g_cclosure_marshal_generic (closure=0x6bf720, return_gvalue=0x0, n_param_values=, param_values=, invocation_hint=, marshal_data=0x7fffc84e60b0 ) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:1454 #13 0x70fc6620 in g_closure_invoke (closure=0x6bf720, return_value=0x0, n_param_values=4, param_values=0x7fffbff0, invocation_hint=0x7fffbf90) at /build/buildd/glib2.0-2.36.0/./gobject/gclosure.c:777 #14 0x70fd7af8 in signal_emit_unlocked_R (node=node@entry=0x6bf780, detail=detail@entry=0, instance=instance@entry=0x7fff5400f8e0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffbff0) at
[Dx-packages] [Bug 1509826] Re: Window bug Source Applications Linux Mint 17.2
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1509826 Title: Window bug Source Applications Linux Mint 17.2 Status in overlay-scrollbar package in Ubuntu: New Bug description: Window bug Source Applications Postby visterine on Sun Oct 25, 2015 11:16 am Window Application Source does not fit the monitor resolution I'm not sure just me but the Application Sources window insists on not fit the screen. The same does not accept being resized. Someone has been there who knows how to solve? Only occurs in the application source window. Other windows and screens with standard sizing within the monitor settings. In the forum Limun Mint Brazil was told it is an old bug. Nothing to panic too much, more a matter of aesthetics. Using here the Mint XFCE 17.2. Users of other desktop environments have reported the same problem. It would be the text size or the size of the check boxes? Sorry I do not speak the English language. Text with free translation of Google translator. User avatar visterine Level 1 Level 1 Posts: 2 Joined: Sun Jul 20, 2014 9:09 pm Top To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1509826/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity-settings-daemon (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Trusty) Status: New => Fix Released ** Changed in: unity-settings-daemon (Ubuntu Trusty) Status: New => Confirmed ** Changed in: unity-settings-daemon (Ubuntu Trusty) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) -- 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in Unity: Won't Fix Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in unity source package in Trusty: Fix Released Status in unity-settings-daemon source package in Trusty: Confirmed Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor "type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver'" 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438870/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
FYI, I have a merge request pending review that makes the laptop battery have priority over the mouse battery here: https://code.launchpad.net/~mdeslaur/indicator-power/fix- priorities/+merge/260903 This will only display the mouse battery if it's below 10% so that the user will still get a notification that a battery change is required. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in indicator-power package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1442844] Re: loging o unlocking screen with no password
Thanks for your comments. This does not appear to be a bug report and we are closing it. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. Please visit https://answers.launchpad.net/ubuntu/+addquestion ** Information type changed from Private Security to Public ** Changed in: unity (Ubuntu) Status: New = Invalid -- 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/1442844 Title: loging o unlocking screen with no password Status in unity package in Ubuntu: Invalid Bug description: Hi. I can login my session without entering a password.I assigned a password to my account at installation time,and login with just typing enter. And when i lock the screen,can unlock by just clicking enter and typing anything. This problem is also present in the terminal and ttys. I installed ubuntu 14.04 x86 lts with all updates. but i haven't installed any update since installation finish. Can anybody help me with this? Thanks to all ubuntu developers for working on this operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1442844/+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 1447821] Re: Lockscreen does not ask for ldap password
Does this happen at the login screen too, or just at the lock screen? Could you please attach the contents of /etc/pam.d ? ** Information type changed from Private Security to Public Security ** Package changed: gnome-screensaver (Ubuntu) = unity (Ubuntu) ** Changed in: unity (Ubuntu) Status: New = Incomplete -- 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/1447821 Title: Lockscreen does not ask for ldap password Status in unity package in Ubuntu: Incomplete Bug description: I manage desktops where the users log into an today updated ubuntu 14.04.1 amd64 desktop using ldap users. When the desktop goes to lockscreen, in order to unlock I may [see IMG_20150423_182816.jpg attached]: 1. Use my right ldap password: Unlock successfully; 2. Use a wrong ldap password: It doesn't unlock, showing an error message; 3. Don't use any password, just press Enter: Unlock successfully! This is a serious security failure. One unauthorized person walking around could access a machine and use it. There's no references in logs like syslog, auth.log, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1447821/+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 1447821] Re: Lockscreen does not ask for ldap password
Switching package to unity as the screenshot shows unity, not gnome- screensaver. -- 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/1447821 Title: Lockscreen does not ask for ldap password Status in unity package in Ubuntu: Incomplete Bug description: I manage desktops where the users log into an today updated ubuntu 14.04.1 amd64 desktop using ldap users. When the desktop goes to lockscreen, in order to unlock I may [see IMG_20150423_182816.jpg attached]: 1. Use my right ldap password: Unlock successfully; 2. Use a wrong ldap password: It doesn't unlock, showing an error message; 3. Don't use any password, just press Enter: Unlock successfully! This is a serious security failure. One unauthorized person walking around could access a machine and use it. There's no references in logs like syslog, auth.log, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1447821/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
This is CVE-2015-1319 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2015-1319 -- 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in Unity: New Status in unity package in Ubuntu: New Status in unity source package in Trusty: New Status in unity source package in Utopic: New Status in unity source package in Vivid: New Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver' 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1438870/+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 1438870] [NEW] Lock screen doesn't emit ActiveChanged signal
*** This bug is a security vulnerability *** Public security bug reported: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver' 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: unity (Ubuntu Utopic) Importance: Undecided Status: New ** Affects: unity (Ubuntu Vivid) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages vivid -- 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in unity package in Ubuntu: New Status in unity source package in Trusty: New Status in unity source package in Utopic: New Status in unity source package in Vivid: New Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver' 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1438870/+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 1438870] Re: Lock screen doesn't emit ActiveChanged signal
** Attachment removed: JournalErrors.txt https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1438870/+attachment/4362321/+files/JournalErrors.txt ** Also affects: unity (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Utopic) Importance: Undecided Status: New -- 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/1438870 Title: Lock screen doesn't emit ActiveChanged signal Status in unity package in Ubuntu: New Status in unity source package in Trusty: New Status in unity source package in Utopic: New Status in unity source package in Vivid: New Bug description: tl;dr; Unity doesn't emit the ActiveChanged signal when the screen is locked/unlocked Long version: unity-settings-daemon's automount plugin has code to detect whether the screen is locked or not before automatically mounting a volume. This prevents someone from inserting a USB thumb drive when the screen is locked and exploiting a possible nautilus thumbnailer vulnerability. (See bug #714958 for original implementation details.) In Ubuntu 14.04, this code no longer works. Inserting a USB thumb drive while the screen is locked results in a Nautilus window opening underneath the lock screen, and the contents of the USB thumb drive being read. Since the screen lock got switched to Unity in Ubuntu 14.04, Unity no longer emits the org.gnome.ScreenSaver ActiveChanged signal when the screen gets locked or unlocked. To test: 1- in terminal, type: dbus-monitor type='signal',sender='org.gnome.ScreenSaver',interface='org.gnome.ScreenSaver' 2- Lock the screen 3- Unlock the screen 4- Notice that no signal was received ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150330-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 31 15:15:48 2015 InstallationDate: Installed on 2013-11-26 (489 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-07 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1438870/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
JW, It will, yes. If your laptop battery is charging, or is discharging, it will now be shown in preference to your mouse. If your laptop battery is fully charged, your mouse will be shown. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in indicator-power package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
Devices that report a wrong time remaining need to be blacklisted, just like any other misbehaving hardware device. Even if this means most devices will need to be blacklisted? Wouldn't it require an extreme amount of effort to start blacklisting every mouse that doesn't work with this feature? I have never actually seen a mouse that gives an estimated time remaining, so I don't think it would be much of an issue. Most mice I've seen don't give a time remaining, they only give a percentage of battery left, which works fine with the latest commit. Do you own a mouse that gives a time remaining, and that the time remaining is grossly inaccurate? If so, could you please attach the output of upower --dump? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in indicator-power package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
Devices that report a wrong time remaining need to be blacklisted, just like any other misbehaving hardware device. The fact that such devices exist is not a valid reason to get rid of a sane and elegant notification system. Do you own a mouse with an incorrect time remaining estimate? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in indicator-power package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
Here is a patch that implements the preferred sorting order as described by mpt, and described in comment #12. ** Patch added: lp1315434.patch https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+attachment/4334474/+files/lp1315434.patch -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in indicator-power package in Ubuntu: In Progress Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1424308] Re: xkillxkillcompiz crashed with SIGSEGV in xcb_take_socket()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1424308 Title: xkillxkillcompiz crashed with SIGSEGV in xcb_take_socket() Status in unity package in Ubuntu: New Bug description: unity is gone trying to get it back ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sat Feb 21 21:35:21 2015 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2015-02-21 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) ProcCmdline: compiz --replace ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fd8f0d23963 xcb_take_socket+19: mov (%rdi),%edi PC (0x7fd8f0d23963) ok source (%rdi) (0x0001) not located in a known VMA region (needed readable region)! destination %edi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: xcb_take_socket () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XFlush () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XGetRequest () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetSelectionOwner () from /usr/lib/x86_64-linux-gnu/libX11.so.6 Title: compiz crashed with SIGSEGV in xcb_take_socket() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1424308/+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 1425948] Re: The screen freezes and stop all process.
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: indicator-sound (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1425948 Title: The screen freezes and stop all process. Status in indicator-sound package in Ubuntu: Invalid Bug description: The screen freezes and stop all process. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1 Uname: Linux 4.0.0-04rc1-lowlatency x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Thu Feb 26 11:22:22 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service Signal: 5 SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1425948/+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 1424312] Re: compiz crashed with SIGSEGV in unity::XdndStartStopNotifierImp::DndTimeoutSetup()
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1424312 Title: compiz crashed with SIGSEGV in unity::XdndStartStopNotifierImp::DndTimeoutSetup() Status in unity package in Ubuntu: New Bug description: problems with unity ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sat Feb 21 22:08:10 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2015-02-21 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) ProcCmdline: compiz Signal: 11 SourcePackage: unity StacktraceTop: unity::XdndStartStopNotifierImp::DndTimeoutSetup() () from /usr/lib/compiz/libunityshell.so sigc::internal::signal_emit1void, unsigned long, sigc::nil::emit(sigc::internal::signal_impl*, unsigned long const) () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::Notify(CompWindow*, CompWindowNotify) () from /usr/lib/compiz/libunityshell.so unity::UnityWindow::windowNotify(CompWindowNotify) () from /usr/lib/compiz/libunityshell.so CompWindow::windowNotify(CompWindowNotify) () from /usr/lib/x86_64-linux-gnu/libcompiz_core.so.ABI-20140123 Title: compiz crashed with SIGSEGV in unity::XdndStartStopNotifierImp::DndTimeoutSetup() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1424312/+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 1425676] Re: I don't know.
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: indicator-sound (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1425676 Title: I don't know. Status in indicator-sound package in Ubuntu: Invalid Bug description: I don't know. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150219.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Thu Feb 26 03:09:57 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-02-25 (0 days ago) InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service Signal: 5 SourcePackage: indicator-sound UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1425676/+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 1426518] Re: Windowed fullscreen apps left sided corruption
Oh! I see, sorry, I got confused as I thought the video was showing the whole desktop. That really is a weird bug, and I can't reproduce it on my machines with the intel driver. -- 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/1426518 Title: Windowed fullscreen apps left sided corruption Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: This is a bug that I presumed was known but after talking about it on reddit I went looking and couldn't find a report about it. To reproduce the bug: 1. Open either Steam, a game or google chrome 2. Open into fullscreen, if the corruption isn't there toggle fullscreen on and off a few times You will see a bit of dead space on the left side beside the Unity sidebar, the corruption is just graphical so all the buttons still are in their old positions they just look like they are offset. As well as that all the content of the page or what ever is still in the same position so its very easy to miss click things obviously. I made a video of the problem: https://www.youtube.com/watch?v=-wSb93MBCgI ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Fri Feb 27 18:41:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 14.501, 3.13.0-45-generic, x86_64: installed fglrx-core, 14.501, 3.13.0-46-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:048d] InstallationDate: Installed on 2015-02-14 (13 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd02/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Feb 27 16:20:50 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1426518/+subscriptions -- Mailing list:
[Dx-packages] [Bug 1426518] Re: Windowed fullscreen apps left sided corruption
How are you making Chrome go full-screen like that? If I maximize it, I still have the global menu at the top and the unity launcher on the left. If I hit f11, I no longer have the tabs or the URL bar. -- 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/1426518 Title: Windowed fullscreen apps left sided corruption Status in unity package in Ubuntu: Incomplete Bug description: This is a bug that I presumed was known but after talking about it on reddit I went looking and couldn't find a report about it. To reproduce the bug: 1. Open either Steam, a game or google chrome 2. Open into fullscreen, if the corruption isn't there toggle fullscreen on and off a few times You will see a bit of dead space on the left side beside the Unity sidebar, the corruption is just graphical so all the buttons still are in their old positions they just look like they are offset. As well as that all the content of the page or what ever is still in the same position so its very easy to miss click things obviously. I made a video of the problem: https://www.youtube.com/watch?v=-wSb93MBCgI ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Fri Feb 27 18:41:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 14.501, 3.13.0-45-generic, x86_64: installed fglrx-core, 14.501, 3.13.0-46-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:048d] InstallationDate: Installed on 2015-02-14 (13 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd02/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Feb 27 16:20:50 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1426518/+subscriptions -- Mailing
[Dx-packages] [Bug 1426518] Re: Windowed fullscreen apps left sided corruption
Possibly related to bug 1390234 -- 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/1426518 Title: Windowed fullscreen apps left sided corruption Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: This is a bug that I presumed was known but after talking about it on reddit I went looking and couldn't find a report about it. To reproduce the bug: 1. Open either Steam, a game or google chrome 2. Open into fullscreen, if the corruption isn't there toggle fullscreen on and off a few times You will see a bit of dead space on the left side beside the Unity sidebar, the corruption is just graphical so all the buttons still are in their old positions they just look like they are offset. As well as that all the content of the page or what ever is still in the same position so its very easy to miss click things obviously. I made a video of the problem: https://www.youtube.com/watch?v=-wSb93MBCgI ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.4+14.04.20141217-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-46.75-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.7 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: Fri Feb 27 18:41:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx-core, 14.501, 3.13.0-45-generic, x86_64: installed fglrx-core, 14.501, 3.13.0-46-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] [1002:6811] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:048d] InstallationDate: Installed on 2015-02-14 (13 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0805 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0805:bd02/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Feb 27 16:20:50 2015 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1426518/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help :
[Dx-packages] [Bug 1413790] Re: It's possible to bypasss lockscreen if user is in nopasswdlogin group.
In fact, the User Accounts applet in the Settings allows creating a user with no password by putting it in the nopasswdlogin group, but as soon as the screen lock comes up, the user is unable to unlock the screen. So the screen lock definitely needs to honour the nopasswdlogin group, and this is a bug with no real security implications. ** Information type changed from Private Security to Public -- 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/1413790 Title: It's possible to bypasss lockscreen if user is in nopasswdlogin group. Status in Light Display Manager: New Status in Unity: In Progress Status in lightdm package in Ubuntu: New Status in unity package in Ubuntu: In Progress Bug description: Lightdm should not emit logind unlock signal when the user is not prompted for a password. This can lead to a security issue: # Log-in (unity session). # Add the current user to nopasswdlogin group. # Lock the sessions. # Session indicator-Switch account... # Login in again. Expected behavior: The lockscreen is still active. Current behavior: The session in unlocked. We could workaround the issue directly in unity, but IMHO would be cleaner to avoid that lightdm is emitting the logind signal. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1413790/+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 1396151] Re: password not checked on screen unlock
** Package changed: light-locker (Ubuntu) = unity (Ubuntu) -- 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/1396151 Title: password not checked on screen unlock Status in unity package in Ubuntu: New Bug description: On a system upgraded from 12.04 to 14.04: When don't ask for password on login is checked for a user, previous screen locking would still require a password - the preference only applied to logins. Now light locker(?) is showing a password dialog box, but it will accept any (or no) password for screen unlock, just as for login. This might be a good change, but it was surely unexpected, and I found the previous functionality (being able to NOT require the PW for login but still require it for screen unlock) very useful, even if it might seem odd on the surface. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Nov 25 08:29:52 2014 InstallationDate: Installed on 2012-10-08 (777 days ago) InstallationMedia: Xubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.1) SourcePackage: gnome-screensaver Symptom: security Title: Screen locking issue UpgradeStatus: Upgraded to trusty on 2014-09-03 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1396151/+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 1396205] Re: Lock screen can be bypassed using a large monitor
** Information type changed from Private Security to Public Security ** Package changed: unity (Ubuntu) = gnome-screensaver (Ubuntu) ** Changed in: gnome-screensaver (Ubuntu) Status: New = Confirmed -- 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/1396205 Title: Lock screen can be bypassed using a large monitor Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 I've managed to reproduce an error that lets me interact with applications while the lock screen is active. Here are the steps to reproduce, as specifically as I've been able to tell: 1. I have my Dell XPS laptop attached to a Benq desktop monitor via the laptop's mini DVI port. The laptop is closed, the screen is unlocked, and the desktop monitor shows my Ubuntu desktop and apps. 2. Unplug the display cable from the laptop and open the laptop up. Wait a couple of seconds for the monitor to report no input device. The screen should still be unlocked and the laptop screen should show the OS desktop. 3. Plug the display cable back in, and immediately close the laptop. 4. Observe that moving the mouse (Evoluent vertical mouse attached to an Apple keyboard, plugged into the laptop via USB) does not bring up the login dialog. The desktop monitor remains blank. 5. Open the laptop lid slightly, and as soon as the screen blacks out, close it again. The desktop monitor should remain blank. 6. Move the mouse. This time, the lock screen login dialog appears on the desktop monitor, but it does not cover the whole desktop. I am able to interact with a web browser running behind the lock screen, read pages, click links, etc. It seems like the lock screen is drawn for my laptop's small screen, and then not enlarged for the bigger monitor, leaving apps visible and accepting mouse input. See the attached image for an example. I can repro this bug every time by following the above instructions. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-40.69~precise1-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,move,snap,place,session,gnomecompat,mousepoll,regex,resize,imgpng,grid,unitymtgrabhandles,animation,workarounds,wall,fade,scale,expo,ezoom,unityshell] Date: Tue Nov 25 14:53:21 2014 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1396205/+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 1180635] Re: falla el ajuste de sonido
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-applet in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1180635 Title: falla el ajuste de sonido Status in Indicator Applet: New Status in “indicator-applet” package in Ubuntu: New Bug description: No se pude regular, fue despues de una actualización del Sistema, gracias. Pero se escucha el sonido. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1180635/+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 1375271] Re: desktop or other past screen contents visible before lockscreen on resume
What desktop environment are you using? ** Information type changed from Private Security to Public -- 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/1375271 Title: desktop or other past screen contents visible before lockscreen on resume Status in Compiz: New Status in GNOME Screensaver: New Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: This appears to be a regression in 14.10 sometime in September 2014. The behavior appears similar to this bug from 2011: https://bugs.launchpad.net/unity-2d/+bug/830348 On resume from suspend, screen contents are displayed for a brief time (perhaps 0.5 to 1 sec) before the lock dialog appears. These screen contents are not always the desktop or open application beneath the lock screen. On at least one occasion, the screen showed content from a full-screen video that had been playing in Firefox some time before the computer had been suspended: neither the video nor its underlying tab were open anymore, so the image(s) was likely part of a buffer somewhere. (Needless to say, if the wrong full-screen video had been watched, depending on the setting, this could be a quite serious issue for some users). I have not exhaustively tested conditions in which this appears. However, just now, the bug did not appear when keeping the lid open, suspending, and then resuming with the power button. But when suspending from menu, closing the lid, then opening the lid and moving the mouse, the screen displayed contents before showing the lock dialog. The image displayed was of the desktop (with this bug reporting window) and showed the suspend item in the power menu being highlighted/clicked. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 29 08:38:57 2014 InstallationDate: Installed on 2014-08-10 (50 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-08-10 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1375271/+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 1358251] Re: unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children()
** Information type changed from Private Security to Public -- 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/1358251 Title: unity-panel-service crashed with SIGSEGV in panel_indicator_entry_accessible_get_n_children() Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: disturbs me alot ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-services 5.20.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus,staticswitcher] CrashCounter: 1 CrashDB: unity Date: Mon Aug 18 14:04:37 2014 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) MarkForUpload: True ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x804d0b8: cmp%eax,(%edx) PC (0x0804d0b8) ok source %eax ok destination (%edx) (0x0001ae7e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () atk_object_get_n_accessible_children () from /usr/lib/i386-linux-gnu/libatk-1.0.so.0 ?? () from /usr/lib/i386-linux-gnu/gtk-3.0/modules/libatk-bridge.so ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: unity-panel-service crashed with SIGSEGV in atk_object_get_n_accessible_children() UpgradeStatus: Upgraded to precise on 2014-03-19 (151 days ago) UserGroups: sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1358251/+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 1185665] Re: unity-panel-service crashed with signal 7
** Information type changed from Private Security to Public -- 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/1185665 Title: unity-panel-service crashed with signal 7 Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: My machine hanged completely, and i have to restart it again to work. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: indicator-power 2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 CrashCounter: 1 CrashDB: unity Date: Thu May 30 09:17:07 2013 ExecutablePath: /usr/lib/unity/unity-panel-service InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN Signal: 7 SourcePackage: indicator-power StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/i386-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: unity-panel-service crashed with signal 7 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1185665/+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 1334618] Re: Fullscreen apps are displayed on the lock screen for some time after suspend
** Information type changed from Private Security to Public Security -- 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/1334618 Title: Fullscreen apps are displayed on the lock screen for some time after suspend Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: The bug appears on low perfomance hardware (netbooks) Steps to reproduce: 1)Open in Evinve some file on netbook. 2)Go to fullscreen mode (F11) 3)Close the lid of your netbook (or if you are trsting on the desktop press Alt+F10 and navigate by arrow to Suspend button 4)Press suspend and wake up the device 5) So the bug: for 2 or three seconds after waking up The pdf will be displayed on your netbook instead of Unity-greeter. Than unity greeter will ask you your password It is unsecure, because somebody my see your content, while you are just opened the lid To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1334618/+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 1243506] Re: unity no lens, search no dash
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- 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/1243506 Title: unity no lens, search no dash Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: No search in Dash, No lens in the Dash! Вообще в Даше всё пусто, ни чего ни найти в нём! To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243506/+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 1192789] Re: search disrupting unity lens research
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System - About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- 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/1192789 Title: search disrupting unity lens research Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: unity 8 search disrupting unity lens research, several surveys do not work properly, levels of errors are still visible, latches to FIND things simple conflict of languages. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1192789/+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: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators)
This bug is now fixed in both trusty and utopic. Please install your updates. If you see an issue after making sure all updates are applied and restarting your computer, please file a new 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/1349128 Title: Ubuntu 14.04 lock screen doesn't accept keyboard input and sends it back to the underlying window (until using indicators) Status in Unity: Fix Committed Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released 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 1351616] Re: Ubuntu 14.04: multi-touch screen can cause desktop to unlock
** Package changed: unity (Ubuntu) = xorg (Ubuntu) -- 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/1351616 Title: Ubuntu 14.04: multi-touch screen can cause desktop to unlock Status in “xorg” package in Ubuntu: Confirmed Bug description: Steps to reproduce on a laptop with a multitouch screen (in my case, a Lenovo X1 Carbon Gen 2): 1. Lock the desktop. 2. Start lightly tapping away on the laptop screen and triggering various bogus multitouch events. 3. The Xorg issue reported in https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1121379 will eventually trigger and gnome-session will crash 4. You are able to view the unlocked desktop, and have limited keyboard/mouse access to the desktop. The issue seems to be similar to https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1308572 , which is marked fixed, but it looks like in the event of a crash the screen can still become unlocked. Relevant logs: == /var/log/auth.log == Aug 2 09:14:10 SOMEHOST compiz: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or director y Aug 2 09:14:10 SOMEHOST compiz: PAM adding faulty module: pam_kwallet.so Aug 2 09:14:10 SOMEHOST compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user SOMEUSER == /var/log/syslog == Aug 2 09:14:24 SOMEHOST gnome-session[2065]: WARNING: App 'compiz.desktop' respawning too quickly Aug 2 09:14:24 SOMEHOST gnome-session[2065]: WARNING: App 'compiz.desktop' exited with code 1 Aug 2 09:14:24 SOMEHOST gnome-session[2065]: WARNING: App 'compiz.desktop' respawning too quickly == /var/log/Xorg.0.log == [ 445.600] (EE) Backtrace: [ 445.600] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f6921bd8c78] [ 445.600] (EE) 1: /usr/bin/X (0x7f6921a3+0x7d3e7) [0x7f6921aad3e7] [ 445.600] (EE) 2: /usr/bin/X (0x7f6921a3+0x138845) [0x7f6921b68845] [ 445.600] (EE) 3: /usr/bin/X (0x7f6921a3+0x138357) [0x7f6921b68357] [ 445.600] (EE) 4: /usr/bin/X (0x7f6921a3+0x13afa2) [0x7f6921b6afa2] [ 445.601] (EE) 5: /usr/bin/X (0x7f6921a3+0x15c1d4) [0x7f6921b8c1d4] [ 445.601] (EE) 6: /usr/bin/X (mieqProcessDeviceEvent+0x1cd) [0x7f6921bbb0cd] [ 445.601] (EE) 7: /usr/bin/X (mieqProcessInputEvents+0xf7) [0x7f6921bbb1e7] [ 445.601] (EE) 8: /usr/bin/X (ProcessInputEvents+0x9) [0x7f6921ac2fe9] [ 445.601] (EE) 9: /usr/bin/X (0x7f6921a3+0x55802) [0x7f6921a85802] [ 445.601] (EE) 10: /usr/bin/X (0x7f6921a3+0x5994a) [0x7f6921a8994a] [ 445.601] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f691f56cec5] [ 445.601] (EE) 12: /usr/bin/X (0x7f6921a3+0x44e7e) [0x7f6921a74e7e] [ 445.601] (EE) [ 445.724] (EE) BUG: triggered 'if (!(event-device_event.flags (1 5)))' [ 445.724] (EE) BUG: ../../dix/touch.c:644 in TouchConvertToPointerEvent() [ 445.724] (EE) Non-emulating touch event [ 445.725] (EE) [ 445.725] (EE) Backtrace: [ 445.725] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f6921bd8c78] [ 445.725] (EE) 1: /usr/bin/X (0x7f6921a3+0x7d3e7) [0x7f6921aad3e7] [ 445.725] (EE) 2: /usr/bin/X (0x7f6921a3+0x138845) [0x7f6921b68845] [ 445.725] (EE) 3: /usr/bin/X (0x7f6921a3+0x138357) [0x7f6921b68357] [ 445.725] (EE) 4: /usr/bin/X (0x7f6921a3+0x13afa2) [0x7f6921b6afa2] [ 445.726] (EE) 5: /usr/bin/X (0x7f6921a3+0x15c1d4) [0x7f6921b8c1d4] [ 445.726] (EE) 6: /usr/bin/X (mieqProcessDeviceEvent+0x1cd) [0x7f6921bbb0cd] [ 445.726] (EE) 7: /usr/bin/X (mieqProcessInputEvents+0xf7) [0x7f6921bbb1e7] [ 445.726] (EE) 8: /usr/bin/X (ProcessInputEvents+0x9) [0x7f6921ac2fe9] [ 445.726] (EE) 9: /usr/bin/X (0x7f6921a3+0x558c6) [0x7f6921a858c6] [ 445.726] (EE) 10: /usr/bin/X (0x7f6921a3+0x5994a) [0x7f6921a8994a] [ 445.726] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7f691f56cec5] [ 445.726] (EE) 12: /usr/bin/X (0x7f6921a3+0x44e7e) [0x7f6921a74e7e] [ 445.727] (EE) [ 450.837] (II) AIGLX: Suspending AIGLX clients for VT switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1351616/+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 1310690] Re: Lock screen password field does not capture key press - password is disclosed in background application
You need to install your security updates to get unity 7.2.2+14.04.20140714-0ubuntu1.1 See: http://www.ubuntu.com/usn/usn-2303-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/1310690 Title: Lock screen password field does not capture key press - password is disclosed in background application Status in Unity: Expired Status in “unity” package in Ubuntu: Expired Bug description: The new lockscreen in Ubuntu 14.04 is really nice, however I noticed (by 2 times already) that the password field doesn't capture the key presses sometimes. Key presses are not registered by the field and it looks like it is frozen (except by the cursor blinking). What I had to do when this happened was to wait until the tentative expires (screen goes blank) and then try again - then it worked. However the application running in the foregroung (or background, if you consider the lockscreen is on top) received the key presses, i.e, my whole password - you can imagine the implications if it was a chat window. I'm using 14.04, upgraded by 04/17 from 12.04 - all packages updated. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1310690/+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 1315644] Re: Can't unlock screen if VirtualBox runs in full screen mode
** Information type changed from Private Security to Public Security -- 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/1315644 Title: Can't unlock screen if VirtualBox runs in full screen mode Status in “unity” package in Ubuntu: New Bug description: Ubuntu version data: Description: Ubuntu 14.04 LTS Release: 14.04 Unity package data: unity: Instalados: 7.2.0+14.04.20140423-0ubuntu1.2 Candidato: 7.2.0+14.04.20140423-0ubuntu1.2 Hello, I'm running a full updated Ubuntu 14.04 and I've found a problem with the new lock screen (which is otherwise awesome): When VirtualBox is running in full screen mode, and the screen locks (e.g. i'm away from the computer for a while), I'm first unable to write in the password box in the lock screen, even if the input seems to be focused and the writing caret (I mean, the blinking | ) appears in the input field. Anything I type in the password box is sent to the VirtualBox's guest OS currently excecuting program, which in my case is usually VisualStudio (I see the password I typed in the currently opened file in VS, as all input is captured by VirtualBox it seems). To be able to unlock, I need to press RightCtrl + F (which is VirtualBox shortcut for toggling full screen mode) and then I can type in the password input box. So, although I can use the mouse in the lock screen (as I'm able to click to set the focus in the password box and use the indicators there), it seems that all keyboard input is still captured by VirtualBox. I haven't tested the lock screen with other full screen applications (such as games) but if you think it's important I'm willing to help testing that. I think it's a security vulnerability (so I'm marking the check) as the typed password is visible as typed in the active application in the guest operating system. Best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1315644/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
@Jochen: Displaying the mouse only takes priority if the battery is fully charged and not in a state where it's discharging. When that is the case, it's no longer worth displaying it to the user. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in One Hundred Papercuts: In Progress Status in The Power Indicator: In Progress Status in “indicator-power” package in Ubuntu: Fix Released Bug description: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1, Ubuntu 13.10 My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? https://wiki.ubuntu.com/Power#time-presentation: The brief time-remaining string for a component should be: * the time remaining for it to empty or fully charge, if estimable, in H:MM format; otherwise * 'estimating…' if the time remaining has been inestimable for less than 30 seconds; otherwise * 'unknown' if the time remaining has been inestimable for between 30 seconds and one minute; otherwise * the empty string. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1234458/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
Actually, you're right. When my battery is plugged in and charging, it is showing the mouse icon. The spec says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. In this case, my mouse does not provide an estimated time remaining, so it should not be displayed in preference to the battery. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in One Hundred Papercuts: In Progress Status in The Power Indicator: In Progress Status in “indicator-power” package in Ubuntu: Fix Released Bug description: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1, Ubuntu 13.10 My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? https://wiki.ubuntu.com/Power#time-presentation: The brief time-remaining string for a component should be: * the time remaining for it to empty or fully charge, if estimable, in H:MM format; otherwise * 'estimating…' if the time remaining has been inestimable for less than 30 seconds; otherwise * 'unknown' if the time remaining has been inestimable for between 30 seconds and one minute; otherwise * the empty string. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1234458/+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 1315434] [NEW] Mouse with no time remaining estimate showing in preference to battery being charged
Public bug reported: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1315434 Title: Mouse with no time remaining estimate showing in preference to battery being charged Status in “indicator-power” package in Ubuntu: New Bug description: When my laptop battery is in a charging state, but is not fully charged, I expect it to be displayed in preference to my mouse, which has no time remaining estimate. The spec here: https://wiki.ubuntu.com/Power says: If anything is discharging, the menu title should represent the component (not battery, but component) that is estimated to lose power first. For example, if your notebook battery is estimated to discharge in 1 hour 47 minutes, and your wireless mouse battery is estimated to discharge in 27 minutes, the menu title should represent the mouse. but there doesn't seem to be any guideline to what happens when a battery is being charged. I suggest the time remaining to charge a battery should be displayed in preference to the power level in a wireless mouse. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-power 12.10.6+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 2 11:50:36 2014 InstallationDate: Installed on 2013-11-26 (156 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: indicator-power UpgradeStatus: Upgraded to trusty on 2014-01-17 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1315434/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
I've opened bug 1315434 to track that particular issue. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in One Hundred Papercuts: In Progress Status in The Power Indicator: In Progress Status in “indicator-power” package in Ubuntu: Fix Released Bug description: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1, Ubuntu 13.10 My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? https://wiki.ubuntu.com/Power#time-presentation: The brief time-remaining string for a component should be: * the time remaining for it to empty or fully charge, if estimable, in H:MM format; otherwise * 'estimating…' if the time remaining has been inestimable for less than 30 seconds; otherwise * 'unknown' if the time remaining has been inestimable for between 30 seconds and one minute; otherwise * the empty string. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1234458/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
@Jochen: this bug is closed, please comment and send your patch to bug 1315434 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in One Hundred Papercuts: In Progress Status in The Power Indicator: In Progress Status in “indicator-power” package in Ubuntu: Fix Released Bug description: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1, Ubuntu 13.10 My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? https://wiki.ubuntu.com/Power#time-presentation: The brief time-remaining string for a component should be: * the time remaining for it to empty or fully charge, if estimable, in H:MM format; otherwise * 'estimating…' if the time remaining has been inestimable for less than 30 seconds; otherwise * 'unknown' if the time remaining has been inestimable for between 30 seconds and one minute; otherwise * the empty string. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1234458/+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 1246812] Re: Can open Evolution in greeter mode
This is CVE-2013-7374. ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-7374 -- 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/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Triaged Status in “indicator-datetime” source package in Trusty: Fix Released Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+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 1314247] Re: lock screen bypass with ctrl+alt+t
Here's a quick status update: We've been testing some updates to correct this issue, and they solve the problem. While testing, the original bug reporter discovered a regression in the shut down dialogue, which we will address before releasing an update. Thank you for your patience. -- 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: In Progress Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
This was fixed by this security update: http://www.ubuntu.com/usn/usn-2184-1/ ** Changed in: unity (Ubuntu Trusty) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+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 1313885] Re: lock screen bypass
http://www.ubuntu.com/usn/usn-2184-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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
The fix for this issue was included as part of today's security update: http://www.ubuntu.com/usn/usn-2184-1/ As such, I am closing this bug. Thanks! ** Changed in: unity (Ubuntu Trusty) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+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 1246812] Re: Can open Evolution in greeter mode
** Changed in: indicator-datetime (Ubuntu Saucy) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) -- 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/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Triaged Status in “indicator-datetime” source package in Trusty: Fix Released Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+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 1313885] Re: lock screen bypass
@azul: please file a new bug, that is likely a different issue. -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1314247] Re: lock screen bypass with ctrl+alt+t
** Information type changed from Private Security to Public Security -- 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314247] Re: lock screen bypass with ctrl+alt+t
Yes, we've managed to reproduce this, and are working on a fix. Thanks. ** Also affects: unity (Ubuntu Utopic) Importance: Undecided Status: Confirmed ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Trusty) Status: New = Confirmed ** Changed in: unity (Ubuntu Trusty) Importance: Undecided = Critical ** Changed in: unity (Ubuntu Utopic) Importance: Undecided = Critical ** Changed in: unity (Ubuntu Trusty) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Also affects: unity Importance: Undecided Status: New -- 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Confirmed Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+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 1314294] Re: You can get access to Terminal from lock screen by bypassing it with right click on indicators
*** This bug is a duplicate of bug 1314247 *** https://bugs.launchpad.net/bugs/1314247 ** This bug has been marked a duplicate of bug 1314247 lock screen bypass with ctrl+alt+t -- 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/1314294 Title: You can get access to Terminal from lock screen by bypassing it with right click on indicators Status in “unity” package in Ubuntu: New Bug description: As the title says you can bypass lock screen by right clicking on indicators several times and if you had Terminal window opened and focused you can issue commands. How to reproduce: 1. Open Terminal and play some music with mplayer 2. Lock the screen using one of the shortcuts (Super+L or Ctrl+Alt+L) 3. Right click a couple times on keyboard indicator 4. Now you can use Ctrl+C shortcut to stop your mplayer playing music in Terminal and issue any command you want. You can also open another Terminal window. I had no problem to start this way synaptic with synaptic-pkexec command and then typing my password. This all went to Unity under lock screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314294/+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 1314248] Re: lock screen bypass with open terminal
*** This bug is a duplicate of bug 1314247 *** https://bugs.launchpad.net/bugs/1314247 ** Information type changed from Private Security to Public Security ** This bug has been marked a duplicate of bug 1314247 lock screen bypass with ctrl+alt+t -- 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/1314248 Title: lock screen bypass with open terminal Status in “unity” package in Ubuntu: New Bug description: In order to reproduce: Open a Terminal Press CTRL+ALT+L to lock the screen right click the indicators some times type and you will enter into the terminal not the password field The easiest way to reproduce this is to play some music with mplayer in the terminal. If you can stop the music, skip a song etc. with your keys press CTRL+c to quit mplayer. Now you can type whatever you want and it will be executed. This probably affects other Programs. I can even switch the terminal with the default shortcuts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1314248/+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 1313885] Re: lock screen bypass
** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity (Ubuntu) Importance: Undecided = Critical -- 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/1313885 Title: lock screen bypass Status in “unity” package in Ubuntu: Confirmed Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1313885/+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 1313910] [NEW] can launch evolution from the greeter in 13.10
*** This bug is a security vulnerability *** Public security bug reported: In Ubuntu 13.10, indicator-datetime will launch evolution from the greeter. Steps to reproduce: 1- apt-get install evolution 2- From greeter, click on calendar header Expected results: - Nothing happening Actual results: - evolution is launched ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: User Name 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Apr 28 16:39:17 2014 InstallationDate: Installed on 2014-01-31 (87 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1313910 Title: can launch evolution from the greeter in 13.10 Status in “indicator-datetime” package in Ubuntu: New Bug description: In Ubuntu 13.10, indicator-datetime will launch evolution from the greeter. Steps to reproduce: 1- apt-get install evolution 2- From greeter, click on calendar header Expected results: - Nothing happening Actual results: - evolution is launched ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: User Name 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Apr 28 16:39:17 2014 InstallationDate: Installed on 2014-01-31 (87 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1313910/+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 836987] Re: indicator-datetime can launch evolution in lightdm greeter
Unfortunately, the regression in saucy was reported in a closed bug, so nobody noticed. I have opened bug 1313910 to track this issue in Ubuntu 13.10. -- 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/836987 Title: indicator-datetime can launch evolution in lightdm greeter Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: In the lightdm unity greeter, the datetime indicator is shown and can display its dropdown calendar. This dropdown contains an entry to create new calendar events. Clicking this entry launches evolution with the setup assistant. I installed evolution, so I am not sure if this entry is only displayed when evolution is installed. But I think the indicator should never launch Evolution outside a user session. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: indicator-datetime 0.2.93-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 Date: Mon Aug 29 22:41:53 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110803.1) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/836987/+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 1313885] Re: lock screen bypass
** Changed in: unity (Ubuntu) Assignee: Marco Trevisan (Treviño) (3v1n0) = Marc Deslauriers (mdeslaur) ** Also affects: unity (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Utopic) Importance: Critical Assignee: Marc Deslauriers (mdeslaur) Status: In Progress ** Changed in: unity (Ubuntu Trusty) Status: New = In Progress ** Changed in: unity (Ubuntu Trusty) Importance: Undecided = Critical ** Changed in: unity (Ubuntu Trusty) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: unity (Ubuntu Utopic) Assignee: Marc Deslauriers (mdeslaur) = Marco Trevisan (Treviño) (3v1n0) -- 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Status in “unity” source package in Trusty: In Progress Status in “unity” source package in Utopic: In Progress Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+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 1308572] Re: Ubuntu 14.04: security problem in the lock screen
Yes, bug 49579 won't get fixed until we move away from xorg into Mir... -- 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/1308572 Title: Ubuntu 14.04: security problem in the lock screen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: affects ubuntu Hello, I am running Ubuntu 14.04 with all the packages updated. When the screen is locked with password, if I hold ENTER after some seconds the screen freezes and the lock screen crashes. After that I have the computer fully unlocked. -- Marco Agnese This bug is about the lockscreen being bypassed when unity crashes/restarts, which is a critcal security issue. The crash will be handled from bug 1308750 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308572/+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 1307890] Re: virt-manager starts with title bar behind menu bar
I see this too, the titlebar gets consistently placed behind the top menu. Not sure if it's unity or compiz, but I suspect the problem is in one of those. ** Also affects: unity (Ubuntu) Importance: Undecided Status: New -- 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/1307890 Title: virt-manager starts with title bar behind menu bar Status in “unity” package in Ubuntu: New Status in “virt-manager” package in Ubuntu: New Bug description: Virtual MAchine Manager always starts with it's title bar behind the menu bar, I always have to Alt + Click the window to drag it out of there, a bit annoying :) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: virt-manager 0.9.5-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 09:59:59 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-30 (15 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to trusty on 2014-03-30 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1307890/+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 1293677] Re: FFE: Export data to accounts service
So, after discussion on irc with seb128 and tedg is seems this is basically: - indicator-sound in the user's session will export currently playing song information using accountsservice - indicator-sound in the greeter will display it, and will allow controlling it via the session broadcast service (http://bazaar.launchpad.net/~indicator-applet-developers/unity-greeter-session-broadcast/trunk.14.04/view/head:/README) - indicator-sound in the user's session will respond to events from the greeter This exposes user data to the greeter, mainly song titles. Since it is assumed that the song titles that are displayed are only what is currently playing, the amount of information that is being leaked is minimal. I agree to having this information be available to the greeter if the following conditions are met: 1- if the song is no longer _currently_ playing, indicator-sound in the user session needs to clear-out the song information from accounts service 2- The user needs to have a privacy control available that will allow them to turn off song information being sent to accounts service, and turn off indicator-sound from responding to greeter events (this can either be exposed or not in the gui as the design team prefers, as long as a setting _is_ available) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-sound in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1293677 Title: FFE: Export data to accounts service Status in “indicator-sound” package in Ubuntu: New Bug description: To support having a user control of the media player and volume on the greeter data needs to be exported by the sound indicator into the accounts service so that it can be read by the greeter user. This will then be used on the greeter to show the relevant data to the user when that user is selected on the greeter. A user on the Unity7 desktop today will not see the media players in the greeter. They will notice that volume/mute changes that they make while using the greeter will effect their session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1293677/+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 1291370] Re: in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display
Thanks for figuring this out, William! Patch looks good, uploaded. ** Changed in: virt-manager (Ubuntu) Status: Invalid = Confirmed ** Changed in: unity-gtk-module (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1291370 Title: in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display Status in “unity-gtk-module” package in Ubuntu: Invalid Status in “virt-manager” package in Ubuntu: Confirmed Bug description: 1) open virtual manager 2) create / open a virtual machine 3) start it 4) try to open menu Send keys - Ctrl Alt F2 the menu titles File, Virtual Machine, ... are visible but it's not possible to expand them, see any options under them, or click on them. I believe virtual manager is using python-gtk2. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk2-module 0.0.0+14.04.20140311-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: Wed Mar 12 13:24:29 2014 InstallationDate: Installed on 2012-01-12 (789 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) SourcePackage: unity-gtk-module UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1291370/+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 1291370] Re: in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display
I can confirm this is a regression in unity-gtk-module. Downgrading to 0.0.0+14.04.20140213.2-0ubuntu1 fixes the issue, and upgrading back to 0.0.0+14.04.20140311-0ubuntu1 breaks it again. ** Changed in: virt-manager (Ubuntu) Status: New = Invalid ** Changed in: unity-gtk-module (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-gtk-module in Ubuntu. https://bugs.launchpad.net/bugs/1291370 Title: in virtual-manager, the global-menu or local integrated menus stopped working in the vm-display Status in “unity-gtk-module” package in Ubuntu: Confirmed Status in “virt-manager” package in Ubuntu: Invalid Bug description: 1) open virtual manager 2) create / open a virtual machine 3) start it 4) try to open menu Send keys - Ctrl Alt F2 the menu titles File, Virtual Machine, ... are visible but it's not possible to expand them, see any options under them, or click on them. I believe virtual manager is using python-gtk2. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-gtk2-module 0.0.0+14.04.20140311-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: Wed Mar 12 13:24:29 2014 InstallationDate: Installed on 2012-01-12 (789 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318) SourcePackage: unity-gtk-module UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-gtk-module/+bug/1291370/+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 1287854] [NEW] newly created windows get progressively smaller
*** This bug is a duplicate of bug 1287472 *** https://bugs.launchpad.net/bugs/1287472 Public bug reported: Since I dist-upgraded this morning, newly created windows get progressively smaller. Steps to reproduce: 1- Click middle button on firefox in launcher repeatedly 2- Notice Firefox windows are opening at a smaller and smaller size Not sure if this was caused by which of the following: compiz 1:0.9.11+14.04.20140303-0ubuntu1 unity 7.1.2+14.04.20140303-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 4 13:52:10 2014 InstallationDate: Installed on 2013-11-26 (97 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (45 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1287854 Title: newly created windows get progressively smaller Status in “unity” package in Ubuntu: New Bug description: Since I dist-upgraded this morning, newly created windows get progressively smaller. Steps to reproduce: 1- Click middle button on firefox in launcher repeatedly 2- Notice Firefox windows are opening at a smaller and smaller size Not sure if this was caused by which of the following: compiz 1:0.9.11+14.04.20140303-0ubuntu1 unity 7.1.2+14.04.20140303-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Mar 4 13:52:10 2014 InstallationDate: Installed on 2013-11-26 (97 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1287854/+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 1283156] [NEW] menus switch to window title when window is unmaximized
Public bug reported: When running with Application Menu set to In top bar, applications menus switch to the window title bar when a window is unmaximized, until a different window gets focus. Steps to reproduce: 1- Launch gnome-terminal 2- hover mouse on window title bar to make sure there is no menu 3- maximize gnome-terminal 4- unmaximize gnome-terminal 5- hover mouse on window title...notice that the application menus appear in window title bar 6- Click on another window to take focus away from gnome-terminal 7-Click on gnome-terminal again 8- Hover mouse on window title, menu is now gone ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 21 12:38:20 2014 InstallationDate: Installed on 2013-11-26 (86 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (34 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lim trusty -- 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/1283156 Title: menus switch to window title when window is unmaximized Status in “unity” package in Ubuntu: New Bug description: When running with Application Menu set to In top bar, applications menus switch to the window title bar when a window is unmaximized, until a different window gets focus. Steps to reproduce: 1- Launch gnome-terminal 2- hover mouse on window title bar to make sure there is no menu 3- maximize gnome-terminal 4- unmaximize gnome-terminal 5- hover mouse on window title...notice that the application menus appear in window title bar 6- Click on another window to take focus away from gnome-terminal 7-Click on gnome-terminal again 8- Hover mouse on window title, menu is now gone ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140220-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Feb 21 12:38:20 2014 InstallationDate: Installed on 2013-11-26 (86 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1283156/+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 1283156] Re: menus switch to window title when window is unmaximized
When the problems occurs:
$ gdbus call -e -d com.canonical.Unity -o /com/canonical/Unity/Debug --method
com.canonical.Autopilot.Introspection.GetState
/Unity/PanelController/UnityPanel/MenuView/
([('/Unity/PanelController/UnityPanel/MenuView', {'id': [uint32 0, 24],
'globalRect': [uint32 1, 0, 0, 1570, 24], 'x': [uint32 0, 0],
'y': [uint32 0, 0], 'width': [uint32 0, 1570], 'height': [uint32
0, 24], 'entries': [uint32 0, uint64 7], 'opacity': [uint32 0,
0.0], 'mouse_inside': [uint32 0, false], 'grabbed': [uint32 0,
false], 'active_win_maximized': [uint32 0, false],
'active_win_is_desktop': [uint32 0, false], 'panel_title': [uint32 0,
'Terminal'], 'desktop_active': [uint32 0, false], 'monitor': [uint32
0, 0], 'active_window': [uint32 0, uint64 67109000], 'draw_menus':
[uint32 0, false], 'draw_window_buttons': [uint32 0, false],
'controls_active_window': [uint32 0, true], 'fadein_duration': [uint32
0, uint32 100], 'fadeout_duration': [uint32 0, uint32 120],
'discovery_duration': [uint32 0, uint32 2], 'discovery_fadein_duration':
[uint32 0, uint32 200], 'discovery_fadeout_duration': [uint32 0,
uint32 300], 'has_menus': [uint32 0, true], 'title_geo': [uint32 1,
6, 3, 62, 17], 'Children': [uint32 0, ['WindowButtons',
'GrabArea', 'IndicatorEntryDropdownView', 'IndicatorEntry', 'IndicatorEntry',
'IndicatorEntry', 'IndicatorEntry', 'IndicatorEntry', 'IndicatorEntry']]})],)
--
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/1283156
Title:
menus switch to window title when window is unmaximized
Status in “unity” package in Ubuntu:
New
Bug description:
When running with Application Menu set to In top bar, applications
menus switch to the window title bar when a window is unmaximized,
until a different window gets focus.
Steps to reproduce:
1- Launch gnome-terminal
2- hover mouse on window title bar to make sure there is no menu
3- maximize gnome-terminal
4- unmaximize gnome-terminal
5- hover mouse on window title...notice that the application menus appear in
window title bar
6- Click on another window to take focus away from gnome-terminal
7-Click on gnome-terminal again
8- Hover mouse on window title, menu is now gone
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.1.2+14.04.20140220-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Fri Feb 21 12:38:20 2014
InstallationDate: Installed on 2013-11-26 (86 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64
(20131016.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-01-17 (34 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1283156/+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 1259564] Re: GPG_AGENT_INFO not being passed to thunderbird
This may be caused by bug 1271591 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1259564 Title: GPG_AGENT_INFO not being passed to thunderbird Status in “indicator-messages” package in Ubuntu: New Bug description: On Trusty, if I launch thunderbird from the terminal or from the Dash, then thunderbird is able to use enigmail. If I launch via indicator- messages, it is not. Steps to reproduce: 1. adjust /usr/lib/thunderbird/thunderbird.sh to have: echo TEST: $GPG_AGENT_INFO /tmp/tbird.gpg 2. Launch from a terminal: $ rm -f /tmp/tbird.gpg ; thunderbird $ cat /tmp/tbird.gpg # separate terminal TEST: /run/user/1000/keyring-bzAKyI/gpg:0:1 (It worked!) 3. Launch from the Dash: $ rm -f /tmp/tbird.gpg launch from Dash $ cat /tmp/tbird.gpg # separate terminal TEST: /run/user/1000/keyring-bzAKyI/gpg:0:1 (It worked!) 4. Launch from indicator-messages: $ rm -f /tmp/tbird.gpg select Thunderbird Mail from indicator-messages $ cat /tmp/tbird.gpg # separate terminal TEST: (It did not work) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-messages 13.10.1+14.04.20131125-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 10 07:59:07 2013 InstallationDate: Installed on 2011-06-28 (895 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110425.2) SourcePackage: indicator-messages UpgradeStatus: Upgraded to trusty on 2013-11-04 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1259564/+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 1232814] Re: Hibernate option is missing from menu in 13.10 even after trying to re-enable
Kevin, This patch is required to make the documented workaround work with newer releases. Either this change gets accepted, or the whole section needs to be taken out, but we shouldn't have it present and broken as it currently stands. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1232814 Title: Hibernate option is missing from menu in 13.10 even after trying to re-enable Status in The Session Menu: New Status in Ubuntu Documentation: Invalid Status in “indicator-session” package in Ubuntu: Confirmed Bug description: Summary: The issues stopped appearing from 2013-11-07 onwards. The menu is built correctly now, but it is unknown which version of an updated package from that timeframe actually fixed the menu issue. The documentation needs to be updated with the instructions from the solution below to reenable hibernation in 13.10. - Solution to reenable to hibernate menuentry: File /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable- hibernate.pkla needs to contain: [Re-enable hibernate by default in upower] Identity=unix-user:* Action=org.freedesktop.upower.hibernate ResultActive=yes [Re-enable hibernate by default in logind] Identity=unix-user:* Action=org.freedesktop.login1.hibernate ResultActive=yes - I upgraded from raring to saucy on my notebook, where hibernate was enabled and working fine. Now the hibernate option is missing. I followed the instructions on how to reenable hibernate (https://help.ubuntu.com/13.10/ubuntu-help/power-hibernate.html) but the option is still missing. Hibernating from terminal via s2disk works. File exists with proper content and permissions: $ sudo ls -l /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla -rw-r--r-- 1 root root 111 Sep 29 18:52 /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla $ sudo cat /etc/polkit-1/localauthority/50-local.d/com.ubuntu.enable-hibernate.pkla [Re-enable hibernate by default] Identity=unix-user:* Action=org.freedesktop.upower.hibernate ResultActive=yes To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1232814/+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 1231529] Re: ubuntu-standard is uninstallable with only security repo enabled : language-selector-common depends unavailable version of accountsservice
** Package changed: dutch (Ubuntu) = language-selector (Ubuntu) -- 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/1231529 Title: ubuntu-standard is uninstallable with only security repo enabled : language-selector-common depends unavailable version of accountsservice Status in “accountsservice” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Invalid Bug description: We're using unattended-upgrades in Ubuntu 12.04 LTS, configured to only update packages from ubuntu-security repository. language-selector-common (0.79.4) was added to ubuntu-security repository on Friday 2013/09/13. This package depends on accountsservice (= 0.6.15-2ubuntu9.5), but this version is not presend in the ubuntu-security repository (0.6.15-2ubuntu9.1). As a matter of fact, our systems can not upgrade this package : The following packages have been kept back: language-selector-common This also breaks fresh installations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1231529/+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 1250632] Re: Date and time indicator option Add an event doesn't work.
It seems this needs evolution to be installed to do anything. Since we don't install evolution by default, perhaps the entry in the menu should be greyed out or even removed if evolution isn't available. ** Tags added: rls-t-incoming -- 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/1250632 Title: Date and time indicator option Add an event doesn't work. Status in The Date and Time Indicator: New Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: When I clicking Add an event it does nothing... ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131023.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 12 23:11:32 2013 InstallationDate: Installed on 2013-11-10 (2 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1250632/+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 1244680] Re: Clock freezes after changing timezone
** Tags added: rls-t-incoming -- 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/1244680 Title: Clock freezes after changing timezone Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: The time in the datetime indicator freezes when you change the timezone. To reproduce: 1) Note the current time in the datetime indicator 2) Change the system timezone, such as by clicking a different timezone in the datetime indicator menu or changing timezone in the date/time system settings app Expected results: The clock in the datetime indicator updates to show the current time in the new timezone. The clock continues to function normally, updating the minutes/hours as time progresses Actual results: The clock in the datetime indicator freezes. It does not update to the new timezone and no longer updates the minutes/hours - it stays frozen at the time it displayed when you updated the timezone. The system time is not affected; running 'date' from a terminal displays the correct time. The menu in the datetime indicator will display the correct time. It's just the clock in the panel that is broken. This is 100% reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20131016.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Oct 25 10:07:03 2013 InstallationDate: Installed on 2010-09-17 (1134 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True SourcePackage: indicator-datetime UpgradeStatus: Upgraded to saucy on 2013-08-07 (78 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1244680/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
Well, Logitech mice do provide useful percentage of battery remaining information. I think this simply needs to be fixed to remove the time estimation if the device doesn't provide it. Knowing that my mouse battery is at 10% remaining before going on a trip is useful to know. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in The Power Indicator: New Status in “indicator-power” package in Ubuntu: Confirmed Bug description: My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 20:19:51 2013 InstallationDate: Installed on 2012-11-13 (323 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-08-19 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1234458/+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 1243166] Re: memory leaks leading to performance issues in global menu
** Tags added: rls-t-incoming -- 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/1243166 Title: memory leaks leading to performance issues in global menu Status in “unity” package in Ubuntu: Confirmed Bug description: Since upgrading to saucy, I've seen a lot of memory consumption with unity-panel-service, leading to menus taking a second or two to draw when simply hovering over File, View, etc. mdeslaur@mdlinux:~$ uptime 07:31:12 up 4 days, 17:04, 10 users, load average: 0.42, 0.55, 0.45 mdeslaur@mdlinux:~$ ps aux | grep panel mdeslaur 3331 2.4 5.1 102 410144 ? Ssl Oct17 163:52 /usr/lib/unity/unity-panel-service ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19+kmemleak-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 22 07:26:46 2013 InstallationDate: Installed on 2012-11-13 (342 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-08-19 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1243166/+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 1243166] [NEW] memory leaks leading to performance issues in global menu
Public bug reported: Since upgrading to saucy, I've seen a lot of memory consumption with unity-panel-service, leading to menus taking a second or two to draw when simply hovering over File, View, etc. mdeslaur@mdlinux:~$ uptime 07:31:12 up 4 days, 17:04, 10 users, load average: 0.42, 0.55, 0.45 mdeslaur@mdlinux:~$ ps aux | grep panel mdeslaur 3331 2.4 5.1 102 410144 ? Ssl Oct17 163:52 /usr/lib/unity/unity-panel-service ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19+kmemleak-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 22 07:26:46 2013 InstallationDate: Installed on 2012-11-13 (342 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-08-19 (63 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug rls-t-incoming saucy -- 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/1243166 Title: memory leaks leading to performance issues in global menu Status in “unity” package in Ubuntu: Confirmed Bug description: Since upgrading to saucy, I've seen a lot of memory consumption with unity-panel-service, leading to menus taking a second or two to draw when simply hovering over File, View, etc. mdeslaur@mdlinux:~$ uptime 07:31:12 up 4 days, 17:04, 10 users, load average: 0.42, 0.55, 0.45 mdeslaur@mdlinux:~$ ps aux | grep panel mdeslaur 3331 2.4 5.1 102 410144 ? Ssl Oct17 163:52 /usr/lib/unity/unity-panel-service ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19+kmemleak-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Oct 22 07:26:46 2013 InstallationDate: Installed on 2012-11-13 (342 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-08-19 (63 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1243166/+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 1199877] Re: unity-panel-service pegs one of my CPUs at 100%
** Tags added: rls-t-incoming ** Summary changed: - unity-panel-service pegs one of my CPUs at 100% + unity-panel-service memory leak and 100% CPU usage -- 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/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Ubuntu Power Consumption Project: New Status in Unity: In Progress Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: Triaged Bug description: Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel- service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1199877/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
** Tags added: rls-t-incoming -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in “indicator-power” package in Ubuntu: Confirmed Bug description: My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 20:19:51 2013 InstallationDate: Installed on 2012-11-13 (323 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-08-19 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1234458/+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 1234458] Re: Indicator stuck on mouse icon, along with estimating...
** Attachment added: upower --dump when problem is happening https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1234458/+attachment/3887431/+files/upower-dump.txt -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in The Power Indicator: New Status in “indicator-power” package in Ubuntu: Confirmed Bug description: My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 20:19:51 2013 InstallationDate: Installed on 2012-11-13 (323 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-08-19 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1234458/+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 1231529] Re: ubuntu-standard is uninstallable with only security repo enabled : language-selector-common depends unavailable version of accountsservice
I will rebuild accountsservice in the -security pocket. ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: accountsservice (Ubuntu) Status: New = Confirmed ** Changed in: language-selector (Ubuntu) Status: Confirmed = Invalid ** Changed in: accountsservice (Ubuntu) Importance: Undecided = High -- 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/1231529 Title: ubuntu-standard is uninstallable with only security repo enabled : language-selector-common depends unavailable version of accountsservice Status in “accountsservice” package in Ubuntu: Confirmed Status in “language-selector” package in Ubuntu: Invalid Bug description: We're using unattended-upgrades in Ubuntu 12.04 LTS, configured to only update packages from ubuntu-security repository. language-selector-common (0.79.4) was added to ubuntu-security repository on Friday 2013/09/13. This package depends on accountsservice (= 0.6.15-2ubuntu9.5), but this version is not presend in the ubuntu-security repository (0.6.15-2ubuntu9.1). As a matter of fact, our systems can not upgrade this package : The following packages have been kept back: language-selector-common This also breaks fresh installations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1231529/+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 1238258] [NEW] indicator-power tries to use icons that don't exist
Public bug reported: When I log in, my mouse is shown as not present until the first upower statistics arrive. While that happens, indicator-power tries to use an icon that doesn't exist: ie, from src/device.c: g_ptr_array_add (names, g_strdup_printf(%s-missing-symbolic, kind_str)); g_ptr_array_add (names, g_strdup_printf(gpm-%s-missing, kind_str)); g_ptr_array_add (names, g_strdup_printf(%s-missing, kind_str)); kind_str is mouse. mouse-missing isn't an icon available anywhere, including gnome-icon- themes, or ubuntu-mono. Perhaps it should use gpm-mouse-000? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20131008-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Thu Oct 10 16:44:39 2013 InstallationDate: Installed on 2012-11-13 (330 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-08-19 (52 days ago) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Attachment added: screenshot showing the issue https://bugs.launchpad.net/bugs/1238258/+attachment/3872987/+files/Screenshot%20from%202013-10-10%2016%3A11%3A39.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1238258 Title: indicator-power tries to use icons that don't exist Status in “indicator-power” package in Ubuntu: New Bug description: When I log in, my mouse is shown as not present until the first upower statistics arrive. While that happens, indicator-power tries to use an icon that doesn't exist: ie, from src/device.c: g_ptr_array_add (names, g_strdup_printf(%s-missing-symbolic, kind_str)); g_ptr_array_add (names, g_strdup_printf(gpm-%s-missing, kind_str)); g_ptr_array_add (names, g_strdup_printf(%s-missing, kind_str)); kind_str is mouse. mouse-missing isn't an icon available anywhere, including gnome- icon-themes, or ubuntu-mono. Perhaps it should use gpm-mouse-000? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20131008-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Thu Oct 10 16:44:39 2013 InstallationDate: Installed on 2012-11-13 (330 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-08-19 (52 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1238258/+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 1234458] [NEW] Indicator stuck on mouse icon, along with estimating...
Public bug reported: My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 20:19:51 2013 InstallationDate: Installed on 2012-11-13 (323 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-08-19 (44 days ago) ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1234458 Title: Indicator stuck on mouse icon, along with estimating... Status in “indicator-power” package in Ubuntu: New Bug description: My power indicator is stuck on the mouse icon. When I click on it, it says Mouse (estimating). Why is it stuck on estimating? Why show the icon at all if I'm using a Logitech mouse with a battery? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-power 12.10.6+13.10.20130918.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2 Uname: Linux 3.11.0-9-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 2 20:19:51 2013 InstallationDate: Installed on 2012-11-13 (323 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: indicator-power UpgradeStatus: Upgraded to saucy on 2013-08-19 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1234458/+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 1223389] Re: indicator-datetime-service crashed with SIGSEGV
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a regular (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1223389/+attachment/3813383/+files/CoreDump.gz ** Information type changed from Public Security to Public -- 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/1223389 Title: indicator-datetime-service crashed with SIGSEGV Status in “indicator-datetime” package in Ubuntu: New Bug description: The Time and Date is not displayed in the Panel after upgrading vom 13.04 to 13.10... ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: indicator-datetime 13.10.0+13.10.20130903-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 10 16:25:35 2013 Disassembly: = 0x7f7a7c32ff90: Cannot access memory at address 0x7f7a7c32ff90 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime-service InstallationDate: Installed on 2013-04-05 (158 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=de_DE LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f7a7c32ff90:Cannot access memory at address 0x7f7a7c32ff90 PC (0x7f7a7c32ff90) ok SP (0x7fffb7c0e910) ok Reason could not be automatically determined. Signal: 11 SourcePackage: indicator-datetime Stacktrace: #0 0x7f7a7c32ff90 in ?? () No symbol table info available. #1 0x in ?? () No symbol table info available. StacktraceTop: ?? () ?? () Title: indicator-datetime-service crashed with SIGSEGV UpgradeStatus: Upgraded to saucy on 2013-09-07 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1223389/+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
