[Dx-packages] [Bug 1506744] Re: Newly installed applications do not show in the dash
To elaborate on the previous remark: why didn't we just replace: menu_monitor_queue_event (event_info); with: g_timeout_add_seconds (2, menu_monitor_queue_event, event_info); (and make sure menu_monitor_queue_event() returns FALSE)? -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in gnome-menus package in Ubuntu: In Progress Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1506744] Re: Newly installed applications do not show in the dash
The latest patch looks good to me, but with a couple of notes (no need to fix these): - using the _full() version of the timeout call is not necessary here - now that this patch is simplified it becomes easy to see how all of this is just putting values into one structure and then later moving them into another structure. It seems like we could have just used the first structure type, or even just fixed the other queue mechanism to add the delay. Oh well. No real gain from making that change at this point. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in gnome-menus package in Ubuntu: In Progress Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1506744] Re: Newly installed applications do not show in the dash
Switching away from Unity (and Ubuntu). This should be of high priority...especially because there is no launcher menu or other alternative to find your app. I'll try Ubuntu again in a year or so. -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in gnome-menus package in Ubuntu: In Progress Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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 1362962] Re: Calendar icon usually shows the wrong date
This should be closed as "won't fix," marking it as "released" is misleading. -- 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/1362962 Title: Calendar icon usually shows the wrong date Status in Canonical System Image: Fix Committed Status in Ubuntu Calendar App: Invalid Status in indicator-datetime package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity-scope-click package in Ubuntu: Confirmed Bug description: Problem occurs with: Ubuntu 14.10 r203 Does not occur with: iOS, Windows Phone 1. In the clock menu, find the calendar app and launch it. 2. In the Launcher or Dash, find the Calendar app. What you see: 1. The icon always says "25", regardless of the actual date. 2. The icon always says "28", regardless of the actual date. What you should see: 1. The icon shows the current date. 2. The icon shows the current date. The equivalent for PC is bug 1362033, and for the Clock app is bug 1362964. This depends on bug 1453795 for Unity letting an app change its own icon. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362962/+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 1506744] Re: Newly installed applications do not show in the dash
The patch in comment 42 is not acceptable, for two big reasons. First: you need to hold a ref on the GFile object when you put it into the info struct. This means that you cannot simply use g_free for the struct: you need to write a custom free func that handles the unref as well. Also: you can't cast g_source_remove() to a GDestroyNotify and expect that to work... one takes a pointer, and the other an int. This may randomly work on some architectures, sometimes, but you cannot rely on this. The entire act of keeping the list is slightly suspect. At the sprint I think I mentioned that it would be better to have one global timeout that is set (and reset) when any activity happens. The timeout would run after the activity died down, and it would handle all things together in one go. In that case, you'd still need a list, except for the info objects themselves. It's also fine to keep the list of the timeout IDs, but you can't free it in the way that you're doing in the current patch. Another nice approach, if you want to avoid running the callbacks after teardown: store a weak pointer to the main object in each of the info structs (g_object_add_weak_pointer). The info structs are then used as the user_data to the timeout (this assumes you keep the multiple timeouts). If you find the weak pointer to be empty, then just return without doing anything. That also means that you don't need to handle the "cleanup" -- it will happen automatically. It also means that you can avoid the custom free function if you are clever: the timeout will always run once, and you can do the cleanup from the normal handler (taking care regarding the early exit discussed above). -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1506744 Title: Newly installed applications do not show in the dash Status in GLib: Confirmed Status in gnome-menus package in Ubuntu: In Progress Status in libunity package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: I am running 15.10 development version fully up to date, I installed it a few days ago and I have an issue with newly installed applications not appearing in the dash when I search for them, they can be started via console but the icons/launchers of newly installed applications will only appear in the dash after session is restarted. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity 7.3.2+15.10.20151002.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Oct 16 08:41:39 2015 InstallationDate: Installed on 2015-10-11 (4 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1506744/+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"
Although I agree that it makes sense to allow the user to modify their own data even if not "actively logged in", I think it would also be interesting to track down the program that is the real source of this problem. ie: let's figure out which part of the session is writing to accountsservice at random times... -- 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: Confirmed 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 1485659] Re: Date/time indicator doesn't update after changing time zone
A couple of notes: - this is fixed upstream in GLib already - watching dbus for the signal is fine, but you should not use dbus to read the property in the first place. This will result in activation of the datetime service, which is expensive. -- 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/1485659 Title: Date/time indicator doesn't update after changing time zone Status in indicator-datetime package in Ubuntu: In Progress Bug description: After changing the timezone the time displayed in the date/time indicator is still in my old time zone. I sent a signal to the indicator-datetime-service process, and after it restarted the correct time was displayed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 17 08:51:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-19 (178 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+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 1390625] Re: mouse cursor gets corrupted
On my XPS 13, my trackpad stopped working after I installed xserver- xorg. I was able to fix the problem by installing xserver-xorg-input- synaptics. Thanks! :) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] 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 Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Installed a pristine trusty system, configured lib{nss,pam}-ldapd, and
confirmed that updating to nslcd 0.8.13-3ubuntu1 from trusty-proposed
allows LDAP users to unlock the Unity lockscreen.
--
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/1314095
Title:
Unity Lockscreen in 14.04 can't unlock when using LDAP account
Status in Unity:
Invalid
Status in nss-pam-ldapd package in Ubuntu:
Fix Released
Status in unity package in Ubuntu:
Invalid
Status in nss-pam-ldapd source package in Trusty:
Fix Committed
Status in unity source package in Trusty:
Invalid
Status in nss-pam-ldapd source package in Utopic:
Fix Released
Status in unity source package in Utopic:
Invalid
Status in nss-pam-ldapd package in Debian:
Fix Released
Bug description:
SRU justification:
[Impact]
* Summary: in Trusty, when libnss-ldapd is used, LDAP users are not
able to unlock the Unity lockscreen. Utopic and later are not
affected. Some workarounds are listed in comment #29.
* nslcd in Trusty and earlier does not permit unprivileged users to
read shadow entries. When invoked by the Unity lockscreen, running as
the logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in
pam_acct_mgmt when it tries to get password expiry information from
shadow. This leads to an authorization failure, so Unity refuses to
unlock the screen. pam_ldap is not consulted for pam_acct_mgmt after
pam_unix fails because its rule is in the Additional section.
* In Utopic and later, nslcd returns partial shadow entries to
unprivileged users. This is enough for the expiry check in pam_unix to
succeed, so the screen can be unlocked. See
http://bugs.debian.org/706913 for a discussion of the upstream fix.
* This proposed SRU backports the upstream solution to Trusty's nslcd.
This is a change of behaviour for shadow queries from unprivileged
users, compared to the current package. An alternative, more targeted
fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from
pam_acct_mgmt, like gnome-screensaver already does (see comment #29).
The nslcd change is a more general fix for not just Unity, but any
PAM-using program run by an unprivileged user.
[Test Case]
* Install and configure libnss-ldapd. Ensure ldap is enabled for at
least the passwd and shadow services in /etc/nsswitch.conf.
* Log into Unity as an LDAP user, lock the screen, and then try to
unlock it again.
[Regression Potential]
* The patch is minimal, was written by the upstream author, and was
backported (adjusting for whitespace changes) to Trusty. The change
has already been released in Utopic and will be included in Debian
Jessie as well.
* Regression testing should include checking that shadow queries, both
by name and for listing all users, are unchanged when issued as root.
[Other Info]
* Packages for testing are available in ppa:rtandy/lp1314095
Original description:
My setup is:
Ubuntu 14.04 LTS,
ldap accounts,
krb5 authentication,
Lightdm,
Unity session
ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent
passwd and getent shadow works fine.
I am able to login in console without any problems.
I was able to login in lightdm.
Then I used the lock screen.
I could not disable the lock screen using my password.
I rebooted my computer.
Now:
After logging in through lightdm, the unity lockscreen locks the screen
immediately and I can not disable it using my password.
From my short inspection of auth.log and unix_chkpwd sources it seems,
that unix_chkpwd works fine when called from lightdm and fails to get
user info when called from unity lockscreen.
lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
apt-cache policy unity lightdm libpam-modules
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://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
*** 1.10.0-0ubuntu3 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
libpam-modules:
Installed: 1.1.8-1ubuntu2
Candidate: 1.1.8-1ubuntu2
Version table:
*** 1.1.8-1ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
Contents of /var/log/auth.log:
Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement
user ingroup nopasswdlogin not met by user user
Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user
Apr 29
[Dx-packages] [Bug 1390625] Re: mouse cursor gets corrupted
I'll add my 2 cents into this discussion as well. First bug I ran into when using elementary OS Freya on my Lenovo X201 w/Integrated Intel Graphics. The cursor gets corrupted whenever I click and drag a file or shortcut somewhere on the desktop. I can click and drag scroll bars, windows, etc... It only ever happens when I click drag a file or short cut. As soon as I drag the cursor gets corrupted and displays two arrows and a small sliver of whatever was open on the screen at that time. Switching to a different work space seems to clear it up as well. -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Confirmed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when dragdropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a dragdrop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] 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 Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+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 1443774] [NEW] Horizontal scrolling is backwards
Public bug reported: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) ** Affects: unity (Ubuntu) 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/1443774 Title: Horizontal scrolling is backwards Status in unity package in Ubuntu: New Bug description: Don't know where to report this specifically, sorry. In native gnome applications (file manager, gedit, etc), scrolling horizontally via Trackpoint middle-button scrolling is backwards: * Middle button + trackpoint move up = scroll up (expected) * Middle button + trackpoint move down = scroll down (expected) * Middle button + trackpoint move left = scroll right (backwards) * Middle button + trackpoint move right = scroll left (backwards) Scolling horizontally in Firefox and Chromium work as expected. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3 Uname: Linux 3.19.0-13-generic x86_64 ApportVersion: 2.17-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Apr 13 23:36:58 2015 InstallationDate: Installed on 2015-03-07 (38 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1443774/+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 1437767] Re: Icons contain pixellated artifacts
** Attachment added: aa1.gif https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437767/+attachment/4364775/+files/aa1.gif -- 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/1437767 Title: Icons contain pixellated artifacts Status in unity package in Ubuntu: New Bug description: After upgrading from utopic to vivid beta, many (but apparently not all) icons in Unity contain pixellation artifacts, as if it's been scaled up very slightly. Please see the attachment and note the launcher, as well as Security Privacy which was highlighted when taking the screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150324.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu5 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: Sat Mar 28 19:48:12 2015 DistUpgraded: 2015-03-28 19:13:12,615 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2226] InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) XorgConf: Section Monitor Identifier default monitor DisplaySize276 156# In millimeters EndSection dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Mar 28 19:26:54 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1005 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437767/+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 1437767] Re: Icons contain pixellated artifacts
Updating and rebooting trusty today did not help. Note in the original screenshot how the chevron in the terminal icon is lopsided (enlarged 400% in aa2.png), and the top edge of the disk icon at the bottom is jagged. Also, I've made aa1.gif (also at 400%), which shows when the security icon is hovered over, its gets a badly antialiased dark border. (The 256 color limitation of gif introduces its own artifacts, but the original problem is still clearly visible.) ** Changed in: unity (Ubuntu) Status: Incomplete = 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/1437767 Title: Icons contain pixellated artifacts Status in unity package in Ubuntu: New Bug description: After upgrading from utopic to vivid beta, many (but apparently not all) icons in Unity contain pixellation artifacts, as if it's been scaled up very slightly. Please see the attachment and note the launcher, as well as Security Privacy which was highlighted when taking the screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150324.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu5 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: Sat Mar 28 19:48:12 2015 DistUpgraded: 2015-03-28 19:13:12,615 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2226] InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) XorgConf: Section Monitor Identifier default monitor DisplaySize276 156# In millimeters EndSection dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Mar 28 19:26:54 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1005 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437767/+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 1437767] Re: Icons contain pixellated artifacts
** Attachment added: aa2.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437767/+attachment/4364776/+files/aa2.png -- 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/1437767 Title: Icons contain pixellated artifacts Status in unity package in Ubuntu: New Bug description: After upgrading from utopic to vivid beta, many (but apparently not all) icons in Unity contain pixellation artifacts, as if it's been scaled up very slightly. Please see the attachment and note the launcher, as well as Security Privacy which was highlighted when taking the screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150324.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu5 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: Sat Mar 28 19:48:12 2015 DistUpgraded: 2015-03-28 19:13:12,615 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2226] InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) XorgConf: Section Monitor Identifier default monitor DisplaySize276 156# In millimeters EndSection dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Mar 28 19:26:54 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1005 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1437767/+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 553918] Re: Keyboard shortcut usage blocks keyboard and other menus
*** This bug is a duplicate of bug 658723 *** https://bugs.launchpad.net/bugs/658723 ** This bug is no longer a duplicate of bug 568401 Indicator applets open when pressing S or M key via NX, VNC ** This bug has been marked a duplicate of bug 658723 VNCServer - Super modifier is always applied -- 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/553918 Title: Keyboard shortcut usage blocks keyboard and other menus Status in Indicator Applet: Fix Released Status in indicator-applet package in Ubuntu: Incomplete Bug description: STR: 1. Use Super+S shortcut. 2. Dismiss the selection (Esc)/ Select something from the menu 3. Try typing something in the terminal or select anything from menu bar (including Gnome menu bar) Actual behavior: Menus do not open and keystrokes are not sent to the applications. Expected behavior: Everything should work as before. Tested on desktop and UNR installs of Lucid with latest updates. This can also be reproduced in VM indicator-session: Installed: 0.2.7-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/553918/+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 568401] Re: Indicator applets open when pressing S or M key via NX, VNC
*** This bug is a duplicate of bug 658723 *** https://bugs.launchpad.net/bugs/658723 ** This bug has been marked a duplicate of bug 658723 VNCServer - Super modifier is always applied -- 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/568401 Title: Indicator applets open when pressing S or M key via NX, VNC Status in Indicator Applet: Fix Released Status in gnome-do package in Ubuntu: New Status in indicator-applet package in Ubuntu: Fix Released Status in gnome-do source package in Lucid: New Status in indicator-applet source package in Lucid: Fix Released Bug description: Binary package hint: indicator-applet When logging into a session user NX or VNC, whenever I press the S key (without modifiers), the logout menu is opened. When I press M, the messaging menu is opened. Other programs in the NX/VNC session don't have this problem. When I remove the indicator applets from the panel, the M and S keys work OK. Tested using the NX client for Mac OS X and Jolly's Fast VNC. The Windows client of NX doesn't have the problem. xkeycaps shows the following info: * Mac OS NX client: pressing M key gives keycode C 0x36 54 066 and KeySym m M mu U02DC. * Windows NX client: pressing M key gives keycode M 0x3A 58 072 and KeySym m M mu masculine mu masculine. indicator-applet: Installed: 0.3.6-0ubuntu2 Candidate: 0.3.6-0ubuntu2 Version table: *** 0.3.6-0ubuntu2 0 500 http://nl.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/568401/+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 1437767] [NEW] Icons contain pixellated artifacts
Public bug reported: After upgrading from utopic to vivid beta, many (but apparently not all) icons in Unity contain pixellation artifacts, as if it's been scaled up very slightly. Please see the attachment and note the launcher, as well as Security Privacy which was highlighted when taking the screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150324.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu5 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: Sat Mar 28 19:48:12 2015 DistUpgraded: 2015-03-28 19:13:12,615 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2226] InstallationDate: Installed on 2015-03-07 (22 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: LENOVO 20CMCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor psmouse.proto=imps quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) XorgConf: Section Monitor Identifier default monitor DisplaySize276 156# In millimeters EndSection dmi.bios.date: 01/23/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET28W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CMCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CMCTO1WW dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.59-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Sat Mar 28 19:26:54 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1005 vendor LGD xserver.version: 2:1.17.1-0ubuntu3 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu vivid ** Attachment added: Screenshot from 2015-03-28 19:45:29.png https://bugs.launchpad.net/bugs/1437767/+attachment/4359430/+files/Screenshot%20from%202015-03-28%2019%3A45%3A29.png -- 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/1437767 Title: Icons contain pixellated artifacts Status in unity package in Ubuntu: New Bug description: After upgrading from utopic to vivid beta, many (but apparently not all) icons in Unity contain pixellation artifacts, as if it's been scaled up very slightly. Please see the attachment and note the launcher, as well as Security Privacy which was highlighted when taking the screenshot. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150324.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.16.2-0ubuntu5 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: Sat Mar 28 19:48:12 2015 DistUpgraded: 2015-03-28 19:13:12,615 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device
[Dx-packages] [Bug 1315434] Re: Mouse with no time remaining estimate showing in preference to battery being charged
Just to play devil's advocate a bit here: The logic taken in this bug (that we should show the device that will run out of power first) seems perfectly sound, but it makes a very large assumption, which I suspect will often be untrue: that reporting of time remaining on mice will always be completely accurate. I think there are two problems with the assumption. The first is that there have been reports (one just now on IRC from jcastro) about faulty hardware/driver combos that report things like 1 minute remaining all the time. Users with this hardware would probably like that fixed, but for lack of a fix, would probably prefer to be able to go on with their lives with the minimum amount of disruption. Second issue is that I wonder if estimated time left reporting on a device which has a battery that lasts up to a year is _ever_ accurate to the hours or minutes that we would need it to be in order to meaningfully compare it against laptop battery life. Those two point combined cause me to believe that the only case in which this feature would be engaged would be in the wrong case. Maybe it makes sense to just remove it entirely after all? -- 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 1430542] [NEW] Indicator doesn't use weighted average with different-sized batteries
Public bug reported: The indicator implements the spec: https://wiki.ubuntu.com/Power#Handling_multiple_batteries which states: Their percentages should be averaged. Apparently this was taken to mean the simple arithmetic mean, and not the weighted average (by the capacity of each battery). http://bazaar.launchpad.net/~indicator-applet-developers/indicator- power/trunk.15.04/view/head:/src/service.c#L1316 shows: const double percent = sum_percent / n_batteries; This means that if one battery is twice as large as another, then after that battery is discharged, 50% would be reported. I'd expect 33%. The spec needs to be updated to be less ambiguous about the intended meaning of the word average and the code needs to be fixed. ** Affects: indicator-power (Ubuntu) Importance: Undecided Status: New -- 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/1430542 Title: Indicator doesn't use weighted average with different-sized batteries Status in indicator-power package in Ubuntu: New Bug description: The indicator implements the spec: https://wiki.ubuntu.com/Power#Handling_multiple_batteries which states: Their percentages should be averaged. Apparently this was taken to mean the simple arithmetic mean, and not the weighted average (by the capacity of each battery). http://bazaar.launchpad.net/~indicator-applet-developers/indicator- power/trunk.15.04/view/head:/src/service.c#L1316 shows: const double percent = sum_percent / n_batteries; This means that if one battery is twice as large as another, then after that battery is discharged, 50% would be reported. I'd expect 33%. The spec needs to be updated to be less ambiguous about the intended meaning of the word average and the code needs to be fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1430542/+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 1426597] Re: please respect org.gnome.desktop.screensaver idle-activation-enabled key
Setting idle-delay does disable the screensaver, but at the expense of having my session no longer marked idle at all. So for example, configuring logind to suspend or shutdown an idle computer is no longer effective. IMO this conflates two different things: whether or not the session is marked idle, and whether or not the screensaver is activated when that happens. But if that is indeed the intent of the design, feel free to reject this; and my apologies for wasting your time. -- 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/1426597 Title: please respect org.gnome.desktop.screensaver idle-activation-enabled key Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: GNOME Screensaver allowed me to disable screen blanking while still having the desktop marked idle if I don't touch it for some time. Unity allows the idle-activation-enabled key for schema compatibility but does not use it at all; the UI for disabling screen blanking implicitly disables marking the system idle altogether (this was true in GNOME too). I don't have a patch ready right now but will work on one. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-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 CasperVersion: 1.351 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 28 00:12:20 2015 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150225) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.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/unity/+bug/1426597/+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 1426597] Re: please respect org.gnome.desktop.screensaver idle-activation-enabled key
** Changed in: unity (Ubuntu) Status: Incomplete = Invalid ** Changed in: unity Status: Incomplete = 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/1426597 Title: please respect org.gnome.desktop.screensaver idle-activation-enabled key Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: GNOME Screensaver allowed me to disable screen blanking while still having the desktop marked idle if I don't touch it for some time. Unity allows the idle-activation-enabled key for schema compatibility but does not use it at all; the UI for disabling screen blanking implicitly disables marking the system idle altogether (this was true in GNOME too). I don't have a patch ready right now but will work on one. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-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 CasperVersion: 1.351 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 28 00:12:20 2015 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150225) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.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/unity/+bug/1426597/+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 1426597] [NEW] please respect org.gnome.desktop.screensaver idle-activation-enabled key
Public bug reported: GNOME Screensaver allowed me to disable screen blanking while still having the desktop marked idle if I don't touch it for some time. Unity allows the idle-activation-enabled key for schema compatibility but does not use it at all; the UI for disabling screen blanking implicitly disables marking the system idle altogether (this was true in GNOME too). I don't have a patch ready right now but will work on one. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-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 CasperVersion: 1.351 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 28 00:12:20 2015 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150225) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** 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/1426597 Title: please respect org.gnome.desktop.screensaver idle-activation-enabled key Status in Unity: New Status in unity package in Ubuntu: New Bug description: GNOME Screensaver allowed me to disable screen blanking while still having the desktop marked idle if I don't touch it for some time. Unity allows the idle-activation-enabled key for schema compatibility but does not use it at all; the UI for disabling screen blanking implicitly disables marking the system idle altogether (this was true in GNOME too). I don't have a patch ready right now but will work on one. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20150219.2-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 CasperVersion: 1.351 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Feb 28 00:12:20 2015 LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150225) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.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/unity/+bug/1426597/+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 1237554] Re: compiz crashed with SIGSEGV in _wordcopy_fwd_aligned()
** Tags added: 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/1237554 Title: compiz crashed with SIGSEGV in _wordcopy_fwd_aligned() Status in nvidia-graphics-drivers-304 package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: No further information. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Wed Oct 9 14:51:38 2013 ExecutablePath: /usr/bin/compiz MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f861c2778a5 _wordcopy_fwd_aligned+181:mov (%rsi),%rax PC (0x7f861c2778a5) ok source (%rsi) (0x7fc18bf7d000) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: _wordcopy_fwd_aligned (dstp=195493360, srcp=140469253689344, len=608) at wordcopy.c:79 ?? () from /usr/lib/nvidia-304-updates/libnvidia-glcore.so.304.108 ?? () from /usr/lib/nvidia-304-updates/libnvidia-glcore.so.304.108 ?? () from /usr/lib/nvidia-304-updates/libnvidia-glcore.so.304.108 ?? () from /usr/lib/nvidia-304-updates/libnvidia-glcore.so.304.108 Title: compiz crashed with SIGSEGV in _wordcopy_fwd_aligned() 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/nvidia-graphics-drivers-304/+bug/1237554/+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 1418939] Re: unity actively overrides system-wide gsettings as current user, making some vendor overrides ineffective
I think the indicator-keyboard code for migrating settings is
responsible, at least for the layout setting. I worked around it by
writing a gschema override for org.gnome.libgnomekbd.keyboard.layouts,
the old location where settings are migrated from, instead of
org.gnome.desktop.input-sources.sources.
http://bazaar.launchpad.net/~indicator-applet-developers/indicator-
keyboard/trunk/view/head:/lib/main.vala#L389
--
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/1418939
Title:
unity actively overrides system-wide gsettings as current user, making
some vendor overrides ineffective
Status in Unity:
Confirmed
Status in unity package in Ubuntu:
Confirmed
Bug description:
How to reproduce:
as root execute
# echo -e [org.gnome.desktop.input-sources]\nsources=[('xkb', 'us'), ('xkb',
'hu')]\n\n /usr/share/glib-2.0/schemas/99_my.gschema.override
# echo -e [org.compiz.unityshell]\nlauncher-minimize-window=true\n\n
/usr/share/glib-2.0/schemas/99_my.gschema.override
# glib-compile-schemas /usr/share/glib-2.0/schemas
and, either remove contents of home directory or create a new user,
and, reboot and log in as the appropriate user.
Result is that launcher-minimize-window settings=true as expected and
launcher behaves accordingly, however input sources is just [('xkb',
'us')], where as it should be [('xkb', 'us'), ('xkb', 'hu')].
The launcher-minimize-window is just a random example. For most
settings the vendor override method works.
But for a few, like org.gnome.desktop.input-sources sources, they
will not take effect, as some process, related to Unity, will override
them for the current user after login.
Proof of this, is that running `gsettings reset org.gnome.desktop
.input-sources sources` will result in [('xkb', 'us'), ('xkb', 'hu')],
and the panel offering both layouts. Hence the vendor-override-method
of setting system-wide defaults does work, but Unity ruins it for a
few settings.
The proof that this bug is in Unity is that, installing another
desktop environment, like gnome-shell, and logging into it, leaves all
the system-wide defaults effective.
This bug makes vendor overrides, that should affect all fresh user
accounts, ineffective.
The appropriate behaviour would be that a new user, or one that has
its home directory cleared, to have the system-wide default gsettings
in effect for their unity session.
Original problem statement: http://askubuntu.com/questions/582083
/what-is-overriding-the-systemwide-keyboard-layout-settings
To get a more comprehensive but still incomplete listing of the settings that
Unity overrides, log in into a fresh Unity session,
$ gsettings list-recursively /tmp/01
$ gsettings list-schemas | xargs -n 1 gsettings reset-recursively
$ gsettings list-recursively /tmp/02
$ diff /tmp/0* | less
This listing is incomplete, because it only lists non-relocatable schemas,
and also because your system-wide defaults may match those of what Unity sets
the users settings to. For example, not changing the layout setting to
[('xkb', 'us'), ('xkb', 'hu')] with a vendor override, would cause it not to
be listed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1418939/+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 1284017] Re: gnome-shell crashed with SIGABRT in g_thread_abort()
It's worth noting that this bug can no longer occur as it is described here -- g_mutex_lock() has been rewritten and the new version doesn't abort. That said, the underlying issue that was causing the misuse of a mutex could very well still exist... Unfortunately, it's very difficult to guess what that may be, at this point. ** Bug watch added: GNOME Bug Tracker #724929 https://bugzilla.gnome.org/show_bug.cgi?id=724929 -- 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/1284017 Title: gnome-shell crashed with SIGABRT in g_thread_abort() Status in A simple key-based configuration system: Unknown Status in d-conf package in Ubuntu: New Bug description: gnome-shell crashed on system restart. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-shell 3.10.4-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 CurrentDesktop: GNOME Date: Mon Feb 24 12:24:40 2014 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2014-02-09 (14 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: gnome-shell --mode=gdm ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so Title: gnome-shell crashed with SIGABRT in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1284017/+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 1284017] Re: gnome-shell crashed with SIGABRT in g_thread_abort()
In fact, I think this was fixed a year ago already: https://bugzilla.gnome.org/show_bug.cgi?id=724929 Did anyone see this in newer Ubuntu releases (ie: the released version of trusty or later)? -- 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/1284017 Title: gnome-shell crashed with SIGABRT in g_thread_abort() Status in A simple key-based configuration system: Unknown Status in d-conf package in Ubuntu: New Bug description: gnome-shell crashed on system restart. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gnome-shell 3.10.4-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 CurrentDesktop: GNOME Date: Mon Feb 24 12:24:40 2014 DisplayManager: gdm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2014-02-09 (14 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121.1) ProcCmdline: gnome-shell --mode=gdm ProcEnviron: SHELL=/bin/false PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so Title: gnome-shell crashed with SIGABRT in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1284017/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hello sponsors, Please consider uploading the attached nslcd patch to trusty-proposed to resolve this bug. Thank you! ** Description changed: + SRU justification: + + [Impact] + + * Summary: in Trusty, when libnss-ldapd is used, LDAP users are not able + to unlock the Unity lockscreen. Utopic and later are not affected. Some + workarounds are listed in comment #29. + + * nslcd in Trusty and earlier does not permit unprivileged users to read + shadow entries. When invoked by the Unity lockscreen, running as the + logged-in user, pam_unix returns PAM_AUTHINFO_UNAVAIL in pam_acct_mgmt + when it tries to get password expiry information from shadow. This leads + to an authorization failure, so Unity refuses to unlock the screen. + pam_ldap is not consulted for pam_acct_mgmt after pam_unix fails because + its rule is in the Additional section. + + * In Utopic and later, nslcd returns partial shadow entries to + unprivileged users. This is enough for the expiry check in pam_unix to + succeed, so the screen can be unlocked. See + http://bugs.debian.org/706913 for a discussion of the upstream fix. + + * This proposed SRU backports the upstream solution to Trusty's nslcd. + This is a change of behaviour for shadow queries from unprivileged + users, compared to the current package. An alternative, more targeted + fix would be to change Unity to ignore AUTHINFO_UNAVAIL results from + pam_acct_mgmt, like gnome-screensaver already does (see comment #29). + The nslcd change is a more general fix for not just Unity, but any PAM- + using program run by an unprivileged user. + + [Test Case] + + * Install and configure libnss-ldapd. Ensure ldap is enabled for at + least the passwd and shadow services in /etc/nsswitch.conf. + + * Log into Unity as an LDAP user, lock the screen, and then try to + unlock it again. + + [Regression Potential] + + * The patch is minimal, was written by the upstream author, and was + backported (adjusting for whitespace changes) to Trusty. The change has + already been released in Utopic and will be included in Debian Jessie as + well. + + * Regression testing should include checking that shadow queries, both + by name and for listing all users, are unchanged when issued as root. + + [Other Info] + + * Packages for testing are available in ppa:rtandy/lp1314095 + + Original description: + My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. - lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules 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://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + 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://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status lightdm: - Installed: 1.10.0-0ubuntu3 - Candidate: 1.10.0-0ubuntu3 - Version table: - *** 1.10.0-0ubuntu3 0 - 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.10.0-0ubuntu3 + Candidate: 1.10.0-0ubuntu3 + Version table: + *** 1.10.0-0ubuntu3 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status libpam-modules: - Installed: 1.1.8-1ubuntu2 - Candidate: 1.1.8-1ubuntu2 - Version table: - *** 1.1.8-1ubuntu2 0 - 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.1.8-1ubuntu2 + Candidate: 1.1.8-1ubuntu2 + Version table: + *** 1.1.8-1ubuntu2 0 + 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Hi, Grzegorz Gutowski (gzegzol) wrote on 2014-04-29: Without suid it seems that call (with correct username) to getspnam in function get_account_info in file passverify.c in pam/modules/pam_unix returns NULL. I don't understand this behaviour. I wrote a simple c program that calls getspnam and it works as expected when called from unprivileged user. A call to getspnam(3) as an unprivileged user returns NULL; that's expected. (nss_compat returns errno = EACCESS since we can't read /etc/shadow; nss_ldapd returns errno = ENOENT as a generic not found code.) The unix_chkpwd helper is sgid to shadow so that it can read /etc/shadow, but nss_ldapd still returns ENOENT to shadow queries. If we make unix_chkpwd suid, then nss_ldapd returns real shadow results; but this is only a workaround (and a potentially dangerous one, at that). What I see happening when I attempt to unlock the screen: - the auth stack is fine; - in the account stack, pam_unix returns PAM_AUTHINFO_UNAVAIL (from unix_chkpwd), and it falls into pam_deny after that (since pam_ldap is Additional). gnome-screensaver works only because it actually ignores the result from the account stack and proceeds anyway: http://bazaar.launchpad.net /~ubuntu-branches/ubuntu/trusty/gnome-screensaver/trusty/view/head:/src /gs-auth-pam.c#L519 Some possible workarounds are: - chmod u+s /sbin/unix_chkpwd (potentially dangerous, not recommended); - dpkg-reconfigure libnss-ldapd and disable the shadow service (then pam_unix doesn't try consulting it); - use libnss-ldap instead of libnss-ldapd, since it allows everyone to read shadow entries; - use libnss-sss instead of libnss-ldapd, since it does not support the shadow service at all (in trusty, at least); - make libpam-ldapd's account rule Primary instead of Additional (but this was already done and subsequently reverted by its maintainer in 0.8.8-1 and 0.8.8-2). I'm not sure why some people reported experiencing this bug when using libnss-ldap or libnss-sss. I'd want to review their PAM and NSS setups in that case. This is all about trusty so far... still have to look at utopic/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/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules 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://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated
[Dx-packages] [Bug 269904] Re: Screen refresh problems with nvidia cards
I'd been experiencing this bug for a few days now. It stared after installing the proprietary NVIDIA driver. It was SUPER annoying. But I installed compiz from trusty-proposed and it plagues me no longer! Before, this bug would show itself once every few minutes. But now, it's been about 4 hours with no sign of it! And I haven't noticed any new bugs either. Not sure what info you all need, but here's some: ryan@charles:~$ compiz --version Compiz 0.9.11.3 ryan@charles:~$ cat /proc/driver/nvidia/version NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.29 Thu Jul 31 20:23:19 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) Let me know if you need any more info. And thank you so much. -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/269904 Title: Screen refresh problems with nvidia cards Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in Compiz Core: New Status in Compiz Core 0.9.8 series: New Status in compiz package in Ubuntu: Fix Released Status in compiz-fusion-plugins-main package in Ubuntu: Fix Released Status in compiz-plugins-main package in Ubuntu: Fix Released Status in compiz source package in Precise: New Status in compiz-plugins-main source package in Precise: Confirmed Status in compiz source package in Trusty: Fix Committed Status in compiz-plugins-main source package in Trusty: Invalid Status in compiz source package in Intrepid: Fix Released Status in compiz-plugins-main source package in Intrepid: Won't Fix Status in compiz-fusion-plugins-main package in Debian: Fix Released Bug description: [Impact] Users of Nvidia gfx using the proprietary driver may see screen corruption during certain operations. [Test Case] * Install an Nvidia graphics adapter and the proprietary driver. * Observe the graphics corrupt. * Install the version of Compiz with this fix. * Observe corruption is gone. [Regression Potential] The patch for this was provided by Nvidia. There could be some corner cases users hit that may cause other issues. That said, enough testing has been done to confidently say that the gains provided by this fix far outweigh any corner cases. --- Original Description: == Proposed compiz-fusion-plugins-main patch == See comment 234 by Anders Kaseorg and attached compiz-fusion-plugins-main_0.8.2-0ubuntu2.debdiff. == Original report == Binary package hint: compiz I'm using latest compiz on intrepid. Since jockey-gtk does not work on my box (I already filed a bug), I manually installed nvidia-glx-177 and added the driver → nvidia line to xorg.conf. Now I seem to be having some screen refresh problems when using compiz: parts of the screen are refreshed, but others aren't. That means nautilus doesn't show files or folders until I move the cursor over them, firefox doesn't show webpages properly until I scroll down, and so on. Please, tell me if there is any additional info I can provide to find out the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/269904/+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 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
Ahh, right. So this is almost certainly the change that fixed it for utopic: - nslcd will now return partial shadow information to non-root users to avoid authorisation problems with setgid shadow authentication helpers with some PAM stacks (closes: #706913) I bet backporting that to trusty will resolve this. ** Also affects: nss-pam-ldapd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #706913 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706913 ** Also affects: nss-pam-ldapd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706913 Importance: Unknown Status: Unknown -- 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/1314095 Title: Unity Lockscreen in 14.04 can't unlock when using LDAP account Status in Unity: Confirmed Status in nss-pam-ldapd package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Status in nss-pam-ldapd package in Debian: Unknown Bug description: My setup is: Ubuntu 14.04 LTS, ldap accounts, krb5 authentication, Lightdm, Unity session ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent passwd and getent shadow works fine. I am able to login in console without any problems. I was able to login in lightdm. Then I used the lock screen. I could not disable the lock screen using my password. I rebooted my computer. Now: After logging in through lightdm, the unity lockscreen locks the screen immediately and I can not disable it using my password. From my short inspection of auth.log and unix_chkpwd sources it seems, that unix_chkpwd works fine when called from lightdm and fails to get user info when called from unity lockscreen. lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 apt-cache policy unity lightdm libpam-modules 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://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libpam-modules: Installed: 1.1.8-1ubuntu2 Candidate: 1.1.8-1ubuntu2 Version table: *** 1.1.8-1ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Contents of /var/log/auth.log: Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session): session closed for user lightdm Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user (user) Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user authenticated as user@NETWORK Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info (user) Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info (user) Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement user ingroup nopasswdlogin not met by user user cat /etc/pam.d/common-auth account requiredpam_unix.so authrequiredpam_group.so auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200 authrequisite pam_deny.so authrequiredpam_permit.so authoptionalpam_afs_session.so minimum_uid=200 authoptionalpam_ecryptfs.so unwrap authoptionalpam_cap.so cat /etc/pam.d/common-account account requiredpam_unix.so cat /etc/pam.d/lightdm authrequisite pam_nologin.so authsufficient pam_succeed_if.so user ingroup nopasswdlogin @include common-auth authoptionalpam_gnome_keyring.so @include common-account session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close authoptionalpam_group.so session requiredpam_limits.so @include common-session session [success=ok ignore=ignore
[Dx-packages] [Bug 1314095] Re: Unity Lockscreen in 14.04 can't unlock when using LDAP account
This seems to be fixed in later releases. Using lib{nss,pam}-ldapd and
nslcd, with no custom configuration beyond dpkg-reconfigure nslcd, I
experience this bug in trusty, but not in utopic or vivid.
Also, in trusty I do not experience it when using alternative lockers
such as gnome-screensaver or light-locker, only with the Unity
lockscreen.
Setting status back to Confirmed, and I'll try to isolate the change
that fixed it.
** Changed in: unity
Status: Incomplete = Confirmed
** Changed in: unity (Ubuntu)
Status: Incomplete = 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/1314095
Title:
Unity Lockscreen in 14.04 can't unlock when using LDAP account
Status in Unity:
Confirmed
Status in unity package in Ubuntu:
Confirmed
Bug description:
My setup is:
Ubuntu 14.04 LTS,
ldap accounts,
krb5 authentication,
Lightdm,
Unity session
ldap+krb5 is configured using nss-ldapd and nslcd. It works fine. getent
passwd and getent shadow works fine.
I am able to login in console without any problems.
I was able to login in lightdm.
Then I used the lock screen.
I could not disable the lock screen using my password.
I rebooted my computer.
Now:
After logging in through lightdm, the unity lockscreen locks the screen
immediately and I can not disable it using my password.
From my short inspection of auth.log and unix_chkpwd sources it seems,
that unix_chkpwd works fine when called from lightdm and fails to get
user info when called from unity lockscreen.
lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
apt-cache policy unity lightdm libpam-modules
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://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
lightdm:
Installed: 1.10.0-0ubuntu3
Candidate: 1.10.0-0ubuntu3
Version table:
*** 1.10.0-0ubuntu3 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
libpam-modules:
Installed: 1.1.8-1ubuntu2
Candidate: 1.1.8-1ubuntu2
Version table:
*** 1.1.8-1ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
Contents of /var/log/auth.log:
Apr 29 06:49:27 localhost lightdm: pam_succeed_if(lightdm:auth): requirement
user ingroup nopasswdlogin not met by user user
Apr 29 06:49:31 localhost lightdm: pam_unix(lightdm:auth): authentication
failure; logname= uid=0 euid=0 tty=:2 ruser= rhost= user=user
Apr 29 06:49:31 localhost lightdm: pam_krb5(lightdm:auth): user user
authenticated as user@NETWORK
Apr 29 06:49:32 localhost lightdm[15604]: pam_unix(lightdm-greeter:session):
session closed for user lightdm
Apr 29 06:49:37 localhost unix_chkpwd[15825]: check pass; user unknown
Apr 29 06:49:37 localhost unix_chkpwd[15825]: password check failed for user
(user)
Apr 29 06:49:37 localhost compiz: pam_unix(lightdm:auth): authentication
failure; logname= uid=1001 euid=1001 tty= ruser= rhost= user=user
Apr 29 06:49:37 localhost compiz: pam_krb5(lightdm:auth): user user
authenticated as user@NETWORK
Apr 29 06:49:37 localhost unix_chkpwd[15826]: could not obtain user info
(user)
Apr 29 06:49:37 localhost unix_chkpwd[15827]: could not obtain user info
(user)
Apr 29 06:49:37 localhost compiz: pam_succeed_if(lightdm:auth): requirement
user ingroup nopasswdlogin not met by user user
cat /etc/pam.d/common-auth
account requiredpam_unix.so
authrequiredpam_group.so
auth [success=2 default=ignore] pam_unix.so try_first_pass nullok_secure
auth [success=1 default=ignore] pam_krb5.so try_first_pass minimum_uid=200
authrequisite pam_deny.so
authrequiredpam_permit.so
authoptionalpam_afs_session.so minimum_uid=200
authoptionalpam_ecryptfs.so unwrap
authoptionalpam_cap.so
cat /etc/pam.d/common-account
account requiredpam_unix.so
cat /etc/pam.d/lightdm
authrequisite pam_nologin.so
authsufficient pam_succeed_if.so user ingroup nopasswdlogin
@include common-auth
authoptionalpam_gnome_keyring.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so close
authoptionalpam_group.so
session requiredpam_limits.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad]
pam_selinux.so open
session optionalpam_gnome_keyring.so auto_start
session requiredpam_env.so readenv=1
session requiredpam_env.so readenv=1 user_readenv=1
[Dx-packages] [Bug 1364070] Re: vivid, utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up
Yup. This is a GIO issue. We register a file monitor and don't bother checking if desktop files changed until we see the file monitor has fired. Due to inotify implementation issues, this usually happens about ~1s later. We will need to add a mechanism to force a reload and/or do it automatically in case we see a lookup failure. -- 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/1364070 Title: vivid, utopic and trusty unity (7.3.1+14.10.20140811-0ubuntu1) launcher addition through gsettings isn't picked up Status in The G Library - GLib: Unknown Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: As discussed on IRC, I tried to change the favorites key, and 3 trials on 10 didn't make any change in what the launcher displays. seb128 reproduced it as well. (just be aware that we just create the .desktop file just before). The exact same code seems to work 100% of the time on trusty. So, we: 1. create the desktop file 2. from gi.repository import GLib, Gio gsettings = Gio.Settings(schema_id=com.canonical.Unity.Launcher, path=/com/canonical/unity/launcher/) then, get the favorites list and add the desktop file. 3. gsettings.set_strv(favorites, new_launcher_list) - No launcher icon added from new launcher list. However, a $ gsettings get shows that desktop file (which is present. Note that changing the list and changing it back works. This was first experimented on June 2014 and reported on IRC. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1364070/+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 1405024] [NEW] Dash display corruption with nouveau on GeForce 6150SE
Public bug reported: On a system with a GeForce 6150SE integrated GPU, opening and closing the Dash a few times results in moderate or severe corruption, and eventually a complete lockup where the display is completely scrambled in a repeating pattern. When the lockup happens, the system stops responding on the network as well. In the attached dmesg, the ttm errors seem to be the relevant ones; the MMIO errors go away when booting with nouveau.config=PMPEG=0, while the corruption and lockups still happen. I'm also attaching the session log, which contains an interesting splat from nouveau. This happens to me in quantal and every subsequent release, while it does not happen in precise. Notably, precise does not show the problem even when running a more recent kernel (via HWE stacks). The nouveau splat mentioned Cannot allocate memory, so I increased the RAM allocated to the integrated GPU in the BIOS setup to the maximum of 256M (the default is 128M). That seems to have fixed the problem, even if I open a lot of windows and tabs. Running the proprietary nvidia-304 driver on the same hardware, everything works fine, regardless of the VRAM setting. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.1+15.04.20141216-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 ApportVersion: 2.15.1-0ubuntu1 Architecture: amd64 CasperVersion: 1.347 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Dec 23 00:04:39 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. Device [105b:0efb] LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141222) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business Bus 002 Device 002: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: initrd=username/vivid/desktop/amd64/casper/initrd.lz boot=casper netboot=nfs nfsroot=10.0.2.1:/var/lib/tftpboot/username/vivid/desktop/amd64 quiet splash file=/cdrom/preseed/username.seed url=http://10.0.2.64/preseed/ubiquity.cfg nouveau.config=NvMSI=0 BOOT_IMAGE=username/vivid/desktop/amd64/casper/vmlinuz.efi SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M61PMP/M61PMP-K dmi.board.vendor: FOXCONN dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnM61PMP/M61PMP-K:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.0+15.04.20141219-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Mon Dec 22 16:02:40 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Optical Mouse MOUSE, id 8 inputLogitech USB Keyboard KEYBOARD, id 9 inputLogitech USB Keyboard KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.2.901-1ubuntu3 xserver.video_driver: nouveau ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid ** Attachment added: gnome-session-Unity.log https://bugs.launchpad.net/bugs/1405024/+attachment/4286066/+files/gnome-session-Unity.log --
[Dx-packages] [Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
** Changed in: accountsservice (Ubuntu) Assignee: aminebend (alg-amine) = (unassigned) ** Changed in: accountsservice (Ubuntu Precise) Assignee: aminebend (alg-amine) = (unassigned) -- 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/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Released Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+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 1348668] Re: Unity lockscreen lets applications capture keyboard input
That affects different Google Chrome inputs. Address bar, Google search bar, Google Keep inputs and so on. It's not limited to a special extension. (I use a Zenbook Prime UX31A with Ubuntu 14.04 running.) Maybe other programs are affected too, but I don't think so. Can't reproduce it with Gedit for example. -- 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/1348668 Title: Unity lockscreen lets applications capture keyboard input Status in “unity” package in Ubuntu: New Bug description: I noticed that with the Vimium extension activated in Google Chrome, I cannot unlock Unity's lockscreen because keyboard input is hijacked by Vimium. The lockscreen really should not let this happen, and it can even be considered a potential security vulnerability as it might allow applications to capture a user's password. I have noticed this before as well when using another application, though I can't remember which one it was at the moment. The workaround is to use the mouse to choose the Switch user-option, but this is really not obvious to anyone who might encounter this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1348668/+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 1283979] Re: moving windows causes the top bar and the launcher bar to flicker
Silviu, the workaround does stop the flickering, however it introduces a different issue. After opening the unity launcher and closing it dragging any window at the top of the screen near the launcher causes bad tearing/glitching. Ubuntu/Unity 14.04 is pretty much unusable right now on a nvidia 770 and 760 as the opensource drivers do not perform well with these video cards. -- 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/1283979 Title: moving windows causes the top bar and the launcher bar to flicker Status in “unity” package in Ubuntu: Confirmed Bug description: As the title says, when I grab a window and move it around the top bar and the launcher disappear and then re-appear. Unity does not crash. During the move these elements flicker on and off. It looks more like a graphical glitch. This seems to have started after I got the packages that introduced the anti-aliased window corners. 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 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-16ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Feb 24 09:49:18 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:843b] InstallationDate: Installed on 2014-02-13 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140111) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-11-generic root=UUID=c59b4ac8-ab41-40df-aa23-ee39891ed79c ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 LE 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.:bvr1104:bd10/27/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67LE:rvrRevX.0X:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 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-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Feb 24 09:44:57 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1283979/+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 1283702] Re: Dash appears instead of Spread when Super+W is tapped faster than dash_tap_duration
Works for me as well on the current daily live image. ** Changed in: unity (Ubuntu) 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/1283702 Title: Dash appears instead of Spread when Super+W is tapped faster than dash_tap_duration Status in “unity” package in Ubuntu: Fix Released Bug description: The bug: When Super+W is pressed quickly, the Dash appears instead of the Spread. The fact that W has also been pressed is ignored. “Quickly” means the duration less than the dash_tap_duration parameter which is found in Launcher tab of the CompizConfig Settings Manager as the “Dash tap duration”. Steps to reproduce: – open CompizConfig Settings Manager – in Launcher tab, change the parameter “Dash tap duration” to some high value, say 1000 milliseconds (more is prohibited) – press Super+W within the duration not more than one second – WHAT IS EXPECTED: Spread mode should appear – WHAT HAPPENS INSTEAD: Dash appears Obviously, this bug can also be reproduced with the default value of dash_tap_duration (250ms) but with the higher value it's more evident and easier to reproduce. 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: Sun Feb 23 15:57:16 2014 InstallationDate: Installed on 2014-01-27 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ru_RU.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/unity/+bug/1283702/+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 976100] Re: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic
With the merge of lp:~robert-ancell/indicator-datetime/no-panel, released in 13.10.0+14.04.20140217-0ubuntu1, the behaviour is correct in Trusty now, so marking fixed. ** Branch unlinked: lp:~rtandy/indicator-datetime/lp976100 ** Changed in: indicator-datetime Status: In Progress = Fix Released ** Changed in: indicator-datetime (Ubuntu) Status: In Progress = Fix Released ** Changed in: indicator-datetime Assignee: Ryan Tandy (rtandy) = (unassigned) -- 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/976100 Title: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic 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 Precise: Won't Fix Bug description: STEPS TO REPRODUCE: 1) Install gnome-panel to have Ubuntu Classic 2) Login to Ubuntu Gnome Classic with Effects 3) Click on the Time Indicator 4) Select Time and Date Settings 5) System Settings is opened. We have to find date and time manually. DESIRED OUTPUT: 4) Select Time and Date Settings 5) System Settings- Date and Time should be opened. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-datetime 0.3.94-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 10:49:05 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) 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/976100/+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 976100] Re: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic
For completeness, here's a debdiff that fixes the bug in precise. Given the very small impact of this bug, though, I'd personally be inclined to wontfix the precise task sooner than go through the SRU dance... ** Patch added: indicator-datetime_0.3.94-0ubuntu2.1.debdiff https://bugs.launchpad.net/indicator-datetime/+bug/976100/+attachment/3938390/+files/indicator-datetime_0.3.94-0ubuntu2.1.debdiff ** Changed in: indicator-datetime Assignee: (unassigned) = Ryan Tandy (rtandy) ** Changed in: indicator-datetime Status: New = In Progress -- 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/976100 Title: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic Status in The Date and Time Indicator: In Progress Status in “indicator-datetime” package in Ubuntu: Triaged Status in “indicator-datetime” source package in Precise: Triaged Bug description: STEPS TO REPRODUCE: 1) Install gnome-panel to have Ubuntu Classic 2) Login to Ubuntu Gnome Classic with Effects 3) Click on the Time Indicator 4) Select Time and Date Settings 5) System Settings is opened. We have to find date and time manually. DESIRED OUTPUT: 4) Select Time and Date Settings 5) System Settings- Date and Time should be opened. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-datetime 0.3.94-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 10:49:05 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) 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/976100/+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 976100] Re: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic
** Also affects: indicator-datetime Importance: Undecided Status: New ** Branch linked: lp:~rtandy/indicator-datetime/lp976100 -- 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/976100 Title: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic Status in The Date and Time Indicator: New Status in “indicator-datetime” package in Ubuntu: Triaged Status in “indicator-datetime” source package in Precise: Triaged Bug description: STEPS TO REPRODUCE: 1) Install gnome-panel to have Ubuntu Classic 2) Login to Ubuntu Gnome Classic with Effects 3) Click on the Time Indicator 4) Select Time and Date Settings 5) System Settings is opened. We have to find date and time manually. DESIRED OUTPUT: 4) Select Time and Date Settings 5) System Settings- Date and Time should be opened. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-datetime 0.3.94-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 10:49:05 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) 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/976100/+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 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
** Changed in: accountsservice (Ubuntu) Assignee: Marcus Colla Magnus O.R. (collamagnus-or) = (unassigned) ** Changed in: accountsservice (Ubuntu Precise) Assignee: Marcus Colla Magnus O.R. (collamagnus-or) = (unassigned) -- 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/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Released Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+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
Re: [Dx-packages] [Bug 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
Hi Marcus, On Wed, Dec 18, 2013 at 12:09 PM, Marcus Colla Magnus O.R. collamagnus...@gmail.com wrote: ** Changed in: accountsservice (Ubuntu Precise) Status: Fix Committed = Fix Released I don't think this is correct. The fixed package is still in precise-proposed and hasn't been released to precise-updates yet, so the status should still be Fix Committed. The status will be changed automatically once the package migrates to precise-updates. -- 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/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Released Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+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 1131385] Re: Always on top prevents application spread from working
** Changed in: unity Assignee: Ryan Nathaniel Smith (ryan-smith) = (unassigned) -- 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/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+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 682788] Re: Improve Unity Global Menu
@Mateusz Stachowski: I am currently working on a patch to do that for unity-control-center. -- 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/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+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 682788] Re: Improve Unity Global Menu
@Aleve Sicofante: Can you explain what you mean by resist updates? I attached the patch for the newly forked unity-control-center that adds the option to enable or disable com.canonical.Unity.Panel.menubar- always-visible. ** Patch added: Add option in appearance panel to enable or disable always showing global menu bar https://bugs.launchpad.net/unity/+bug/682788/+attachment/3923354/+files/always-show-menubar.patch -- 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/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+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 682788] Re: Improve Unity Global Menu
@Aleve Sicofante: As far as I can tell, you will have to apply the patch every time. @TomasHnyk: The patch doesn't show the title for maximized windows. -- 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/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Unity: Confirmed Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: New Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+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 967879] Re: hud-service has a memory leak (I think)
** Changed in: indicator-appmenu (Ubuntu) Assignee: Ryan Lortie (desrt) = (unassigned) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-appmenu in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/967879 Title: hud-service has a memory leak (I think) Status in “indicator-appmenu” package in Ubuntu: Confirmed Bug description: After about 8 hours of use, I closed all the following programs: Pidgin Eclipse Rational Team Concert ATT's AGNclient VPN software Banshee Chrome Synaptic Gnome-Calculator Gnome-Terminal Nautilus Lotus Notes ...and noticed that hud-service is taking up 162M of RAM. It started out taking up something like 24M. Isn't that memory usage a little high? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/967879/+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 1131385] Re: Always on top prevents application spread from working
** Changed in: unity Assignee: (unassigned) = Ryan Nathaniel Smith (ryan-smith) -- 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/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: Triaged Status in “unity” package in Ubuntu: Confirmed Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+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 1131385] Re: Always on top prevents application spread from working
** Changed in: unity Status: Triaged = In Progress -- 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/1131385 Title: Always on top prevents application spread from working Status in Ayatana Design: Invalid Status in Compiz: Invalid Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Bug description: Consider you have many windows of the same type open. One method of switching between them is clicking the launcher icon which reveals the application spread. Now you can choose between the windows. This is how it should be. However, the design idea was, if the windows are marked Always on Top there is no need for an application spread, as they are always on top. This is a bug and needs to be changed, because it does not consider minimized windows and therefore prevents switching to those windows. If you have windows of the same application open, some of them minimized and ALL non-minimized windows are marked as Always on top, the application spread does not work anymore, clicking the launcher does nothing. Whether the minimized windows are marked always on top or not does not matter. So the simplest way to reproduce this bug would be: 1.) Open two windows of the same application. 2.) Minimize one and mark the other (non-minimized) as Always on top. 3.) Try to switch to the minimized window using application spread To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131385/+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 1255356] Re: gdm-session-worker crashed with SIGSEGV in malloc_consolidate()
The problem seems to go away after backporting accountsservice from quantal. ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1255356 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() Status in “accountsservice” package in Ubuntu: New Status in “gdm” package in Ubuntu: New Bug description: On an otherwise clean and up-to-date precise installation, the conditions to reproduce this gdm crash seem to be: * libnss-ldapd is installed and configured for at least passwd lookups in nsswitch. * the LDAP user being tested is not in the gdm user list. After filling in credentials and pressing Login, gdm-session-worker crashes and the login screen hangs waiting for it. For a user who is already shown in the list, whether because of being present in /etc/passwd or the wtmp history, logging in seems to work normally. I don't know whether this bug is in gdm, nss-pam-ldapd, accountsservice, or somewhere else, but gdm seems like a reasonable place to start. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Nov 26 15:46:58 2013 ExecutablePath: /usr/lib/gdm/gdm-session-worker MarkForUpload: True ProcCmdline: /usr/lib/gdm/gdm-session-worker ProcEnviron: LANG=en_CA.UTF-8 TERM=linux LANGUAGE=en_CA: PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f99dc051e08 malloc_consolidate+232: mov 0x8(%r12),%r15 PC (0x7f99dc051e08) ok source 0x8(%r12) (0x028e7388) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gdm StacktraceTop: malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4272 malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4247 _int_malloc (av=0x7f99dc38c720, bytes=1072) at malloc.c:3564 __GI___libc_malloc (bytes=1072) at malloc.c:2924 pam_modutil_getpwnam () from /lib/x86_64-linux-gnu/libpam.so.0 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1255356/+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 1255356] Re: gdm-session-worker crashed with SIGSEGV in malloc_consolidate()
Fixing the double free of user-language as per http://cgit.freedesktop.org/accountsservice/commit/?id=4399a03316bfc2b5a6f666b0606e5eece167d44a seems to be sufficient to fix this. I'll test this a few more times to convince myself of that. ** No longer affects: gdm (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/1255356 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() Status in “accountsservice” package in Ubuntu: New Bug description: On an otherwise clean and up-to-date precise installation, the conditions to reproduce this gdm crash seem to be: * libnss-ldapd is installed and configured for at least passwd lookups in nsswitch. * the LDAP user being tested is not in the gdm user list. After filling in credentials and pressing Login, gdm-session-worker crashes and the login screen hangs waiting for it. For a user who is already shown in the list, whether because of being present in /etc/passwd or the wtmp history, logging in seems to work normally. I don't know whether this bug is in gdm, nss-pam-ldapd, accountsservice, or somewhere else, but gdm seems like a reasonable place to start. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Nov 26 15:46:58 2013 ExecutablePath: /usr/lib/gdm/gdm-session-worker MarkForUpload: True ProcCmdline: /usr/lib/gdm/gdm-session-worker ProcEnviron: LANG=en_CA.UTF-8 TERM=linux LANGUAGE=en_CA: PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f99dc051e08 malloc_consolidate+232: mov 0x8(%r12),%r15 PC (0x7f99dc051e08) ok source 0x8(%r12) (0x028e7388) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gdm StacktraceTop: malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4272 malloc_consolidate (av=0x7f99dc38c720) at malloc.c:4247 _int_malloc (av=0x7f99dc38c720, bytes=1072) at malloc.c:3564 __GI___libc_malloc (bytes=1072) at malloc.c:2924 pam_modutil_getpwnam () from /lib/x86_64-linux-gnu/libpam.so.0 Title: gdm-session-worker crashed with SIGSEGV in malloc_consolidate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1255356/+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 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
I reported bug #1255356 separately and discovered the same double free as the cause. I have verified that accountsservice from precise-proposed fixes the bug reported by Wookey and fixes the bug I reported as well. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Committed Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+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 1067414] Re: gdm crashes if a user account is deleted or added (nslcd, ldap)
*** This bug is a duplicate of bug 1004515 *** https://bugs.launchpad.net/bugs/1004515 ** This bug has been marked a duplicate of bug 1004515 segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted -- 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/1067414 Title: gdm crashes if a user account is deleted or added (nslcd,ldap) Status in “accountsservice” package in Ubuntu: Confirmed Status in “gdm” package in Ubuntu: Confirmed Bug description: Scenario: * LDAP User Account (NFS Home Directory) * nslcd and gdm are used * user account information is manipulated, e.g. apt-get remove --purge tomcat7* Result: gdm session crashed Syslog: Oct 16 17:48:29 dilbert kernel: [24735.236935] gdm-session-wor[4316] general protection ip:7f28a91545a1 sp:7fff6dc110d0 error:0 in l This can be reproduced on 2 different machines and user accounts ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu14 Architecture: amd64 Date: Tue Oct 16 18:00:05 2012 SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm.Xsession: 2012-06-25T12:57:29.554078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1067414/+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 1004515] Re: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted
** Changed in: accountsservice (Ubuntu) Assignee: shan (shan40) = (unassigned) -- 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/1004515 Title: segfault in accounts-daemon when logging in / gdm crash if user account is added or deleted Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Precise: Fix Committed Bug description: [Impact] libaccountsservice contains a double free which under certain circumstances will cause accounts-daemon to segfault, and under other circumstances will cause gdm to segfault when a user account is added or removed. [Test case] In a precise machine with kerberos authentication, adding a new user via sudo adduser test will cause an X session running under GDM to crash with a segfault. Once the patch is applied, running the same command line should not affect a running X session. For the test to have value, the session needs to have been started after the new accountsservice packages were installed. [Possible regressions] This is just one line removing a double free that has been applied upstream for 16 months, so the code itself should be fine. To be certain that everything is alright, not only gdm but also lightdm should be tested. [Original description] I noticed this in my logs. It's not obviously broken anything, but segfaults are bad so I thought it worth reporting. May 25 14:16:16 e102475-lin gdm-session-worker[2198]: AccountsService-WARNING: SetLanguage call failed: not access to HOME yet so language not saved May 25 14:16:17 e102475-lin kernel: [ 6288.041531] accounts-daemon[2200]: segfault at 596fa6 ip 7f283fad1e40 sp 7fff221eb4e0 error 4 in libc-2.15.so[7f$ M --- ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 DistroRelease: Ubuntu 12.04 Package: accountsservice 0.6.15-2ubuntu9 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Tags: precise third-party-packages Uname: Linux 3.2.0-24-generic x86_64 UpgradeStatus: Upgraded to precise on 2011-11-09 (197 days ago) UserGroups: adm fuse sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1004515/+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 1246509] Re: Computer Freezes when Fullscreening Application (Snapping to Fullscreen)
** Changed in: unity (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/1246509 Title: Computer Freezes when Fullscreening Application (Snapping to Fullscreen) Status in “unity” package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 13.10, and about twice a day, when I try to full- screen an application, Unity/Ubuntu partially crashes. I am trying to full screen the application by dragging the window to the top of the screen, something I do many, many times a day. I expect for the animation to finish, and the window that I'm dragging to pop into full-screen mode, where it takes the entire window. Instead, the animation hangs half-way before I release the mouse (while I'm still dragging), and the computer partially hangs. The mouse still will move, but doesn't have any effect on the desktop. I _am_ able to Control-alt [1-6] to get into an alternative terminal, and I can execute most commands, however trying to logout of Ubuntu from the terminal or kill Unity has no effect, the graphics remain frozen on the screen. I don't know any more debugging actions to take, I'd be happy to submit more if someone had an idea of which diagnostics/logs I should run or look at. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Oct 30 17:53:41 2013 InstallationDate: Installed on 2013-05-02 (180 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-23 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1246509/+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 1246509] [NEW] Computer Freezes when Fullscreening Application (Snapping to Fullscreen)
Public bug reported: I'm running Ubuntu 13.10, and about twice a day, when I try to full- screen an application, Unity/Ubuntu partially crashes. I am trying to full screen the application by dragging the window to the top of the screen, something I do many, many times a day. I expect for the animation to finish, and the window that I'm dragging to pop into full-screen mode, where it takes the entire window. Instead, the animation hangs half-way before I release the mouse (while I'm still dragging), and the computer partially hangs. The mouse still will move, but doesn't have any effect on the desktop. I _am_ able to Control-alt [1-6] to get into an alternative terminal, and I can execute most commands, however trying to logout of Ubuntu from the terminal or kill Unity has no effect, the graphics remain frozen on the screen. I don't know any more debugging actions to take, I'd be happy to submit more if someone had an idea of which diagnostics/logs I should run or look at. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Oct 30 17:53:41 2013 InstallationDate: Installed on 2013-05-02 (180 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-23 (7 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy third-party-packages -- 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/1246509 Title: Computer Freezes when Fullscreening Application (Snapping to Fullscreen) Status in “unity” package in Ubuntu: New Bug description: I'm running Ubuntu 13.10, and about twice a day, when I try to full- screen an application, Unity/Ubuntu partially crashes. I am trying to full screen the application by dragging the window to the top of the screen, something I do many, many times a day. I expect for the animation to finish, and the window that I'm dragging to pop into full-screen mode, where it takes the entire window. Instead, the animation hangs half-way before I release the mouse (while I'm still dragging), and the computer partially hangs. The mouse still will move, but doesn't have any effect on the desktop. I _am_ able to Control-alt [1-6] to get into an alternative terminal, and I can execute most commands, however trying to logout of Ubuntu from the terminal or kill Unity has no effect, the graphics remain frozen on the screen. I don't know any more debugging actions to take, I'd be happy to submit more if someone had an idea of which diagnostics/logs I should run or look at. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Oct 30 17:53:41 2013 InstallationDate: Installed on 2013-05-02 (180 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-10-23 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1246509/+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
Re: [Dx-packages] [Bug 1072887] Re: indicator-datetime-service crashed with SIGSEGV in update_appointment_menu_items()
I'm not having this issue anymore. Sent from my iPhone On Oct 26, 2013, at 1:05 PM, Oibaf 1072...@bugs.launchpad.net wrote: Is this still an issue? ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Incomplete ** Changed in: indicator-datetime Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1072887 Title: indicator-datetime-service crashed with SIGSEGV in update_appointment_menu_items() To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1072887/+subscriptions -- 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/1072887 Title: indicator-datetime-service crashed with SIGSEGV in update_appointment_menu_items() Status in The Date and Time Indicator: Incomplete Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: erro popped up after restart after todays upgrade ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: indicator-datetime 12.10.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 Date: Mon Oct 29 14:04:14 2012 ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2012-05-16 (166 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True ProcCmdline: /usr/lib/indicator-datetime/indicator-datetime-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_US:en LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x804d966: mov(%esi),%eax PC (0x0804d966) ok source (%esi) (0x) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: indicator-datetime StacktraceTop: ?? () ?? () g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: indicator-datetime-service crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECTv() UpgradeStatus: Upgraded to quantal on 2012-10-06 (22 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1072887/+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 1167561] Re: rhythmbox indicator buttons do not work
I have upgraded to 13.10 since, where this bug does not exist any more. With rhythmbox indicator I mean the rhythmbox panel that can be accessed by pressing the sound indicator at the top right corner. -- 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/1167561 Title: rhythmbox indicator buttons do not work Status in “indicator-sound” package in Ubuntu: Incomplete Bug description: Rhythmbox indicator buttons Previous, Next and Pause/Play are not working (they cause no action). LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch:desktop-3.1-amd64:desktop-3.1-noarch:desktop-3.2-amd64:desktop-3.2-noarch:desktop-4.0-amd64:desktop-4.0-noarch:graphics-2.0-amd64:graphics-2.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch:graphics-3.1-amd64:graphics-3.1-noarch:graphics-3.2-amd64:graphics-3.2-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-3.2-amd64:printing-3.2-noarch:printing-4.0-amd64:printing-4.0-noarch:qt4-3.1-amd64:qt4-3.1-noarch rhythmbox: Installed: 2.98-0ubuntu5 Candidate: 2.98-0ubuntu5 Version table: *** 2.98-0ubuntu5 0 500 http://archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1167561/+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 1241690] [NEW] package python-appindicator 12.10.1daily13.04.15-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1234147 *** https://bugs.launchpad.net/bugs/1234147 Public bug reported: Trying to upgrade from 13.04 to 13.10. During upgrade, I couldn't go back and look at all the details in the terminal leading up to this crash... ProblemType: Package DistroRelease: Ubuntu 13.10 Package: python-appindicator 12.10.1daily13.04.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Oct 17 23:57:25 2013 DuplicateSignature: package:python-appindicator:12.10.1daily13.04.15-0ubuntu1:ErrorMessage: subprocess new pre-removal script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess new pre-removal script returned error exit status 1 MarkForUpload: True SourcePackage: libappindicator Title: package python-appindicator 12.10.1daily13.04.15-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago) ** Affects: libappindicator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of DX Packages, which is subscribed to libappindicator in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1241690 Title: package python-appindicator 12.10.1daily13.04.15-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 1 Status in “libappindicator” package in Ubuntu: New Bug description: Trying to upgrade from 13.04 to 13.10. During upgrade, I couldn't go back and look at all the details in the terminal leading up to this crash... ProblemType: Package DistroRelease: Ubuntu 13.10 Package: python-appindicator 12.10.1daily13.04.15-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Oct 17 23:57:25 2013 DuplicateSignature: package:python-appindicator:12.10.1daily13.04.15-0ubuntu1:ErrorMessage: subprocess new pre-removal script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess new pre-removal script returned error exit status 1 MarkForUpload: True SourcePackage: libappindicator Title: package python-appindicator 12.10.1daily13.04.15-0ubuntu1 failed to install/upgrade: ErrorMessage: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to saucy on 2013-10-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libappindicator/+bug/1241690/+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 976100] Re: Time and Date Settings don't load in Ubuntu Precise/Quantal/Raring with Gnome Classic
Still present in Saucy. ** Summary changed: - Time and Date Settings don't load in Ubuntu Precise/Quantal/Raring with Gnome Classic + Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic ** Tags added: 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/976100 Title: Time and Date Settings don't load in Ubuntu Precise and newer with Gnome Classic Status in “indicator-datetime” package in Ubuntu: Triaged Status in “indicator-datetime” source package in Precise: Triaged Bug description: STEPS TO REPRODUCE: 1) Install gnome-panel to have Ubuntu Classic 2) Login to Ubuntu Gnome Classic with Effects 3) Click on the Time Indicator 4) Select Time and Date Settings 5) System Settings is opened. We have to find date and time manually. DESIRED OUTPUT: 4) Select Time and Date Settings 5) System Settings- Date and Time should be opened. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: indicator-datetime 0.3.94-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sat Apr 7 10:49:05 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) 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/976100/+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 949988] Re: Unity reacts to left side touch even though set to top left corner.
** Changed in: unity-2d (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity-2d in Ubuntu. https://bugs.launchpad.net/bugs/949988 Title: Unity reacts to left side touch even though set to top left corner. Status in “unity-2d” package in Ubuntu: Fix Released Bug description: This only happens on one of the two computers I have Ubuntu on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-2d/+bug/949988/+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
