[Dx-packages] [Bug 1366277] [NEW] After restarting incorrect time is displayed
Public bug reported: Every time i shutdown my system and later i start i found that incorrect time is being displayed. so i need to change it manually. again when i shutdown and start my system same problem happens. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- 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/1366277 Title: After restarting incorrect time is displayed Status in “indicator-datetime” package in Ubuntu: New Bug description: Every time i shutdown my system and later i start i found that incorrect time is being displayed. so i need to change it manually. again when i shutdown and start my system same problem happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1366277/+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 1310316] Re: Text scaling factor changing unexpectedly
This also affects or maybe affected me. I think the problem appears because the x server does not set the right dpi value - and for some reason the text-scale factor keeps to be reseted from time to time, maybe because of an update. I manually set the correct dpi value of my screen (122dpi) in /etc/lightdm/lightdm.conf with adding this line: xserver-command=X -dpi 122 and restartet the x-server. Xorg.0.log now says: [ 3033.310] (++) intel(0): DPI set to (122, 122) - this was (96, 96) before The Text-scale factor has been set to a usable value after that. Maybe some of you can try this as well (with your individual dpi settings for your monitor) to see if this really fixes the problem. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1310316 Title: Text scaling factor changing unexpectedly Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: I have a MacBook pro with a Retina display. I have set the Scale for menu and title bars setting (into Settings Displays) to 1.5 to make the UI looks good on my screen. That works very well. But sometimes, usually after logging, all the fonts of the UI become much bigger. When that happen I open unity tweat tool and notice that the text scaling factor changed to 2.25. If I reset it to 1 the all the fonts go back to normal. The problem does not happen all the time. I would say it happen one time out of three logging. It may also happen when installing applications from the software center. I have yet to find a procedure to reproduce it all the times. 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 x86_64 NonfreeKernelModules: wl nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .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: Sun Apr 20 18:21:02 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00f2] InstallationDate: Installed on 2014-04-19 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac (20140417) MachineType: Apple Inc. MacBookPro10,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=3d5a4115-5e15-4eca-bd1c-0bee2543a1cb ro quiet splash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP101.88Z.00EE.B03.1212211437 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-C3EC7CD22292981F dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro10,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-C3EC7CD22292981F dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F: dmi.product.name: MacBookPro10,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple 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.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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: Sun Apr 20 18:04:05 2014 xserver.configfile: default
[Dx-packages] [Bug 1365875] Re: mail notification displayed even when phone locked
** Also affects: unity8 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/1365875 Title: mail notification displayed even when phone locked Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: New Bug description: I had just woken up the phone (screen was displaying the welcome greeter) but had not yet unlocked the device (I have set a pin code) when a mail notification appeared on screen that divulged the sender. This is a privacy issue. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1365875/+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 1350952] Re: [Indicators] replace the text Empty! with something more useful
** Also affects: indicator-transfer 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/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: New Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Triaged Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Triaged Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+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 978742] Re: notification-daemon crashed with signal 5 in g_return_if_fail_warning()
Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636323) has a patch available. ** Bug watch added: Debian Bug tracker #636323 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636323 ** Also affects: notification-daemon (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636323 Importance: Unknown Status: Unknown ** Tags added: patch patch-accepted-debian -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/978742 Title: notification-daemon crashed with signal 5 in g_return_if_fail_warning() Status in “notification-daemon” package in Ubuntu: Confirmed Status in “notification-daemon” package in Debian: Unknown Bug description: i get this crash when i get notified of a download with ubuntu one ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: notification-daemon 0.7.3-1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu1 Architecture: i386 Date: Wed Apr 11 11:27:07 2012 ExecutablePath: /usr/lib/notification-daemon/notification-daemon ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_get_boolean () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_return_if_fail_warning() UpgradeStatus: Upgraded to precise on 2012-03-13 (28 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/978742/+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 1341562] Re: indicator-printers not working on Ubuntu 14.04
I am affected from this bug too. Ubuntu 14.04 Kernel 3.14.0-031400 0.1.7+14.04.20140527-0ubuntu1 -- 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/1341562 Title: indicator-printers not working on Ubuntu 14.04 Status in “indicator-printers” package in Ubuntu: Confirmed Bug description: This is a regression from bug 1304434 The bug is still there for quite a lot of users including myself. Please can the Ubuntu Dev Team look into this bug again for us please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-printers/+bug/1341562/+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 978742] Re: notification-daemon crashed with signal 5 in g_return_if_fail_warning()
** Changed in: notification-daemon (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to notification-daemon in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/978742 Title: notification-daemon crashed with signal 5 in g_return_if_fail_warning() Status in “notification-daemon” package in Ubuntu: Confirmed Status in “notification-daemon” package in Debian: Fix Released Bug description: i get this crash when i get notified of a download with ubuntu one ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: notification-daemon 0.7.3-1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 ApportVersion: 2.0.1-0ubuntu1 Architecture: i386 Date: Wed Apr 11 11:27:07 2012 ExecutablePath: /usr/lib/notification-daemon/notification-daemon ProcCmdline: /usr/lib/notification-daemon/notification-daemon ProcEnviron: LANG=it_IT.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: notification-daemon StacktraceTop: g_return_if_fail_warning () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_variant_get_boolean () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () g_cclosure_marshal_VOID__VOID () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: notification-daemon crashed with signal 5 in g_return_if_fail_warning() UpgradeStatus: Upgraded to precise on 2012-03-13 (28 days ago) UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/978742/+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 1352784] [NEW] GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled.
You have been subscribed to a public bug: There is inconsistency between the bluetooth indicator and the location indication. Currently (image #171): - if location+GPS are disabled, the indicator persists. - if bluetooth is disabled, it disappaears. Which behaviour is correct? Further, even if the location indicator behaviour is correct, surely we should consider greying out the indicator so that the user can see at a glance that that indicator is disabled? ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Affects: indicator-location (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: avengers qa-daily-testing rtm14 -- GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled. https://bugs.launchpad.net/bugs/1352784 You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth 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 1352784] Re: GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled.
deleting the indicator-bluetooth line, that's already tracked in bug #1285951 ** Project changed: indicator-bluetooth = indicator-bluetooth (Ubuntu) ** No longer affects: indicator-bluetooth (Ubuntu) -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1352784 Title: GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled. Status in “indicator-location” package in Ubuntu: Confirmed Bug description: There is inconsistency between the bluetooth indicator and the location indication. Currently (image #171): - if location+GPS are disabled, the indicator persists. - if bluetooth is disabled, it disappaears. Which behaviour is correct? Further, even if the location indicator behaviour is correct, surely we should consider greying out the indicator so that the user can see at a glance that that indicator is disabled? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1352784/+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 1352784] Re: GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1352784 Title: GPS indicator does not disappear when location services disabled, but bluetooth indicator does disappear when disabled. Status in “indicator-location” package in Ubuntu: Confirmed Bug description: There is inconsistency between the bluetooth indicator and the location indication. Currently (image #171): - if location+GPS are disabled, the indicator persists. - if bluetooth is disabled, it disappaears. Which behaviour is correct? Further, even if the location indicator behaviour is correct, surely we should consider greying out the indicator so that the user can see at a glance that that indicator is disabled? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1352784/+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 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware
** Also affects: nouveau 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/1357746 Title: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware Status in Compiz: Invalid Status in Accelerated Xorg driver for nVidia cards: New Status in “unity” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Seen here with Haswell (Mobile) Logs into a session with black desktop no unity panel a non functional launcher Nothing can be done in the session except go to a tty If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then all is well compiz loads as expected ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0 Uname: Linux 3.16.0-8-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 16 12:29:42 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2014-08-16 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140813) MachineType: LENOVO 20217 ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-8-generic.efi.signed root=UUID=1696b1d2-76dc-4df4-bafc-65f8cd743e53 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 12:28:54 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 729 vendor LGD xserver.version: 2:1.15.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1357746/+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 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware
If I either blacklist nouveau or remove the xserver-xorg-video-nouveau package then everything works as expected with the current xserver-xorg-video-intel package. This also *seems* to make restarts shutdowns more reliable makes going to a tty not be liable to cause some sort of looping kernel panic (happens about 40% of the time with nouveau package installed not blacklisted So choices here on Haswell Mobile - Downgrade xserver-xorg-video-intel Blacklist nouveau Remove xserver-xorg-video-nouveau -- 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/1357746 Title: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware Status in Compiz: Invalid Status in Accelerated Xorg driver for nVidia cards: New Status in “unity” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Seen here with Haswell (Mobile) Logs into a session with black desktop no unity panel a non functional launcher Nothing can be done in the session except go to a tty If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then all is well compiz loads as expected ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0 Uname: Linux 3.16.0-8-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 16 12:29:42 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2014-08-16 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140813) MachineType: LENOVO 20217 ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR=set ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-8-generic.efi.signed root=UUID=1696b1d2-76dc-4df4-bafc-65f8cd743e53 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 12:28:54 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 729 vendor LGD xserver.version: 2:1.15.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1357746/+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 1350952] Re: [Indicators] replace the text Empty! with something more useful
Indicator messages should use something contextual such as No current messages. Providing the more specific context will make this much more obvious what this indicator is used for, especially to the first time user. -- 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/1350952 Title: [Indicators] replace the text Empty! with something more useful Status in Transfer Indicator: New Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Triaged Status in “indicator-messages” package in Ubuntu: Confirmed Status in “indicator-transfer” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: when clearing the menu on this indicator (and others), the text Empty! is displayed. Can we please remove that and put something more useful there. It looks bad. Need advise from design.. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-transfer/+bug/1350952/+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 1354400] Re: Implement Alarm Snooze functionality
** Changed in: ubuntu-clock-app Status: Triaged = In Progress -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: In Progress Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+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 990032] Re: Dual monitor sticky edges are still enabled when turned off in display manager and Launcher placement is All Displays
@johnlea: well, there is one problematic case: if the launcher is set to autohide and it's placed only on one screen, edges shouldn't be sticky. For example, i have autohidden launcher on the left edge of my laptop screen (with an external display positioned to the right of the laptop, see attached). There should be no sticky edges in this situation, but for me the edge is sticky when travelling leftwards - and it's driving me nuts!! ** Attachment added: display-conf.png https://bugs.launchpad.net/ubuntu/+source/unity/+bug/990032/+attachment/4197181/+files/display-conf.png -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/990032 Title: Dual monitor sticky edges are still enabled when turned off in display manager and Launcher placement is All Displays Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: See also: bug 987787 Release: Ubuntu 12.04 LTS Unity Version: 5.10.0-0ubuntu6 Expected: Sticky edges turns off when the switch is set to Off Actual: Sticky edges remains on regardless of switch position I've got two dual monitors running as an extended desktop. By default the Launcher placement property is set to All Displays and sticky edges is set to On. I like having the launcher on both desktops, but sticky edges is driving me nuts. So, naturally, I turned off sticky edges and left the launcher on all displays. Unfortunately, it seems that the On/Off switch for sticky edges serves no purpose when Launcher Placement is set to All Displays. The option to disable sticky edges in this scenario should be allowed, or at the very least the On/Off switch should be disabled and forced to On as to not confuse the user. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.10.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu6 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,imgpng,move,unitymtgrabhandles,snap,regex,resize,gnomecompat,animation,place,session,vpswitch,workarounds,grid,mousepoll,expo,wall,ezoom,fade,scale,unityshell] Date: Fri Apr 27 14:07:34 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/990032/+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 1354400] Re: Implement Alarm Snooze functionality
** Branch linked: lp:~nik90/ubuntu-clock-app/implement-snooze-settings -- 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/1354400 Title: Implement Alarm Snooze functionality Status in Clock application for Ubuntu devices: In Progress Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: - Background Info - Currently the snap notification shown when an alarm is triggered shows the buttons Ok and Show which both does the same thing which is to dismiss the alarm. Since Snap notifications require a minimum of 2 buttons, the only choice is to implement the Snooze functionality and replace the Show button with Snooze. However Snooze was decided to be implemented as part of the SDK Alarms API which is worked on by zsombor. As per the blueprint at [1], the snooze functionality was to be implemented in revision 0.2 (post- RTM). However we require a solution to the above issue before RTM. - Proposed Solution - It was decided after discussing with Mirco Mueller, Giorgio Venturi and Daniela Ferrai to implement the Snooze functionality as a workaround in the Indicator-datetime by dismissing the notification and showing it again after the snooze duration. The full design spec is described below. 1. Provide a settings option in dbus to set the snooze duration that the clock app can expose in the settings page to allow the user to choose the snooze duration. This is shown in [2]. The snooze duration options will be 2, 4, 5 and 10 minutes. 2. On pressing the Ok button in the snap notification, the alarm will be dismissed permanently for the day. 3. If the user pressed Snooze, then indicator-datetime should dismiss the snap notification and show it again after the snooze duration. This process will be repeated until the alarm timeout defined by the user in the clock app settings. By default that timeout is 30 minutes. This will require a Go/No-Go decision from Charles Kerr regarding the implementation in indicator-datetime since as mentioned above this will be a workaround and workaround are not permanent solutions. [1] https://blueprints.launchpad.net/ubuntu/+spec/sdk-system-alarm-api [2] https://docs.google.com/presentation/d/1JvDyhsW17d1-Mz8OY1YMBKwfRI2z9qgyRjbujEsxEMk/edit#slide=id.g18895458d_024 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1354400/+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 1365875] Re: mail notification displayed even when phone locked
** Information type changed from Public to Public Security -- 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/1365875 Title: mail notification displayed even when phone locked Status in The Unity 8 shell: New Status in “indicator-messages” package in Ubuntu: New Bug description: I had just woken up the phone (screen was displaying the welcome greeter) but had not yet unlocked the device (I have set a pin code) when a mail notification appeared on screen that divulged the sender. This is a privacy issue. To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1365875/+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 1366426] [NEW] [Super][Alt] is interpreted as [Super] if [Super] is pressed first
Public bug reported: If Super is pressed first in a SuperAltkey chord, Alt is disregarded. Steps: - go to Settings-Keyboard-Shortcuts-Launchers - set the shortcut for Launch calculator to Alt+Super+C (note, here the order in which Alt and Super are pressed does not matter) - press Alt+Super+C (in that order, Alt first). The calculator launches. - press Super+Alt+C (in that order, Super first). The dash opens with the Photos lens. Tested on two different machines (14.04) and keyboards, and with a freshly created user. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Sep 7 00:12:12 2014 InstallationDate: Installed on 2014-09-01 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1366426 Title: [Super][Alt] is interpreted as [Super] if [Super] is pressed first Status in “unity” package in Ubuntu: New Bug description: If Super is pressed first in a SuperAltkey chord, Alt is disregarded. Steps: - go to Settings-Keyboard-Shortcuts-Launchers - set the shortcut for Launch calculator to Alt+Super+C (note, here the order in which Alt and Super are pressed does not matter) - press Alt+Super+C (in that order, Alt first). The calculator launches. - press Super+Alt+C (in that order, Super first). The dash opens with the Photos lens. Tested on two different machines (14.04) and keyboards, and with a freshly created user. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Sep 7 00:12:12 2014 InstallationDate: Installed on 2014-09-01 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) 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/1366426/+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 1366277] Re: After restarting incorrect time is displayed
Please confirm that your BIOS battery is not the problem. This is a typical BIOS battery issue after power off or sometimes after reboot, the system's time may be incorrect. The EASIEST way, is to replace the CMOS battery, which is just about $2USD. If the clock problem is no longer an issue, it was not a problem with the software. To test your system to confirm a CMOS battery problem Go into BIOS and set the time (not through the operating systems). Save your BIOS settings and reboot. Allow the OS to load, then do a clean shut down. Remove power for a few minutes, then re-apply power and go into BIOS again..If the time is not correct, it is likely a battery issue. Please get bak to us so we can follow up ** Changed in: indicator-datetime (Ubuntu) Status: New = Incomplete -- 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/1366277 Title: After restarting incorrect time is displayed Status in “indicator-datetime” package in Ubuntu: Incomplete Bug description: Every time i shutdown my system and later i start i found that incorrect time is being displayed. so i need to change it manually. again when i shutdown and start my system same problem happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1366277/+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 1317391] Re: ginn error subscribing to gestures
*** This bug is a duplicate of bug 985121 *** https://bugs.launchpad.net/bugs/985121 ** This bug has been marked a duplicate of bug 985121 Ginn doesn't subscribe to gestures -- 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/1317391 Title: ginn error subscribing to gestures Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: ginn doesn't work. To solve the problem, see http://askubuntu.com/questions/57586/how-can-i-disable-arbitrary- default-multitouch-gestures-in-unity/90383#90383Answer #9 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 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu May 8 09:55:24 2014 InstallationDate: Installed on 2013-10-15 (204 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131007) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-18 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317391/+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
