[Dx-packages] [Bug 1312010] Re: slow performance with NVidia 6150SE and nvidia-304
@mruk69: Unity doesn't crash... It's just too slow. I'm using GNOME fallback session though it's just inconvenient. I tested nvidia-173 and mainline kernel and had no success. -- 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/1312010 Title: slow performance with NVidia 6150SE and nvidia-304 Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Everything is too slow. I able to launch terminal and select Metacity. Now I'm using Xubuntu-desktop to report this issue. 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: 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 304.117 Tue Nov 26 21:25:36 PST 2013 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: None Date: Thu Apr 24 06:36:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.117, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8234] Lsusb: Bus 001 Device 003: ID 1058:074a Western Digital Technologies, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic root=UUID=da84c996-f7d0-4fe8-8822-407e4f6c5c22 ro quiet splash nomdmonddf nomdmonisw SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/26/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N-MX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd03/26/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MX:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11+14.04.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: Thu Apr 24 04:16:54 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1312010/+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 1276177] Re: Applications using client-side decorations are not resizable in Unity
It seems to me that these CSD apps aren't resizable anywhere except for Gnome Shell. ** Bug watch added: Debian Bug tracker #744249 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744249 ** Also affects: gtk+3.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=744249 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1276177 Title: Applications using client-side decorations are not resizable in Unity Status in Themes for Ubuntu: In Progress Status in Unity: In Progress Status in “unity” package in Ubuntu: Triaged Status in “gtk+3.0” package in Debian: Unknown Bug description: GNOME applications that use client-side decorations can't be resized on Unity. I think it's because the frame extents hint is not supported. gnome-clocks and gnome-tweak-tool are two apps in the archive that have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1276177/+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 1276177] Re: Applications using client-side decorations are not resizable in Unity
** Changed in: gtk+3.0 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1276177 Title: Applications using client-side decorations are not resizable in Unity Status in Themes for Ubuntu: In Progress Status in Unity: In Progress Status in “unity” package in Ubuntu: Triaged Status in “gtk+3.0” package in Debian: Confirmed Bug description: GNOME applications that use client-side decorations can't be resized on Unity. I think it's because the frame extents hint is not supported. gnome-clocks and gnome-tweak-tool are two apps in the archive that have this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1276177/+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 1318321] Re: "the cache has no package" error when wine (-compholio) update is available
** Also affects: indicator-applet (Ubuntu) Importance: Undecided Status: New -- 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/1318321 Title: "the cache has no package" error when wine (-compholio) update is available Status in Pipelight: New Status in Wine "Compholio" Edition: Triaged Status in “indicator-applet” package in Ubuntu: New Status in “wine” package in Ubuntu: Confirmed Bug description: (Note: This also affects the regular Wine package, see below) Hello, On Ubuntu 14.04 x64, each time there is an update for wine-compholio available, but not installed yet, update-manager has the following error in system indicator : class 'KeyError' The cache has no package named wine-compholio-i386 Installing the updates removes the error message. I attach a screenshot of the whole message. To manage notifications about this bug go to: https://bugs.launchpad.net/pipelight/+bug/1318321/+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 1238410] Re: Inconsistent cursor visibility with cursor plugin enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1238410 Title: Inconsistent cursor visibility with cursor plugin enabled Status in GNOME Desktop Common Files: Fix Released Status in Gnome Settings Daemon: New Status in Unity: New Status in X.Org X server: In Progress Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: Confirmed Status in “unity” source package in Saucy: Invalid Status in “xorg-server” source package in Saucy: Fix Released Bug description: On fresh boots the greeter & desktop may have the cursor visible or may not until mouse is moved. On a log out/in the cursor is almost always invisible until mouse is moved. (unless made visible in greeter screen, then visible on Desktop This is all well & good, maybe some intentional aesthetics/design (https://bugzilla.gnome.org/show_bug.cgi?id=687791) , however sometimes the cursor never becomes visible. In that case hitting some keys or context menu can cause it to show, though most times a log out is needed. (with the removal of ctrl+alt+delete > log out this means most users will need to either blindly find the session indicator or hit power button. When the g-s-d cursor plugin is disabled then the cursor is always visible, it the plugin has no use in an ubuntu session then maybe it should be default disabled There is also the possibility, particularly on ssd drives, of a login with no session indicator. This occasionally combines with no visible cursor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 11 00:38:16 2013 InstallationDate: Installed on 2013-10-03 (8 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131002) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1238410/+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 1377709] [NEW] menu icons can't be disabled
Public bug reported: With appmenu-qt5 icons in menu are always displayed, despite the application setting setAttribute(Qt::AA_DontShowIconsInMenus) or explicitly disabling menu icons for particular actions with iconVisibleInMenu = false Description:Ubuntu 14.04.1 LTS Release:14.04 appmenu-qt5: Installed: 0.3.0+14.04.20140415-0ubuntu1 Candidate: 0.3.0+14.04.20140415-0ubuntu1 Version table: *** 0.3.0+14.04.20140415-0ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: appmenu-qt5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to appmenu-qt5 in Ubuntu. https://bugs.launchpad.net/bugs/1377709 Title: menu icons can't be disabled Status in “appmenu-qt5” package in Ubuntu: New Bug description: With appmenu-qt5 icons in menu are always displayed, despite the application setting setAttribute(Qt::AA_DontShowIconsInMenus) or explicitly disabling menu icons for particular actions with iconVisibleInMenu = false Description: Ubuntu 14.04.1 LTS Release: 14.04 appmenu-qt5: Installed: 0.3.0+14.04.20140415-0ubuntu1 Candidate: 0.3.0+14.04.20140415-0ubuntu1 Version table: *** 0.3.0+14.04.20140415-0ubuntu1 0 500 http://pl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1377709/+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 1292391] Re: lockscreen - wallpaper is not properly resized when unplugging monitors
I just checked on the affected setup and the proposed SRU fixes the bug. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1292391 Title: lockscreen - wallpaper is not properly resized when unplugging monitors Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: Fix Committed Bug description: [Impact] Wallpapers have an invalid aspect ratio in the lockscreen, when attaching/detaching monitors, while the screen is locked I attached photos taken of the same screen with and without aritfacts (same size, though the dots have different spacing). Wallpaper used is from the current default selection. [Test case] - Have 2 monitors/displays with different resolutions setup on your trusty installation. (In my case: Primary 1600x900 laptop screen and secondary 1920x1080 external monitor.) - Lock the screen via shortcut. - Remove one monitor. (In my case: Remove the external one.) - Result: The display setup change is detected and the wallpaper on the remaining screen is properly resized to respect the new aspect ratio. [Regression potential] None To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292391/+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 1201180] Re: powerbtn.sh conflicts with logind
https://bugs.launchpad.net/ubuntu/+source/xfce4-power- manager/+bug/1319134 seems to be related with this bug. -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1201180 Title: powerbtn.sh conflicts with logind Status in “acpid” package in Ubuntu: Fix Released Status in “gnome-session” package in Ubuntu: Fix Released Status in “kde-workspace” package in Ubuntu: Triaged Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Invalid Bug description: In saucy the PC powers down as soon as I press the power button, it seems that systemd is calling "poweroff", but I'm not sure if it's doing that in response of some other event (i.e. as callback of a dbus call): root 4998 0.0 0.0 177932 2104 ?Sl 20:41 0:00 /usr/lib/x86_64-linux-gnu/systemd-shim root 5012 0.0 0.0 4440 624 ?S20:41 0:00 \_ sh -c /sbin/poweroff root 5013 0.0 0.0 4440 628 ?S20:41 0:00 \_ /bin/sh /sbin/shutdown -h -P now In any case the caller or systemd itself should be aware that there's a session-manager running and that it shouldn't actually directly power off the system then. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1201180/+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 1377537] Re: Screen does not lock or turn off automatically
same here, screen never shuts off no matter what i set it to in "brightness and lock". daily fresh installed about a week ago. 64bit ubuntu with nvidia graphics. -- 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/1377537 Title: Screen does not lock or turn off automatically Status in “unity” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10 (upgraded from 14.04), the screen does not lock or turn off after the designated time in System Settings / Brightness and Lock. The screen lock can still be activated manually from the System menu or keyboard shortcut (although I notice that the default has changed from CTRL-ALT-DEL to Super-L, and if I change this back in the System Settings / Keyboard / Shortcuts, both combinations work - it seems that the unity plugin in compiz (CCSM / unity / general) has aother screen lock key short cut). Other users are reporting the same issue: see http://ubuntuforums.org/showthread.php?t=2246601&highlight=turn. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 Uname: Linux 3.17.0-rc7-git-20140929.1829 x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 5 08:07:30 2014 InstallationDate: Installed on 2014-02-08 (238 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140207) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377537/+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 1372061] Re: SMS notification: time format not translatable
** Changed in: telephony-service (Ubuntu) Importance: Undecided => High ** Changed in: telephony-service (Ubuntu) Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) ** Tags added: rtm14 touch-2014-10-23 -- 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/1372061 Title: SMS notification: time format not translatable Status in Ubuntu Translations: Triaged Status in “indicator-messages” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: New Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to "hh:mm - mm, d". This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be "d mm". The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1372061/+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 1352604] Re: clear option is painful to use if you get a lot of notifications
** Also affects: ubuntu-ux 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/1352604 Title: clear option is painful to use if you get a lot of notifications Status in Ubuntu UX bugs: New Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: This bug is exacerbated by bug 1352602 To reproduce:- 1. In ubuntu system settings -> accounts, add a google or twitter account 2. Once created, enable the "Notifications" option in the account 3. Wait (also rebooting the phone can trigger this) 4. Tweets / email notifications are shown as notifications Expected behaviour * Pull down the messaging indicator and find lots of notifications to clear * Find a button easily to clear the notifications Actual behaviour * Pull down the messaging indicator and find lots of notifications to clear * Have to scroll many many times to get to the bottom of a gigantic list of notifications before finding the [Clear all] button. In my opinion "clear" should be easier to find and hit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1352604/+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 1367920] Re: dialer not brought to foreground when launched from messaging-menu
** Changed in: indicator-messages (Ubuntu) Importance: High => Critical ** Changed in: unity8 (Ubuntu) Importance: High => Critical ** No longer affects: dialer-app -- 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/1367920 Title: dialer not brought to foreground when launched from messaging-menu Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: How to reproduce === 1 - Make sure that you have a missing call/voice mail message on messaging menu 2 - Open dialer app 3 - Open the messaging menu 4 - Click to expand the message 5 - Click on the phone app icon in the top right Expected The messaging menu disappear and the dialer app appears Current == The message is removed but the messaging menu still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367920/+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 1369737] Re: Send button does not enable until you press spacebar
** Changed in: indicator-messages (Ubuntu) Importance: High => Critical -- 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/1369737 Title: Send button does not enable until you press spacebar Status in “indicator-messages” package in Ubuntu: Confirmed Bug description: krillin build 40, rtm image - make sure word prediction/preditive text is turned on (this is now the default) - receive a text message on your phone - pull down messaging indicator - click on the message - type "Hello" in the entry field Expected result: - the send button should become active as soon as you start typing Actual result: - send button stays disabled until you press the spacebar The send button should not wait until the word is committed before becoming active, but instead should listen for any change and enable the button accordingly. The messaging app does this correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1369737/+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 1377537] Re: Screen does not lock or turn off automatically
Can confirm, fresh install here, not upgrade - same issue. Same issue with default mesa and mesa git from Oibaf PPA, so it's not that I suppose (I'm on AMD). -- 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/1377537 Title: Screen does not lock or turn off automatically Status in “unity” package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10 (upgraded from 14.04), the screen does not lock or turn off after the designated time in System Settings / Brightness and Lock. The screen lock can still be activated manually from the System menu or keyboard shortcut (although I notice that the default has changed from CTRL-ALT-DEL to Super-L, and if I change this back in the System Settings / Keyboard / Shortcuts, both combinations work - it seems that the unity plugin in compiz (CCSM / unity / general) has aother screen lock key short cut). Other users are reporting the same issue: see http://ubuntuforums.org/showthread.php?t=2246601&highlight=turn. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu2 Uname: Linux 3.17.0-rc7-git-20140929.1829 x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Oct 5 08:07:30 2014 InstallationDate: Installed on 2014-02-08 (238 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140207) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1377537/+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 1367920] Re: dialer not brought to foreground when launched from messaging-menu
@Josh - please try the latest image, this might have been fixed with Nick's indicator branch ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Gerry Boland (gerboland) ** Changed in: unity8 (Ubuntu) Assignee: Gerry Boland (gerboland) => Josh Arenson (josharenson) ** Tags added: touch-2014-10-30 -- 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/1367920 Title: dialer not brought to foreground when launched from messaging-menu Status in “indicator-messages” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: How to reproduce === 1 - Make sure that you have a missing call/voice mail message on messaging menu 2 - Open dialer app 3 - Open the messaging menu 4 - Click to expand the message 5 - Click on the phone app icon in the top right Expected The messaging menu disappear and the dialer app appears Current == The message is removed but the messaging menu still visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1367920/+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 1240595] Re: [regression] Unity Launcher & Panel is gone after leaving full screen unredirected windows
** Also affects: mypaint 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/1240595 Title: [regression] Unity Launcher & Panel is gone after leaving full screen unredirected windows Status in MyPaint: New Status in Unity: Fix Released Status in Unity 7.1 series: Fix Committed Status in “evince” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Status in “evince” source package in Saucy: Invalid Status in “unity” source package in Saucy: Invalid Bug description: Unity launcher is gone after fullscreen windows are minimized! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2 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 Date: Wed Oct 16 19:11:56 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed virtualbox, 4.2.16, 3.11.0-12-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5011] MachineType: LENOVO 37612ZG MarkForUpload: True ProcEnviron: LANGUAGE=lv PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lv_LV.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=65f7e510-9ce8-4bf6-9fb0-9e6d8c6b4714 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H9ET63WW (0.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 37612ZG dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH9ET63WW(0.63):bd09/05/2012:svnLENOVO:pn37612ZG:pvrLenovoB590:rvnLENOVO:rn37612ZG:rvrWin8STDMMDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 37612ZG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 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-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Oct 16 18:19:24 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8684 vendor AUO xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/mypaint/+bug/1240595/+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 1353989] Comment bridged from LTC Bugzilla
*** This bug is a duplicate of bug 1355966 *** https://bugs.launchpad.net/bugs/1355966 --- Comment From vaish...@in.ibm.com 2014-10-06 05:26 EDT--- Any updates on the issue ? -- You received this bug notification because you are a member of DX Packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1353989 Title: Errors on cleaning up cgroups Status in “systemd-shim” package in Ubuntu: Triaged Status in “systemd-shim” package in Debian: New Bug description: Problem Description -- Lot of systemd failure messages pops up on console as well as seen in dmesg ---uname output--- Linux u10vm14 3.16.0-6-generic #11-Ubuntu SMP Mon Jul 28 02:00:45 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Power 8 ---Debugger--- A debugger is not configured Steps to Reproduce -- 1) Install Ubuntu 14.10 August 6th build 2) After the installation while logging in seen multiple systemd failed messages on console and on dmesg Failed messages: [ 58.564179] systemd-logind[1420]: Failed to enable subscription: No such method 'Subscribe' [ 58.576888] systemd-logind[1420]: New seat seat0. [ 58.580312] systemd-logind[1420]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 58.581059] systemd-logind[1420]: Failed to start user service: Unknown unit: user@1000.service [ 58.584561] systemd-logind[1420]: New session c1 of user ubuntu. [11293.015056] init: hvc0 main process ended, respawning [11293.045923] systemd-logind[1420]: Failed to abandon scope session-c1.scope [11293.046499] systemd-logind[1420]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [17818.110774] systemd-logind[1420]: Failed to start unit user@0.service: Unknown unit: user@0.service [17818.111944] systemd-logind[1420]: Failed to start user service: Unknown unit: user@0.service [17818.115571] systemd-logind[1420]: New session c2 of user root. [18812.879680] systemd-logind[1420]: New session 22 of user root. [18814.620794] systemd-logind[1420]: Failed to abandon scope session-22.scope [18814.622186] systemd-logind[1420]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2d22_2escope To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1353989/+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
