[Dx-packages] [Bug 1336657] Re: unity-panel-service crashed with SIGSEGV in strrchr()
*** This bug is a duplicate of bug 1332968 *** https://bugs.launchpad.net/bugs/1332968 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1332968, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1336657/+attachment/4143623/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1336657/+attachment/4143626/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1336657/+attachment/4143639/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1336657/+attachment/4143641/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1336657/+attachment/4143642/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1336657/+attachment/4143643/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1336657/+attachment/4143644/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1332968 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1336657 Title: unity-panel-service crashed with SIGSEGV in strrchr() Status in “unity” package in Ubuntu: New Bug description: happens ramdomly ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-services 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,imgpng,grid,snap,gnomecompat,place,move,wall,resize,regex,vpswitch,commands,unitymtgrabhandles,animation,session,expo,ezoom,workarounds,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 CurrentDesktop: Unity Date: Tue Jul 1 23:53:36 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobility Radeon HD 5650 [104d:9071] InstallationDate: Installed on 2014-06-01 (30 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140510) MachineType: Sony Corporation VPCEB2C5E ProcCmdline: /usr/lib/unity/unity-panel-service ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.15.0-6-generic root=UUID=c72ec9e3-fe9d-4672-8784-3117789d48f3 ro persistent quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f31d9e477d5 : movdqu (%rdi),%xmm0 PC (0x7f31d9e477d5) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: strrchr () at ../sysdeps/x86_64/strrchr.S:32 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: unity-panel-service crashed with SIGSEGV in strrchr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 07/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0300Y8 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0300Y8:bd07/20/2010:svnSonyCorporation:pnVPCEB2C5E:pvrC605XTV0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCEB2C5E dmi.product.version: C605XTV0 dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.1-2ubun
[Dx-packages] [Bug 1048163] Re: Cannot switch off sticky edges between displays
Bug persists in Ubuntu 12.04 64 bit 3.11.0-20-generic, gnome-control- center 3.4.2. In particular, sticky edges effect only shows up on one display edge, not on the other one. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1048163 Title: Cannot switch off sticky edges between displays Status in One Hundred Papercuts: Confirmed Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I switch Sticky edges off in Display but it persists even though the settings stays set as Off. It also makes it difficult to drag a window between monitor displays. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sun Sep 9 18:49:00 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-07-27 (43 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.14-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1048163/+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 1318997] Re: Provide a way to change alarm sound
This bug was fixed in the package indicator-datetime - 13.10.0+14.10.20140701-0ubuntu1 --- indicator-datetime (13.10.0+14.10.20140701-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Add the ability to have per-alarm custom sounds. (LP: #1318997) * Expose the new alarm settings as DBus properties. (LP: #1318997) -- Ubuntu daily releaseTue, 01 Jul 2014 09:37:06 + ** Changed in: indicator-datetime (Ubuntu) Status: New => Fix Released -- 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/1318997 Title: Provide a way to change alarm sound Status in The Date and Time Indicator: In Progress Status in Clock application for Ubuntu devices: New Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: New Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1290785] Re: Users with UID > 60000 are invisible in login and Settings->User unless /etc/login.defs updated
This seems to lead into the right direction - my user account ist classified as 'SystemAccount': root@pc220hh2:~# for i in 1000 101265 101125 101139; do gdbus call --system --dest org.freedesktop.Accounts --object-path /org/freedesktop/Accounts/User$i --method org.freedesktop.DBus.Properties.GetAll org.freedesktop.Accounts.User|sed -e 's/),/),\n/g;s/>,/>,\n/g'|grep SystemAccount; done 'SystemAccount': , 'SystemAccount': , 'SystemAccount': , 'SystemAccount': , But why? I will attach the full info for this user. ** Attachment added: "accounts-daemon info for user 101125" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+attachment/4143755/+files/accountsservice-user101125 -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290785 Title: Users with UID > 6 are invisible in login and Settings->User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Triaged Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID > 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID < UID_MIN. In 13.10 this was changed to UID < UID_MIN or UID > UID_MAX. [Test Case] 1. Create a user with a UID > UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: "big-uid" is shown in the greeter. Once logged in "big-uid" is shown in system settings. Observed result: "big-uid" is not shown in the greeter (14.04 LTS, 14.10) "big-uid" is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts > UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1290785] Re: Users with UID > 60000 are invisible in login and Settings->User unless /etc/login.defs updated
Thanks to the hint from Robert, I finally found a solution for my user to be listed again: There actually seems to be a method for setting the account type in the interface of org.freedesktop.Accounts.User, namely 'SetAccountType(in i accountType);' but I could not find a list of valid values for accountType. So I just uncached and then (re-)cached the user: gdbus call --system --dest org.freedesktop.Accounts --object-path /org/freedesktop/Accounts --method org.freedesktop.Accounts.UncacheUser euhus () gdbus call --system --dest org.freedesktop.Accounts --object-path /org/freedesktop/Accounts --method org.freedesktop.Accounts.CacheUser euhus (objectpath '/org/freedesktop/Accounts/User101125',) Now the 'SystemAccount' property is set to false and the user is shown in the login window. But I still have no idea, why this account was ever marked as system account. What stil remains to be done is release a fix for the currently stable (and even LTS-) release. P.S.: to find out about the available methods etc. I used: gdbus introspect --system --dest org.freedesktop.Accounts --object-path /org/freedesktop/Accounts --recurse | less -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290785 Title: Users with UID > 6 are invisible in login and Settings->User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Triaged Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID > 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID < UID_MIN. In 13.10 this was changed to UID < UID_MIN or UID > UID_MAX. [Test Case] 1. Create a user with a UID > UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: "big-uid" is shown in the greeter. Once logged in "big-uid" is shown in system settings. Observed result: "big-uid" is not shown in the greeter (14.04 LTS, 14.10) "big-uid" is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts > UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1336260] Re: compiz crashed with signal 5 in g_type_create_instance()
I worked around this in the following way: $ DISPLAY=:0.0 unity --replace produced http://pastebin.ubuntu.com/7736128/ Which led me to try to start bamfdaemon manually, $ /usr/lib/x86_64-linux-gnu/bamf/bamfdaemon This produced an error message saying that the shared library libgtop-2.0.so.7 could not be found. $ sudo ln -s libgtop-2.0.so.10 libgtop-2.0.so.7 Fixed the problem for me. Does the fault lie in the way bamfdaemon is built? -- 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/1336260 Title: compiz crashed with signal 5 in g_type_create_instance() Status in “unity” package in Ubuntu: New Bug description: Happened after upgrade from Trusty to Utopic. The upgrade complained about not being properly completed, but without giving me any information. What happened: Upgraded to utopic. Compiz crashes after login. It crashes even after creating a new user profile. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Jul 1 15:12:07 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/bin/compiz ExecutableTimestamp: 1402198967 InstallationDate: Installed on 2013-08-27 (308 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcCmdline: compiz ProcCwd: /home/jgdx Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /tmp/apport_sandbox_Y_mtqX/usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance (type=) at /build/buildd/glib2.0-2.41.1/./gobject/gtype.c:1866 g_object_new_internal (class=class@entry=0x27411f0, params=params@entry=0x0, n_params=n_params@entry=0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1741 g_object_newv (object_type=object_type@entry=41158480, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1885 g_object_new (object_type=41158480, first_property_name=0x0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1585 Title: compiz crashed with signal 5 in g_type_create_instance() UpgradeStatus: Upgraded to utopic on 2014-07-01 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1336260/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1290785] Re: Users with UID > 60000 are invisible in login and Settings->User unless /etc/login.defs updated
Poking around a bit further it seems like the 'SetAccountType(in i accountType);' method mentioned above can take only values of 0 and 1 (which I would rather regard as boolean, than integer) and changes only the 'AccountType' property of that user. This property seems different from the SystemAccount property. I have no idea what the AccountType means, but i noticed that it is set to 1 for my local user and to 0 for the domain/winbind users. On the other hand, there is another special boolean property called LocalAccount ... oh well, who needs docs anyway? So to me it looks like there is no way to correct the wrongly detected SystemAccount property for a user, but to Uncache and then Cache this user. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1290785 Title: Users with UID > 6 are invisible in login and Settings->User unless /etc/login.defs updated Status in “accountsservice” package in Ubuntu: Fix Released Status in “accountsservice” source package in Trusty: Triaged Bug description: [Impact] Users of Ubuntu 14.04 LTS with UID > 6 will not show in the greeter or system settings without editing UID_MAX in /etc/login.defs. This was not required in 12.04 LTS. In 12.04 LTS users were only hidden if they had UID < UID_MIN. In 13.10 this was changed to UID < UID_MIN or UID > UID_MAX. [Test Case] 1. Create a user with a UID > UID_MAX: $ adduser --uid 60001 big-uid 2. Restart system Expected result: "big-uid" is shown in the greeter. Once logged in "big-uid" is shown in system settings. Observed result: "big-uid" is not shown in the greeter (14.04 LTS, 14.10) "big-uid" is not shown in system settings (13.10, 14.04LTS, 14.10) [Regression Potential] This could cause users that were previously hidden to be shown. This seems unlikely to be a problem as all system created user accounts are less than UID_MIN and there doesn't seem be a convention to use accounts > UID_MAX for this case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1253889] Re: dash bug impossible search
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1253889 Title: dash bug impossible search Status in “unity” package in Ubuntu: Confirmed Bug description: toto@pc5:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 toto@pc5:~$ apt-cache policy unity unity: Installé : 7.1.2+14.04.20131106.1-0ubuntu1 Candidat : 7.1.2+14.04.20131106.1-0ubuntu1 Table de version : *** 7.1.2+14.04.20131106.1-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status The Search of the dash, opens and closes very quickly. impossible to do a search. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Nov 22 06:03:54 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650] [1002:9498] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e930] InstallationDate: Installed on 2013-05-24 (181 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130421) MachineType: Gigabyte Technology Co., Ltd. EP31-DS3L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic root=UUID=8bcbc64e-864b-4dce-ab1e-731c3916d0e0 ro SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FDc dmi.board.name: EP31-DS3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFDc:bd05/22/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP31-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP31-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP31-DS3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46+git20130910.58d00888-0ubuntu0sarvatt version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.99~git20130816.d0323622-0ubuntu0smartboyhw version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904+git20131009.b9ad5b62-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Nov 13 06:14:13 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1253889/+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 1336260] Re: compiz crashed with signal 5 in g_type_create_instance()
This problem is unlikely related to the way bamfdaemon is built, but could be related to the libgtop2-7 package. The bamfdaemon package was built against libgtop2-7 package version 2.28.5-2 in Ubuntu 14.04 and the binaries copied to Utopic. The version of libgtop2-7 that the Ubuntu 14.10 "Utopic Unicorn" development prerelease is shipping as of this date is 2.30.0.is.2.28.5-0ubuntu1 which contains /usr/lib/libgtop-2.0.so.7.2.0 and which satisfies the runtime bamfdaemon dependencies. I see from the attached Dependencies.txt file that you have the package libgtop2-7 2.30.0-0ubuntu1 installed on your system. I'm not sure where that package came from or if there is some convoluted history to be revealed in the Ubuntu archives (I mean, look at the package version, will ya?), but my guess is it contains libgtop-2.0.so.10.* which will not satisfy the runtime dependencies of bamfdaemon. I think the proper fix for this problem is to remove your hand-crafted symbolic link and then downgrade the version of the libgtop2-7 to the one in Utopic. Please do that and let us know how it turns out so we can further process this bug. ** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1336260 Title: compiz crashed with signal 5 in g_type_create_instance() Status in “unity” package in Ubuntu: Incomplete Bug description: Happened after upgrade from Trusty to Utopic. The upgrade complained about not being properly completed, but without giving me any information. What happened: Upgraded to utopic. Compiz crashes after login. It crashes even after creating a new user profile. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Jul 1 15:12:07 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/bin/compiz ExecutableTimestamp: 1402198967 InstallationDate: Installed on 2013-08-27 (308 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcCmdline: compiz ProcCwd: /home/jgdx Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /tmp/apport_sandbox_Y_mtqX/usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance (type=) at /build/buildd/glib2.0-2.41.1/./gobject/gtype.c:1866 g_object_new_internal (class=class@entry=0x27411f0, params=params@entry=0x0, n_params=n_params@entry=0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1741 g_object_newv (object_type=object_type@entry=41158480, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1885 g_object_new (object_type=41158480, first_property_name=0x0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1585 Title: compiz crashed with signal 5 in g_type_create_instance() UpgradeStatus: Upgraded to utopic on 2014-07-01 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1336260/+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 1253889] Re: dash bug impossible search
This could be related to #978626. This also affects the HUD. For me this bug does not appear all the time, I have not yet been able to reproduce it or find a work around other than logging out and in again. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1253889 Title: dash bug impossible search Status in “unity” package in Ubuntu: Confirmed Bug description: toto@pc5:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 toto@pc5:~$ apt-cache policy unity unity: Installé : 7.1.2+14.04.20131106.1-0ubuntu1 Candidat : 7.1.2+14.04.20131106.1-0ubuntu1 Table de version : *** 7.1.2+14.04.20131106.1-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status The Search of the dash, opens and closes very quickly. impossible to do a search. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Nov 22 06:03:54 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730 PRO [Radeon HD 4650] [1002:9498] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e930] InstallationDate: Installed on 2013-05-24 (181 days ago) InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Release amd64 (20130421) MachineType: Gigabyte Technology Co., Ltd. EP31-DS3L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic root=UUID=8bcbc64e-864b-4dce-ab1e-731c3916d0e0 ro SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FDc dmi.board.name: EP31-DS3L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFDc:bd05/22/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP31-DS3L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP31-DS3L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP31-DS3L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46+git20130910.58d00888-0ubuntu0sarvatt version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.99~git20130816.d0323622-0ubuntu0smartboyhw version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904+git20131009.b9ad5b62-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Nov 13 06:14:13 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1253889/+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 1299916] Re: Alarm Clock does not ring when phone is locked
Thanks, I guess I am on devel now. [UT 14.10 r106] The bug is still not fixed for me. Should I file a new bug? -- 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/1299916 Title: Alarm Clock does not ring when phone is locked Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: TSIA. I woke up two hours late today because my alarm clock on UT failed. I need this fixed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1299916/+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 1299916] Re: Alarm Clock does not ring when phone is locked
Are you sure? I am unable to reproduce the bug anymore. Every time I set an alarm in the morning, it rings as expected. -- 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/1299916 Title: Alarm Clock does not ring when phone is locked Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: TSIA. I woke up two hours late today because my alarm clock on UT failed. I need this fixed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1299916/+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 1331037] Re: Touchscreens: The mouse cursor disappears when touching the screen
** Changed in: oem-priority Importance: Undecided => Medium ** Changed in: unity (Ubuntu) Status: New => Confirmed ** Changed in: oem-priority Status: New => Confirmed ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Also affects: unity (Ubuntu Trusty) 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/1331037 Title: Touchscreens: The mouse cursor disappears when touching the screen Status in OEM Priority Project: Confirmed Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: New Bug description: Single touch does cursor emulation, so I would expect that when I touch the touchscreen, the cursor jumps to the touch position. Instead of doing that, the cursor disappears until I use the mouse again. Touch events work correctly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Jun 17 17:03:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-29 (48 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1331037/+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 1310518] Re: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen
** Changed in: oem-priority Status: New => Triaged -- 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/1310518 Title: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen Status in OEM Priority Project: Triaged Status in OEM Priority Project precise series: New Status in OEM Priority Project trusty series: New Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Touch screen and touchpad lost click function after quickly tapped dash home repeatly by touch screen, Installed 14.04, still have same issue. Quickly tapped dash home more than three times by touch screen.Found touch screen and touchpad lost click function. Note: 1.When this issue occured, cursor still can be moved by touch screen/touchpad. 2.When this issue occured ,click/double click by touch screen/touchpad,left click/right click by touchpad all were not workable. Steps to Reproduce: 1.install 12.04.4 image or 14.04 image, boot into Ubuntu OS. 2.Quickly tapped dash home more than three times by touch screen. 3.Found touch screen and touchpad lost click function. This bug is reported from private OEM project, also check https://launchpad.net/bugs/1297067 == using xinput --query-state can actually see the button press event ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ syntp id=6[slave pointer (2)] ⎜ ↳ ELAN Touchscreen id=11[slave pointer (2)] #xinput --query-state 11 2 classes : ButtonClass button[1]=up button[2]=up button[3]=up button[4]=up button[5]=up ValuatorClass Mode=Absolute Proximity=In valuator[0]=398 valuator[1]=1652 valuator[2]=5 valuator[3]=3 valuator[4]=0 valuator[5]=399 valuator[6]=1653 #xinput --query-state 6 2 classes : ButtonClass button[1]=down button[2]=up button[3]=up button[4]=up button[5]=up button[6]=up button[7]=up button[8]=up ValuatorClass Mode=Relative Proximity=In valuator[0]=1 valuator[1]=394 touchpad's button and touchpanel's valuator[2] and valuator[3] will changed after we press the button (or monitor) Also I found press "super" on keyboard will recover the touchscreen/touchpad loss. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.20.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-18.32~precise1-generic 3.11.10.4 Uname: Linux 3.11.0-18-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Mon Apr 21 16:50:04 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-daan2-precise-amd64-20140416-1 InstallationMedia: Ubuntu 12.04 "Precise" - Failed to find casper uuid.conf in 'binary/casper/initrd.img-3.11.0-18-generic.old-dkms' LIVE Binary 20140416-06:52 MarkForUpload: True ProcEnviron: LANGUAGE=en_US: TERM=xterm PATH=(custom, no user) 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/oem-priority/+bug/1310518/+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 1311403] Re: Can't type password after resume.
I can reproduce this reliably on my thinkpad t420. I just close the lid and when I resume I can not type into the password box. If I click on a menu item, then I can click again. This is a *major* nuisance at this point, and I'll willing to help debug just ping me on IRC. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: Incomplete => Confirmed ** Changed in: unity 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/1311403 Title: Can't type password after resume. Status in Unity: Confirmed Status in “lightdm” package in Ubuntu: New Status in “unity” package in Ubuntu: Confirmed Bug description: I couldn't type password after resume - no characters displayed this time. I had to Ctrl+alt+f2 and service lightdm restart. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 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 Date: Tue Apr 22 17:37:49 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-23 (150 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-04-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I get this issue once every couple days so if you need specific information or if you need me to perform tests, don't hesitate to contact me. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
Hello Iain, or anyone else affected, Accepted compiz into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/compiz/1:0.9.11.1+14.04.20140701-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed -- 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/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz- trusty-sru-2.debdiff * Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 1299916] Re: Alarm Clock does not ring when phone is locked
I only get very short "bursts" of the alarm sound when the screen is sleeping. It is only working after I activated the phone but then I don't need the alarm anymore. :( ** Attachment added: "A short burst of alarm sound can be heared at second 7" https://bugs.launchpad.net/ubuntu-clock-app/+bug/1299916/+attachment/4143884/+files/noAlarm.ogv -- 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/1299916 Title: Alarm Clock does not ring when phone is locked Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: TSIA. I woke up two hours late today because my alarm clock on UT failed. I need this fixed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1299916/+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 1318997] Re: Provide a way to change alarm sound
** Changed in: indicator-datetime Status: In Progress => Fix Committed -- 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/1318997 Title: Provide a way to change alarm sound Status in The Date and Time Indicator: Fix Committed Status in Clock application for Ubuntu devices: New Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: New Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+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 1336827] [NEW] New message indication says "SMS" also for MMS
Public bug reported: When receiving a multimedia message, the UI indicates it as "New SMS received from +12345678". This is misleading, it be changed to either - distinguishing MMS from SMS - or just using a neutral expression like "New message received". ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-messages in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1336827 Title: New message indication says "SMS" also for MMS Status in “indicator-messages” package in Ubuntu: New Bug description: When receiving a multimedia message, the UI indicates it as "New SMS received from +12345678". This is misleading, it be changed to either - distinguishing MMS from SMS - or just using a neutral expression like "New message received". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1336827/+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 1309063] Re: It's confusing to use the Incoming Call sound for Alarms
** Changed in: indicator-datetime Status: In Progress => Fix Released -- 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/1309063 Title: It's confusing to use the Incoming Call sound for Alarms Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: indicator-datetime is currently playing /usr/share/sounds/ubuntu/stereo/phone-incoming-call.ogg when an alarm goes off. This was chosen because it's the closest conceptual fit from the ubuntu-sounds that are available, but IMO a poor fit. Using the same sound for two unrelated events is confusing; we should have a separate, unique alarm sound. Assigning to Design for feedback. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1309063/+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 1336260] Re: compiz crashed with signal 5 in g_type_create_instance()
I did $ sudo apt-get purge libgtop2-7 Reinstall did not change anything. -- 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/1336260 Title: compiz crashed with signal 5 in g_type_create_instance() Status in “unity” package in Ubuntu: Incomplete Bug description: Happened after upgrade from Trusty to Utopic. The upgrade complained about not being properly completed, but without giving me any information. What happened: Upgraded to utopic. Compiz crashes after login. It crashes even after creating a new user profile. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Jul 1 15:12:07 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 ExecutablePath: /usr/bin/compiz ExecutableTimestamp: 1402198967 InstallationDate: Installed on 2013-08-27 (308 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20120703-15:08 ProcCmdline: compiz ProcCwd: /home/jgdx Signal: 5 SourcePackage: unity StacktraceTop: ?? () from /tmp/apport_sandbox_Y_mtqX/usr/lib/x86_64-linux-gnu/libbamf3.so.2 g_type_create_instance (type=) at /build/buildd/glib2.0-2.41.1/./gobject/gtype.c:1866 g_object_new_internal (class=class@entry=0x27411f0, params=params@entry=0x0, n_params=n_params@entry=0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1741 g_object_newv (object_type=object_type@entry=41158480, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1885 g_object_new (object_type=41158480, first_property_name=0x0) at /build/buildd/glib2.0-2.41.1/./gobject/gobject.c:1585 Title: compiz crashed with signal 5 in g_type_create_instance() UpgradeStatus: Upgraded to utopic on 2014-07-01 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1336260/+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 1296814] Re: When Unity.Session is available, use its API for logging out
** Changed in: indicator-session Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-session in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1296814 Title: When Unity.Session is available, use its API for logging out Status in The Session Menu: Fix Released Status in Unity: New Status in “indicator-session” package in Ubuntu: Fix Released Status in “unity8-desktop-session” package in Ubuntu: In Progress Bug description: The session indicator always uses gnome-session to end the session (log out), but gnome-session is not guaranteed to be available under, for example, a Unity8 desktop preview session. It should use Upstart where available. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/1296814/+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 1308037] Re: No results from application scope
** Also affects: unity-lens-applications Importance: Undecided Status: New ** Changed in: unity-lens-applications 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/1308037 Title: No results from application scope Status in LibUnity: Confirmed Status in Unity Applications Lens: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Unity is in a state where I don't get any results from the applications lens. This sometimes happens for one search but either re-entering the search or toggling the lens has always fixed it in the past for me. This time neither of these steps work. I'm attaching a bustle log of the problem in case that's helpful. I searched for "spotify", which I've got installed, and got 0 results. The only way to fix the issue is to log out and back in. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 15 13:29:40 2014 InstallationDate: Installed on 2012-10-07 (554 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (343 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1308037/+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 1299916] Re: Alarm Clock does not ring when phone is locked
I did a factory reset and it works now. (There was still a lot of clutter from the 13.10 install) -- 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/1299916 Title: Alarm Clock does not ring when phone is locked Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: TSIA. I woke up two hours late today because my alarm clock on UT failed. I need this fixed To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1299916/+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 1305586] Re: Lock screen is unusable when some windows have a keyboard/mouse grab
** 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 unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1305586 Title: Lock screen is unusable when some windows have a keyboard/mouse grab Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Confirmed Bug description: [Impact] Some windows will grab the keyboard/mouse and when the lockscreen kicks in, this window will still have the grab and thusly, ou can enter your password in the lockscreen. [Test case] 1. Open a window that will hold the grab, such as the ssh password dialog. 2. Wait for the lock screen to activate. 3. Enter your password to unlock the screen. [Regression potential] This particular fix doesn't fix all cases, but does fix it for some. That said, no new regressions are expected. * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz- trusty-sru-2.debdiff * Original Description: My screen just timed out and locked when a password prompt which had a grab was displaying. I couldn't type my password or interact with the indicators. gnome-screensaver just refuses to lock in this situation, perhaps unity could do the same unless it's possible to remove and readd the grabs yourself, but I don't think XLib lets you do that (you can only remove your own grabs AFAIK). TEMPORARY WORKAROUND TO LOGIN AGAIN: Click on the guest session Once the guest session is started log out This takes you back to the lightdm session screen you can then login to your user session and it be in the same state ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140409-0ubuntu1 [origin: unknown] ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CrashDB: unity CurrentDesktop: Unity Date: Thu Apr 10 09:39:45 2014 InstallationDate: Installed on 2012-10-07 (549 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-05-07 (338 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1305586/+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 1334809] Re: Sound indicator controller is buggy, if you are dragging it using mouse
*** This bug is a duplicate of bug 1284325 *** https://bugs.launchpad.net/bugs/1284325 ** Project changed: unity => ido (Ubuntu) ** This bug has been marked a duplicate of bug 1284325 Volume slider don't follow pointer position -- You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1334809 Title: Sound indicator controller is buggy, if you are dragging it using mouse Status in “ido” package in Ubuntu: New Bug description: Video demo http://youtu.be/m3jeok2aOP4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ido/+bug/1334809/+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 1334809] [NEW] Sound indicator controller is buggy, if you are dragging it using mouse
You have been subscribed to a public bug: Video demo http://youtu.be/m3jeok2aOP4 ** Affects: ido (Ubuntu) Importance: Undecided Status: New -- Sound indicator controller is buggy, if you are dragging it using mouse https://bugs.launchpad.net/bugs/1334809 You received this bug notification because you are a member of DX Packages, which is subscribed to ido in Ubuntu. -- 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 1320556] Re: "Show copy dialog" right click launcher entry doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1320556 Title: "Show copy dialog" right click launcher entry doesn't work Status in “unity” package in Ubuntu: Confirmed Bug description: I noticed that right-clicking on the and clicking "show copy dialogue" doesn't work (again) with 14.04. Seems to be a regression bug of #887821 my nautilus version is: GNOME nautilus 3.10.1 unity version: unity 7.2.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat May 17 23:48:56 2014 InstallationDate: Installed on 2014-05-03 (14 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) 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/1320556/+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 1313597] Re: Shortcut overlay cannot be closed by clicking the close button in 14.04
I agree with Ro's comment above. The priority should be raised. This bug is the VERY FIRST thing you see when installing Ubuntu 14.04 LTS. -- 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/1313597 Title: Shortcut overlay cannot be closed by clicking the close button in 14.04 Status in Unity: In Progress Status in Unity 7.2 series: Confirmed Status in “unity” package in Ubuntu: In Progress Bug description: In 14.04, the shortcut overlay would pop-out automatically on first boot. Although there is a close button on the top-left corner, it cannot be closed by clicking it. (it could be dismissed by the super key, or open a new window) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313597/+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
