[Desktop-packages] [Bug 1397878] [NEW] nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build
*** This bug is a duplicate of bug 1268257 *** https://bugs.launchpad.net/bugs/1268257 Public bug reported: Got crash when restarted laptop - as soon as I logged into Ubuntu, unity started and the crash dialog appeared. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 08:40:57 2014 InstallationDate: Installed on 2014-03-25 (250 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-23 (38 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397878 Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: Got crash when restarted laptop - as soon as I logged into Ubuntu, unity started and the crash dialog appeared. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 08:40:57 2014 InstallationDate: Installed on 2014-03-25 (250 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397846] Re: package thunderbird 1:31.1.2+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thund
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: thunderbird (Ubuntu) Importance: Undecided = Low ** Changed in: thunderbird (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1397846 Title: package thunderbird 1:31.1.2+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so .dpkg-new': unexpected end of file or stream Status in thunderbird package in Ubuntu: Invalid Bug description: Not sure what the problem is. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: thunderbird 1:31.1.2+build1-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.14.1-0ubuntu3.5 AptOrdering: thunderbird: Install thunderbird: Configure thunderbird-gnome-support: Configure Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vishal 1804 F pulseaudio /dev/snd/pcmC0D0p: vishal 1804 F...m pulseaudio BuildID: 20140924103150 Channel: Unavailable Date: Sun Nov 30 19:26:21 2014 DuplicateSignature: package:thunderbird:1:31.1.2+build1-0ubuntu0.14.04.1:cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-24 (129 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IpRoute: default via 192.168.100.1 dev eth0 proto static 192.168.100.0/22 dev eth0 proto kernel scope link src 192.168.101.20 metric 1 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: thunderbird Title: package thunderbird 1:31.1.2+build1-0ubuntu0.14.04.1 failed to install/upgrade: cannot copy extracted data for './usr/lib/thunderbird/libxul.so' to '/usr/lib/thunderbird/libxul.so.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: Dec 1 12:15:22 vishal-Inspiron-N5050 kernel: [ 2526.634715] systemd-hostnamed[14810]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 01HXXJ dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd08/03/2012:svnDellInc.:pnInspironN5050:pvrNotSpecified:rvnDellInc.:rn01HXXJ:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5050 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1397846/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397878] Re: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build
*** This bug is a duplicate of bug 1268257 *** https://bugs.launchpad.net/bugs/1268257 ** This bug has been marked a duplicate of bug 1268257 nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397878 Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: Got crash when restarted laptop - as soon as I logged into Ubuntu, unity started and the crash dialog appeared. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Tue Nov 25 08:40:57 2014 InstallationDate: Installed on 2014-03-25 (250 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140323) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.89-0ubuntu5: nvidia-331-updates kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397862] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build [Error! Bad return status for module build on kernel: 3.16.0-23-generi
*** This bug is a duplicate of bug 1370859 *** https://bugs.launchpad.net/bugs/1370859 ** This bug has been marked a duplicate of bug 1370859 Error! Bad return status for module build on kernel: 3.16.0-16-generic (x86_64) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397862 Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build [Error! Bad return status for module build on kernel: 3.16.0-23-generic (x86_64)] Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: Utopic/64bit apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: linux-headers-generic linux-image-3.16.0-23-generic linux-image-extra-3.16.0-23-generic linux-image-generic thermald 0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded. After this operation, 203 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 238667 files and directories currently installed.) Removing linux-headers-generic (3.16.0.25.26) ... Removing linux-image-generic (3.16.0.25.26) ... Removing linux-image-extra-3.16.0-23-generic (3.16.0-23.31) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.16.0-23-generic /boot/vmlinuz-3.16.0-23-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.16.0-23-generic /boot/vmlinuz-3.16.0-23-generic Error! Bad return status for module build on kernel: 3.16.0-23-generic (x86_64) Consult /var/lib/dkms/nvidia-331-updates-uvm/331.89/build/make.log for more information. sed: -e expression #1, char 6: unknown command: `m' ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-23-generic Date: Mon Dec 1 08:20:20 2014 InstallationDate: Installed on 2014-11-12 (18 days ago) InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Release amd64 (20141022.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397751] Re: empty desktop
** Tags added: bios-outdated-0603 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1397751 Title: empty desktop Status in xorg package in Ubuntu: New Bug description: user is new to ubuntu (windows user) using Geforce 220 (driver problem) observation: ubuntu is usable but unstable. some things will disappear, except for wallper and mouse pointer, hdd light becomes stuck. only way to go is push reset button ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Dec 1 07:29:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0715] InstallationDate: Installed on 2014-11-25 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=2c0148c9-0e22-4bd2-87de-5f13f5c8f003 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0407 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.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.:bvr0407:bd08/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM:rvrx.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.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git20141122.ec65f8d7-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141120.0f15b8b4-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2 xserver.bootTime: Mon Dec 1 07:14:49 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1397751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1376764] Re: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta
** Branch linked: lp:~timo- jyrinki/ubuntu/vivid/onboard/onboard_fix1378739_1376764 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1376764 Title: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta Status in Onboard on-screen keyboard: Fix Committed Status in onboard package in Ubuntu: Confirmed Bug description: Activating the on-screen keyboard in the settings menu has no effect. Trying to manually execute /usr/bin/onboard via pointing-and-clicking opens up gedit (i.e., it's not recognised as an executable). No other keyboard input is available for the device in question, so further tests via command line (such as confirming that `python /usr/bin/onboard' starts onboard normally) are not feasible. Thus, 14.10 final beta is bootable but completely unusable on some tablet devices (Surface Pro 3 here). (Filing against `onboard' because this might be an `onboard' installation issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1376764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397753] Re: everything keeps closing cannot be opened unless i restart
Mpendulo, thank you for reporting this and helping make Ubuntu better. Does this issue when: 1) you are not connected to the internet at all? 2) If you are only connected to the internet via WiFi only? This is asked as per your https://launchpadlibrarian.net/191564648/CurrentDmesg.txt : [ 245.020031] atl1c :09:00.0: vpd r/w failed. This is likely a firmware bug on this device. Contact the card vendor for a firmware update. ** Package changed: xorg (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1397753 Title: everything keeps closing cannot be opened unless i restart Status in linux package in Ubuntu: Incomplete Bug description: the system keeps closing programms like fire fox and downloaded videos even most applications ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Dec 1 01:39:54 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.20, 3.13.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:049b] Subsystem: Acer Incorporated [ALI] Device [1025:049b] InstallationDate: Installed on 2014-11-27 (3 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: eMachines eME528 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=e3756dd5-74d6-4441-af68-28ad3e2a9a3a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2011 dmi.bios.vendor: Phoenix dmi.bios.version: V1.3408 dmi.board.name: HM55-MV dmi.board.vendor: eMachines dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: eMachines dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenix:bvrV1.3408:bd02/14/2011:svneMachines:pneME528:pvrNotApplicable:rvneMachines:rnHM55-MV:rvrNotApplicable:cvneMachines:ct10:cvrN/A: dmi.product.name: eME528 dmi.product.version: Not Applicable dmi.sys.vendor: eMachines version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 1 01:26:07 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12369 vendor SEC xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397751] Re: [xorg-edgers] empty desktop
ralleon, thank you for reporting this and helping make Ubuntu better. As per http://www.asus.com/Motherboards/P5KPLAM/HelpDesk_Download/ an update to your BIOS is available (0603). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. As well, you don't have to create a new bug report. Once the BIOS is updated, then please mark this report Status New. Thank you for your understanding. ** Summary changed: - empty desktop + [xorg-edgers] empty desktop ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1397751 Title: [xorg-edgers] empty desktop Status in xorg package in Ubuntu: Incomplete Bug description: user is new to ubuntu (windows user) using Geforce 220 (driver problem) observation: ubuntu is usable but unstable. some things will disappear, except for wallper and mouse pointer, hdd light becomes stuck. only way to go is push reset button ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Mon Dec 1 07:29:12 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-40-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0715] InstallationDate: Installed on 2014-11-25 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=2c0148c9-0e22-4bd2-87de-5f13f5c8f003 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/28/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0407 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5KPL-AM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.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.:bvr0407:bd08/28/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM:rvrx.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.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git20141122.ec65f8d7-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0~git20141122.3d9c1a9d-0ubuntu0ricotz~trusty version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141120.0f15b8b4-0ubuntu0sarvatt~trusty
[Desktop-packages] [Bug 1397791] Re: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
*** This bug is a duplicate of bug 1268257 *** https://bugs.launchpad.net/bugs/1268257 ** This bug has been marked a duplicate of bug 1268257 nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1397791 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: This is automatically reported. I did not notice a problem. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: openafs nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-26-generic Date: Sun Nov 30 21:56:03 2014 InstallationDate: Installed on 2014-09-06 (85 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-24 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1397791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378739] Re: Updated package with patch for autostart problem LP: #1376764
Seems good to me. I built it at https://launchpad.net/~timo- jyrinki/+archive/ubuntu/ppa and tested a few times logging in/out with onboard set to start or not in the settings. I've also made a branch out of your debdiff, retargeted to vivid, so that it's easier to sponsor since I cannot sponsor a main package myself. ** Branch linked: lp:~timo- jyrinki/ubuntu/vivid/onboard/onboard_fix1378739_1376764 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1378739 Title: Updated package with patch for autostart problem LP: #1376764 Status in onboard package in Ubuntu: New Bug description: Hi, Onboard does not always automatically start up when logging in , even though it is set to do so in the system preferences. We think that it is because the D-Bus name org.gnome.Shell now also exist in Unity Utopic. Thus, we have patched the onboard- autostart.desktop file, in a way that we think would cover the needs of Unity, GNOME and GNOME fallback/fallback-sessions. As a side effect, Onboard now also starts in other sessions like KDE, XFCE,... but this might be tolerable as they don't have a switch to enable it. We are proposing this fix, because it only needs changes in two lines of the onboard version currently shipping with Ubuntu Utopic. However, Onboard trunk has in the meantime also a more soffisticated solution involving additional checks of XDG_CURRENT_DESKTOP. This latter solution however requires changes to the code base of Onboard. Thus, I am attaching here an updated package of Onboard with the first solution involving only changes to the onboard-autostart.desktop file. If you prefer the latter, please let us know and we will look whether we can do something. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397734] Re: euuuuh
franki1999, thank you for taking the time to report this and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read How to report bugs effectively http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and https://wiki.ubuntu.com/ReportingBugs . We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem, 2. The behavior you expected, and 3. The behavior you actually encountered (in as much detail as possible). Thank you for your understanding. ** Tags added: latest-bios-2.09 ** Changed in: xorg (Ubuntu) Importance: Undecided = Low ** Changed in: xorg (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1397734 Title: eh Status in xorg package in Ubuntu: Incomplete Bug description: Donnow ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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: Sun Nov 30 22:37:06 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400] [1002:9830] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:076b] MachineType: Acer Aspire E1-522 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=b821166e-f395-4dbf-9fa7-a139d9618fb5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire E1-522 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/19/2013:svnAcer:pnAspireE1-522:pvrV2.09:rvnAcer:rnAspireE1-522:rvrV2.09:cvnAcer:ct10:cvrV2.09: dmi.product.name: Aspire E1-522 dmi.product.version: V2.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 30 11:51:32 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1397734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286878] Re: Doesn't scale well on a hidpi display
I made this patch and it can fix the problem. Please help to review it, thanks in advance. ** Patch added: hidpi_support.patch https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1286878/+attachment/4271918/+files/hidpi_support.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1286878 Title: Doesn't scale well on a hidpi display Status in unity-greeter package in Ubuntu: Triaged Bug description: unity-greeter does not scale on hidpi diplays like the rest of unity does in trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1286878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296020] Re: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04)
@witem: the log shows that the laptop display (LVDS) was detected and that the driver was enabled. Maybe you're dealing with a bug in the nvidia driver 340.58. Feel free to file a separate bug report for that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1296020 Title: [Asus U36JC] Non-existent display detected in both intel driver and nvidia driver (Optimus Laptop) (ubuntu trusty 14.04) Status in nvidia-prime package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Precise: Confirmed Status in ubuntu-drivers-common source package in Precise: Invalid Status in nvidia-prime source package in Trusty: Invalid Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: SRU Request Systems with Optimus (Intel+NVIDIA GPUs) can have ghost VGA devices hardcoded in the BIOS. This leads the system into thinking that there is actually one more active output than there really is. [Impact] * The ghost VGA output confuses lightdm and the gnome-settings-daemon making the system unusable. [Test Case] * Install the nvidia binary driver, reboot, and check the output of the xrandr -q command - Expected: only the outputs that are actually connected will be marked as active. - Bad behavior: a non-existent VGA device will show up in the output. [Regression Potential] * Low, as it only disables CRT outputs in the nvidia driver. [Other Info] * N/A -- There is a non existent display detected in both intel driver only and nvidia 331 driver installation. The non existent display is Unknown Display shown in gnome-control-center -- display and CRT-0 in nvidia-settings, and VGA-0 in xrandr -q output. It will cause gdm failed to start. gnome-shell has some crazy layouts. lightdm will only occupy 2/3 of monitor in top left corner. I tested this in intel driver only environment. and nvidia-331 installation environment. My laptop is Asus U36JC. My monitor correct resolution is 1366x768. The following is the output of xrandr -q in gnome-shell with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 680x384+0+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x384 60.0*+ 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x720 60.0 928x696 60.1 896x672 60.0 960x600 60.0 960x540 60.0 800x600 60.0 60.3 56.2 840x525 60.0 59.9 800x512 60.2 700x525 60.0 640x512 60.0 720x450 59.9 640x480 60.0 59.9 680x384 59.8 60.0 576x432 60.1 512x384 60.0 400x300 60.3 56.3 320x240 60.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1-0 disconnected (normal left inverted right x axis y axis) 1366x768 (0x46) 69.3MHz h: width 1366 start 1425 end 1464 total 1472 skew 0 clock 47.1KHz v: height 768 start 773 end 782 total 785 clock 60.0Hz 1360x768 (0x48) 72.0MHz h: width 1360 start 1408 end 1440 total 1520 skew 0 clock 47.4KHz v: height 768 start 771 end 781 total 790 clock 60.0Hz 680x384 (0x5c) 36.0MHz h: width 680 start 704 end 720 total 760 skew 0 clock 47.4KHz v: height 384 start 385 end 390 total 395 clock 60.0Hz The following is the output of xrandr -q in lxde with nvidia-331 installed: $ xrandr -q Screen 0: minimum 8 x 8, current 1366 x 768, maximum 8192 x 8192 VGA-0 connected primary 1024x768+31+0 (normal left inverted right x axis y axis) 0mm x 0mm panning 1366x768+0+0 680x38460.0 + 1366x768 60.0 1360x768 60.0 HDMI-0 disconnected (normal left inverted right x axis y axis) LVDS-1-0 connected 1366x768+0+0 (normal left inverted right x axis y axis) 293mm x 165mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 60.0 960x72060.0 928x69660.1 896x67260.0 960x60060.0 960x54060.0 800x60060.0 60.3 56.2 840x52560.0 59.9 800x51260.2 700x52560.0 640x51260.0 720x45059.9 640x48060.0 59.9 680x38459.8 60.0 576x43260.1 512x38460.0 400x30060.3 56.3 320x24060.1 VGA-1-0 disconnected (normal left inverted right x axis y axis) HDMI-1-0 disconnected (normal left
[Desktop-packages] [Bug 1397124] Re: gpu-manager tries to use pci-stub module as a vga driver
Please attach your /var/log/gpu-manager.log and your /etc/init/gpu- manager.lspci. This is definitely a use case that I didn't handle. ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New = Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided = Medium ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1397124 Title: gpu-manager tries to use pci-stub module as a vga driver Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: There is two AMD gpu:s installed in my computer. The first one uses the fglrx module and is the one that is intended to be used for the linux desktop. The second is intended for gpu passthrough and owned by pci-stub. gpu-manager makes the assumption that a card shall be used based on vendor/device id and if the fglrx module is loaded. That is not sufficient in this case. I have not verified if the same applies to xen-pciback but it seems likely. My workaround has been to use the fake lspci file option and a manually created xorg.conf. Everything worked fine before I changed one of the cards to use the pci-stub module. The result before use of fake_lspci was a permanently blank screen. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-drivers-common 1:0.2.98.4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 27 22:07:08 2014 InstallationDate: Installed on 2014-01-18 (312 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to utopic on 2014-10-29 (29 days ago) mtime.conffile..etc.init.gpu.manager.conf: 2014-11-26T23:10:48.005964 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1397124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1394189] Re: [Samsung NP-RF711-S07UK] Nvidia proprietary driver stopped working after ubuntu 14.04 updates from 18 November 2014
Thanks Christopher. I've read the link you sent and decided not to go down this route at this stage due to the warnings and my relatively limited knowledge. I'm using the nouveau drivers and they are currently working for what I need, so I will stick with these until I hit something that I can't do with them. Thanks again for your support. On 1 December 2014 at 01:53, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Larry, you would want to start with the readme that comes with the driver, as well as https://help.ubuntu.com/community/NvidiaManual . -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1394189 Title: [Samsung NP-RF711-S07UK] Nvidia proprietary driver stopped working after ubuntu 14.04 updates from 18 November 2014 Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Incomplete Bug description: Dual Screen not working on 14.04 when I log in today. Get error message: Failed to apply configuration: %s GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 63 Yesterday I applied updates. Ubuntu software history shows these as: bsdutils(2.20.1-5.1ubuntu20.2,2.20.1-5.1ubuntu20.3) xserver-xorg-video-intel(2.99.910-0ubuntu1.2,2.99.910-0ubuntu1.3) Previous to this I have had no problems with dual screen on 14.04. WORKAROUND: Reverted to the Nouveau driver. The nvidia driver 331.38 previously worked but doesn't now after the above Ubuntu updates. --- .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 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 DistUpgraded: Fresh install DistroCodename: trusty DistroRelease: Ubuntu 14.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Device [144d:c0a5] Subsystem: Samsung Electronics Co Ltd Device [144d:c0a5] InstallationDate: Installed on 2014-08-30 (91 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xorg 1:7.7+1ubuntu8 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=2d9f275c-a65b-4e1a-a20b-e2ad679f1109 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Tags: trusty ubuntu compiz-0.9 Uname: Linux 3.13.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 15HX.M042.20120302.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 15HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr15HX.M042.20120302.SSH:bd03/02/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pnRF511/RF411/RF711:pvr15HX:rvnSAMSUNGELECTRONICSCO.,LTD.:rnRF511/RF411/RF711:rvr15HX:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: RF511/RF411/RF711 dmi.product.version: 15HX dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Nov 30 12:26:46 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.
[Desktop-packages] [Bug 1397897] Re: chromium-browser crashed with SIGSEGV
*** This bug is a duplicate of bug 1378627 *** https://bugs.launchpad.net/bugs/1378627 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1378627, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1397897/+attachment/4271920/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1397897/+attachment/4271922/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1397897/+attachment/4271925/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1397897/+attachment/4271926/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1397897/+attachment/4271927/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1397897/+attachment/4271930/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1397897/+attachment/4271931/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1378627 chromium-browser crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1397897 Title: chromium-browser crashed with SIGSEGV Status in chromium-browser package in Ubuntu: New Bug description: Changing proxy settings. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: chromium-browser 39.0.2171.65-0ubuntu0.14.10.1.1106 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Dec 1 09:10:06 2014 ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationDate: Installed on 2014-09-07 (84 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) ProcCmdline: chromium-browser\ --type=gpu-process\ --channel=14924.0.279269498\ --supports-dual-gpus=false\ --gpu-driver-bug-workarounds=1,11,15,38\ --disable-accelerated-video-decode\ --gpu-vendor-id=0x8086\ --gpu-device-id=0x0a16\ --gpu-driver-vendor\ --gpu-driver-versi SegvAnalysis: Segfault happened at: 0x7fe2592386af:mov0x1f8(%rax),%r15 PC (0x7fe2592386af) ok source 0x1f8(%rax) (0x01f8) not located in a known VMA region (needed readable region)! destination %r15 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: chromium-browser StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so ?? () from /usr/lib/chromium-browser/libs/libgpu.so ?? () from /usr/lib/chromium-browser/libs/libcontent.so ?? () from /usr/lib/chromium-browser/libs/libcontent.so Title: chromium-browser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1397897/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397908] [NEW] sorting by mtime not working when subdirectories are present
Public bug reported: When sorting by modification date Nautilus does not seem to look into subdirectories. OS: Xubuntu 14.10 GNOME nautilus 3.10.1 kernel: 3.16.0-26-generic #34-Ubuntu SMP Tue Nov 25 00:37:24 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1397908 Title: sorting by mtime not working when subdirectories are present Status in nautilus package in Ubuntu: New Bug description: When sorting by modification date Nautilus does not seem to look into subdirectories. OS: Xubuntu 14.10 GNOME nautilus 3.10.1 kernel: 3.16.0-26-generic #34-Ubuntu SMP Tue Nov 25 00:37:24 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1397908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
** Changed in: unity8 (Ubuntu) Status: Opinion = In Progress ** Changed in: unity8 (Ubuntu RTM) Status: Opinion = New ** Changed in: unity8 (Ubuntu RTM) Assignee: Albert Astals Cid (aacid) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone Status in network-manager package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: New Bug description: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10
Bug still present in java programs on 14.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10, 14.04, 14.04.1, 14.10 Status in Aptana Studio Installer: New Status in Default settings for the Baltix GNU/Linux OS and desktop: New Status in LibreOffice Productivity Suite: Confirmed Status in IBus: New Status in Indicator keyboard: Fix Released Status in Inkscape: A Vector Drawing Tool: New Status in MonoDevelop: New Status in Mutter: Fix Released Status in The OpenOffice.org Suite: New Status in Unity: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in indicator-keyboard package in Ubuntu: Triaged Status in openjdk-7 package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in Fedora: Unknown Status in gnome-shell package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. Dear Ubuntu users and developers! Please include the following information to your comment about non-latin shortcuts problems: 1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean installed 2. What keyboard layout do you have 3. What shortcut for keyboard layout switching do you use 4. On which session you have problems - that is one from Unity, GNOME Shell, GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz) 5. With which program and its version and origin (Ubuntu repositories, PPA, non-deb binary package from some website) you have problems. By providing this information you can make bug-fixing much simpler and may be faster. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397887] [NEW] Apport asks to install 'bluez-hcidump' but this package does not exist
You have been subscribed to a public bug: I wanted to file a bug regarding bluetooth, so I run 'ubuntu-bug bluez'. Apport is launched and proposes the following: Your bug report will be processed in few seconds. If you can reproduce it, please follow the next steps: - Install the package 'bluez-hcidump' - Open a new terminal - Run the command sudo hcidump -XYt $HOME/hci.log - Reproduce the actions until the error happens - On the terminal, press Ctrl+C to stop hcidump. - Attach the file hci.log to the bug report. So I try to install the 'bluez-hcidump' package, but... % sudo apt-get install bluez-hcidump Reading package lists... Done Building dependency tree Reading state information... Done Package bluez-hcidump is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'bluez-hcidump' has no installation candidate ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez 4.101-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 1 16:50:04 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-15 (15 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire VN7-591G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-591G dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-591G:pvrV1.08:rvnAcer:rnAspireVN7-591G:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08: dmi.product.name: Aspire VN7-591G dmi.product.version: V1.08 dmi.sys.vendor: Acer hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 5C:93:A2:EB:FF:43 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:5529 acl:0 sco:0 events:856 errors:0 TX bytes:6892 acl:0 sco:0 commands:727 errors:0 syslog: Dec 1 16:21:16 Miles bluetoothd[631]: Discovery session 0x7fa5da51da30 with :1.228 activated Dec 1 16:27:43 Miles bluetoothd[631]: Discovery session 0x7fa5da530a50 with :1.230 activated ** Affects: apport (Ubuntu) Importance: Low Status: Triaged ** Tags: amd64 apport-bug utopic -- Apport asks to install 'bluez-hcidump' but this package does not exist https://bugs.launchpad.net/bugs/1397887 You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397887] Re: Apport asks to install 'bluez-hcidump' but this package does not exist
Pierre Equoy, thank you for reporting this and helping make Ubuntu better. As per https://launchpad.net/ubuntu/+source/bluez-hcidump the package is not available in Utopic+. Hence, it would appear apport would want to be adjusted for these releases to not include this request, and/or provide some other suggestion. ** Package changed: bluez (Ubuntu) = apport (Ubuntu) ** Changed in: apport (Ubuntu) Importance: Undecided = Low ** Changed in: apport (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1397887 Title: Apport asks to install 'bluez-hcidump' but this package does not exist Status in apport package in Ubuntu: Triaged Bug description: I wanted to file a bug regarding bluetooth, so I run 'ubuntu-bug bluez'. Apport is launched and proposes the following: Your bug report will be processed in few seconds. If you can reproduce it, please follow the next steps: - Install the package 'bluez-hcidump' - Open a new terminal - Run the command sudo hcidump -XYt $HOME/hci.log - Reproduce the actions until the error happens - On the terminal, press Ctrl+C to stop hcidump. - Attach the file hci.log to the bug report. So I try to install the 'bluez-hcidump' package, but... % sudo apt-get install bluez-hcidump Reading package lists... Done Building dependency tree Reading state information... Done Package bluez-hcidump is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'bluez-hcidump' has no installation candidate ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: bluez 4.101-0ubuntu20 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 1 16:50:04 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-15 (15 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Acer Aspire VN7-591G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-591G dmi.board.vendor: Acer dmi.board.version: V1.08 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: V1.08 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd09/12/2014:svnAcer:pnAspireVN7-591G:pvrV1.08:rvnAcer:rnAspireVN7-591G:rvrV1.08:cvnChassisManufacturer:ct10:cvrV1.08: dmi.product.name: Aspire VN7-591G dmi.product.version: V1.08 dmi.sys.vendor: Acer hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 5C:93:A2:EB:FF:43 ACL MTU: 1022:8 SCO MTU: 183:5 UP RUNNING PSCAN ISCAN RX bytes:5529 acl:0 sco:0 events:856 errors:0 TX bytes:6892 acl:0 sco:0 commands:727 errors:0 syslog: Dec 1 16:21:16 Miles bluetoothd[631]: Discovery session 0x7fa5da51da30 with :1.228 activated Dec 1 16:27:43 Miles bluetoothd[631]: Discovery session 0x7fa5da530a50 with :1.230 activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1397887/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1393523] Re: Dragging windows in Expo mode occasionally results in weird behavior
This bug occurred again now, but this time Super+S didn't close Expo mode. The window drag action got stuck in Expo mode, and every time I pressed the Super key, the window moved to to cursor position. I had to run sudo restart lightdm from a virtual console to restart the session. This should be of high importance! Could a developer check (triage) this bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1393523 Title: Dragging windows in Expo mode occasionally results in weird behavior Status in compiz package in Ubuntu: New Status in unity package in Ubuntu: New Bug description: There are some times where dragging windows in Expo mode doesn't work or results in weird behaviors. Sometimes, when dragging a window, the drag fails midway and then clicking anywhere on the screen does nothing (even when clicking in the Expo button, needing to press Super+S to exit Expo mode). I have also noticed that, when moving the cursor around in Expo mode, the close/minimize/maximize buttons of the windows would sometimes highlight and the locally integrated menus would be displayed. This seems to occur in the current workspace (the one where I was before entering Expo mode) when I move the cursor over where the buttons or menu are when out of the Expo mode. To reproduce that: * Open a window (terminal, nautilus, or anything else) * Move the window to the center (to make the next step easier) * Move the mouse cursor to a few pixels to the left of the close button of the window * Open Expo mode by pressing Super+S * Now start moving the cursor slowly to the right and see if the buttons (and menu) of the window are highlighted * When one of the buttons is highlighted, click. The action of that button will be performed (and it shouldn't) and Expo mode will exit to that workspace This may be the cause of the problem. I have also reproduced this in the guest session and in a 14.04.1 virtual machine (not updated). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.3+14.04.20140826-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Nov 17 18:56:18 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-13 (35 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/compiz/+bug/1393523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378739] Re: Updated package with patch for autostart problem LP: #1376764
** Branch linked: lp:ubuntu/vivid-proposed/onboard -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1378739 Title: Updated package with patch for autostart problem LP: #1376764 Status in onboard package in Ubuntu: New Bug description: Hi, Onboard does not always automatically start up when logging in , even though it is set to do so in the system preferences. We think that it is because the D-Bus name org.gnome.Shell now also exist in Unity Utopic. Thus, we have patched the onboard- autostart.desktop file, in a way that we think would cover the needs of Unity, GNOME and GNOME fallback/fallback-sessions. As a side effect, Onboard now also starts in other sessions like KDE, XFCE,... but this might be tolerable as they don't have a switch to enable it. We are proposing this fix, because it only needs changes in two lines of the onboard version currently shipping with Ubuntu Utopic. However, Onboard trunk has in the meantime also a more soffisticated solution involving additional checks of XDG_CURRENT_DESKTOP. This latter solution however requires changes to the code base of Onboard. Thus, I am attaching here an updated package of Onboard with the first solution involving only changes to the onboard-autostart.desktop file. If you prefer the latter, please let us know and we will look whether we can do something. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1376764] Re: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta
** Branch linked: lp:ubuntu/vivid-proposed/onboard -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1376764 Title: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta Status in Onboard on-screen keyboard: Fix Committed Status in onboard package in Ubuntu: Confirmed Bug description: Activating the on-screen keyboard in the settings menu has no effect. Trying to manually execute /usr/bin/onboard via pointing-and-clicking opens up gedit (i.e., it's not recognised as an executable). No other keyboard input is available for the device in question, so further tests via command line (such as confirming that `python /usr/bin/onboard' starts onboard normally) are not feasible. Thus, 14.10 final beta is bootable but completely unusable on some tablet devices (Surface Pro 3 here). (Filing against `onboard' because this might be an `onboard' installation issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1376764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1058623] Re: APM settings are not persistent after a reboot
Just FYI, udisks2 handles drives (at least in 14.04+) and you can
configure things like APM level for individual disks by putting an entry
into /etc/udisks2 with a filename that matches the drive id and serial
number (which you can read from gnome-disks/palimpsest), eg with the
contents:
[ATA]
StandbyTimeout=60
Do man 8 udisks for more info about the format of the file.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1058623
Title:
APM settings are not persistent after a reboot
Status in gnome-disk-utility package in Ubuntu:
Confirmed
Bug description:
In order to keep my data storage disks from slowly committing suicide
by unloading their heads, I have to disable APM for both of them.
Usually I would be able to do so by putting 'hdparm -B255 -S0
/dev/sdx*' in /etc/rc.local.
Since Ubuntu 12.10, Palimpsest has a built-in function to modify APM
settings if required. Sadly, after a reboot, these settings aren't
kept. Even though the Palimpsest interface still claims APM is set to
255, running sudo hdparm -I /dev/sdx* will show the default value of
128 again. The desired behaviour is hdparm showing 'APM = off', and,
more importantly, the disks not breaking themselves.
The only way to keep my disks from dying is by adding
/dev/sdx* {
apm = 255
spindown_time = 0
}
to /etc/hdparm.conf, as everything in /etc/rc.local seems to be
ignored as well. The problem is no different for my SSD, but it
doesn't make a difference for that one, obviously. Disabling and re-
enabling the APM settings from Palimpsest does seem to work though,
but it's impossible to do/remember that after every bootup. And
forgetting to do so would most likely lead to premature disk failure.
* 'sdx' is 'sdb' and 'sdc' in my case
ProblemType: Bug
ApportVersion: 2.5.3-0ubuntu1
Architecture: amd64
Date: Sat Sep 29 15:28:24 2012
DistroRelease: Ubuntu 12.10
Package: gnome-disk-utility 3.6.0-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.5.0-16.24-generic 3.5.4
SourcePackage: gnome-disk-utility
Tags: quantal
Uname: Linux 3.5.0-16-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1058623/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
You have been subscribed to a public bug: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dell Importance: Undecided Status: Confirmed ** Affects: hwe-next Importance: Undecided Status: Confirmed ** Affects: nouveau Importance: Low Status: Confirmed ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server Importance: Low Status: Confirmed ** Tags: amd64 apport-bug precise trusty utopic -- [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep https://bugs.launchpad.net/bugs/1268151 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
You have been subscribed to a public bug: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dell Importance: Undecided Status: Confirmed ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Affects: nouveau Importance: Low Status: Confirmed ** Affects: xorg-server Importance: Low Status: Confirmed ** Tags: amd64 apport-bug precise trusty utopic -- [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep https://bugs.launchpad.net/bugs/1268151 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
You have been subscribed to a public bug: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server Importance: Low Status: Confirmed ** Tags: amd64 apport-bug precise trusty utopic -- [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep https://bugs.launchpad.net/bugs/1268151 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
You have been subscribed to a public bug: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: nouveau Importance: Low Status: Confirmed ** Affects: xorg-server Importance: Low Status: Confirmed ** Tags: amd64 apport-bug precise trusty utopic -- [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep https://bugs.launchpad.net/bugs/1268151 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397934] [NEW] problema na instalação do pacote latex-sanskrit 2.2-10
Public bug reported: Eu uso o ubuntu 14.4 e frequentemente tenho recebido mensagens dizendo que há algum problema no sistema ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lmodern 2.004.4-3 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 Date: Mon Dec 1 07:26:47 2014 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2010-04-29 (1676 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) PackageArchitecture: all SourcePackage: lmodern Title: package lmodern 2.004.4-3 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to trusty on 2014-08-29 (94 days ago) ** Affects: lmodern (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lmodern in Ubuntu. https://bugs.launchpad.net/bugs/1397934 Title: problema na instalação do pacote latex-sanskrit 2.2-10 Status in lmodern package in Ubuntu: New Bug description: Eu uso o ubuntu 14.4 e frequentemente tenho recebido mensagens dizendo que há algum problema no sistema ProblemType: Package DistroRelease: Ubuntu 14.04 Package: lmodern 2.004.4-3 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 Date: Mon Dec 1 07:26:47 2014 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2010-04-29 (1676 days ago) InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) PackageArchitecture: all SourcePackage: lmodern Title: package lmodern 2.004.4-3 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to trusty on 2014-08-29 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lmodern/+bug/1397934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] [NEW] [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
You have been subscribed to a public bug: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise trusty utopic -- [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep https://bugs.launchpad.net/bugs/1268151 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 622965] Re: New windows always use active window's keyboard layout
I can no longer reproduce it on my system. Can anyone confirm it? ** Changed in: compiz Status: Confirmed = Incomplete ** Changed in: unity Status: Confirmed = Incomplete ** Changed in: compiz (Ubuntu) Status: Triaged = Incomplete ** Changed in: unity (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/622965 Title: New windows always use active window's keyboard layout Status in Compiz: Incomplete Status in GNOME Control Center: Unknown Status in Unity: Incomplete Status in compiz package in Ubuntu: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: If Compiz used (e.g. Ubuntu with Unity), Gnome keyboard settings Allow different layouts for individual windows New windows use the default layout doesn't work properly. New windows always use last active window's layout ignoring default keyboard layout. This bug affects all Ubuntu versions using Compiz as window manager (including Ubuntu 12.04 LTS and Ubuntu 12.10-beta1). Steps to reproduce this bug. Required settings: 1. Ubuntu with Compiz as window manager (e.g. Ubuntu with Unity, which is based on Compiz). 2. Two or more input languages in the Keyboard Layout Settings (e.g. 1st - English (US), 2nd - Russian). 3. Keyboard Layout Settings: a) Allow different layouts for individual windows; b) New windows use the default layout. [Default layout is the first one in the layouts list, I think] *** Scenario 1 1. Open Text Editor (gedit). 2. Switch input language to Russian. 3. Type some text in the gedit window in russian. 4. Start Terminal (gnome-terminal). 5. Type some text in the Terminal window (without keyboard layout switching). Expected behavior: Typed symbols in the terminal are English (because English was set as default input language in Keyboard Settings, and new windows should use the default layout). What actually happens: Typed symbols in the terminal are Russian (same input language as in the previous active window). *** Scenario 2 1. Open Text Editor (gedit). 2. Switch input language to Russian. 3. Type some text in the gedit window in russian. 4. Leave your computer with no activity for 10 minutes (wait for screen locking). 5. Try to enter password in the logon screen (without keyboard layout switching). Expected behavior: Password is entered in English (because English was set as default input language in Keyboard Settings, and new windows should use the default layout). What actually happens: Password is entered in Russian (same input language as in the previous active window). To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/622965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378739] Re: Updated package with patch for autostart problem LP: #1376764
This bug was fixed in the package onboard - 1.0.0-0ubuntu5 --- onboard (1.0.0-0ubuntu5) vivid; urgency=medium * Request for sponsorship (LP: #1378739) * debian/patches: - Add fix_autostart.patch (LP: #1376764) -- Francesco Fumanti francesco.fuma...@gmx.net Wed, 08 Oct 2014 21:52:03 +0200 ** Changed in: onboard (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1378739 Title: Updated package with patch for autostart problem LP: #1376764 Status in onboard package in Ubuntu: Fix Released Bug description: Hi, Onboard does not always automatically start up when logging in , even though it is set to do so in the system preferences. We think that it is because the D-Bus name org.gnome.Shell now also exist in Unity Utopic. Thus, we have patched the onboard- autostart.desktop file, in a way that we think would cover the needs of Unity, GNOME and GNOME fallback/fallback-sessions. As a side effect, Onboard now also starts in other sessions like KDE, XFCE,... but this might be tolerable as they don't have a switch to enable it. We are proposing this fix, because it only needs changes in two lines of the onboard version currently shipping with Ubuntu Utopic. However, Onboard trunk has in the meantime also a more soffisticated solution involving additional checks of XDG_CURRENT_DESKTOP. This latter solution however requires changes to the code base of Onboard. Thus, I am attaching here an updated package of Onboard with the first solution involving only changes to the onboard-autostart.desktop file. If you prefer the latter, please let us know and we will look whether we can do something. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1378739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
Michael Neuffer, could you please boot into the kernel that comes with Ubuntu by default (i.e. not 3.11.x) and execute the following in a terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1268151 Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information. Thank you for your understanding. Helpful bug reporting tips: https://wiki.ubuntu.com/ReportingBugs ** No longer affects: xserver-xorg-video-nouveau (Ubuntu) ** No longer affects: nvidia-graphics-drivers-331-updates (Ubuntu) ** No longer affects: nvidia-graphics-drivers-331 (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Project changed: oem-priority = xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: Confirmed = New ** No longer affects: xorg (Ubuntu) ** Project changed: hwe-next = xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: Confirmed = New ** No longer affects: xorg (Ubuntu) ** Project changed: dell = xorg (Ubuntu) ** No longer affects: xorg (Ubuntu) ** Project changed: nouveau = xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: Confirmed = New ** Changed in: xorg (Ubuntu) Remote watch: LibreOffice Bugzilla #85459 = None ** No longer affects: xorg (Ubuntu) ** Project changed: xorg-server = xorg (Ubuntu) ** Changed in: xorg (Ubuntu) Status: Confirmed = New ** Changed in: xorg (Ubuntu) Remote watch: freedesktop.org Bugzilla #85459 = None ** Changed in: xorg (Ubuntu) Status: New = Incomplete ** Description changed: - Also affects nvidia-graphics-drivers-319 + With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: + xset dpms force off; sleep 30; xset dpms force on - The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 - but with Nvidia instead of AMD/ATI drivers. + WORKAROUND: A restart of the Xserver will bring back the display. - HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ - display + WORKAROUND: Don't allow DPMS to switch off the display: + xset dpms 0 0 0 - Once the display shuts off, it will not be woken up anymore and the screen stays dark. - Only a restart of the Xserver will bring back the display at that point. - - A cycle of - xset dpms force off; sleep 30; xset dpms force on - will leave the display dark. - - At the moment I help myself by not allowing DPMS to switch off the display: - neuffer@charion:~$ xset dpms 0 0 0 - - neuffer@charion:~$ xset -q -d :0.0 + xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+
[Desktop-packages] [Bug 1376764] Re: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta
This bug was fixed in the package onboard - 1.0.0-0ubuntu5 --- onboard (1.0.0-0ubuntu5) vivid; urgency=medium * Request for sponsorship (LP: #1378739) * debian/patches: - Add fix_autostart.patch (LP: #1376764) -- Francesco Fumanti francesco.fuma...@gmx.net Wed, 08 Oct 2014 21:52:03 +0200 ** Changed in: onboard (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1376764 Title: on-screen keyboard requires expert knowledge to launch in 14.10 Final Beta Status in Onboard on-screen keyboard: Fix Committed Status in onboard package in Ubuntu: Fix Released Bug description: Activating the on-screen keyboard in the settings menu has no effect. Trying to manually execute /usr/bin/onboard via pointing-and-clicking opens up gedit (i.e., it's not recognised as an executable). No other keyboard input is available for the device in question, so further tests via command line (such as confirming that `python /usr/bin/onboard' starts onboard normally) are not feasible. Thus, 14.10 final beta is bootable but completely unusable on some tablet devices (Surface Pro 3 here). (Filing against `onboard' because this might be an `onboard' installation issue.) To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1376764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397924] [NEW] [Clickpads] Cursor jumps when clicking
You have been subscribed to a public bug: I am running Ubuntu 14.04 x64 on my Acer Travelmate B115-M and sometimes when i use the left or right touchpad key to make a mouse click, the cursor jumps to another place on the screen far away from its inital location and executes the click at that location. For example: I want to perform a left click in the upper section of my screen with the touchpad key to open a browser tab What is expected to happen: I move the cursor to the browser tab and press the left key and the tab opens What happens instead: The cursor jumps to the lower left corner and performs the click there, the trash folder opens instead That problem is not always happening and i do not know how to produce it, however usually after a few minutes of working on my notebook and clicking around it will occur. Likely not a hardware problem as i already had the whole notebook replaced by my vendor, also with Win7 it seemed to work fine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-40-generic 3.13.0-40.69 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: simon 1363 F pulseaudio CurrentDesktop: Unity Date: Mon Dec 1 10:53:42 2014 HibernationDevice: RESUME=UUID=ed9e8c10-35d7-4c2a-bfb6-64752c8fa146 InstallationDate: Installed on 2014-11-21 (9 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. Bus 001 Device 006: ID 04e8:331e Samsung Electronics Co., Ltd Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer TravelMate B115-M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed root=UUID=0520439d-62c3-4835-a7a8-42d3a7ca0c2d ro quiet splash acpi_backlight=vendor acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-40-generic N/A linux-backports-modules-3.13.0-40-generic N/A linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.22:bd08/27/2014:svnAcer:pnTravelMateB115-M:pvrV1.22:rvnAcer:rnRoxy:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: TravelMate B115-M dmi.product.version: V1.22 dmi.sys.vendor: Acer ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Medium Status: Triaged ** Tags: amd64 apport-bug trusty -- [Clickpads] Cursor jumps when clicking https://bugs.launchpad.net/bugs/1397924 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1369053] Re: Unable to disable text file preview in Nautilus
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1369053 Title: Unable to disable text file preview in Nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: UI / tweak issue: Problem: - Unable to disable text preview of text files in Nautilus. Details: - In previous versions of Nautilus (prior to Ubuntu 14.04) users were able to disable thumbnail preview of text file in nautilus icons. Now this option is not available. - Users can disable thumbnails for *all* files, or none, but can no longer select to include plaintext files. - This also cannot be disabled from dconf-editor or by other means. Desired behavior: - Be able to disable preview of text files from Nautilus settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1369053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397924] Re: [Clickpads] Cursor jumps when clicking
Simon P., I've been battling with parts of this same issue for a while since I bought a laptop with a clickpad. The root cause is the default settings for the Synaptics driver when using any clickpad are distinctly user unfriendly for a default install. Hence, it may require some additional work to check for a clickpad (if possible) and then adjust accordingly. This suggested terminal commands won't fix everything if applied upstream, but would go a long way in addressing many of these issues. Despite this, the issue you are reporting is an upstream one. Could you please report this problem to them via https://bugs.freedesktop.org/enter_bug.cgi?product=xorg : Component: Input/Synaptics Version: 7.7 (2012.06) Severity: Enhancement Hardware: All OS: All Priority: Lowest Please provide a direct URL to your report once you have made it so that it may be tracked. Thank you for your understanding. ** Package changed: linux (Ubuntu) = xserver-xorg-input-synaptics (Ubuntu) ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Importance: Low = Medium ** Changed in: xserver-xorg-input-synaptics (Ubuntu) Status: Incomplete = Triaged ** Description changed: - I am running Ubuntu 14.04 x64 on my Acer Travelmate B115-M and sometimes - when i use the left or right touchpad key to make a mouse click, the - cursor jumps to another place on the screen far away from its inital - location and executes the click at that location. + With my Acer Travelmate B115-M running Ubuntu 14.04 x64, when I click + the bottom left or right area on my clickpad to either primary or + secondary click, the cursor jumps to another place on the screen far + away from its initial location and executes the click at that location. + The problem applies generally to clickpads in any laptop. - For example: I want to perform a left click in the upper section of my screen with the touchpad key to open a browser tab - What is expected to happen: I move the cursor to the browser tab and press the left key and the tab opens - What happens instead: The cursor jumps to the lower left corner and performs the click there, the trash folder opens instead - - That problem is not always happening and i do not know how to produce it, however usually after a few - minutes of working on my notebook and clicking around it will occur. Likely not a hardware problem as i already had the whole notebook replaced by my vendor, also with Win7 it seemed to work fine. + WORKAROUND: Execute the following at a terminal: + synclient RTCornerButton=0 + synclient RBCornerButton=0 + synclient LTCornerButton=0 + synclient LBCornerButton=0 + synclient AreaBottomEdge=3900 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-40-generic 3.13.0-40.69 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: simon 1363 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: simon 1363 F pulseaudio CurrentDesktop: Unity Date: Mon Dec 1 10:53:42 2014 HibernationDevice: RESUME=UUID=ed9e8c10-35d7-4c2a-bfb6-64752c8fa146 InstallationDate: Installed on 2014-11-21 (9 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. - Bus 001 Device 006: ID 04e8:331e Samsung Electronics Co., Ltd - Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 1bcf:2c57 Sunplus Innovation Technology Inc. + Bus 001 Device 006: ID 04e8:331e Samsung Electronics Co., Ltd + Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer TravelMate B115-M ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic.efi.signed root=UUID=0520439d-62c3-4835-a7a8-42d3a7ca0c2d ro quiet splash acpi_backlight=vendor acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.13.0-40-generic N/A - linux-backports-modules-3.13.0-40-generic N/A - linux-firmware 1.127.8 + linux-restricted-modules-3.13.0-40-generic N/A + linux-backports-modules-3.13.0-40-generic N/A + linux-firmware 1.127.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/27/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Roxy dmi.board.vendor: Acer
[Desktop-packages] [Bug 1394653] Re: gpu-manager's xorg.conf generation should be configurable
Can you please attach a xorg.conf that works for you (and a /var/log/Xorg.0.log), so that I can see what's going on? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1394653 Title: gpu-manager's xorg.conf generation should be configurable Status in ubuntu-drivers-common package in Ubuntu: New Bug description: There is no way to edit xorg.conf permanently, for any modification will be removed by gpu-manager. This is not the same issue az bug #1310489. My system is a Dell Inspiron N7110 with nvidia optimus. I use the closed-source nvidia drivers. The problem: After a switch with prime-select intel my xorg.conf is removed, which is required to make the intel config operational. Upon switching back to nvidia (prime-select nvidia) gpu-manager regenerates my xorg.conf The problem is, that the default xorg.conf is broken (does not enable me to use the internal laptop screen), so it needs to be modified. This, however, can not be done now, as changes will always be overwritten. Note the difference from #1310489: We need a way to configure the generation, not just be able to preserve an already present file. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-drivers-common 1:0.2.98.4 Uname: Linux 3.16.1-031601-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 20 17:37:49 2014 InstallationDate: Installed on 2014-03-11 (254 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to utopic on 2014-11-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1394653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
This bug was fixed in the package qtbase-opensource-src - 5.3.2+dfsg- 4ubuntu8 --- qtbase-opensource-src (5.3.2+dfsg-4ubuntu8) vivid; urgency=medium * Pick up one more DBus fix (LP: #1384776): - debian/patches/Break-after-handling-the-read-write.patch qtbase-opensource-src (5.3.2+dfsg-4ubuntu7) vivid; urgency=medium * Pick up upstream 5.3 branch DBus fixes (LP: #1384776) - debian/patches/Always-lock-the-DBus-dispatcher-before-dbus_connecti.patch - debian/patches/Partially-revert-Fix-a-deadlock-introduced-by-the-ra.patch - debian/patches/QDBusConnection-Merge-the-dispatch-and-the-watch-and.patch -- Timo Jyrinki timo-jyri...@ubuntu.com Thu, 27 Nov 2014 13:11:36 + ** Changed in: qtbase-opensource-src (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone Status in network-manager package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: New Bug description: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
** Changed in: unity8 (Ubuntu) Status: In Progress = Invalid ** Changed in: unity8 (Ubuntu RTM) Status: New = Invalid ** Changed in: unity8 (Ubuntu) Assignee: Albert Astals Cid (aacid) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone Status in network-manager package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in unity8 package in Ubuntu RTM: Invalid Bug description: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
Alistair: apparently, the gpu-manager detected zero GPUs on your previous boot (last cards number = 0). I'm not sure why that is. The number of GPUs from last boot is usually available in /var/lib/ubuntu- drivers-common/last_gfx_boot. Is it possible that the said file was removed? As that would explain the zero GPUs statement in the log. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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 CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor:
[Desktop-packages] [Bug 1394653] Re: gpu-manager's xorg.conf generation should be configurable
I've figured out (by looking through the xorg.0.log) that there's a config directory: /usr/share/X11/xorg.conf.d/ where I can put config snippets, so this bug report in the present form is invalid, as there is a way to configure X besides the autogenerated xorg.conf. I've created a file in the xorg.conf.d directory: 90-force-crt to force a virtual display to be recognized by the nvidia card, so i can align my laptop's internal screen to cover this virtual crt, thus being able to the internal screen. 90-force-crt content: Section Screen Identifier nvidia Device nvidia Option AllowEmptyInitialConfiguration on Option IgnoreDisplayDevices EndSection ** Attachment added: generated xorg.conf https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1394653/+attachment/4272021/+files/xorg.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1394653 Title: gpu-manager's xorg.conf generation should be configurable Status in ubuntu-drivers-common package in Ubuntu: New Bug description: There is no way to edit xorg.conf permanently, for any modification will be removed by gpu-manager. This is not the same issue az bug #1310489. My system is a Dell Inspiron N7110 with nvidia optimus. I use the closed-source nvidia drivers. The problem: After a switch with prime-select intel my xorg.conf is removed, which is required to make the intel config operational. Upon switching back to nvidia (prime-select nvidia) gpu-manager regenerates my xorg.conf The problem is, that the default xorg.conf is broken (does not enable me to use the internal laptop screen), so it needs to be modified. This, however, can not be done now, as changes will always be overwritten. Note the difference from #1310489: We need a way to configure the generation, not just be able to preserve an already present file. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-drivers-common 1:0.2.98.4 Uname: Linux 3.16.1-031601-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 20 17:37:49 2014 InstallationDate: Installed on 2014-03-11 (254 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to utopic on 2014-11-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1394653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394653] Re: gpu-manager's xorg.conf generation should be configurable
I must mention that to make things work, I've written a bash script to add and set 1600x900 mode to the virtual crt screen at login, so it matches the resolution of my laptop's screen. The script is the following: (VGA-0 is the non-existent display recognized by the nvidia driver) #!/bin/bash if prime-select query | grep -q nvidia; then if xrandr | grep -q HDMI-0 connected; then xrandr --newmode 1600x900_60.00 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync xrandr --addmode VGA-0 1600x900 xrandr --output VGA-0 --mode 1600x900 fi fi ** Attachment added: xorg.0.log with the above config https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1394653/+attachment/4272028/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1394653 Title: gpu-manager's xorg.conf generation should be configurable Status in ubuntu-drivers-common package in Ubuntu: New Bug description: There is no way to edit xorg.conf permanently, for any modification will be removed by gpu-manager. This is not the same issue az bug #1310489. My system is a Dell Inspiron N7110 with nvidia optimus. I use the closed-source nvidia drivers. The problem: After a switch with prime-select intel my xorg.conf is removed, which is required to make the intel config operational. Upon switching back to nvidia (prime-select nvidia) gpu-manager regenerates my xorg.conf The problem is, that the default xorg.conf is broken (does not enable me to use the internal laptop screen), so it needs to be modified. This, however, can not be done now, as changes will always be overwritten. Note the difference from #1310489: We need a way to configure the generation, not just be able to preserve an already present file. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-drivers-common 1:0.2.98.4 Uname: Linux 3.16.1-031601-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 20 17:37:49 2014 InstallationDate: Installed on 2014-03-11 (254 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to utopic on 2014-11-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1394653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201679] Re: ibus' Super+Space shortcut (usually) doesn't work
Super+space shortcut seems to work fine here now. Can you confirm? ** Changed in: unity Status: Triaged = Incomplete ** Changed in: gnome-settings-daemon (Ubuntu) Status: Triaged = Incomplete ** Changed in: unity (Ubuntu) Status: Triaged = Incomplete ** Changed in: hundredpapercuts Status: Triaged = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1201679 Title: ibus' Super+Space shortcut (usually) doesn't work Status in One Hundred Papercuts: Incomplete Status in Unity: Incomplete Status in gnome-settings-daemon package in Ubuntu: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: 1. Add the ubuntu-desktop PPA on Ubuntu 13.10 Saucy sudo add-apt-repository ppa:ubuntu-desktop/ppa sudo apt-get update sudo apt-get upgrade sudo apt-get install indicator-keyboard 2. Log out and log back in. 2. Open System SettingsRegion Language 3. Switch to the Text Entry tab. 4. Click the + button to add at least two more keyboard layouts. 5. Log out and log back in. 6. Try to use the (new) default Super+Space keyboard shortcut to switch between keyboard layouts. What happens --- Usually, Super+Space is ignored. It worked for me once on login but every other time I tested it didn't work. It works fine in GNOME Shell but not in Unity. gsettings reset org.gnome.settings-daemon.plugins.media-keys switch-input-source seems to be enough to nudge Unity into respecting the Super+Space keyboard shortcut. My guess is that Unity is too aggressive in binding the Super key to itself. Workaround - Shift+Super+Space, the keyboard shortcut to switch backward between keyboard layouts works. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130705.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jul 16 00:28:27 2013 InstallationDate: Installed on 2013-06-14 (31 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Alpha amd64 (20130613) MarkForUpload: True SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1201679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962581] Re: compiz crashed with SIGSEGV in empty() from check_selection() [unity-rvgrid-accessible.cpp:171]
Should be fixed in most recent unity releases. ** Changed in: unity Status: Confirmed = Fix Released ** Changed in: unity (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/962581 Title: compiz crashed with SIGSEGV in empty() from check_selection() [unity- rvgrid-accessible.cpp:171] Status in Unity: Fix Released Status in Unity 5.0 series: Confirmed Status in Unity 6.0 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: on update today ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.6.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 Date: Thu Mar 22 14:41:58 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120201) ProcCmdline: compiz ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity Title: compiz crashed with SIGSEGV in g_main_context_dispatch() 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/962581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394665] Re: internal display does not show up in nvidia-settings nor in xorg.conf, making it unusable
I forgot to mention that I'm using the xorg-edgers ppa, but everything is the same with stock kubuntu and ubuntu 14.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1394665 Title: internal display does not show up in nvidia-settings nor in xorg.conf, making it unusable Status in nvidia-prime package in Ubuntu: New Bug description: I have a Dell Inspiron N7110, with nvidia graphics card. My problem is, that when I try to use my external monitor in a dual display setup via HDMI, the internal screen is unusable. I can mouse over to the internal screen. In KDE I can drag windows there, but otherwise it acts as if it was not part of the desktop. Under unity the whole desktop (both screens) just show some disorted desktop. What I expected to happen: Internal screen shows up in nvidia-settings and I'm able to arrange the displays. What happens: Only the HDMI screen shows up in nvidia-settings (HDMI is rigged to the NVIDIA card, internal display is rigged to intel). I can see and arrange both displays in the display managers, which affects the displays' position, but does not solve the effect described above. More problems: I can modify xorg.conf to force it to crt recognition (remove the line Option IgnoreDisplayDevices CRT from xorg.conf). This causes a phantom crt display to appear in the display manager and the nvidia-settings. If i manage to get this crt overlapping with the internal screen in the display manager, everything looks good. The problem is, everything gets lost when switching to intel, because xorg.conf gets removed. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-prime 0.6.7 Uname: Linux 3.16.1-031601-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 20 17:55:16 2014 InstallationDate: Installed on 2014-03-11 (254 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311) SourcePackage: nvidia-prime UpgradeStatus: Upgraded to utopic on 2014-11-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1394665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394665] Re: internal display does not show up in nvidia-settings nor in xorg.conf, making it unusable
Update: I've managed to get things working, here is what I've done: First I've created a file, 90-force-crt.conf in /usr/share/X11/xorg.conf.d with the following content: Section Screen Identifier nvidia Device nvidia Option AllowEmptyInitialConfiguration on Option IgnoreDisplayDevices EndSection This made sure nvidia recognizes a non-existent display even when xorg.conf is regenerated. Next, using the built in display manager, I've aligned the displays so the HDMI display is on the right and the internal display and the non-existent display are on the left, the internal screen completely overlapping with the virtual display. This worked pretty well, but I had to write a small script to set the resolution of virtual display to match the laptop screen size. The script runs at login and contains the following: #!/bin/bash if prime-select query | grep -q nvidia; then if xrandr | grep -q HDMI-0 connected; then xrandr --newmode 1600x900_60.00 118.25 1600 1696 1856 2112 900 903 908 934 -hsync +vsync xrandr --addmode VGA-0 1600x900 xrandr --output VGA-0 --mode 1600x900 fi fi Now everything works. I'll attach my xorg.0.log created with the above config. ** Attachment added: Xorg.0.conf https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1394665/+attachment/4272037/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1394665 Title: internal display does not show up in nvidia-settings nor in xorg.conf, making it unusable Status in nvidia-prime package in Ubuntu: New Bug description: I have a Dell Inspiron N7110, with nvidia graphics card. My problem is, that when I try to use my external monitor in a dual display setup via HDMI, the internal screen is unusable. I can mouse over to the internal screen. In KDE I can drag windows there, but otherwise it acts as if it was not part of the desktop. Under unity the whole desktop (both screens) just show some disorted desktop. What I expected to happen: Internal screen shows up in nvidia-settings and I'm able to arrange the displays. What happens: Only the HDMI screen shows up in nvidia-settings (HDMI is rigged to the NVIDIA card, internal display is rigged to intel). I can see and arrange both displays in the display managers, which affects the displays' position, but does not solve the effect described above. More problems: I can modify xorg.conf to force it to crt recognition (remove the line Option IgnoreDisplayDevices CRT from xorg.conf). This causes a phantom crt display to appear in the display manager and the nvidia-settings. If i manage to get this crt overlapping with the internal screen in the display manager, everything looks good. The problem is, everything gets lost when switching to intel, because xorg.conf gets removed. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-prime 0.6.7 Uname: Linux 3.16.1-031601-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 20 17:55:16 2014 InstallationDate: Installed on 2014-03-11 (254 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140311) SourcePackage: nvidia-prime UpgradeStatus: Upgraded to utopic on 2014-11-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1394665/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1285977] Re: Ubuntu 14.04 daily build crash after install
Is this bug still exist? We verified Ubuntu 14.04 and 14.10 server version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1285977 Title: Ubuntu 14.04 daily build crash after install Status in compiz package in Ubuntu: New Bug description: Ubuntu Desktop 64-bit 14.04 daily buid 27.02.2014 installing in Microsoft Hyper-V 2008 R2 SP1. After install i'n have crash desktop. See sreenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1285977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 934240] Re: Sometimes title bar doesn't integrate when maximising games.
Please reopen if you can still reproduce it on ubuntu 14.04+. ** Changed in: unity Status: New = Fix Released ** Changed in: unity (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/934240 Title: Sometimes title bar doesn't integrate when maximising games. Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: When maximising windowed OpenGL games... usually the window title bar integrates with the top-bar as expected, but sometimes it does not. After it fails once, this is repeatable. Tested in 12.04 Alpha1 + patches to 16/2/2012 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/934240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390338] Re: No recommanded driver for [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840]
** Changed in: jockey (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1390338 Title: No recommanded driver for [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] Status in HWE Next Project: New Status in jockey package in Ubuntu: New Bug description: This is a system with APU and ATI graphic chip, APU works fine without extra driver. But Jockey does show any drivers for ATI graphic chip, so users are not able to use jockey install driver for this graphic chip. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-common 0.9.7-0ubuntu7.15 ProcVersionSignature: Ubuntu 3.13.0-40.68~precise1-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.8 Architecture: amd64 Date: Thu Nov 6 07:55:40 2014 InstallationMedia: Ubuntu 12.04.5 LTS Precise Pangolin - Release amd64 (20140807.1) MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=2b2e3844-604a-4074-9bbb-9a9e76412c6e ro quiet splash initcall_debug vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 184C dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.34 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd10/17/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr089D1100501020100:rvnHewlett-Packard:rn184C:rvr57.34:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g7 Notebook PC dmi.product.version: 089D1100501020100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1390338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1007501] Re: Applications fail to open
** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1007501 Title: Applications fail to open Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: Dash is not responding to open applications ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dash 0.5.7-2ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 Date: Fri Jun 1 21:26:27 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm LANG=en_IN SHELL=/bin/bash SourcePackage: dash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1007501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1325650] Re: CTRL+F turns search off
In addition to that, old behavior of Ctrl+F used to be to select all text content in search box, so that what you type right after Ctrl+F replaces a previous search. I think this is what is expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1325650 Title: CTRL+F turns search off Status in evince package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy evince evince: Installed: 3.10.3-0ubuntu10 Candidate: 3.10.3-0ubuntu10 Version table: *** 3.10.3-0ubuntu10 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status My problem is that CTRL+F acts as a switch for search mode: it turns it on (when it is off) and off (when it is already on). While this could make sense, I find it quite counter intuitive: * I'm reading a PDF * I want to search foo: I type CTRL+F and foo, it works * I find the occurence of foo I'm interested in * I continue reading, *without leaving the search mode* * at some point, I want to search for bar, so * I type CTRL+F and bar... but CTRL+F just turns off the search mode, and bar is ignored This is quite frustrating. As the search mode can be left with ESC, I suggest to change the behaviour of CTRL+F to setting the focus to the search box, so that CTRL+F *always* results in searching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1325650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1325650] Re: CTRL+F turns search off
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: evince (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1325650 Title: CTRL+F turns search off Status in evince package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy evince evince: Installed: 3.10.3-0ubuntu10 Candidate: 3.10.3-0ubuntu10 Version table: *** 3.10.3-0ubuntu10 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status My problem is that CTRL+F acts as a switch for search mode: it turns it on (when it is off) and off (when it is already on). While this could make sense, I find it quite counter intuitive: * I'm reading a PDF * I want to search foo: I type CTRL+F and foo, it works * I find the occurence of foo I'm interested in * I continue reading, *without leaving the search mode* * at some point, I want to search for bar, so * I type CTRL+F and bar... but CTRL+F just turns off the search mode, and bar is ignored This is quite frustrating. As the search mode can be left with ESC, I suggest to change the behaviour of CTRL+F to setting the focus to the search box, so that CTRL+F *always* results in searching To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1325650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 971805] Re: Unity isn't responsive(?)
** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/971805 Title: Unity isn't responsive(?) Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: I test Ubuntu 12.04 and installed the latest updates. Several problems appear, which could relate to each other: - the Dash doesn't blur its background, though it is set in ccsm - radiotray in the panel doesn't react on scrolling with the mousewheel anymore to change the volume - under attached devices in indicator-session no update appears when plugging in the webcam or scanner I don't know how to research this exactly ... Possibly it's related to Unity?? To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/971805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 856520] Re: Make the Alt-tab explode timer count from when the frame was dislayed, not when it happened
Alt-tab is faster in most recent unity versions. Please reopen it if you can still reproduce the bug. ** Changed in: ayatana-design Status: New = Incomplete ** Changed in: unity Status: New = Invalid ** Changed in: ayatana-design Status: Incomplete = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/856520 Title: Make the Alt-tab explode timer count from when the frame was dislayed, not when it happened Status in Ayatana Design: Invalid Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: In the alt-tab switcher the latency of the Alt-tab switcher frame rate gets quite close to the Alt-tab expanding exploder time out. This means that if you wait until to see which icons is actually highlighted that icon could have exploded into a set of window previews by the time it the seen has seen it. Ideally the exploder timer should be tied to the point at which the frame was displayed. This can be approximated by adding on the current inverse of the current framerate. This would mean that the user always has a consistent and predictable reaction time ceiling, rather than having to keep alt-tabbing ahead just to stop the window display exploding on the off-chance that the current FPS is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/856520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 906472] Re: Emoticons not shown on global menu
Pretty sure it's not a unity bug. Please install and use gnome-classic sessions and try to reproduce the bug. ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/906472 Title: Emoticons not shown on global menu Status in Unity: Incomplete Status in Unity GTK+ module: New Status in empathy package in Ubuntu: Confirmed Status in unity package in Ubuntu: Incomplete Status in unity-gtk-module package in Ubuntu: Confirmed Bug description: Whilst focused on a conversation window, going to Conversation Insert smiley in the global menu, will display a list of blank entires where there should be emoticons. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: empathy 3.2.0.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Mon Dec 19 18:39:11 2011 ExecutablePath: /usr/lib/empathy/empathy-chat InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: empathy UpgradeStatus: Upgraded to oneiric on 2011-11-08 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/906472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286878] Re: Doesn't scale well on a hidpi display
The attachment hidpi_support.patch seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1286878 Title: Doesn't scale well on a hidpi display Status in unity-greeter package in Ubuntu: Triaged Bug description: unity-greeter does not scale on hidpi diplays like the rest of unity does in trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1286878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 926357] Re: Windows can be hidden on another workspace
** Changed in: compiz Status: New = Confirmed ** Changed in: unity Status: New = Confirmed ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: compiz Importance: Undecided = Medium ** Changed in: unity Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/926357 Title: Windows can be hidden on another workspace Status in Compiz: Confirmed Status in One Hundred Papercuts: Invalid Status in Unity: Confirmed Status in compiz package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: What happens: A window can be moved so that just a part of its lower edge is below the bottom boundary of the current workspace (workspace 1). If I later swicth to the workspace below (workspace 2), the window is registered as being on that workspace -- even though the lower edge of the window is hidden by the top panel of workspace 2. This means I can't activate the window by clicking its icon in the Dash; I will have to switch back to workspace 1 before I can interact with the window again. (see attached screenshot) This is a minor annoyance if you are familiar with workspaces. If you, however, accidentally switch workspace this can be really bad, since you do not know how to go back, and the application window will just appear to be gone even though it is still running. The only way for such a user to get back to the application is to restart it, losing potential work in the process. Expected behavior: Clicking the icon of a running applicaiton in the Dash should bring you to the workspace/viewport were it occupies the biggest part of the screen. This way, an application window cannot accidentally disappear. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/926357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364292] Re: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset
I tried the release you asked me to (12.04.0) and it exhibits the same problem. The VGA output works fine when the monitor is plugged in at boot up, but not if plugged in after booting. By the way, I didn't state this before, but the VGA output worked fine under Windows, even when plugged in after booting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1364292 Title: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset Status in xorg package in Ubuntu: Incomplete Bug description: I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege R600-10Q laptop (a model from 2009). I am now trying to display the desktop on a BenQ Senseye3 22 monitor, via the vga output, but it's not working - the monitor says No Signal Detected!. What I've done: I have gone into Screen Display, where I can see the monitor is detected by the laptop. The monitor has a 1920 x 1080 native resolution, which I have tried to use, but I have also set it to lower resolutions, e.g. 1024 x 576. I have tried to use the monitor in dual screen, mirrored and single screen mode - none work. I have tried pressing Fn + F5 to get single screen output - the laptop screen goes blank, but still no output on the monitor. I have tried several monitors (of the same type, and also of a different make), so I don't think it's that. If I plug the vga cable in after boot up, then the monitor receives no signal. WORKAROUND: If, and only if, the monitor was plugged in to the PC's VGA output during boot up, then the display outputs to the monitor correctly. The laptop has the Intel® GS45 Express chipset for graphics acceleration. I installed mesa-utils and ran glxinfo in a terminal. Amongst the output was: OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset Also, in the About This Computer window I see: Graphics: Mobile Intel® GM45 Express Chipset I wonder if the problem is that my chipset is GS45 not GM45. The output of sudo lshw -C video is: *-display:0 description: VGA compatible controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:44 memory:ff40-ff7f memory:e000-efff ioport:cff8(size=8) *-display:1 UNCLAIMED description: Display controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 07 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:ffc0-ffcf ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Tue Sep 2 10:00:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:000c] Subsystem: Toshiba America Info Systems Device [1179:000c] InstallationDate: Installed on 2014-08-28 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA PORTEGE R600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=fe977943-4013-472e-b627-f7184c9e190f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd11/27/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE R600 dmi.product.version: PPR61E-00Q00CEN dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A
Re: [Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
Well it wasn't removed by me. This problem only seems to happen when there is an update for the graphics drivers. This kicks off DKMS on next boot, so perhaps gpu-manager is looking for the driver before DKMS has rebuilt it? On 1 December 2014 at 11:29, Alberto Milone alberto.mil...@canonical.com wrote: Alistair: apparently, the gpu-manager detected zero GPUs on your previous boot (last cards number = 0). I'm not sure why that is. The number of GPUs from last boot is usually available in /var/lib/ubuntu- drivers-common/last_gfx_boot. Is it possible that the said file was removed? As that would explain the zero GPUs statement in the log. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error -- AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] but it changed not the bug of overwriting the xorg.conf. Regards, Uwe 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 NonfreeKernelModules: fglrx .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 CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64
[Desktop-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
me@machine:~/Escritorio$ patch -p1 0001-upowerd-Fix-cleanup-in-up_device_idevice_coldplug-fi.patch [sudo] password for whk: can't find file to patch at input line 20 Perhaps you used the wrong -p or --strip option? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() Status in upower package in Ubuntu: Confirmed Bug description: it looks like nothing happend. When I switch on the PC and after loging in this window with 'report an error/bug' appeard. so I guess it is minor. thanks for doing :) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 Date: Wed Apr 9 15:37:43 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-04-04 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0xb74e9919 service_client_free+25: mov (%esi),%eax PC (0xb74e9919) ok source (%esi) (0x302e) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: upower StacktraceTop: service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 property_list_service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 ?? () g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: upowerd crashed with SIGSEGV in service_client_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 926357] Re: Windows can be hidden on another workspace
** Changed in: compiz (Ubuntu) Status: Confirmed = Invalid ** Changed in: compiz Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/926357 Title: Windows can be hidden on another workspace Status in Compiz: Invalid Status in One Hundred Papercuts: Invalid Status in Unity: Confirmed Status in compiz package in Ubuntu: Invalid Status in unity package in Ubuntu: Confirmed Bug description: What happens: A window can be moved so that just a part of its lower edge is below the bottom boundary of the current workspace (workspace 1). If I later swicth to the workspace below (workspace 2), the window is registered as being on that workspace -- even though the lower edge of the window is hidden by the top panel of workspace 2. This means I can't activate the window by clicking its icon in the Dash; I will have to switch back to workspace 1 before I can interact with the window again. (see attached screenshot) This is a minor annoyance if you are familiar with workspaces. If you, however, accidentally switch workspace this can be really bad, since you do not know how to go back, and the application window will just appear to be gone even though it is still running. The only way for such a user to get back to the application is to restart it, losing potential work in the process. Expected behavior: Clicking the icon of a running applicaiton in the Dash should bring you to the workspace/viewport were it occupies the biggest part of the screen. This way, an application window cannot accidentally disappear. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/926357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397983] [NEW] Slow Single Click Fails to Work
Public bug reported: I already asked about this in Launchpad Question #256474, but with no answer. If I single-click on an Ubuntu Unity Launcher Tile, I expect that to launch the application. It only does so if I can click--release extremely rapidly (less than one tenth of a second - who can measure?). At my normal click--release timing, the action is interpreted as click--hold, so the Tile just wobbles (preliminary to being moved in/from the Launcher) and the application is NOT launched. For personal reasons, I am not able to click--release any faster. There must be many other people (older, handicapped, etc) in the same situation. We need to be able to reset the threshold between click--release and click--hold to get satisfactory functionality with Unity. In the same way everybody can already reset the timing for double-click to suit their equipment physiology. The same problem occurs with Window Menus in Unity (with Menus on Windows) where a slowish single click fails to open the Menu is interpreted as a desire to move the Window. For information, MS Windows 8.1 works perfectly for me, with the same hardware... Ubuntu 14.04.1 unity: Installed: 7.2.2+14.04.20140714-0ubuntu1.1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Dec 1 13:41:47 2014 InstallationDate: Installed on 2014-10-23 (38 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 Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1397983 Title: Slow Single Click Fails to Work Status in unity package in Ubuntu: New Bug description: I already asked about this in Launchpad Question #256474, but with no answer. If I single-click on an Ubuntu Unity Launcher Tile, I expect that to launch the application. It only does so if I can click--release extremely rapidly (less than one tenth of a second - who can measure?). At my normal click--release timing, the action is interpreted as click--hold, so the Tile just wobbles (preliminary to being moved in/from the Launcher) and the application is NOT launched. For personal reasons, I am not able to click--release any faster. There must be many other people (older, handicapped, etc) in the same situation. We need to be able to reset the threshold between click--release and click--hold to get satisfactory functionality with Unity. In the same way everybody can already reset the timing for double-click to suit their equipment physiology. The same problem occurs with Window Menus in Unity (with Menus on Windows) where a slowish single click fails to open the Menu is interpreted as a desire to move the Window. For information, MS Windows 8.1 works perfectly for me, with the same hardware... Ubuntu 14.04.1 unity: Installed: 7.2.2+14.04.20140714-0ubuntu1.1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Dec 1 13:41:47 2014 InstallationDate: Installed on 2014-10-23 (38 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/1397983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397982] [NEW] nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: After kernel update NVIDIA driver displayed the system error ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Mon Dec 1 18:25:43 2014 InstallationDate: Installed on 2014-11-29 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397982 Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: After kernel update NVIDIA driver displayed the system error ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Mon Dec 1 18:25:43 2014 InstallationDate: Installed on 2014-11-29 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311788] Re: compiz lower window:AltButton5 stops working
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1311788 Title: compiz lower window:AltButton5 stops working Status in Compiz: Fix Released Status in Compiz 0.9.11 series: In Progress Status in compiz package in Ubuntu: Fix Released Status in compiz source package in Trusty: Fix Committed Bug description: [Impact] Users who have the horizontal scroll buttons mapped with a modifier such as 'Alt' to other functions using CCSM no longer have working mapped functions. This breaks the user's workflow. [Test case] * Need a mouse with horizontal scrolling, ie, click the mouse wheel left and right. * Open CCSM. * Map a function to the horizontal scroll buttons, ie, buttons 6 7. For example: * Enable workspaces. * CCSM-Viewport Switcher-Desktop-based Viewport Switching * Set Move Next to Alt + button 6 and Move Prev to Alt + button 7. [Regression potential] None identified. Original Description: Since upgrading to 14.04, compiz Lower Window key binding as alt+button5 is no longer working completely. It used to nicely cycle through windows but now if a window surfaces that is scrollable, the 'lower window' command stops responding and the window content starts scrolling vertically even though the alt key is still pressed. Clicking the window and then triggering 'lower window' again causes it to temporarily start working again until another scrollable window surfaces. This is configured under ccsm General Options-Key Bindings-Lower Window. It worked previously in 13.10. I have since tried unity-reset and reverting all compiz settings. Other settings: Click To Focus: off Raise On Click: on Auto-Raise: off Focus Prevention Level: Low I tested a different plugin Opacity, Brightness and Saturation with the same key binding AltButton5 and it does not demonstrate the same behavior; I can tune any window opacity whether the window is scrollable or not. Setting the alternative Lower Window keyboard binding ControlDown works without the same interference. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1311788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397986] [NEW] nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build
Public bug reported: The system reported and error during booting ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Wed Nov 26 11:56:49 2014 InstallationDate: Installed on 2014-06-11 (173 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-29 (32 days ago) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397986 Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Bug description: The system reported and error during booting ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Wed Nov 26 11:56:49 2014 InstallationDate: Installed on 2014-06-11 (173 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-29 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397985] [NEW] File browser crashes moving files
Public bug reported: Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Nautilus crashes very often while trying to move files or folder using the Move to... command located in the right-click menu. In most of the crashes it remains halted without the possibility to reload; it is needed to close the current session and start again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.3 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 1 08:11:46 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-08-12 (110 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-08-12 (110 days ago) usr_lib_nautilus: deja-dup 30.0-0ubuntu4 evince 3.10.3-0ubuntu10.1 file-roller3.10.2.1-0ubuntu4.1 nautilus-share 0.7.3-1ubuntu5 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1397985 Title: File browser crashes moving files Status in nautilus package in Ubuntu: New Bug description: Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Nautilus crashes very often while trying to move files or folder using the Move to... command located in the right-click menu. In most of the crashes it remains halted without the possibility to reload; it is needed to close the current session and start again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.3 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Dec 1 08:11:46 2014 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where'] InstallationDate: Installed on 2014-08-12 (110 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-08-12 (110 days ago) usr_lib_nautilus: deja-dup 30.0-0ubuntu4 evince 3.10.3-0ubuntu10.1 file-roller3.10.2.1-0ubuntu4.1 nautilus-share 0.7.3-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1397985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 927826] Re: When a folder bookmarked in Nautilus is deleted, it doesn't disappear in the Unity quicklist inmediatelly
** Changed in: nautilus (Ubuntu) Status: New = Invalid ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid ** Changed in: nautilus (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/927826 Title: When a folder bookmarked in Nautilus is deleted, it doesn't disappear in the Unity quicklist inmediatelly Status in Unity: Invalid Status in nautilus package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: When I delete a folder bookmarked in Nautilus, it still appears in the Unity quicklist inmediatelly, but disappears after a while. I don't know how long it takes to disappear ;). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-12.21-generic-pae 3.2.2 Uname: Linux 3.2.0-12-generic-pae i686 .tmp.unity.support.test.0: ApportVersion: 1.91-0ubuntu1 Architecture: i386 CasperVersion: 1.303 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,grid,imgpng,mousepoll,move,place,regex,resize,session,snap,vpswitch,wall,animation,expo,ezoom,fade,scale,unityshell,workarounds] CompositorRunning: compiz Date: Mon Feb 6 19:15:31 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2000] Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2000] LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120201.1) MachineType: Olidata Chile S.A. A1xIM0 ProcEnviron: PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=es keyboard-configuration/layoutcode=latam SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.04 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A1xIM0 dmi.board.vendor: Olidata Chile S.A. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Olidata Chile S.A. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.04:bd02/23/2010:svnOlidataChileS.A.:pnA1xIM0:pvrToBeFilledByO.E.M.:rvnOlidataChileS.A.:rnA1xIM0:rvrTobefilledbyO.E.M.:cvnOlidataChileS.A.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: A1xIM0 dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata Chile S.A. version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.11.3-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901-1ubuntu3 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/927826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397982] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build
*** This bug is a duplicate of bug 1268257 *** https://bugs.launchpad.net/bugs/1268257 ** This bug has been marked a duplicate of bug 1268257 nvidia-331-updates 331.38-0ubuntu3: nvidia-331-updates kernel module failed to build, with only error: objdump: '... .tmp_nv.o': No such file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397982 Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: New Bug description: After kernel update NVIDIA driver displayed the system error ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Mon Dec 1 18:25:43 2014 InstallationDate: Installed on 2014-11-29 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1397986] Re: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-331-updates (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1397986 Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build Status in nvidia-graphics-drivers-331-updates package in Ubuntu: Confirmed Bug description: The system reported and error during booting ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates-uvm 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Wed Nov 26 11:56:49 2014 InstallationDate: Installed on 2014-06-11 (173 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates-uvm 331.89-0ubuntu5: nvidia-331-updates-uvm kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-10-29 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1397986/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 937300] Re: Make maximised window button controls appear in line with left window margin, use space above launcher for launcher toggle switch
It's has already been largely discussed somewhere else (can't find where now). Marking as invalid. ** Changed in: ayatana-design Status: New = Invalid ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/937300 Title: Make maximised window button controls appear in line with left window margin, use space above launcher for launcher toggle switch Status in Ayatana Design: Invalid Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: I apologise for the lengthy summary, this is the first bug I've ever opened here. And it is a bug IMHO, a design bug more precisely. When using maximised application windows, and with the launcher being set to permanently show, the button controls intentionally don't show in line with the left application window margin, but above the launcher. I've seen that especially novice users are confused by the window controls being placed strangely away from the window to which they're supposed to belong to (even more the bigger the launcher size). I understand that the devs want to have some coherence with the dash window controls being placed at the same spot (which now sport the same looks as the application window controls), but I think this only adds to confusion. Launcher and applications are just of a different kind. My proposal is to use the freed up space above the launcher for an auto-hide/permanent show launcher toggle switch. This could provide for a quick and intuitive way to pin or unpin the launcher to the desktop - most novice users wouldn't know that they can also find this functionality in the system settings, and it would even be handy for the more advanced when they need more screen width once in a time. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/937300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 932688] Re: Unity 3D causes video apps to malfunction
Is this still an issue? ** Changed in: unity Status: New = Incomplete ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/932688 Title: Unity 3D causes video apps to malfunction Status in Unity: Incomplete Status in nvidia-graphics-drivers package in Ubuntu: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: I am getting very weird behavior: - starting XBMC results in XBMC maxing out one of my cores and the XBMC UI is unresponsive (updates once in several seconds, at best) - if XBMC started normally, toggling fullscreen/window mode will make it exhibit the above behavior - after toggling fullscreen/window the screen/window will sometime contain garbage - TV-MAXE, uses VLC as backend, works normally while not in fullscreen. When I switch it to fullscreen I get a blank screen or a static video frame. - totem works normally while not in fullscreen. When I switch it to fullscreen I get a blank screen or a static video frame (usually the video frame is in the top left corner, unresized, and the rest of the screen is blank). This has been happening from the start on Oneiric with unity and nvidia proprietary drivers from the stock versions up to unity 5.0.0 and nvidia drivers 295.20. All these apps function properly under Gnome Shell and Unity 2D. I have run out of ideas on what I can do/try to be able to use Unity 3D and these apps together. I think there's a good chance this bug might be present in the current development version of unity in precise and would hate it if Precise would be released with this bug still present. --- .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 295.20 Mon Feb 6 21:07:30 PST 2012 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) .tmp.unity.support.test.0: ApportVersion: 1.23-0ubuntu4 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,copytex,place,move,snap,commands,imgpng,regex,animation,vpswitch,mousepoll,wall,gnomecompat,workarounds,session,grid,resize,compiztoolbox,expo,fade,ezoom,scale,unityshell] CompositorRunning: None DistUpgraded: Log time: 2011-11-22 12:43:23.029973 DistroCodename: oneiric DistroRelease: Ubuntu 11.10 DistroVariant: ubuntu DkmsStatus: nvidia-current, 295.20, 3.0.0-16-generic, x86_64: installed virtualbox, 4.1.2, 3.0.0-16-generic, x86_64: installed GraphicsCard: nVidia Corporation G73 [GeForce 7600 GT] [10de:0391] (rev a1) (prog-if 00 [VGA controller]) Subsystem: LeadTek Research Inc. Device [107d:209c] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia Package: unity 5.0.0+bzr1879ubuntu0+622 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-16-generic root=UUID=bdd0f7f0-e92e-40fb-989d-7daec91beae7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Tags: oneiric running-unity oneiric running-unity oneiric running-unity ubuntu Uname: Linux 3.0.0-16-generic x86_64 UnreportableReason: This is not a genuine Ubuntu package UpgradeStatus: Upgraded to oneiric on 2012-01-30 (15 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare XorgConf: Section Device Identifier Default Device Option NoLogoTrue EndSection dmi.bios.date: 09/30/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1238 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B-Deluxe 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.:bvr1238:bd09/30/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B-Deluxe: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.6+bzr20110929-0ubuntu6.1 version.ia32-libs: ia32-libs 20090808ubuntu26 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
[Desktop-packages] [Bug 943813] Re: unity crashed with SIGSEGV
Seems like cairo releated. It's an old bug and without duplicated. Marking as invalid. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/943813 Title: unity crashed with SIGSEGV Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: 1. opened dash menu 2. inserted usb-flash unity freezed 3. after removing flash unity/compiz were restarted ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.93-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Thu Mar 1 08:44:32 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120228) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0xb3f4a558:or %bh,(%ecx) PC (0xb3f4a558) ok source %bh ok destination (%ecx) (0x0014) 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/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 ?? () from /usr/lib/i386-linux-gnu/libcairo.so.2 Title: compiz crashed with SIGSEGV 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/943813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 946527] Re: compiz crashed with SIGSEGV in operator nux::Property, int, float, int() (MouseOverTopScrollArea)
It's an old bug withoud duplicated. I think it's safe to close it. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/946527 Title: compiz crashed with SIGSEGV in operator nux::Property, int, float, int() (MouseOverTopScrollArea) Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: couldn't click on dash icons run unity - reset from remote ssh session and received this error during reset procedure reset completed ok and icons on dash are now clickable ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 1.94-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sun Mar 4 18:09:43 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: compiz --replace ProcEnviron: LANGUAGE=en_GB:en TERM=xterm LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb4798514 _ZN5unity8launcher8Launcher22MouseOverTopScrollAreaEv+20: fildl 0x14(%eax) PC (0xb4798514) ok source 0x14(%eax) (0x0014) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: unity::launcher::Launcher::MouseOverTopScrollArea() () from /usr/lib/compiz/libunityshell.so unity::launcher::Launcher::OnScrollTimeout(void*) () from /usr/lib/compiz/libunityshell.so ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: compiz crashed with SIGSEGV in unity::launcher::Launcher::MouseOverTopScrollArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XsessionErrors: EggSMClient-CRITICAL **: egg_sm_client_set_mode: assertion `global_client == NULL || global_client_mode == EGG_SM_CLIENT_MODE_DISABLED' failed gnome-session[3092]: WARNING: Application 'compiz.desktop' killed by signal To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/946527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 948017] Re: compiz crashed with SIGSEGV in empty()
This code path no longer exists. It's safe to close this bug. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/948017 Title: compiz crashed with SIGSEGV in empty() Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: Unity crashed when Im create new profile in compizconfig. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 ApportVersion: 1.94-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Tue Mar 6 20:40:10 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb4728795 _ZN5unity5panel10Controller4Impl10GetTrayXidEv+21:mov(%edx),%ecx PC (0xb4728795) ok source (%edx) (0x0028) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: unity::panel::Controller::Impl::GetTrayXid() () from /usr/lib/compiz/libunityshell.so unity::panel::Controller::GetTrayXid() () from /usr/lib/compiz/libunityshell.so unity::UnityWindow::glPaint(GLWindowPaintAttrib const, GLMatrix const, CompRegion const, unsigned int) () from /usr/lib/compiz/libunityshell.so GLWindow::glPaint(GLWindowPaintAttrib const, GLMatrix const, CompRegion const, unsigned int) () from /usr/lib/compiz/libopengl.so PrivateGLScreen::paintOutputRegion(GLMatrix const, CompRegion const, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so Title: compiz crashed with SIGSEGV in unity::panel::Controller::Impl::GetTrayXid() 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/948017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950702] Re: unity-panel-service crashed with SIGSEGV in quark_strdup()
It's an old bug without duplicates. It's safe to close it. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/950702 Title: unity-panel-service crashed with SIGSEGV in quark_strdup() Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: occured after installing ati driver and system restart ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-services 5.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 1.94.1-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Sun Mar 4 17:34:57 2012 DistUpgraded: Log time: 2012-03-01 22:24:15.556757 DistroCodename: precise DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service GraphicsCard: Advanced Micro Devices [AMD] nee ATI Whistler [AMD Radeon HD 6600M Series] [1002:6741] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:050e] InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20111005) JockeyStatus: xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) xorg:fglrx - ATI/AMD proprietary FGLRX graphics driver (Proprietary, Enabled, In use) MachineType: Acer Aspire 7750G ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) TERM=xterm LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic-pae root=UUID=ac575190-9fec-4c9b-aa08-3621dc13625b ro elevator=noop SegvAnalysis: Segfault happened at: 0xb6e41fb4 g_quark_from_string+436: jmp 0xb6e41eb2 g_quark_from_string+178 PC (0xb6e41fb4) ok source 0xb6e41eb2 (0xb6e41eb2) ok SP (0xbf9aa8d0) ok Reason could not be automatically determined. Signal: 11 SourcePackage: unity Stacktrace: #0 0xb6e41fb4 in g_quark_from_string () from /lib/i386-linux-gnu/libglib-2.0.so.0 No symbol table info available. #1 0x in ?? () No symbol table info available. StacktraceTop: g_quark_from_string () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: unity-panel-service crashed with SIGSEGV in g_quark_from_string() UpgradeStatus: Upgraded to precise on 2012-03-01 (7 days ago) UserGroups: dmi.bios.date: 05/24/2011 dmi.bios.vendor: Acer dmi.bios.version: V1.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE70_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnAcer:bvrV1.11:bd05/24/2011:svnAcer:pnAspire7750G:pvrV1.11:rvnAcer:rnJE70_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11: dmi.product.name: Aspire 7750G dmi.product.version: V1.11 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.7.0~bzr2995-0ubuntu5 version.fglrx-installer: fglrx-installer N/A version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/950702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398000] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
Public bug reported: Apport reported the bug. I did not experience any problems. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Mon Dec 1 14:29:14 2014 InstallationDate: Installed on 2014-10-05 (57 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-11-03 (27 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1398000 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in nvidia-graphics-drivers-331 package in Ubuntu: New Bug description: Apport reported the bug. I did not experience any problems. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 DKMSKernelVersion: 3.16.0-25-generic Date: Mon Dec 1 14:29:14 2014 InstallationDate: Installed on 2014-10-05 (57 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: Upgraded to utopic on 2014-11-03 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1398000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 510625] Re: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english.
** Changed in: duplicity Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/510625 Title: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english. Status in Duplicity - Bandwidth Efficient Encrypted Backup: Confirmed Status in duplicity package in Ubuntu: Confirmed Status in duplicity package in Debian: Confirmed Bug description: this is a forward/extract of debian bug #565398, which lives over there: http://bugs.debian.org/565398 summary: when using gpg and --encrypt-key, and only if LANG is set to de_AT and LC_CTYPE is set to de_AT (or POSIX or C, but not iso-8859-1 or utf-8), then incremental backups fail completely. somehow or other duplicity mis-interprets gnupg output and errors out: i assume it would be the 8-bit nature of certain phrases like Schlüssel (german for key) which causes the mess, but i can't identify the code in question. reproducible: always. needs only an empty backup dir (source), an empty target dir (target), a gpg key and locale de_AT available. duplicity --encrypt-key KEYID source file://target works fine, creates a (minuscule) full backup running it again, with LANG unset (or to something purely 7bit like en_US) works perfect again, no problems. but running it with LANG=de_AT and LC_CTYPE=de_AT causes duplicity to attempt some gnupg decryption (of what? the cache and archive are in sync), and it dies with a gpg failure (with the gpg message being the german equivalent of encryption failed: bad passphrase, not surprising as no passphrase was given, nor should one be necessary). i'm attaching the relevant -v9 logs, first of the successful full run, then of a failed inc run (LANG and LC_CTYPE=de_AT) and then of the successful inc run (LANG=, LC_CTYPE=de_AT). no changes were made to the source dir between runs. regards, az To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/510625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 953434] Re: compiz crashed with SIGSEGV in std::basic_streambufchar, std::char_traitschar ::xsputn()
Old bug without duplicates. Closing it. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/953434 Title: compiz crashed with SIGSEGV in std::basic_streambufchar, std::char_traitschar ::xsputn() Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: had just completed update and re-booted. was using firefox at the time of the crash. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9 Uname: Linux 3.2.0-18-generic-pae i686 NonfreeKernelModules: fglrx ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 12 21:05:20 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20111220) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb73ef2f6:rep movsl %ds:(%esi),%es:(%edi) PC (0xb73ef2f6) ok source %ds:(%esi) (0x0b17207b) not located in a known VMA region (needed readable region)! destination %es:(%edi) (0xa751d463) ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () std::basic_streambufchar, std::char_traitschar ::xsputn(char const*, int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 std::basic_ostreamchar, std::char_traitschar std::__ostream_insertchar, std::char_traitschar (std::basic_ostreamchar, std::char_traitschar , char const*, int) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 unity::IconLoader::Impl::Hash(std::string const, unsigned int) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in std::basic_streambufchar, std::char_traitschar ::xsputn() UpgradeStatus: Upgraded to precise on 2012-02-17 (24 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/953434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962526] Re: Unity crash (reproduced)
Cannot reproduce on unity 7+ ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/962526 Title: Unity crash (reproduced) Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: While performing tests: * Open application (any will do) * Right click on top bar * Move to workspace left|right|top|down * Go to that workspace * Right on top bar again * Select Move to Another Workspace - click any * BOOM Restarted with $ unity /dev/null disown Did the same thing again, and with different applications, same problem! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+10ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Thu Mar 22 19:53:17 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8243] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: System manufacturer P5K ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-20-generic root=UUID=f4e3f738-e5b9-4dce-bcda-0b6546e87126 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to precise on 2012-03-22 (0 days ago) dmi.bios.date: 10/14/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5K 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.:bvr1201:bd10/14/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5K dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.7.2-0ubuntu1~ppa2 version.ia32-libs: ia32-libs 20090808ubuntu35 version.libdrm2: libdrm2 2.4.30-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/962526/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 963067] Re: Atfter upgrading or updating lastest recomended software in ubuntu 10.10, surfing the net has slowed down and opening apt. usually become slow and freeze up. having
** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/963067 Title: Atfter upgrading or updating lastest recomended software in ubuntu 10.10, surfing the net has slowed down and opening apt. usually become slow and freeze up. having to always reboot and problem always repeats. Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: Ubuntu 10.10 was release last year , the package is from software center and was one the the recommended udates to install., nothing else I can think of to further add, Thanks. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: unity 4.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic i686 .tmp.unity.support.test.1: ApportVersion: 1.23-0ubuntu4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Mar 23 08:21:06 2012 DistUpgraded: Log time: 2011-10-14 16:37:59.792169 DistroCodename: oneiric DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device [8086:2562] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:5641] InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=b58d8699-4ead-4b79-a2e1-3110a87f987a ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to oneiric on 2012-03-21 (1 days ago) dmi.bios.date: 02/16/2004 dmi.bios.vendor: Intel Corp. dmi.bios.version: VA84510A.86A.0030.P10.0402160229 dmi.board.name: D845GVSR dmi.board.vendor: Intel Corporation dmi.board.version: AAC44953-300 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrVA84510A.86A.0030.P10.0402160229:bd02/16/2004:svn:pn:pvr:rvnIntelCorporation:rnD845GVSR:rvrAAC44953-300:cvn:ct2:cvr: version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1 version.libdrm2: libdrm2 2.4.26-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3 version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/963067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 962882] Re: Unity becomes unusable after trying to maximize a window with Alt+F10
Alt+F10 opens the menu. Also I'm closing the bug, please reopen if you can still reproduce it. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Opinion ** Changed in: unity (Ubuntu) Status: Opinion = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/962882 Title: Unity becomes unusable after trying to maximize a window with Alt+F10 Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: Whenever I try to maximize a window with the keyboard (using Alt+F10), at first the shortcut doesn't work/opens the application menu, then after some tries Unity goes to a weird state where I cannot click/type anywhere. I can only move the mouse and that highlights the application menu labels (as if the menu was open, but it's not). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.6.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CheckboxSubmission: 09dbd627e3fe3b084ce04f5a0f0c32a6 CheckboxSystem: b8f3ec504801f13fc208edb5c785b099 CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,imgpng,regex,unitymtgrabhandles,animation,resize,workarounds,snap,place,move,vpswitch,grid,mousepoll,gnomecompat,expo,session,ezoom,wall,fade,scale,unityshell] Date: Fri Mar 23 09:24:01 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110922) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-02-21 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/962882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1398008] [NEW] Caps. Lock LED keyboard indicator not working
Public bug reported: Ubuntu Trusty running on an Apple MacBook 4,1 (white, early 2008) Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Caps. Lock keyboard LED indicator remains always off even if the lock its activated and working properly when writing. This issue doesn't happens when in the session log screen. There it always works fine. Issue starts when loggin into my session account. I've 2 GB RAM, 4 GB SWAP space, /home and SWAP are encrypted. Please let me know if you ned further information. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 1 08:58:24 2014 DistUpgraded: 2014-08-12 15:32:20,840 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00a1] Subsystem: Apple Inc. Device [106b:00a1] InstallationDate: Installed on 2014-08-12 (110 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: Apple Inc. MacBook4,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=bed91342-3e5e-483d-af89-b95cc986250e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-08-12 (110 days ago) dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB41.88Z.00C1.B00.0802091535 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788A9 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788A9 dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: dmi.product.name: MacBook4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 1 08:25:50 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40031 vendor APP xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1398008 Title: Caps. Lock LED keyboard indicator not working Status in xorg package in Ubuntu: New Bug description: Ubuntu Trusty running on an Apple MacBook 4,1 (white, early 2008) Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Caps. Lock keyboard LED indicator remains always off even if the lock its activated and working properly when writing. This issue doesn't happens when in the session log screen. There it always works fine. Issue starts when loggin into my session account. I've 2 GB RAM, 4 GB SWAP space, /home and SWAP are encrypted. Please let me know if you ned further information. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins:
[Desktop-packages] [Bug 987295] Re: package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lirc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lirc in Ubuntu. https://bugs.launchpad.net/bugs/987295 Title: package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in lirc package in Ubuntu: Confirmed Bug description: Have had multiple update problems with lirc failing I am not compitent to expand or comment on specific details ProblemType: Package DistroRelease: Ubuntu 12.04 Package: lirc 0.9.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 Date: Mon Apr 23 01:02:50 2012 DuplicateSignature: Setting up lirc (0.9.0-0ubuntu1) ... /var/lib/dpkg/info/lirc.postinst: 4: /etc/lirc/hardware.conf: I: not found dpkg: error processing lirc (--configure): subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 SourcePackage: lirc Title: package lirc 0.9.0-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: Upgraded to precise on 2012-03-26 (27 days ago) mtime.conffile..etc.lirc.hardware.conf: 2010-05-30T16:31:14 mtime.conffile..etc.lirc.lircd.conf: 2010-05-30T16:31:14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lirc/+bug/987295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364292] Re: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset
** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1364292 Title: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset Status in xorg package in Ubuntu: Incomplete Bug description: I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege R600-10Q laptop (a model from 2009). I am now trying to display the desktop on a BenQ Senseye3 22 monitor, via the vga output, but it's not working - the monitor says No Signal Detected!. What I've done: I have gone into Screen Display, where I can see the monitor is detected by the laptop. The monitor has a 1920 x 1080 native resolution, which I have tried to use, but I have also set it to lower resolutions, e.g. 1024 x 576. I have tried to use the monitor in dual screen, mirrored and single screen mode - none work. I have tried pressing Fn + F5 to get single screen output - the laptop screen goes blank, but still no output on the monitor. I have tried several monitors (of the same type, and also of a different make), so I don't think it's that. If I plug the vga cable in after boot up, then the monitor receives no signal. WORKAROUND: If, and only if, the monitor was plugged in to the PC's VGA output during boot up, then the display outputs to the monitor correctly. The laptop has the Intel® GS45 Express chipset for graphics acceleration. I installed mesa-utils and ran glxinfo in a terminal. Amongst the output was: OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset Also, in the About This Computer window I see: Graphics: Mobile Intel® GM45 Express Chipset I wonder if the problem is that my chipset is GS45 not GM45. The output of sudo lshw -C video is: *-display:0 description: VGA compatible controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:44 memory:ff40-ff7f memory:e000-efff ioport:cff8(size=8) *-display:1 UNCLAIMED description: Display controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 07 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:ffc0-ffcf ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Tue Sep 2 10:00:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:000c] Subsystem: Toshiba America Info Systems Device [1179:000c] InstallationDate: Installed on 2014-08-28 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA PORTEGE R600 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=fe977943-4013-472e-b627-f7184c9e190f ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.60 dmi.board.asset.tag: 00 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd11/27/2008:svnTOSHIBA:pnPORTEGER600:pvrPPR61E-00Q00CEN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE R600 dmi.product.version: PPR61E-00Q00CEN dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 963571] Re: compiz crashed with SIGSEGV in sigc::internal::trackable_callback_list::remove_callback()
Unity QuickList code changed in the last years. The bug should be gone. Closing it. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/963571 Title: compiz crashed with SIGSEGV in sigc::internal::trackable_callback_list::remove_callback() Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: Using Precise on an usb key build with unetbootin ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6 Uname: Linux 3.2.0-17-generic-pae i686 ApportVersion: 1.93-0ubuntu2 Architecture: i386 CasperVersion: 1.305 Date: Fri Mar 23 23:47:11 2012 ExecutablePath: /usr/bin/compiz LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120301) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb71c4476 _ZN4sigc8internal23trackable_callback_list15remove_callbackEPv+38:cmp %edx,0x8(%esi) PC (0xb71c4476) ok source %edx ok destination 0x8(%esi) (0x0018) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: sigc::internal::trackable_callback_list::remove_callback(void*) () from /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 sigc::trackable::remove_destroy_notify_callback(void*) const () from /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 sigc::internal::typed_slot_repsigc::bind_functor-1, sigc::bound_mem_functor4nux::BaseTexture*, unity::dash::ResultRendererTile, std::string const, int, int, _GdkPixbuf*, _GdkPixbuf*, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil, sigc::nil ::destroy(void*) () from /usr/lib/compiz/libunityshell.so sigc::slot_base::~slot_base() () from /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 unity::dash::ResultRendererTile::IconLoaded(std::string const, unsigned int, _GdkPixbuf*, std::string, unity::dash::Result) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in sigc::internal::trackable_callback_list::remove_callback() 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/963571/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964092] Re: Super key and Alt+F2 do not show same list, yet look the same visually
That's the wanted design. Closing the bug. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/964092 Title: Super key and Alt+F2 do not show same list, yet look the same visually Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: This bug affects Unity in Ubuntu 12.04 Beta. To repeat: - Press Super key and do a search for an application (firefox for example): a list of applications show up. Dismiss with Esc - Now press Alt+F2 and do a search for application (firefox for example): a list of most recently used applications show up. - Visually they both look and fee the same but behave very differently. This is potentially very confusing to power users. In the example above there is no confusion between the two prompts, however if you are searching for AMD Catalyst Control Centre then the results are different and confusing. AMD Catalyst Control Centre only starts when the Super key prompt was used, but for some reason it does not start when Alt+F2 prompt was used (even the commands displayed are different). The same confusion can be observed with the Chromium brower, entering the first few chars of chromium with the Super key prompt works fine but it does not with the Alt+F2 prompt (even though the entire word chromium is entered). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/964092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964298] Re: unity-panel-service crashed with SIGSEGV
Incomplete stackstrace, also old bug. Closing it. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/964298 Title: unity-panel-service crashed with SIGSEGV Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: I was watching a music video with vlc player when this error displayed itself. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity-services 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,compiztoolbox,grid,imgpng,place,gnomecompat,resize,move,vpswitch,session,mousepoll,animation,unitymtgrabhandles,workarounds,wall,wobbly,expo,fade,scale,ezoom,unityshell] CompositorRunning: compiz Date: Sat Mar 24 22:31:26 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExecutablePath: /usr/lib/unity/unity-panel-service InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: Acer, inc. Aspire 4720Z ProcCmdline: /usr/lib/unity/unity-panel-service ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=24cdd675-c111-4900-8a6a-1c44df3fa040 ro quiet splash vt.handoff=7 SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: unity-panel-service crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/18/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3808 dmi.board.name: Nestos dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3808:bd02/18/2008:svnAcer,inc.:pnAspire4720Z:pvrNotApplicable:rvnAcer,Inc.:rnNestos:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 4720Z dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz 1:0.9.7.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/964298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964282] Re: compiz unity crashes in intelCopyPixels
** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/964282 Title: compiz unity crashes in intelCopyPixels Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: COMPIZ / UNITY Crashes on load/a few moments after load Here is the log created by compiz Leyendo símbolos desde /usr/bin/compiz...(no se encontraron símbolos de depuración)hecho. Adjuntando al programa: /usr/bin/compiz, process 5449 Leyendo símbolos desde /usr/lib/libcompiz_core.so.ABI-20120305...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/libcompiz_core.so.ABI-20120305 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libstdc++.so.6...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libstdc++.so.6 Leyendo símbolos desde /lib/i386-linux-gnu/libgcc_s.so.1...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /lib/i386-linux-gnu/libgcc_s.so.1 Leyendo símbolos desde /lib/i386-linux-gnu/libc.so.6...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /lib/i386-linux-gnu/libc.so.6 Leyendo símbolos desde /lib/i386-linux-gnu/libpthread.so.0...(no se encontraron símbolos de depuración)hecho. [Depuración de hilo usando libthread_db enabled] Using host libthread_db library /lib/i386-linux-gnu/libthread_db.so.1. [Nuevo Thread 0xac455b40 (LWP 5492)] [Nuevo Thread 0xb34ffb40 (LWP 5486)] [Nuevo Thread 0xb3ecab40 (LWP 5484)] [Nuevo Thread 0xb7016b40 (LWP 5450)] Símbolos cargados para /lib/i386-linux-gnu/libpthread.so.0 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libX11.so.6...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libX11.so.6 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libXrandr.so.2...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libXrandr.so.2 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libXinerama.so.1...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libXinerama.so.1 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libXext.so.6...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libXext.so.6 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libICE.so.6...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libICE.so.6 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libSM.so.6...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libSM.so.6 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libglibmm-2.4.so.1...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libglibmm-2.4.so.1 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libsigc-2.0.so.0...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libsigc-2.0.so.0 Leyendo símbolos desde /lib/i386-linux-gnu/libglib-2.0.so.0...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /lib/i386-linux-gnu/libglib-2.0.so.0 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libstartup-notification-1.so.0...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libstartup-notification-1.so.0 Leyendo símbolos desde /lib/i386-linux-gnu/libdl.so.2...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /lib/i386-linux-gnu/libdl.so.2 Leyendo símbolos desde /lib/i386-linux-gnu/libm.so.6...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /lib/i386-linux-gnu/libm.so.6 Leyendo símbolos desde /lib/ld-linux.so.2...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /lib/ld-linux.so.2 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libxcb.so.1...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libxcb.so.1 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libXrender.so.1...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libXrender.so.1 Leyendo símbolos desde /lib/i386-linux-gnu/libuuid.so.1...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /lib/i386-linux-gnu/libuuid.so.1 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libgobject-2.0.so.0...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Leyendo símbolos desde /usr/lib/i386-linux-gnu/libgmodule-2.0.so.0...(no se encontraron símbolos de depuración)hecho. Símbolos cargados para
[Desktop-packages] [Bug 965214] Re: Hitting TAB on dash does not reveal the next lens.
That's the wanted behavior! Closing the bug. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/965214 Title: Hitting TAB on dash does not reveal the next lens. Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: In Ubuntu 11.10 hitting TAB while dash is open used to reveal the next lens and the arrow keys were used to maneuver through the lens page. However, in Ubuntu 12.04 both TAB and arrow keys are used for similar purpose and now we must either have to come down by arrow keys or exclusively use mouse to switch lenses. It makes it harder to switch lenses using keyboard. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,move,resize,imgpng,vpswitch,place,gnomecompat,grid,compiztoolbox,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,wobbly,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Mon Mar 26 17:48:08 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120315) MachineType: Dell Inc. Inspiron 1525 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=0be1edf2-88f6-467a-8b42-0b5db7bfc269 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/965214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 964807] Re: Shortcut markers remain on Unity Launcher after releasing the Super key
Fixed some months ago. Cannot find a duplicate right now. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Opinion ** Changed in: unity (Ubuntu) Status: Opinion = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/964807 Title: Shortcut markers remain on Unity Launcher after releasing the Super key Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: Ways to reproduce this bug: 1. While holding Super down, press W once. Release the Super key. Again, hold Super down, and press W once. Release the Super key. 2. While holding Super down, press W twice or press S twice. Release the Super key. 3. While holding Super down, press an undefined shortcut key (such as Q, E, R, Y, U, I, etc.) once. Release the Super key. Somehow, the markers on the launcher remain. I expected the markers to go away. By markers on the launcher, I mean the 1, 2, 3, etc. on the applications, S on the switcher, and T on the trash. I'm using 12.4 LTS beta (precise) and reporting a bug on unity. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Sun Mar 25 14:58:11 2012 DistUpgraded: 2012-03-25 13:42:10,044 DEBUG enabling apt cron job DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 4294CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=607270ec-3c8a-4263-963c-39df0bb70b09 ro quiet quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to precise on 2012-03-25 (0 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4294CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4294CTO:pvrThinkPadX220Tablet:rvnLENOVO:rn4294CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4294CTO dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.7.2-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/964807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 966200] Re: Guake has no tooltip, unlike other apps in the launcher
Guake should not appear on the launcher. Fixed in 14.04+ ** Changed in: unity (Ubuntu) Status: New = Invalid ** Changed in: unity Status: New = Opinion ** Changed in: unity Status: Opinion = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/966200 Title: Guake has no tooltip, unlike other apps in the launcher Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: unity 5.8.0-0ubuntu2, Ubuntu Pangolin 1. In Ubuntu Software Center, install Guake Terminal. 2. Once it has installed, mouse over its launcher tile. What happens: Nothing. What should happen: either * Guake should have the tooltip Guake Terminal, or * other applications in the launcher shouldn't have tooltips either. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/966200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 965756] Re: compiz crashed with SIGSEGV in _M_data() (unity::UBusManager::UnregisterInterest)
That code path is gone. Closing the bug. ** Changed in: unity Status: New = Invalid ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/965756 Title: compiz crashed with SIGSEGV in _M_data() (unity::UBusManager::UnregisterInterest) Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Bug description: I do not know what happened. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: unity 5.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Mar 26 23:59:16 2012 ExecutablePath: /usr/bin/compiz InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcCmdline: compiz SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity Title: compiz crashed with SIGSEGV in unity::UBusManager::UnregisterInterest() 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/965756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1342312] Re: ghostscript hangs reading certain pdfs
I have the same problem on Ubuntu 14.04 LTS, take a look at this bug report: http://bugs.ghostscript.com/show_bug.cgi?id=694811 The infinite loop occurs on line 2256 in base/gdevp14.c, see the attached patch. It's already fixed on 14.10. ** Bug watch added: Ghostscript (AFPL) Bugzilla #694811 http://bugs.ghostscript.com/show_bug.cgi?id=694811 ** Patch added: overprint-infinite-loop.patch https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1342312/+attachment/4272164/+files/overprint-infinite-loop.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1342312 Title: ghostscript hangs reading certain pdfs Status in ghostscript package in Ubuntu: Confirmed Bug description: On a few pdfs, gs hangs and uses 100% cpu forever. This could be used as a denial of service through imagemagick which uses ghostscript as a delegate, and commonly used in php etc... which is how I found the issue. The packages from utopic (9.14~dfsg-0ubuntu3) processes these pdfs correctly. To reproduce: gs WaddellAndReedJCL0814ThirdHProvSE.pdf ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ghostscript 9.10~dfsg-0ubuntu10.2 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity Date: Tue Jul 15 14:34:26 2014 InstallationDate: Installed on 2014-04-20 (86 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Lpstat: device for Bizhub7222: socket://10.0.0.201:9100 device for HP-Photosmart-6520-series: dnssd://Photosmart%206520%20series%20%5B1B47AD%5D._ipp._tcp.local/ MachineType: ASUSTeK COMPUTER INC. UX32VD Papersize: letter PpdFiles: HP-Photosmart-6520-series: HP Photosmart 6520 Series, hpcups 3.14.3 Bizhub7222: HP LaserJet 5L - CUPS+Gutenprint v5.2.10-pre2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=2f256b0b-ee87-463a-af04-e892e0be9192 ro quiet splash pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 SourcePackage: ghostscript UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32VD.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32VD.213:bd11/16/2012:svnASUSTeKCOMPUTERINC.:pnUX32VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1342312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364292] Re: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset
Oliver Woodford, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested exactly shown as: kernel-fixed-upstream-3.18-rc7 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1364292 Title: [Toshiba Portégé R600-10Q] VGA output doesn't work with Intel GM45 chipset Status in xorg package in Ubuntu: Incomplete Bug description: I have just installed Ubuntu 14.04 64-bit on my Toshiba Portege R600-10Q laptop (a model from 2009). I am now trying to display the desktop on a BenQ Senseye3 22 monitor, via the vga output, but it's not working - the monitor says No Signal Detected!. What I've done: I have gone into Screen Display, where I can see the monitor is detected by the laptop. The monitor has a 1920 x 1080 native resolution, which I have tried to use, but I have also set it to lower resolutions, e.g. 1024 x 576. I have tried to use the monitor in dual screen, mirrored and single screen mode - none work. I have tried pressing Fn + F5 to get single screen output - the laptop screen goes blank, but still no output on the monitor. I have tried several monitors (of the same type, and also of a different make), so I don't think it's that. If I plug the vga cable in after boot up, then the monitor receives no signal. WORKAROUND: If, and only if, the monitor was plugged in to the PC's VGA output during boot up, then the display outputs to the monitor correctly. The laptop has the Intel® GS45 Express chipset for graphics acceleration. I installed mesa-utils and ran glxinfo in a terminal. Amongst the output was: OpenGL renderer string: Mesa DRI Mobile Intel® GM45 Express Chipset Also, in the About This Computer window I see: Graphics: Mobile Intel® GM45 Express Chipset I wonder if the problem is that my chipset is GS45 not GM45. The output of sudo lshw -C video is: *-display:0 description: VGA compatible controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 07 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:44 memory:ff40-ff7f memory:e000-efff ioport:cff8(size=8) *-display:1 UNCLAIMED description: Display controller product: Mobile 4 Series Chipset Integrated Graphics Controller vendor: Intel Corporation physical id: 2.1 bus info: pci@:00:02.1 version: 07 width: 64 bits clock: 33MHz capabilities: pm bus_master cap_list configuration: latency=0 resources: memory:ffc0-ffcf ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Tue Sep 2 10:00:57 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:000c] Subsystem: Toshiba America Info Systems Device [1179:000c] InstallationDate: Installed on
[Desktop-packages] [Bug 1395970] Re: Aw Snap! crash on Google Chrome Webstore
39.0.2171.65 Built on Ubuntu 14.04, running on LinuxMint 17 i have the same issue : can't visit the web store. also you tube full scren resolution creates the same aw snap i'm not sure,but think that the problems starts with the recent update to 39. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1395970 Title: Aw Snap! crash on Google Chrome Webstore Status in chromium-browser package in Ubuntu: New Bug description: Chromium is crashing when I visit https://www.google.com/chrome/webstore/ It seems it has been fixed in the stable version of chrome https://code.google.com/p/chromium/issues/detail?id=432488 The current version 38.0.2125.111 in 14.04 LTS repositories has this problem. Since all the extensions and apps become unusable due to this, I was wondering if an updated version could be added to the 14.04 LTS repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1395970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
** Also affects: ibus (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: indicator-keyboard (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: ibus (Ubuntu) Status: Triaged = Fix Released ** Changed in: indicator-keyboard (Ubuntu) Status: Triaged = Won't Fix ** Changed in: indicator-keyboard (Ubuntu Trusty) Status: New = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in indicator-keyboard package in Ubuntu: Won't Fix Status in ibus source package in Trusty: New Status in indicator-keyboard source package in Trusty: Won't Fix Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240198] Re: [SRU]Wrong keyboard layout active after booting into desktop
** Summary changed: - Wrong keyboard layout active after booting into desktop + [SRU]Wrong keyboard layout active after booting into desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1240198 Title: [SRU]Wrong keyboard layout active after booting into desktop Status in ibus package in Ubuntu: Fix Released Status in indicator-keyboard package in Ubuntu: Won't Fix Status in ibus source package in Trusty: New Status in indicator-keyboard source package in Trusty: Won't Fix Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 629357] Re: [Feature Request] support xz for compressing volumes
** Changed in: duplicity (Ubuntu) Status: Confirmed = Opinion ** Changed in: duplicity Status: New = Opinion ** Changed in: duplicity Importance: Wishlist = Undecided -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/629357 Title: [Feature Request] support xz for compressing volumes Status in Duplicity - Bandwidth Efficient Encrypted Backup: Opinion Status in duplicity package in Ubuntu: Opinion Bug description: xz offers a superior compression ratio at the cost of higher CPU load during creation of backup, but still decompresses (when you need it most) at a rapid pace. I don't know if it should be the default but adding it as an option could save yottabytes of bandwidth :) To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/629357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
