[Dx-packages] [Bug 1307048] Re: calendar icon wrong colour (compared to clock) for upcoming appointments
** Changed in: unity8 (Ubuntu) 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/1307048 Title: calendar icon wrong colour (compared to clock) for upcoming appointments Status in “indicator-datetime” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: Have appointments sync via calendar, note that pulling down indicator reveals icon which is black-on-grey whereas clock items appear white-on-grey. Calendar icons are hard to see compared to clock items. See photo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1307048/+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 1170647] Re: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations
I had the problem in Ubuntu 13.04 but not anymore in Ubuntu 14.04. I believe it could related to the way how you mount it. I will check the fstab as soon as I will be back at home. -- 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/1170647 Title: Clicking on Nautilus’ launcher icon opens new window instead of restoring the minimized one when browsing external drives/locations Status in “bamf” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Sometimes left clicking the nautilus launcher icon doesn't bring up a minimized nautilus window. Instead of restoring the window a new instance of nautilus is showing up. Steps to reproduce: 1. Open a nautilus window by clicking on the launcher icon. 2. Navigate to a symlinked directory whose target is located on a different harddrive (for example: a symlink to a folder on a sd-card). 3. Minimize the nautilus window. 4. Try to bring up that window again by clicking the launcher icon. What happens: 1. A new instance (window) of nautilus is opened. 2. There's no obvious way to access the first window again. The only way is ALT+TAB. What schould happen: If a nautilus window is already open and minimized clicking the launcher icon should bring up that window. This was the behavior of nautilus windows in Ubuntu 12.10 (quantal). Ubuntu 13.04 Raring Ringtail (development branch) nautilus 3.6.3-0ubuntu16 unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6 Uname: Linux 3.8.0-18-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Fri Apr 19 11:33:13 2013 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'814x493+136+38' b'org.gnome.nautilus.window-state' b'sidebar-width' b'182' InstallationDate: Installed on 2011-07-23 (635 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to raring on 2013-04-14 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/1170647/+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 1313280] Re: Fullscreen window set to Always on Top will hide the lockscreen
I'll try get a video of the bug in action when im home. Is there any other information that could be useful to provide? -- 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/1313280 Title: Fullscreen window set to Always on Top will hide the lockscreen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: Im running on Ubuntu 14.04 and noticed this while watching a video last time. There is a really easy way to replicate this bug: * Open a video in Totem * Set Totem to Always on Top * Make Totem full screen * Manually Lock the screen using Super+L * Notice that the lockscreen is hidden by totem. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308850] Re: Dash is visible on top of the lockscreen after screen monitor auto locks
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.1 --- unity (7.2.0+14.04.20140423-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: lock screen bypass (LP: #1313885) - debian/patches/lp1313885.patch: improve lockscreen logic in lockscreen/LockScreenController.cpp, lockscreen/LockScreenShield.*, plugins/unityshell/src/unityshell.*. -- Marc Deslauriers marc.deslauri...@ubuntu.com Mon, 28 Apr 2014 22:29:13 -0400 ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1308850 Title: Dash is visible on top of the lockscreen after screen monitor auto locks Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] This is 100% reproducible on my side with an updated 14.04 I have a laptop that after 3 minutes of inactivity shutdown the screen and lock-it. If I press the SUPER button to activate the dash and then I wait 3 minutes for auto screen locking the screen become black. After that when I move the mouse to go to lockscreen and unlock my session, I see the dash on top of the lockscreen. I can digit my password and unlock the laptop pressing enter but I cannot see the username, box, dots etc I think that the screenshot attached explain very whell what I'm writing. I think that this is a security problem because as you can see from my screenshot other people can see my personal data (file and folders) without authorization. [Test Case] (1) Make sure the screen lock is enabled and has a reasonable timeout set. (2) Use the Super button to activate the Dash. (3) Wait for the screen lock timeout so the lockscreen / screensaver comes up. (4) Move the mouse or press a shift key to display the lockscreen. (5) The Dash should not appear on top of the lockscreen. [Regression Potential] None. The fix is to explicitly undisplay the dash when the screen is locked. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1308850/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1313885] Re: lock screen bypass
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.1 --- unity (7.2.0+14.04.20140423-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: lock screen bypass (LP: #1313885) - debian/patches/lp1313885.patch: improve lockscreen logic in lockscreen/LockScreenController.cpp, lockscreen/LockScreenShield.*, plugins/unityshell/src/unityshell.*. -- Marc Deslauriers marc.deslauri...@ubuntu.com Mon, 28 Apr 2014 22:29:13 -0400 ** Changed in: unity (Ubuntu Utopic) Status: In Progress = 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/1313885 Title: lock screen bypass Status in Unity: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: Fix Released Bug description: I found a bug allowing a user to bypass the new lock screen of Ubuntu 14.04 1 - When the screen is locked just right click multiple times on the indicator bar (for example on the battery indicator), then shortcuts are available. 2 - Press ALT+F2 3 - you can execute the command you whant on behalf of the logged user. Here is a video demonstrating this bug : http://www.youtube.com/watch?v=d4UUB0sI5Fc lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 Ubuntu version updated the 04/28/2014 apt-cache policy unity unity: Installed: 7.2.0+14.04.20140416-0ubuntu1 Candidate: 7.2.0+14.04.20140416-0ubuntu1 Version table: *** 7.2.0+14.04.20140416-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313885/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1291362] Re: Apps locked to launcher only launch once per session on dual monitor system.
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.1 --- unity (7.2.0+14.04.20140423-0ubuntu1.1) trusty-security; urgency=medium * SECURITY UPDATE: lock screen bypass (LP: #1313885) - debian/patches/lp1313885.patch: improve lockscreen logic in lockscreen/LockScreenController.cpp, lockscreen/LockScreenShield.*, plugins/unityshell/src/unityshell.*. -- Marc Deslauriers marc.deslauri...@ubuntu.com Mon, 28 Apr 2014 22:29:13 -0400 ** Changed in: unity (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1291362 Title: Apps locked to launcher only launch once per session on dual monitor system. Status in Unity: Fix Committed Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Bug description: [Impact] Users having the Launcher only on a monitor that is not the left-most monitor can only open the application once. This can lead to much frustration and a restart of the system in order to open the application again using the Launcher. [Test Case] * Have a multi-monitor setup. * Using System Settings, go to Displays. * Under General options, click the drop down for Launcher placement and select the right-most monitor. * Click an icon to open a application. Close that application and click the icon again. * The application should open again with this fix. [Regression Potential] None identified. Original Description: In Trusty: On a dual monitor system with the launcher on the right hand screen, an application that has been locked to launcher, (including those there by default) can only be clicked on once per session to actually launch the application. After that it's unresponsive to clicks, although right-click actions work. Seems to affect all apps, including Files. To repeat, for any application not already on the launcher bar: Launch the application using the dash. Right-click on its launcher icon and select Lock to Launcher Quit the application. Click on its launcher icon. It should launch again. Quit it again. Click on its launcher icon again. It won't work this time. It looks like dragging would work, but its operation as a launcher will not. NB: I haven't installed any hacks eg: click-to-minimise. Seen this on two systems upgraded from saucy to trusty. (One with AMD graphics, one with Intel, so I doubt that's relevant either.) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 13:10:56 2014 InstallationDate: Installed on 2014-03-08 (3 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-10 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291362/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1249663] Re: Trusty gnome flashback indicator-applet-complete disappeared completely. Nothing displays in the top right panel.
created a new panel? Would you please elaborate on how? A little searching suggested right-click on the panel and choose New but when I right-click, nothing happens. -- 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/1249663 Title: Trusty gnome flashback indicator-applet-complete disappeared completely. Nothing displays in the top right panel. Status in Indicator Applet: New Status in “indicator-applet” package in Ubuntu: Triaged Bug description: After an update the other day in Trusyt 14.04 Gnome Flashback indicator-applet-complete got an error during an update. Then all of the indicators disappeared. There is no date/time, no network indicator, etc. It's just a blank panel with nothing on it. I have to use Cairo Dock to logout, restart etc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-applet-complete 12.10.2+13.10.20130924.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.5-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 Date: Sat Nov 9 14:48:57 2013 InstallationDate: Installed on 2013-10-23 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20131021.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-applet/+bug/1249663/+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 1291383] Re: Dash/Hud stays open in front of the lockscreen
i am using unity 7.2.0, trusty x64. the above bug appears to be fixed when manually locking using CTRL+ALT+L but not when screen is set to turn-off and lock automatically after X minutes. i set my screen to turn off in 5 minutes and lock screen when that happens. then i left the dash open. on resuming the screen turns on with dash open (like above screenshot by donarsson). blindly typing in the passwd and pressing enter logs me in though. -- 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/1291383 Title: Dash/Hud stays open in front of the lockscreen Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: When you lock the screen while the dash is open, the dash stays open in front of the lockscreen. It's still possible to enter the password and unlock normally, but the dash looks like it had focus. Steps to reproduce: * Open the dash (home, run command or hud) * Lock the screen using the keyboard shortcut The result is illustrated in the attached screenshot. I think the dash should close upon locking, or remain open in the background (I can't remember how it worked with the old lockscreen, but I think it would just close). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140311-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Mar 12 14:41:23 2014 InstallationDate: Installed on 2014-02-24 (16 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140223) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1291383/+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 1314587] Re: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04
Issue still occurs when Maximus is not running. -- 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/1314587 Title: Windows slow/stall/freeze when minimizing/restoring/etc in Unity 7 14.04 Status in “unity” package in Ubuntu: New Status in “xorg” package in Ubuntu: New Bug description: Steps to reproduce: * Minimize current window or alt-tab between windows * Reveal launcher to click on application * Click `Super` to bring up Dash * Hold `Super` to bring up Keyboard Shortcuts What should happen: Action completes smoothly and quickly. What happens instead: * Action may be slow / animation jerky. * Action may stall (animation frozen on given frame, e.g. window partially minimized) - initiating another action cancels first action and second action may succeed (most often calling Guake with F12 seems to solve the issue) * Action may freeze - cursor no longer moves - a soft reboot (Alt+PrtScr+REISUB) usually works, otherwise a hard reboot Notes: * Not application specific. Minimizing is reliably slow/stalls with minimizing Firefox (including 29, I do not have a lot of bookmarks) or Pidgin, but I use those programs more often. * I am using an Nvidia Optimus machine with the default Nouveau driver - no `nvidia-prime`, no Bumblebee. I temporarily installed the latest stable Nvidia driver (including `nvidia-prime`) and it made no difference. * I did not experience this issue on the same machine running 13.10 (with Bumblebee). * I am running Maximus. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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: Wed Apr 30 12:53:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:04b6] InstallationDate: Installed on 2014-04-24 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3a8fb3f3-1054-45a0-8ec0-0cbeba33da00 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/25/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-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-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Apr 30 12:03:43 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8940 vendor AUO xserver.version: 2:1.15.1-0ubuntu2 To manage
[Dx-packages] [Bug 1246812] Re: Can open Evolution in greeter mode
This is CVE-2013-7374. ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-7374 -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Triaged Status in “indicator-datetime” source package in Trusty: Fix Released Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1314247] Re: lock screen bypass with ctrl+alt+t
Here's a quick status update: We've been testing some updates to correct this issue, and they solve the problem. While testing, the original bug reporter discovered a regression in the shut down dialogue, which we will address before releasing an update. Thank you for your patience. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: In Progress Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1246812] Re: Can open Evolution in greeter mode
This bug was fixed in the package indicator-datetime - 13.10.0+13.10.20131023.2-0ubuntu1.1 --- indicator-datetime (13.10.0+13.10.20131023.2-0ubuntu1.1) saucy-security; urgency=medium * SECURITY UPDATE: able to open evolution from greeter (LP: #1246812) - debian/patches/lp1246812.patch: don't make the date clickable when being displayed in the greeter in src/service.c. - debian/control: added breaks to ensure fixed version of ido is installed. - CVE number pending -- Marc Deslauriers marc.deslauri...@ubuntu.com Tue, 29 Apr 2014 08:32:48 -0400 ** Changed in: indicator-datetime (Ubuntu Saucy) Status: Triaged = 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/1246812 Title: Can open Evolution in greeter mode Status in The Date and Time Indicator: Fix Released Status in “indicator-datetime” package in Ubuntu: Fix Released Status in “indicator-datetime” source package in Saucy: Fix Released Status in “indicator-datetime” source package in Trusty: Fix Released Bug description: You can open evolution from the greeter. To reproduce: 1. Boot to Unity Greeter 2. Click date in the datetime indicator Expected result: Nothing happens Observed result: Evolution first run dialog opens To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1246812/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1197085] Re: Overlay scrollbars are installed in Kubuntu on Quantal upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: overlay-scrollbar (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to overlay-scrollbar in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1197085 Title: Overlay scrollbars are installed in Kubuntu on Quantal upgrade Status in “overlay-scrollbar” package in Ubuntu: Confirmed Bug description: First, let me be clear that this is not a complaint about the use or presence of overlay scrollbars. If I have inappropriately this here and it should have been filed under development discussion, please accept my apology and move it there. I am running Kubuntu, not Ubuntu, I do not have Unity installed. I opened a GTK application in KDE and my scrollbars were not the customary in-line scrollbars. Instead, they were overlay scrollbars. KDE is highly customizable, and even has mechanisms for styling GTK applications; however, there is no mechanism for switching between overlay and in-line scrollbars in KDE. This is not a deficiency in KDE because KDE is not written for scrollbars. The point is that overlay scrollbars are not a dependency and therefore should not be installed in the first place. If the overlay- scrollbars package must be installed for QT applications in non-KDE sessions, they should not affect QT applications in a KDE session. The overlay scrollbar preference should be turned off by default for sessions that are neither Gnome or Unity, or there should be a system preferences add in written for KDE. There are other system preference add ins written for KDE System Preferences. Two well-known examples are the flash control and Catalyst control. I should mention that I have Openbox installed as well, but not Gnome. The release upgrade also pulled in Cairo and Compiz, even though I don't have gnome-session or gnome-shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1197085/+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 1207985] Re: compiz assert failure: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht erfüllt.
** Changed in: xserver-xorg-video-nouveau (Ubuntu) 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/1207985 Title: compiz assert failure: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht erfüllt. Status in “unity” package in Ubuntu: Invalid Status in “xserver-xorg-video-nouveau” package in Ubuntu: Invalid Bug description: Just followed this guide: http://unity.ubuntu.com/mir/using_mir_on_pc.html. After restarting lightdm, unity won't start. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130802-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.12-0ubuntu2 Architecture: amd64 AssertionMessage: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht erfüllt. Date: Sat Aug 3 15:00:00 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-08-03 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130802) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: unity StacktraceTop: __assert_fail_base (fmt=0x7f370806fdbb Address 0x7f370806fdbb out of bounds, assertion=assertion@entry=0x7f370ec207ef mutex-__data.__owner == 0, file=file@entry=0x7f370ec20dfe pthread_mutex_lock.c, line=line@entry=65, function=function@entry=0x7f370ec208c0 __PRETTY_FUNCTION__.8369 __pthread_mutex_lock) at assert.c:92 __GI___assert_fail (assertion=0x7f370ec207ef mutex-__data.__owner == 0, file=0x7f370ec20dfe pthread_mutex_lock.c, line=65, function=0x7f370ec208c0 __PRETTY_FUNCTION__.8369 __pthread_mutex_lock) at assert.c:101 __GI___pthread_mutex_lock (mutex=0xfefefefefefefeff) at pthread_mutex_lock.c:65 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so Title: compiz assert failure: compiz: pthread_mutex_lock.c:65: __pthread_mutex_lock: Zusicherung »mutex-__data.__owner == 0« nicht erfüllt. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1207985/+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 1292623] Re: Alt-F pops up the HUD
*** This bug is a duplicate of bug 1287798 *** https://bugs.launchpad.net/bugs/1287798 ** This bug has been marked a duplicate of bug 1287798 HUD erroneously pops up when not wanted -- 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/1292623 Title: Alt-F pops up the HUD Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When releasing both Alt and F quickly, and Alt slightly before I believe, this annoying 'Pelase type your command' thing pops up. (Even though my app 'did' get a proper Alt-F and popped up its own menu) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 14 13:04:47 2014 InstallationDate: Installed on 2013-08-06 (220 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130805) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-20 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292623/+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 1293638] Re: quick alt+letter sequence interpretted as open HUD.
*** This bug is a duplicate of bug 1287798 *** https://bugs.launchpad.net/bugs/1287798 ** This bug is no longer a duplicate of bug 1292623 Alt-F pops up the HUD ** This bug has been marked a duplicate of bug 1287798 HUD erroneously pops up when not wanted -- 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/1293638 Title: quick alt+letter sequence interpretted as open HUD. Status in “unity” package in Ubuntu: New Bug description: When I press alt + a letter (or any other letter) in quick succession the HUD opens (and the key combination is sent to the focused application). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Mar 17 16:39:02 2014 InstallationDate: Installed on 2014-01-26 (49 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140124) 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/1293638/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1292217] Re: screen lock has triggered but keyboard is still connected to the main session
Yes, has just happened to me - fully updated 14.04 this morning. In my case it was an active Citrix remote session that was left capturing the keyboard when the screen locked itself- the lock screen could be clicked with the mouse, but the keyboard was typing into my Citrix session (so my password was passed into Citrix). -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292217 Title: screen lock has triggered but keyboard is still connected to the main session Status in Unity: Incomplete Status in “unity” package in Ubuntu: Incomplete Bug description: I have a laptop which has screensaved naturally due to timeout (most likely) and it is sitting there showing the lock screen but keyboard is still connected to the session, I can alt-tab to applications and via IRC i was able to send myself messages (blind) so clearly the keyboard is really operational. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 13 20:56:10 2014 EcryptfsInUse: Yes SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-01-17 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292217/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
** Changed in: unity (Ubuntu) Status: Triaged = Invalid ** Also affects: freetype (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: Confirmed Status in “freetype” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() 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/cairo/+bug/1199571/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
This crash happened with libfreetype6 2.4.12-0ubuntu1 installed. Is it still reproducible with 2.5.2-1ubuntu2, the version in Ubuntu 14.04? ** Changed in: freetype (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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: Confirmed Status in “freetype” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Invalid Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() 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/cairo/+bug/1199571/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
actually, based on the previous comment it looks lke it almost certainly would still occur with new freetype since these interfaces are not thread-safe; seems that this need to be fixed in cairo (or in compiz applying its own mutexes). -- 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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: Confirmed Status in “freetype” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Invalid Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() 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/cairo/+bug/1199571/+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 1312073] Re: /usr/bin/compiz:6:__libc_message:malloc_printerr:_int_free:_int_realloc:__GI___libc_realloc
** Changed in: unity (Ubuntu) Status: New = Invalid ** Also affects: freetype (Ubuntu) Importance: Undecided Status: New ** Also affects: cairo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1312073 Title: /usr/bin/compiz:6:__libc_message:malloc_printerr:_int_free:_int_realloc:__GI___libc_realloc Status in “cairo” package in Ubuntu: New Status in “freetype” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity. This problem was most recently seen with version 7.2.0+14.04.20140416-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/0b6f5fbea05701434a48d7685b5e7d783a8b70be contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1312073/+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 1304434] [NEW] indicator-printers not working on ubuntu 14.04 beta
You have been subscribed to a public bug: even after lates updates still no printer notifications in the panel . I checked and the package indicator-printers is correctly installed and the printer prints without problems. But, there is no notification icons on unity panel. I had no problems at all with 13.10 instead ** Affects: indicator-printers (Ubuntu) Importance: Undecided Status: Confirmed -- indicator-printers not working on ubuntu 14.04 beta https://bugs.launchpad.net/bugs/1304434 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers 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 1228593] Re: Some full screen games looks wrong on Unity
*** This bug is a duplicate of bug 1039045 *** https://bugs.launchpad.net/bugs/1039045 ** This bug has been marked a duplicate of bug 1039045 Wine windows can't go fullscreen -- 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/1228593 Title: Some full screen games looks wrong on Unity Status in Compiz: New Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: I am trying to play Age of Mythology using Wine under Unity, but when the game goes full screen the screen looks off. I'm attaching an screenshot of the issue. The game looks correct when I play it on Gnome 3 so this bug is on Unity or in Compiz. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.4-0ubuntu1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 21 10:21:56 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: virtualbox, 4.2.16, 3.11.0-7-generic, i686: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5730 / 6570M] [1002:68c0] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1594] InstallationDate: Installed on 2013-09-16 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130914) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=fc5b-0597-41b2-a6dc-228e3c320252 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.0F dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1594 dmi.board.vendor: Hewlett-Packard dmi.board.version: 91.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.0F:bd07/26/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058B20242B1020100:rvnHewlett-Packard:rn1594:rvr91.36:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 058B20242B1020100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 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.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Sep 21 08:47:36 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-0 LVDS VGA-0 xserver.version: 2:1.14.2.901-2ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1228593/+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 1304434] Re: indicator-printers not working on ubuntu 14.04 beta
Changed affected package from xorg-server to Indicator-printer... I'm no devel, but, well, sure it's not the X server. ** Package changed: xorg-server (Ubuntu) = indicator-printers (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-printers in Ubuntu. https://bugs.launchpad.net/bugs/1304434 Title: indicator-printers not working on ubuntu 14.04 beta Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: even after lates updates still no printer notifications in the panel . I checked and the package indicator-printers is correctly installed and the printer prints without problems. But, there is no notification icons on unity panel. I had no problems at all with 13.10 instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1304434/+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 1221673] Re: compiz crashed with SIGSEGV in CompAction::initiate()
** Changed in: unity Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: unity (Ubuntu) Status: Triaged = In Progress ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** 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/1221673 Title: compiz crashed with SIGSEGV in CompAction::initiate() Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: at boot ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 6 10:38:05 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-09-04 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130904) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_PT.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe02b8d169d _ZN10CompAction8initiateEv+13: mov0x8(%rdi),%rdx PC (0x7fe02b8d169d) ok source 0x8(%rdi) (0x0008) not located in a known VMA region (needed readable region)! destination %rdx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130415 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so unity::launcher::LauncherIcon::Activate(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1221673/+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 1199571] Re: compiz crashed with SIGSEGV in af_latin_hints_compute_edges()
Steve, the latest duplicate shows 2.5.2-1ubuntu2: https://bugs.launchpad.net/bugs/1304763 Is it possible to get some input from cairo maintainers? -- 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/1199571 Title: compiz crashed with SIGSEGV in af_latin_hints_compute_edges() Status in “cairo” package in Ubuntu: Confirmed Status in “freetype” package in Ubuntu: Incomplete Status in “unity” package in Ubuntu: Invalid Bug description: Fresh dist-upgrade; brought up the dash, typed term; single clicked on the terminal app and _bang_. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Tue Jul 9 17:47:10 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-06 (33 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff3b4ed7a10:mov%rdx,0x10(%rax) PC (0x7ff3b4ed7a10) ok source %rdx ok destination 0x10(%rax) (0x0010) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 FT_Load_Glyph () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGSEGV in FT_Load_Glyph() 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/cairo/+bug/1199571/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1314247] Re: lock screen bypass with ctrl+alt+t
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.2 --- unity (7.2.0+14.04.20140423-0ubuntu1.2) trusty-security; urgency=medium * SECURITY UPDATE: more lock screen bypass issues, and regression with shutdown dialog (LP: #1314247) - debian/patches/lp1314247.patch: improve popup menu handling in lockscreen/LockScreenShield.cpp, lockscreen/LockScreenPanel.cpp, services/panel-service.c, plugins/unityshell/src/unityshell.cpp, lockscreen/LockScreenController.*, shutdown/SessionController.cpp, tests/test_session_controller.cpp. -- Marc Deslauriers marc.deslauri...@ubuntu.com Wed, 30 Apr 2014 11:11:18 -0400 ** Changed in: unity (Ubuntu Trusty) Status: In Progress = 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: In Progress Status in “unity” package in Ubuntu: Confirmed Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: Confirmed Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1314247] Re: lock screen bypass with ctrl+alt+t
This bug was fixed in the package unity - 7.2.0+14.04.20140423-0ubuntu1.2 --- unity (7.2.0+14.04.20140423-0ubuntu1.2) trusty-security; urgency=medium * SECURITY UPDATE: more lock screen bypass issues, and regression with shutdown dialog (LP: #1314247) - debian/patches/lp1314247.patch: improve popup menu handling in lockscreen/LockScreenShield.cpp, lockscreen/LockScreenPanel.cpp, services/panel-service.c, plugins/unityshell/src/unityshell.cpp, lockscreen/LockScreenController.*, shutdown/SessionController.cpp, tests/test_session_controller.cpp. -- Marc Deslauriers marc.deslauri...@ubuntu.com Wed, 30 Apr 2014 11:11:18 -0400 ** Changed in: unity (Ubuntu Utopic) 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/1314247 Title: lock screen bypass with ctrl+alt+t Status in Unity: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Released Status in “unity” source package in Utopic: Fix Released Bug description: I can still bypass the logscreen by rightclicking the indicators some times and then pressing CTRL+ALT+t. I lock the screen with CTRL+ALT+L. Then i rightclick on the indicators ( volume, calendar, shutdown) a few times. I have not yet figured out if one of them is the cause... But pressing CTRL+ALT+T shortly after some of those events will open a terminal that i can type into and that will execute commands. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1314247/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1307701] Re: Unity does not get touch events when QML apps running
Any QML application at all will do (such as Item
{width:600;height:600})
What seems to be happening, from what I've learned so far:
- user touches on a qml application
- xserver sends the resulting touch events to both the qmlscene and to
compiz/unity7
- xserver offers ownership to compiz/unity7
- qmlscene does XIGrabDevice on the touch screen
- compiz/unity7 rejects the touch
- user lifts finger and touch ends
- qmlscene does XIUngrabDevice on the touch screen
- user lands a new finger, this time on the desktop
- xserver still has in its bookkeeping that the previous touch is active and
thus deny pointer emulation for that new touch
And from that point onwards xserver is left with a bogus state, even
after the qml app is closed. Restarting it being the sure way to clean
it up and reproduce the issue anew (otherwise further issues seem to
crop up)
--
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/1307701
Title:
Unity does not get touch events when QML apps running
Status in OEM Priority Project:
New
Status in OEM Priority Project trusty series:
Triaged
Status in “unity” package in Ubuntu:
In Progress
Bug description:
When running an SDK app on the desktop, it's not possible to use the
touchscreen to move windows, use the launcher, etc. The SDK app seems
to consume all touchscreen events.
To reproduce:
1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install
14.04 and check that the touchscreen works for moving windows
2) Install the camera-app package from universe (I have
2.9.1+14.04.20140331-0ubuntu1)
3) Launch the camera app
4) Touch once inside the camera-app window
5) Use the touchscreen to drag the camera-app window
Expected results:
You can move the camera-app window using the touchscreen
Actual results:
You cannot move the camera-app window, or perform any other touch tasks in
unity, with the touchscreen
This only affects touchscreen input - mouse/touchpad input is not
affected
This affects all apps written with the SDK (I tried camera-app,
gallery-app, reminders-app). It's 100% reproducible.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+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-0ubuntu2
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]
CurrentDesktop: Unity
Date: Mon Apr 14 14:59:09 2014
DistributionChannelDescriptor:
# This is a distribution channel descriptor
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-precise-amd64-20130203-1
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-12-02 (132 days ago)
InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary
20130203-13:50
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1307701/+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 1314818] Re: Tiny fonts in indicator-sound
I created a new user, and him have a same issue in indicator-sound as a main account. Conclusion: My OS: Ubuntu 14.04 with Linux 3.13 Gnome-session-flashback making something irritable with fonts size in indicator-sound, what concerns a all user on PC. Everyone. -- 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/1314818 Title: Tiny fonts in indicator-sound Status in “indicator-sound” package in Ubuntu: New Bug description: This issue happen after install and short used a gnome-flashback session. For better look what a happen please look a screen: http://i.imgur.com/Xa3GaSw.png It's annoying! And ugly. I try a guest session, which a this issue happen there. Yes. It's happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1314818/+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 1303462] Re: [Regression] Window titlebars placed behind panel
Thank You Whitaar that workaround worked like a charm and fixed all my misbehaving windows on all of my PC's. Your help is very much appreciated. Cheers Wal -- 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/1303462 Title: [Regression] Window titlebars placed behind panel Status in Compiz: Triaged Status in Unity: Invalid Status in “unity” package in Ubuntu: Triaged Bug description: Windows with a height of (Display Height - Panel Height) get placed at y=0 (behind the top panel) which means window titlebars are not reachable without alt-moving the window. I assume this happens with windows that want to resize themselves if their height exceeds the display resolution. Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop application I'm working on. TEMPORARY WORKAROUND: Use the Cntrl+SuperKey+Right or Left Arrow Key This will resize your currently focused window to occupy the Right (Left) half of the screen. The Title Bar should now be visible, so you need to drag it and resize it at your prefered position. This will save the new position in place of the previously hidden state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-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-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 6 21:45:41 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+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 1314869] [NEW] Gmail Webapp Locks System (Firefox 29)
Public bug reported: Fresh install of Ubuntu 14.04 64-bit Mac specific on a MacBook Pro 6,1. Accessed Gmail, logged-in. Let it create a webapp launcher. Closed browser, pulled updates with sudo apt-get update; sudo apt-get upgrade. Launched Firefox, now shows version 29. Run the Gmail launcher. A blank window appears (has a back/forward button at the bottom). Sometimes partially loads Gmail in the window. System locks up, keyboard doesn't respond. Requires hard power cycle to reboot. version info: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ apt-cache policy firefox firefox: Installed: 29.0+build1-0ubuntu0.14.04.2 Candidate: 29.0+build1-0ubuntu0.14.04.2 Version table: *** 29.0+build1-0ubuntu0.14.04.2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 28.0+build2-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ apt-cache policy unity-webapps-service unity-webapps-service: Installed: 2.5.0~+14.04.20140409-0ubuntu1 Candidate: 2.5.0~+14.04.20140409-0ubuntu1 Version table: *** 2.5.0~+14.04.20140409-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140409-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 20:12:52 2014 InstallationDate: Installed on 2014-04-30 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac (20140417) SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libunity-webapps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1314869 Title: Gmail Webapp Locks System (Firefox 29) Status in “libunity-webapps” package in Ubuntu: New Bug description: Fresh install of Ubuntu 14.04 64-bit Mac specific on a MacBook Pro 6,1. Accessed Gmail, logged-in. Let it create a webapp launcher. Closed browser, pulled updates with sudo apt-get update; sudo apt-get upgrade. Launched Firefox, now shows version 29. Run the Gmail launcher. A blank window appears (has a back/forward button at the bottom). Sometimes partially loads Gmail in the window. System locks up, keyboard doesn't respond. Requires hard power cycle to reboot. version info: $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy firefox firefox: Installed: 29.0+build1-0ubuntu0.14.04.2 Candidate: 29.0+build1-0ubuntu0.14.04.2 Version table: *** 29.0+build1-0ubuntu0.14.04.2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 28.0+build2-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ apt-cache policy unity-webapps-service unity-webapps-service: Installed: 2.5.0~+14.04.20140409-0ubuntu1 Candidate: 2.5.0~+14.04.20140409-0ubuntu1 Version table: *** 2.5.0~+14.04.20140409-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-webapps-service 2.5.0~+14.04.20140409-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Apr 30 20:12:52 2014 InstallationDate: Installed on 2014-04-30 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac (20140417) SourcePackage: libunity-webapps UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity-webapps/+bug/1314869/+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 1314818] Re: Tiny fonts in indicator-sound
This is intended. It was designed like this since this menu's inception (2010), and the fact that it briefly used the main font size in all of its components was a regression that got fixed recently. Read bug 1080076 (comment 5) and https://wiki.ubuntu.com/Sound#Indicator_and_menu. Also... I don't really agree it's uglier this way... ** Changed in: indicator-sound (Ubuntu) Status: New = Opinion -- 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/1314818 Title: Tiny fonts in indicator-sound Status in “indicator-sound” package in Ubuntu: Opinion Bug description: This issue happen after install and short used a gnome-flashback session. For better look what a happen please look a screen: http://i.imgur.com/Xa3GaSw.png It's annoying! And ugly. I try a guest session, which a this issue happen there. Yes. It's happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1314818/+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 1252216] Re: The dconf-editor is showing different facts in Ubuntu 13.04 and Ubuntu 13.10.
[Expired for d-conf (Ubuntu) because there has been no activity for 60 days.] ** Changed in: d-conf (Ubuntu) Status: Incomplete = Expired -- 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/1252216 Title: The dconf-editor is showing different facts in Ubuntu 13.04 and Ubuntu 13.10. Status in “d-conf” package in Ubuntu: Expired Bug description: The dconf-editor is showing different facts in Ubuntu 13.04 and Ubuntu 13.10. In Ubuntu 13.04: I have installed four keyboard layouts a) Deutsch (German) b) Avestisch (Avestan) c) AvestanTranscription d) Tamilisch (Tamil) In the dconf-editor they are showed under org gnome libgnomekbd keyboard layouts as a) 'de' b) 'ir\tave' c) 'de\tavestantranscript' d) 'in\ttam' In Ubuntu 13.10 I have installed two keyboard layouts e) Deutsch (German) f) Englisch (USA) (English (USA)) In the dconf-editor they are not showed under org gnome libgnomekbd keyboard layouts There is only one entry [] Is this a bug in Ubuntu 13.10? How may this be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1252216/+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 916879] [NEW] compiz crashed with SIGSEGV in unity::switcher::SwitcherController::CompareSwitcherItemsPriority()
You have been subscribed to a public bug: I might have been switching tabs in lyx...which is probably unrelated. Update: after more occurrences of this, it seems this is triggered by alt-tab. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: unity 4.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-15.25-generic 3.0.13 Uname: Linux 3.0.0-15-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sun Jan 15 19:35:33 2012 Disassembly: = 0x0:Cannot access memory at address 0x0 ExecutablePath: /usr/bin/compiz ProcCmdline: compiz ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () unity::switcher::SwitcherController::CompareSwitcherItemsPriority(AbstractLauncherIcon*, AbstractLauncherIcon*) () from /usr/lib/compiz/libunityshell.so void std::__insertion_sort__gnu_cxx::__normal_iteratorAbstractLauncherIcon**, std::vectorAbstractLauncherIcon*, std::allocatorAbstractLauncherIcon* , bool (*)(AbstractLauncherIcon*, AbstractLauncherIcon*)(__gnu_cxx::__normal_iteratorAbstractLauncherIcon**, std::vectorAbstractLauncherIcon*, std::allocatorAbstractLauncherIcon* , __gnu_cxx::__normal_iteratorAbstractLauncherIcon**, std::vectorAbstractLauncherIcon*, std::allocatorAbstractLauncherIcon* , bool (*)(AbstractLauncherIcon*, AbstractLauncherIcon*)) () from /usr/lib/compiz/libunityshell.so unity::switcher::SwitcherController::Show(unity::switcher::SwitcherController::ShowMode, unity::switcher::SwitcherController::SortMode, bool, std::vectorAbstractLauncherIcon*, std::allocatorAbstractLauncherIcon* ) () from /usr/lib/compiz/libunityshell.so UnityScreen::altTabInitiateCommon(CompAction*, unsigned int, std::vectorCompOption, std::allocatorCompOption ) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in unity::switcher::SwitcherController::CompareSwitcherItemsPriority() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: unity Importance: Critical Status: Fix Released ** Affects: unity-distro-priority Importance: Critical Status: Fix Released ** Affects: unity (Ubuntu) Importance: Critical Status: Fix Released ** Affects: unity (Ubuntu Oneiric) Importance: Critical Status: Confirmed ** Tags: apport-crash distro-priority i386 oneiric running-unity -- compiz crashed with SIGSEGV in unity::switcher::SwitcherController::CompareSwitcherItemsPriority() https://bugs.launchpad.net/bugs/916879 You received this bug notification because you are a member of DX Packages, which is subscribed to unity 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
